Closed lucrenauld closed 2 months ago
maybe the mod is slow? i know it takes a bit to start up
For me it's related to odin. Is there a way to preconfigure some things on Odin to make it start a bit faster ?
odin runs in sub 200ms and its runtime is only 4mb what are you seeing thats slow? thats why its built in rust vs something like python.
Odin Info with Log Name is just a log parser which watches logs for changes using inotify then logging them to stdout/stderr due to there being ~6 logs or so.
That waiting 1hr between log outputs, are you able to see if the log is generated before odin logs it out? that could be an odin issue vs mod issue and id be curious to see
I don't know how I could verify it. I'm just reading docker container logs which are copied un valheim server log file.
docker compose exec valheim tail -f /home/steam/valheim/logs/*
and monitor odins log output as well
see if the logs appear at the same time
I don't have more logs during the process tailing all logs on startup.
Maybe setting up DEBUG_MODE
to 1
as shown here could help ? Do I have to set it in the environment vars in docker compose ?
if you set that in your compose it will be very verbose and is an excellent debug tool
I don't get more logs with this option enabled
what processor are you running on?
Running on one single core of a AMD EPYC 7543P 32-Core Processor.
Hello @mbround18, I haven't waited ~60 minutes to confirm it, but I believe I had the same issue.
I'm running the v3.0.6 (568696a2172b digest) container, with most recent Valheim version and no mods in an AWS EC2 instance.
In single-core instances types, the container never finishes startup while the CPU stays at 100%. Same startup log behavior.
Tried with:
In multi-core, it works normally.
Not sure if this is an issue with Valheim itself or this project.
docker-compose.yml
:
"cap_add":
- "SYS_NICE"
"container_name": "valheim"
"environment":
"AUTO_BACKUP": 1
"AUTO_BACKUP_ON_SHUTDOWN": 1
"AUTO_BACKUP_PAUSE_WITH_NO_PLAYERS": 1
"NAME": "..."
"PASSWORD": "..."
"PLAYER_EVENT_NOTIFICATIONS": 1
"PORT": 2456
"PUBLIC": 1
"TZ": "..."
"WEBHOOK_INCLUDE_PUBLIC_IP": 1
"WEBHOOK_URL": "..."
"WORLD": "..."
"image": "mbround18/valheim:latest"
"ports":
- "2456-2458:2456-2458/udp"
"restart": "no"
"stop_grace_period": "2m"
"volumes":
- "/srv/valheim/backups:/home/steam/backups"
- "/srv/valheim/saves:/home/steam/.config/unity3d/IronGate/Valheim"
- "/srv/valheim/server:/home/steam/valheim"
Hey @g-otn
if you roll back to v3.0.3 does it start up quicker? In 3.0.6 i changed the logic around how i tail logs which is the only thing i can think of off the top of my head
I'm running the v3.0.6 (568696a2172b digest) container, with most recent Valheim version and no mods in an AWS EC2 instance.
Hey @g-otn
if you roll back to v3.0.3 does it start up quicker? In 3.0.6 i changed the logic around how i tail logs which is the only thing i can think of off the top of my head
c390f6d#diff-d66d88a5d8ec0be4e2b1d73fff473f3897fad056ebd719c474788f18df497af5R65-R94
Same problem happens when using 3.0.3, server never starts (I've waited around 10 minutes) and stays at 100% cpu usage.
No startup webhook got triggered and I could not connect to the server.
Hey @lucrenauld, did you manage to solve this?
Hello there,
symptom : Server takes at least 60 minutes to start now. Stucking during Chainloader startup.
Tasks before incident : After a severe situation in game, I tried to copy my save locally to do a bit of cheating commands on it. After that I uploaded the new saves files (db and fwl) on server.
Things tried by myself : Update to 3.0.3 of valheim server. Roll back to old saves before copy. Restart server and host. Switched type from BepInExFull to BepInEx
Other things : I still can see the
odin start
process in my container. And my ciontainer doesn't log anymore after these lines :Wait one hour
Versions :
Files :