Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SIGTERM detection #698

Open
mmonj opened this issue Jul 27, 2024 · 2 comments
Open

SIGTERM detection #698

mmonj opened this issue Jul 27, 2024 · 2 comments
Labels
question Further information is requested

Comments

@mmonj
Copy link

mmonj commented Jul 27, 2024

When i do docker compose down the server is killed without the server saving its state. Is there any way that it can detect the SIGTERM signal and save the state immediately?

@mmonj mmonj changed the title SIGKILL / SIGTERM detection SIGTERM detection Jul 27, 2024
@lloesche
Copy link
Owner

The problem isn't the signal, all relevant signals are properly passed through to the server process. The problem is very likely that your Docker daemon kills the container before the Valheim server can save the world to disk because the default timeout is 10s. That's why the docs say to start the container with --stop-timeout 120.

@lloesche lloesche added the question Further information is requested label Sep 13, 2024
@rdalbuquerque
Copy link

rdalbuquerque commented Nov 12, 2024

I just got passed an issue where state was not saving upon docker stop, even with proper timeouts, in an Azure ubuntu 24 VM, once I rolled back to ubuntu 22, it worked again, I didn't get the chance to investigate further tho.

I monitored the logs after docker stop and got nothing, container wouldn't log anything and then would just exit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants