~dr|z3d
@RN
@StormyCloud
@T3s|4
@T3s|4_
@not_bob
@orignal
@postman
@zzz
%Liorar
%acetone
%cumlord
%mareki2p
%snex
+Onn4l7h
+Onn4|7h
+leopold
+profetikla
+qend-irc2p
+r00tobo
+uop23ip
Arch
BeepyBee
BubbRubb
Dann
Guest99
H20
Irc2PGuest21753
Irc2PGuest32716
Irc2PGuest50537
Irc2PGuest63942
Irc2PGuest74254
Irc2PGuest95708
Meow
Over1
ac9f
anontor
dollarthief
floatyfloatilla
gellegery
halloy13412
makoto
maylay
n1
nZDoYBkF_
ntty
poriori_
r00tobo[2]
shiver_
simprelay
solidx66
thetia
u5657
zer0bitz
uop23ip
I tested my problem regarding getting too low "known" numbers in hidden ip4/6 firewalled noInbounds configuration with canon (should be the same with plus i guess):
uop23ip
switched to nonHidden to test if it is (my) config issue. Had to stop the router complete as the auto-softreset does not really work. After that, router gets more "known" over time and holds them. (no warn or error in logs)
uop23ip
Switched back to hidden mode, with complete restart. reseeded for a couple of times as it seems not to work all the time (got 1xx by reseed but "know" does not increase that much or not at all). Numbers do not last long. some hours and it gets under 50 and triggers a reseed. Fed it with 3k "know" from another router...after 1 day under 50.
uop23ip
log 1 error always comes up with hidden:
uop23ip
ERROR [Queue Pumper] net.i2p.router.JobQueue : Job ReadJob: Job 20: DB Read Job out of order with job TestJob: Job 51208773: Test tunnel difference of 115s
uop23ip
So if there isn't some issue with my setup, i would say that hidden mode does not work as intended, does not gain more "known" without reseed that is needed after a couple of hours. eyedeekay
eyedeekay
Honestly it sounds pretty familiar to me uop23ip and I think zzz will recognize the symptoms too, but do I see a 115s clock skew there? that's a bit weird
eyedeekay
I think pass along any other clues you can see in your logs
uop23ip
clock skew is 0 in sidebar. The error only occurs in hidden mode (3 times in last 3 days). Others are warn and beside ReseedChecker, it's WARN [JobQueue 3/5] orkdb.kademlia.ExpireLeasesJob: Expired local leaseset ...i2p. No more errors or warning of any other kind.
uop23ip
oh missed one, but it's new to me: ERROR [t Runner 164] .i2ptunnel.I2PTunnelClientBase: Unable to build tunnels for the client, retrying in 20 seconds
uop23ip
net.i2p.client.I2PSessionException: [I2P HTTP Proxy(CLOSED)]: Failed to build tunnels - Socket closed, state=CLOSED
uop23ip
got it 2 times
uop23ip
there are some more lines for this error, can paste if wanted. got org.eclipse.jetty.server.Server=WARN set, but no more info/clues i can see
eyedeekay
The one with the tunnel build failure might just be from not having enough peers to build the tunnel, the "Test tunnel difference of 115s" leaps out at me but I don't know if it means anything really
eyedeekay
net.i2p.router.networkdb might be helpful for logging, also possibly StartExplorersJob
uop23ip
just paste them into /configlogging log level overrides i guess?
uop23ip
and add the level =WARN
uop23ip
got it so far, hope it doesn't need a restart