First local wsprdaemon connections gets timeout counter [fixed in v1.811]
I've been running a couple Kiwis with a local machine that launches wsprdaemon for just about all possible bands.
I believe I'm seeing a new behavior in the latest Kiwi software; I've noticed that the first wsprdaemon connections after a Kiwi server restart, though on the local net, get my 120 minute per 24h timeout timer applied:
The number of channels that get a timeout correlates to the 'number of channels w/o password' setting on the Security tab.
When I manually 'kick' these time-limited wsprdaemon connections, they reconnect in a few seconds (as expected) but this time the timeout timer is NOT applied.
Thoughts?
Comments
I've seen this too quite a while ago, so it isn't related to the latest update. Maybe they connect before the timeout-exception is activated in the kiwi-server startup.
I’ll bet this happens if there’s a delay determining the local IP. Although I don’t know why that would be. That should occur almost immediately. I’ll take a look.
Okay, I figured this out. It's exactly what I thought. The routine that determines the local IP has a bunch of stuff in it, one of which is a DNS lookup. If that lookup takes a significant amount of time then a connection can come in before the local IP is known and hence the local-IP-exemption apply.
I was able to simulate this by adding a 10 second delay to the routine and then trying regular user connections which then failed in the same way as your wsprdaemon connections. The solution is to return an HTTP 503 Service Unavailable error until the local IP becomes known. That way things like wsprdaemon/kiwirecorder will simply retry until the connection succeeds.
Fixed in the next release..
Amazing! Thank you!