[dedicated server] repeating log (steamnetworkingsockets) 564

[IC3M4N]

That’s our problem with ETS too, ATS runs smoothly.

It seems that the error appears more in ets then in ats

that's true to 99%, it rarely happens with ets2 with ATS even changing the port doesn't help, and smears steamcmd from me too. even when driving!

[isoprene]

The crashes I'm seeing are Access Violations in the Steam client DLL.

Crash log created on: Sun Jan 8 11:26:14 2023
Build: 1.46.1.0s a155a2c25176
OS: x86_64 / Windows 10 x64 (version 10.0.22621)
CPU: Intel(R) Xeon(R) CPU E5-2640 v3 @ 2.60GHz at 2594000
MEM: Phys:8190 Virt:134217727
GPU: <unknown> Mem:0 Ver: 0

AvailMEM Virt:134211826 Phys:4837 Total:2858
TotalMEM Virt:134217727 Phys:8190 Total:8702
Exception code: C0000005 ACCESS_VIOLATION
EXE Base address: 00007FF6031D0000
Fault address: 00007FFAF4F546E9 0001:009436E9 C:\ets\steamclient64.dll

[Vojtech Hladík]

That’s our problem with ETS too, ATS runs smoothly.

It seems that the error appears more in ets then in ats

it might be the same issue as in
viewtopic.php?p=1778855#p1778855

Only ATS has less servers, so it is more stable.
I have suspicion what is the cause, however it is very hard to test it.

[Eppejr]

That’s our problem with ETS too, ATS runs smoothly.

It seems that the error appears more in ets then in ats

it might be the same issue as in
viewtopic.php?p=1778855#p1778855

Only ATS has less servers, so it is more stable.
I have suspicion what is the cause, however it is very hard to test it.

If it’s hard to test it is possible to test. How can we help testing?

[Eppejr]

Any news on this item?

[Some newbie driver]

If it’s hard to test it is possible to test. How can we help testing?

From the part of us users, that have no access to the code, mainly by the boring and long-time consuming hard job of narrowing down variables.

Launching the server with ONE AND ONLY ONE different change applied to it to see if the behavior persist. So, one can start to narrow what can causes that problem. Probably a combination of several settings that alone would be OK but on an exact combination cause it. So it's possible that a couple of different things can "solve" the problem if changed that specific setting. None will be the "solution" itself, but the proof that it's a setting to factor in the root cause.

Of course, better to do a little investigation first to focus on changes that seemed to have relation with the error message. It's clearly stating something about network problems and specifically with timeouts/long delays; so focus on the settings that have relation with network performance. Also doing a traceroute analysis to your connected peers when the problem appears could show if there's a reliable network connection of those players to the server at that moment.

Regards

[wolkan4510]

src/steamnetworkingsockets/clientlib/steamnetworkingsockets_sdr_common.h (566) : m_pServer->m_nReplyTimeoutsSinceLastRecv == 0
I have the same problem. After a few hours, it gives the "has stopped working" error and the server shuts down.