Opened 5 years ago

Last modified 8 months ago

#1260 assigned defect

I2PBote: Locks up entire console

Reported by: zzz Owned by: str4d
Priority: major Milestone:
Component: apps/plugins Version: 0.9.12
Keywords: I2P-Bote hang Cc: kuri79@…
Parent Tickets:

Description

Report 1: http://forum.i2p/viewtopic.php?t=11340

Reports 2 and 3 below.

Subtickets (add)

Attachments (1)

dump.log (242.1 KB) - added by user 5 years ago.
threaddump

Download all attachments as: .zip

Change History (15)

comment:1 Changed 5 years ago by zzz

  • Cc kuri79@… added

Report 2 via email from kuri79@…:

Hello

I have the same issues as this newbie : http://forum.i2p/viewtopic.php?t=11340
I have no idea what logs I could provide.

Since I upgrade Firefox to 29, and I2P to 0.9.12-14, sometimes my I2P browser can not load the router console pages ( http://127.0.0.1:7657/console ) nor Susimail, but work with some eepsites.

When I disable to proxy (4444) of my Firefox, router console can suddenly be loaded (displayed).

If you need more infos, ask me.

OS : windows 7 (64b). Java: latest (updated this week).

comment:2 Changed 5 years ago by zzz

Report 3 via IRC:

<superuser> darn
<superuser> is there a way to uninstall a plugin without using the console?
<superuser> I rm'ed the respectivre subdirecotry from .i2p/plugins
<superuser> but that didn't make the problem go away

  • user has quit (Connection closed)

<superuser> I was trying an old bote version (0.2.6) and it started and bote page loaded, but router console does not load no more. though i think it's ood, given that both are served by same jetty.
<superuser> anyhow, I figured that jetty version change since then, so i decided the oold plugin must be the reason my my console not loading anymore. so i guess, uninstalling it is the way to go
<superuser> hmm, ok. it seems it doesn't like 127.0.0.1 anymore. localhost works
<superuser> and it shows the plugin _is_ gone
<superuser> who knows what I have screwn up
...
<user> 127.0.0.1:7657 back working here after a total router newstart

Version 0, edited 5 years ago by zzz (next)

comment:3 Changed 5 years ago by zzz

The best way for us to diagnose this is to get a thread dump while locked up. Use 'i2prouter dump' from the command line and then look in wrapper.log.

comment:4 Changed 5 years ago by user

Am not 100% sure it is bote-caused. but it could be.
well, mine was fine with latest bote and -4 router version.

I updated to -14 and didn't play around much, but it still loaded. At leasat I could acceess clientsconfig and remove the plugin and install an OLD bote version (0.2.6 as opposed to 0.2.9).
then, the console was gone. router was running, i could access eepsites and bote interface, but not standard router console - yes odd.
then rm'd the .i2p/plugins/i2pbote dir as I couldn't uninstall via console (maybe I could have, had I tried localhost instead of 127.0.0.1 before. and I think I did restart and console was still inaccessible.
But finally I rebooted (which means a full router stop and closing firefox etc) and back it was, temporarily. I verified bote was not listed under plugins no more and installed current bote again.

http://127.0.0.1:7657/home never loads, it's always in loading state
so, http://127.0.0.1:7657/home is dead, and http://localhost:7657/home is fine, but also taking longer than usually (now 2-15 secs)
and BOTE is NOT runnung

router version: 0.9.12-14-deb

likely not related: for an instant it also warned about being firewalled with inbound tcp enabled, i guess, don't remember exactly as I had hit enter by then and when it reloaded status was back on ok.

Changed 5 years ago by user

threaddump

comment:5 Changed 5 years ago by zzz

  • Component changed from apps/plugins to apps/console
  • Milestone set to 0.9.13
  • Priority changed from minor to major

If you save the client configuration on /configclients in the console, the console "run at startup" checkbox gets unchecked and you will have no console when you restart. The workaround is to stop I2P, edit ~/.i2p/clients.config and change the line clientApp.0.startOnLoad=false back to true, then start I2P. Working on a fix.

Report #2 from kuri79 may also be related to an incorrect proxy setting in firefox. Don't proxy for 127.0.0.1

The issue where localhost works but 127.0.0.1 does not work may be related to IPv4/v6 OS issues. Not sure.

The issue where it works for a while, then is slow, then doesn't work at all, I have no ideas. The thread dump shows nothing unusual.

comment:6 Changed 5 years ago by zzz

/configclients form fixed in 0.9.12-15

comment:7 Changed 5 years ago by user

on windows it works for me with -15.
linux not yet tested, and possibly caused by an incompatible plugin. i doubt it's purely os-related, because it had been working just fine with that os for years. no update to os made, only router updated and plugin installed. so I'd be surprised if it were os-related.
so as localhost works there and here it's working again too, for me the issue is fixed. dunno about others, tho

comment:8 Changed 5 years ago by zzz

see also possible dup #1273

comment:9 Changed 5 years ago by zzz

#1273 is definitely a dup of the /configclients issue in comment 5 above fixed in -15.

The dump.log in this ticket does have a running console (see line 1275), so that's a different issue, cause unknown.

comment:10 Changed 4 years ago by str4d

  • Keywords I2P-Bote hang added
  • Milestone 0.9.13 deleted

comment:11 Changed 3 years ago by str4d

  • Status changed from new to open

comment:12 Changed 2 years ago by zzz

  • Owner set to str4d
  • Status changed from open to assigned

comment:13 Changed 23 months ago by str4d

Migrated to https://github.com/i2p/i2p.i2p-bote/issues - I will close these tickets as things are resolved rather than right now, but please make future comments on GitHub?.

comment:14 Changed 8 months ago by zzz

  • Component changed from apps/console to apps/plugins
Note: See TracTickets for help on using tickets.