search

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
144 stars 20 forks source link

shader error during startup server #60

Closed ad4mny closed 2 days ago

ad4mny commented 5 days ago

Have you read the Important information text above

Current behavior

image

the sample image shown the startup is killed during deployment.

server config used are default except servername, password and LAN set to true.

Desired behavior

Server should be able to start up in LAN.

Links to screenshots

No response

To Reproduce

Steps to reproduce the behavior:

  1. Run the docker deployment code on the installation page.

Software setup

Hardware setup

Additional context

No response

jammsen commented 5 days ago

You dont have enough RAM, see Wiki for Requirement and read the Readme https://github.com/jammsen/docker-sons-of-the-forest-dedicated-server/wiki#%EF%B8%8F-requirements

TheKogoro commented 2 days ago

I have same shaders errors but the Server run on 40Gb Ram so it isnt the Ram in my case. Note the Server is running and can be joint and play on it. Exept somes random little graphical glitch, it Seem working. (Idk If the graphical glitch is due from thoses errors or it present in all dedicated Server).

Note also, when i Shutdown from Portainer, the container exit with code 137.

jammsen commented 2 days ago

@TheKogoro The Shader Warnings and Errors are always there, look at the logs of the first image i wrote for TheForest it was the same there.

The problem @ad4mny is facing that the server is beeing "killed" look at the last line and then at his Hardware-Setup in which he lists his entire system has only 8GB RAM, the server alone needs 10GB to run smoothly. So im guessing he tries to start the server, Docker and the DS use a lot of RAM and the OOM-Killer from the Linux Kernel comes around kills the process.

And if @ad4mny doesnt answers anymore, im gonna inactivity-close this issue.

jammsen commented 2 days ago

I have same shaders errors but the Server run on 40Gb Ram so it isnt the Ram in my case. Note the Server is running and can be joint and play on it. Exept somes random little graphical glitch, it Seem working. (Idk If the graphical glitch is due from thoses errors or it present in all dedicated Server).

Note also, when i Shutdown from Portainer, the container exit with code 137.

Also im pretty sure that some Shader-Erros are even thrown in the native Windows GUI Blackscreen version of the DS, might have changed, but when i tried this the last time, about 6 months ago under native Windows 10 for testing with an GPU in the system, it was like that, even under optimal conditions.

TheKogoro commented 2 days ago

I have same shaders errors but the Server run on 40Gb Ram so it isnt the Ram in my case. Note the Server is running and can be joint and play on it. Exept somes random little graphical glitch, it Seem working. (Idk If the graphical glitch is due from thoses errors or it present in all dedicated Server). Note also, when i Shutdown from Portainer, the container exit with code 137.

Also im pretty sure that some Shader-Erros are even thrown in the native Windows GUI Blackscreen version of the DS, might have changed, but when i tried this the last time, about 6 months ago under native Windows 10 for testing with an GPU in the system, it was like that, even under optimal conditions.

Thanks for an answer, so it's totally normal that i See all wheses warning/error on logs .

For the Shutdown turning into error code 137, it is also normal operation or i need to put somes variable (i use Portainer).

ad4mny commented 2 days ago

Alright thanks for the details regarding the ram information, will upgrade my ram first and see how it goes.

jammsen commented 1 day ago

I have same shaders errors but the Server run on 40Gb Ram so it isnt the Ram in my case. Note the Server is running and can be joint and play on it. Exept somes random little graphical glitch, it Seem working. (Idk If the graphical glitch is due from thoses errors or it present in all dedicated Server). Note also, when i Shutdown from Portainer, the container exit with code 137.

Also im pretty sure that some Shader-Erros are even thrown in the native Windows GUI Blackscreen version of the DS, might have changed, but when i tried this the last time, about 6 months ago under native Windows 10 for testing with an GPU in the system, it was like that, even under optimal conditions.

Thanks for an answer, so it's totally normal that i See all wheses warning/error on logs .

For the Shutdown turning into error code 137, it is also normal operation or i need to put somes variable (i use Portainer).

@TheKogoro look here https://github.com/jammsen/docker-sons-of-the-forest-dedicated-server/issues/4 in the Pastebin and search for Shader and be surprised how much browser-coloring exists for search-keywords 😄 - This is SOTF from about 16-18 months ago.

About the Exit-Code 137 with Portainer, a) sorry i missed this and b) i dont really know, i dont recommend Portainer and i dont use it anymore, im using Dockge, because Portainer caused so many problems in all my images from TF, SOTF to Palworld. It might be okay, it might be caused by Portainer im not really sure, but if the server shuts down savely and your savegame is okay, i would assume its okay?

If you want you can ask in the Discord https://discord.gg/7tacb9Q6tj I forgot to add this community Discord-Link to TF and SOTF, but Palworld has it.

jammsen commented 1 day ago

Added it now to TF and SOTF

TheKogoro commented 1 day ago

I have same shaders errors but the Server run on 40Gb Ram so it isnt the Ram in my case. Note the Server is running and can be joint and play on it. Exept somes random little graphical glitch, it Seem working. (Idk If the graphical glitch is due from thoses errors or it present in all dedicated Server). Note also, when i Shutdown from Portainer, the container exit with code 137.

Also im pretty sure that some Shader-Erros are even thrown in the native Windows GUI Blackscreen version of the DS, might have changed, but when i tried this the last time, about 6 months ago under native Windows 10 for testing with an GPU in the system, it was like that, even under optimal conditions.

Thanks for an answer, so it's totally normal that i See all wheses warning/error on logs . For the Shutdown turning into error code 137, it is also normal operation or i need to put somes variable (i use Portainer).

@TheKogoro look here #4 in the Pastebin and search for Shader and be surprised how much browser-coloring exists for search-keywords 😄 - This is SOTF from about 16-18 months ago.

About the Exit-Code 137 with Portainer, a) sorry i missed this and b) i dont really know, i dont recommend Portainer and i dont use it anymore, im using Dockge, because Portainer caused so many problems in all my images from TF, SOTF to Palworld. It might be okay, it might be caused by Portainer im not really sure, but if the server shuts down savely and your savegame is okay, i would assume its okay?

If you want you can ask in the Discord https://discord.gg/7tacb9Q6tj I forgot to add this community Discord-Link to TF and SOTF, but Palworld has it.

I have also Palworld Server, on Palworld it work Well and Shutdown proprely. But for Sons of the forest, it was ok even If it Shutdown with error code 137, i can boot and load my save without problem.

jammsen commented 1 day ago

Seems to be fine then 👍

jammsen commented 1 day ago

Alright thanks for the details regarding the ram information, will upgrade my ram first and see how it goes.

@ad4mny - Feel free to reach out again in this issue, if you tried more RAM and let me know if that fixed that problem.