Locks up entire console (Trac #1260)

[str4d]

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

Reports 2 and 3 below.

Migrated from https://trac.i2p2.de/ticket/1260

{
    "status": "assigned", 
    "changetime": "2017-01-15T15:30:18", 
    "description": "Report 1: http://forum.i2p/viewtopic.php?t=11340\n\nReports 2 and 3 below.", 
    "reporter": "zzz", 
    "cc": "[email protected]", 
    "resolution": "", 
    "_ts": "1484494218556024", 
    "component": "apps/console", 
    "summary": "I2PBote: Locks up entire console", 
    "priority": "major", 
    "keywords": "I2P-Bote hang", 
    "version": "0.9.12", 
    "parents": "", 
    "time": "2014-05-03T18:57:13", 
    "milestone": "", 
    "owner": "str4d", 
    "type": "defect"
}

[str4d]

Trac update at 20140503T18:58:16:

• zzz changed cc from "" to "[email protected]"
• zzz commented:

Report 2 via email from [email protected]:

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).

[str4d]

Trac update at 20140503T18:59:04:

• zzz changed _comment0 from:

Report 3 via IRC:

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

• user has quit (Connection closed) 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. 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 hmm, ok. it seems it doesn't like 127.0.0.1 anymore. localhost works and it shows the plugin is gone who knows what I have screwn up ... 127.0.0.1:7657 back working here after a total router newstart

to:

1399143674652602

• zzz commented:

Report 3 via IRC:

darn is there a way to uninstall a plugin without using the console? I rm'ed the respectivre subdirecotry from .i2p/plugins but that didn't make the problem go away 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. 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 hmm, ok. it seems it doesn't like 127.0.0.1 anymore. localhost works and it shows the plugin is gone who knows what I have screwn up ... 127.0.0.1:7657 back working here after a total router newstart

[str4d]

Trac update at 20140503T19:19:58: zzz commented:

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.

[str4d]

Trac update at 20140503T21:15:41: user commented:

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.

[str4d]

Trac update at 20140503T21:40:06:

• user changed attachment from "" to "dump.log"
• user commented:

threaddump

[str4d]

Trac update at 20140507T13:53:12:

• zzz commented:

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 https://trac.i2p2.de/ticket/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.

• zzz changed component from "apps/plugins" to "apps/console"
• zzz changed milestone from "" to "0.9.13"
• zzz changed priority from "minor" to "major"

[str4d]

Trac update at 20140507T14:52:37: zzz commented:

/configclients form fixed in 0.9.12-15

[str4d]

Trac update at 20140509T21:54:57: user commented:

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

[str4d]

Trac update at 20140510T13:17:34: zzz commented:

see also possible dup https://trac.i2p2.de/ticket/1273

[str4d]

Trac update at 20140510T13:47:24: zzz commented:

https://trac.i2p2.de/ticket/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.

[str4d]

Trac update at 20150109T23:31:38:

• str4d changed keywords from "" to "I2P-Bote hang"
• str4d changed milestone from "0.9.13" to ""

[str4d]

Trac update at 20160218T04:24:46: str4d changed status from "new" to "open"

[str4d]

Trac update at 20170115T15:30:18:

• zzz changed owner from "" to "str4d"
• zzz changed status from "open" to "assigned"