Opened 10 years ago

Closed 9 years ago

#521 closed defect (fixed)

I2P should be able to retry seeding

Reported by: mk Owned by: zzz
Priority: minor Milestone: 0.9.4
Component: router/netdb Version: 0.8.8
Keywords: Cc:
Parent Tickets: Sensitive: no


If I2P is started when no network connectivity is available yet, it will just go to the CPU-hogging mode (see another bug) after failing to reseed (assuming netDb was empty, for example).

For environments without console, it would be nice if I2P could retry reseeding when netDb has less than net.i2p.router.networkdb.reseed.ReseedChecker.MINIMUM entries every so much number of minutes.


Change History (3)

comment:1 Changed 10 years ago by zzz


Yeah, the thinking was that if reseeding fails, it would take manual intervention by the user to fix the network problem, and in the console there's a big message and manual-reseed button that appears after a failure.

Automatic might be better.

comment:2 Changed 9 years ago by zzz

Status: newaccepted
Type: enhancementdefect

comment:3 Changed 9 years ago by zzz

Resolution: fixed
Status: acceptedclosed

Implemented in 0.9.3-7

Note: See TracTickets for help on using tickets.