Log files are nearly empty and world save does not occur on shutdown #802
Replies: 2 comments 9 replies
-
Thats definitely not expected behavior, i tossed this up as an issue and will take a look at it this weekend #803 |
Beta Was this translation helpful? Give feedback.
-
Potentially related? I'm unable to unsuccessfully shut down the server without losing the latest save.
This continues for dozens of lines until the container is eventually killed. Seems like the PIDs are different each time? Almost like it's restarting the process and immediately killing it? Either way, very unfortunate that the game save keeps getting lost. My configuration is something like this:
And final note, thanks @mbround18 for continuing to update this container after this many years. :) |
Beta Was this translation helpful? Give feedback.
-
There are 2 main problems with my current setup which would otherwise be working fine.
All that appears in the logs at
valheim_server.log
are[ODIN][INFO] - Success, daemonized
which seems to be the same issue described here: Not seeing expected content in server/logs/valheim_server.log anymore. #782 (reply in thread)2. If there is a true issue here and a workaround for this exists, I'd be interested in knowing for the interim.
World save does not seem to be occurring when stopping the container.
- Method A:
docker exec tacticalsrealm-valheim-1 odin stop
- Method B:
docker-compose down
-- Neither A or B will perform a world save. Any progress will be lost. I can click on "Save" in the pause menu and that will save the world which is a workaround I could use for myself, but I don't think the players on the server would remember to do that after becoming accustomed to autosaving. Seems to be similar to this issue: The world isn't saved when docker stops #719 (comment)
docker-compose up --detach
but this stopped happening when I useddocker-compose up
instead.docker-compose up
Beta Was this translation helpful? Give feedback.
All reactions