Opened 6 years ago

Last modified 22 months ago

#926 assigned defect

I2P-Bote: High tunnel count

Reported by: guest Owned by: str4d
Priority: minor Milestone:
Component: apps/plugins Version: 0.9.5
Keywords: I2P-Bote hang Cc: HungryHobo
Parent Tickets:

Description

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.

Subtickets (add)

Attachments (3)

logs.txt (20.0 KB) - added by guest 6 years ago.
wrapper log file from the bug
17.png (32.8 KB) - added by guest 6 years ago.
log-router-1.txt (24.1 KB) - added by guest 6 years ago.
I've trimmed 5 hours worth of similar messages to reduce filesize

Download all attachments as: .zip

Change History (12)

Changed 6 years ago by guest

wrapper log file from the bug

Changed 6 years ago by guest

comment:1 Changed 6 years ago by 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?

Changed 6 years ago by guest

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

comment:2 Changed 6 years ago by 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.

comment:3 Changed 6 years ago by 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?

comment:4 Changed 6 years ago by zzz

  • Cc HungryHobo added

comment:5 Changed 6 years ago by zzz

  • Component changed from router/transport to apps/plugins
  • Owner changed from zzz to HungryHobo
  • Status changed from new to assigned

comment:6 Changed 5 years ago by str4d

  • Keywords i2pbote added

comment:7 Changed 4 years ago by str4d

  • Keywords I2P-Bote hang added; i2pbote removed
  • Milestone 0.9.6 deleted

comment:8 Changed 2 years ago by zzz

  • Owner changed from HungryHobo to str4d
  • Summary changed from High tunnel count to I2P-Bote: High tunnel count

comment:9 Changed 22 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?.

Note: See TracTickets for help on using tickets.