I2P-Bote: High tunnel count

[guest]

I had an unexpectedly high tunnel count in the latest version of i2p. The logs mention low bandwidth availability, but since i2p was the only thing running i doubt that this is in fact the case. A soft restart fixed it fine.

[guest]

wrapper log file from the bug

[zzz]

You had no peers at all. I2P couldn't connect to anybody. Any idea why?

232 client tunnels but no peers - so they were zero-hop tunnels.

Any clues from the router logs?

[guest]

I've trimmed 5 hours worth of similar messages to reduce filesize

[guest]

I see no reason for i2p to be unable to connect. Was the connection error at 5:55 or had it occurred some time previously and only caused a problem at that time? A different install of i2p was unaffected by any issues that did occur.

[zzz]

OK, the job lag got up over 1440000 (20 minutes or so) so it had completely exploded. Couldn't even build a zero-hop exploratory tunnel... but that didn't start until 6:00.

We used to have bugs where a connectivity problem caused high CPU... but those should be fixed... and you said there weren't any real internet issues. So I think the high job lag causes peers to go to 0.

I see you're running i2p-bote... I don't know the version numbers, but for most of last year bote would cause a router to eventually explode... it was fixed in the last couple months? Search on here for tickets.

Or maybe that bote-version-checker stuff caused the problem?

What's your i2p-bote version?

[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?.