Closed abernardi597 closed 2 years ago
Please see #143 and #144
https://questions.satisfactorygame.com/post/632d2441ca608e080351fb69
I read #143 and #144 before opening this issue, and I would like to re-iterate that this is not solved by turning off autopause, so it does not appear to be related to me.
Moreover, the machine that the server is running on does seem to load the world before the timeout occurs (you can see the delta time is 18.46 in the logs I added, which should be close to the time taken to load the world).
If this would be better added to the discussion on #143 I can re-post there, but I don't think this is the same issue.
@abernardi597 my apologies, it is very late here :) I'm assuming that your system specs were recorded while the server was running, as otherwise your RAM would be largely insufficient.
I will look into your issue as soon as possible! But please do read over the other two linked issues, as Update 6 introduced many issues/changes within the server space.
No problem, just didn't want it to get swept under the rug!
If I'm not mistaken, the command in the template reports MemAvailable / MemTotal
:
RAM: $(awk '/MemAvailable/ {printf( "%d\n", $2 / 1024000 )}' /proc/meminfo)GB/$(awk '/MemTotal/ {printf( "%d\n", $2 / 1024000 )}' /proc/meminfo)GB
This would reflect that nothing of note was running on my machine.
This may have been fixed by the latest patch. I was able to log into the server normally after a single failed attempt (the client crashed during the connection). This was with autopause enabled.
Describe the Bug Trying to join the dedicated server, and I'm met with a timeout / reliable buffer overflow.
This seems to occurs regardless of setting
-e AUTOPAUSE=false
or changing my client connection timeout to 300s, so I don't believe it's related to #143.Your Runtime Command or Docker Compose File
Then
podman start satisfactory
.System Specs:
Additional Context The server seems to give up on the first client connection after this (despite
AUTOPAUSE=false
and a client timeout of 300s):Further attempts to login have a vaguely similar warning and still result in a timeout: