Page 1 of 1

Repeated Server Not Responding [0.17.16]

Posted: Wed Mar 20, 2019 6:18 am
by cpaca
Issue: servers are *repeatedly* giving me "Not responding" errors, in many repeated cases
"repeated" not responding means occuring at least once every ten seconds, constantly.

Things I've tried + their results:
Joining public 10-100hour server in .17.16: Repeated "not responding"
Joining public <1hour old server in .17.16: Repeated "not responding"
Joining SP server, .17.16: Just fine (makes me think it's not a CPU issue)
Joining public server in .16 stable: Just fine (makes me think it's the .16 => .17 problem)

I did this one a long time ago, but I'm too lazy to find a server to do it again:
Joining public heavily modded [Seablock] server in .16: Just fine

>Something I realised after writing this: "Just fine" means that I'm not getting a "Server not responding" issue every <10s.

(The expected result in all cases is "Just fine, no 'not responding' repetition")

Attachments don't seem relevant here, and i'm not getting log files since it says "not responding" for a couple of seconds, then it goes back to normal.

It should be noted that the map downloads are 2MB/s (but quickly slow down to 100kb/s), and speedtest.net gives me a 45 megabit download, so even if .17.16 (mysteriously) requires more data it's not locked there.

I tested this on multiple public servers, and in one case where i asked about if anyone else had the issue, i got silence as the response (which i assume to mean "We don't have the issue")

Re: Repeated Server Not Responding [0.17.16]

Posted: Wed Mar 20, 2019 10:45 am
by Twinsen
A log would be extremely relevant as it would tell us how you connected(did you use steam networking?) and if there were any strange packets that we logged. Please include it.

Re: Repeated Server Not Responding [0.17.16]

Posted: Thu Mar 21, 2019 12:57 am
by cpaca
All right then.

I stayed in Redmew's crash site server and hoped to get some progress through the lag

The log is attached, but something I noticed: When I added more things to my logistic network, a *really* long "Not responding" error occurs and then it fixes itself.