jammsen / docker-sons-of-the-forest-dedicated-server

Docker container to easily provision and manage Sons of the Forest Dedicated Server with Wine
https://hub.docker.com/r/jammsen/sons-of-the-forest-dedicated-server
136 stars 20 forks source link

Container crashes after #DSL Loading progress: 19 #31

Closed Jonny-S-River closed 10 months ago

Jonny-S-River commented 10 months ago

Have you read the Important information text above

Current behavior

Container seem to crash after the message #DSL Loading progress: 19

Desired behavior

Server should load normally

Links to screenshots

No response

To Reproduce

Software setup

Hardware setup

Additional context

sons-of-the-forest-dedicated-server | #DSL Loading progress: 13 sons-of-the-forest-dedicated-server | #DSL Loading progress: 16 sons-of-the-forest-dedicated-server | #DSL Loading progress: 19 sons-of-the-forest-dedicated-server | Couldn't create a Convex Mesh from source mesh "ShortPotMesh" within the maximum polygons limit (256). The partial hull will be used. Consider simplifying your mesh. sons-of-the-forest-dedicated-server | #DSL Loading progress: 19 sons-of-the-forest-dedicated-server | #DSL Loading progress: 19 sons-of-the-forest-dedicated-server | /usr/bin/servermanager.sh: line 84: 169 Killed wine64 /sonsoftheforest/SonsOfTheForestDS.exe -userdatapath $USERDATA_PATH

Jonny-S-River commented 10 months ago

After Trying to start the Server manually i get this message:

src\steamnetworkingsockets\clientlib\steamnetworkingsockets_lowlevel.cpp (2124) : Assertion Failed: SteamnetworkingSocke ts service thread waited 95ms for lock! This directly adds to network latency! It could be a bug, but it's usually cau sed by general performance problem such as thread starvation or a debug output handler taking too long.#DSL Loading prog ress: 19

src\steamnetworkingsockets\clientlib\steamnetworkingsockets_lowlevel.cpp (2124) : Assertion Failed: SteamnetworkingSocke ts service thread waited 95ms for lock! This directly adds to network latency! It could be a bug, but it's usually cau sed by general performance problem such as thread starvation or a debug output handler taking too long. Killed

This seems to be a Performance issue right?

jammsen commented 10 months ago

Hello @Jonny-S-River, i dont think i ever had this problem before. You might want to look at this ( https://github.com/jammsen/docker-sons-of-the-forest-dedicated-server/issues/7#issuecomment-1611097781 ) for MSR (Minimum System Requirements).

Maybe that solves your problem.

gitzec commented 10 months ago

I think you run out of memory. this is the startup process of my container:

startup

The container asks the cluster for 4 CPUs and 8 GB RAM.

Jonny-S-River commented 10 months ago

Hi, i managed to get my hands on a bigger VM With dedicated cores and more RAM. 4 Cores 8GB Ram and that really seems to be it. I didnt throw enough money at it ;)