Ticket #518 (new defect)
Opened 21 months ago
clock jump during i2p start results in router hanging on "Network: Testing"
|Reported by:||anonym||Owned by:|
|Keywords:||clock skew jump||Cc:||anonym@…|
Steps to reproduce:
1. Start a i2p (I use KYTV's packages from his/her PPA, on Debian squeeze)
2. Wait a few seconds, then set the clock back 2 hours or so.
According to the router console, the router is stuck on "Network: Testing", and indeed I'm never able to use the I2P network. The HTTP proxy and other client tunnels never starts to listen on any ports according to netstat.
The following is from log-router-0.txt (complete file is also attached):
9/1/11 2:40:54 PM ERROR [rtup tunnels] eaming.I2PSocketManagerFactory: Error creating session for socket manager
net.i2p.client.I2PSessionException: [shared clients #24509]: Cannot connect to the router on [internal connection]:0
[stack trace -- see attached files for full log]
9/1/11 2:40:54 PM ERROR [rtup tunnels] .i2ptunnel.I2PTunnelClientBase: Unable to connect to the router at 127.0.0.1:7654 and build tunnels for the client, retrying in 20 seconds