search

mbround18 / valheim-docker

Valheim Docker powered by Odin. The Valheim dedicated gameserver manager which is designed with resiliency in mind by providing automatic updates, world backup support, and a user friendly cli interface.
https://hub.docker.com/r/mbround18/valheim
BSD 3-Clause "New" or "Revised" License
757 stars 81 forks source link

Log files are nearly empty and world save does not occur on shutdown #803

Closed mbround18 closed 4 months ago

mbround18 commented 4 months ago

Discussed in https://github.com/mbround18/valheim-docker/discussions/802

Originally posted by **ericjgoebel** April 5, 2024 There are 2 main problems with my current setup which would otherwise be working fine. 1. All that appears in the logs at `valheim_server.log` are `[ODIN][INFO] - Success, daemonized` which seems to be the same issue described here: https://github.com/mbround18/valheim-docker/discussions/782#discussioncomment-8259793 2. If there is a true issue here and a workaround for this exists, I'd be interested in knowing for the interim. 1. 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: https://github.com/mbround18/valheim-docker/discussions/719#discussion-5599456 - Note: I did have an issue with AUTO_BACKUP not working when using `docker-compose up --detach` but this stopped happening when I used `docker-compose up` instead. - Note: I created a discord integration that is working fine. - Note: I have logs from the first successful run starting with `docker-compose up` - Note: Both I and players not on LAN can access the server without issue and can play just fine outside of the mentioned issues ``` version: "3" services: valheim: image: mbround18/valheim:latest stop_signal: SIGINT ports: - "2456:2456/udp" - "2457:2457/udp" - "2458:2458/udp" environment: PORT: 2456 NAME: "Tacticals Realm" WORLD: "[mysecretworldname]" PASSWORD: "[mysecretpassword]" TZ: "America/New_York" PUBLIC: 1 AUTO_UPDATE: 1 AUTO_UPDATE_SCHEDULE: "*/15 * * * *" AUTO_UPDATE_PAUSE_WITH_PLAYERS: 1 AUTO_BACKUP: 1 AUTO_BACKUP_SCHEDULE: "*/5 * * * *" #AUTO_BACKUP_SCHEDULE: "0 */1 * * *" AUTO_BACKUP_REMOVE_OLD: 1 AUTO_BACKUP_DAYS_TO_LIVE: 3 AUTO_BACKUP_ON_UPDATE: 1 AUTO_BACKUP_ON_SHUTDOWN: 1 AUTO_BACKUP_PAUSE_WITH_NO_PLAYERS: 0 SCHEDULED_RESTART: 1 SCHEDULED_RESTART_SCHEDULE: "15 4 * * *" UPDATE_ON_STARTUP: 1 WEBHOOK_URL: [mysecretwebhook] volumes: - "S:\\Games\\Docker\\TacticalsRealm\\valheim\\saves:/home/steam/.config/unity3d/IronGate/Valheim" - "S:\\Games\\Docker\\TacticalsRealm\\valheim\\server:/home/steam/valheim" - "S:\\Games\\Docker\\TacticalsRealm\\valheim\\backups:/home/steam/backups" ```
mbround18 commented 4 months ago

Jumping into this

mbround18 commented 4 months ago

Fixed in https://github.com/mbround18/valheim-docker/pull/807