Closed samsunix closed 7 months ago
Hey @samsunix, could you tell me more about your setup? Whats your host system? Is it virtualized?
Could you also post the logs from start (INFO - Running enshrouded-server) to finish (enshrouded-server INFO - Shutdown complete)?
Hi I have the same issue with a Synology NAS. This is my logs of the same issue.
LOG FILE
When I start the container it goes into an endless loop with the enshrouded-updater and the server never starts up. Below are the logs. The server never becomes reachable.
@JoeyDayy there can be multiple reasons why the server is not starting. But in your case, the hosts kernel is probably to old. Can you try to upgrade your system? Kernel version 5 or higher should work. If that doesn't help, it could also be a hardware issue (unsupported cpu instruction set).
@Pacobart hm, the logs are a little short. Could you post your compose file and a little more of the logs?
My first guess, there is a problem with the file permissions. PUIG
/PGID
4711 doesn't exist usually. You should set those to the desired user id (id -u
/ id -g
). And before restarting the docker, just delete the game folder (there should not be a save file yet).
Hey @samsunix, could you tell me more about your setup? Whats your host system? Is it virtualized?
Could you also post the logs from start (INFO - Running enshrouded-server) to finish (enshrouded-server INFO - Shutdown complete)?
Ubuntu 22.04.3 LTS x86_64 - Docker version 25.0.0, build e758fe5
I tried today again and it seems working fine now.
However server is overloaded as soon anyone try join and second player almost always get stuck on loading screen.
@samsunix nice, good that it works. The wine emulation seems to crush the cpu unfortunately. Hopefully the enshrouded team can fix that in future patches. I will also test some changes to improve the performance.
@samsunix nice, good that it works. The wine emulation seems to crush the cpu unfortunately. Hopefully the enshrouded team can fix that in future patches. I will also test some changes to improve the performance.
Thank you for reply and thank you for the great work, Please keep us updated :)
@Pacobart hm, the logs are a little short. Could you post your compose file and a little more of the logs?
My first guess, there is a problem with the file permissions.
PUIG
/PGID
4711 doesn't exist usually. You should set those to the desired user id (id -u
/id -g
). And before restarting the docker, just delete the game folder (there should not be a save file yet).
Here's my docker compose file:
version: "3"
services:
enshrouded:
image: mornedhels/enshrouded-server:0.2.0
container_name: enshrouded-server
restart: unless-stopped
stop_grace_period: 90s
ports:
- "15636-15637:15636-15637/udp"
volumes:
- ./game:/opt/enshrouded
environment:
- SERVER_NAME="xxxx"
- SERVER_PASSWORD="xxx"
- UPDATE_CRON=*/30 * * * *
- PUID=4711
- PGID=4711
I'm not sure what values to set for the PUID and PGID. I've changed them to 1000 which is how I run the palworld container that works fine. Here's the logs. The container never runs the server
@Pacobart what happens after that log? It just exited the updater not the server itself
@Pacobart what happens after that log? It just exited the updater not the server itself
the container does nothing. it will sit there for hours
hm, try to remove the game folder completely and restart the docker container.
For the right PUID you just need to run id -u
and id -g
on the host system with the user you are using.
I tried removing the game folder and it does get re-created with all the other server files. Is there a way to add more verbose logging or disable the updater to only run the server?
well yes and no. The updater always run as a entry script.
But you can use docker compose exec enshrouded supervisorctl stop enshrouded-updater
wait for the logs to stop and run docker compose exec enshrouded supervisorctl start enshrouded-server
. Hopefully you get better logs that way.
also you can check the logs directory game/server/logs
for any files. And is there a current_version
besides the server directory?
current_version
= 13283438
I noticed in the game/server
directory there wasn't a log
or savegame
directory.
Here's the error after running supervisorctl stop enshrouded-server
and then supervisorctl start enshrouded-server
2024-01-27 11:22:19 2024-01-27 18:22:19,850 INFO spawned: 'enshrouded-server' with pid 231
2024-01-27 11:22:19 2024-01-27 18:22:19.858 supervisord: enshrouded-server INFO - Running enshrouded-server
2024-01-27 11:22:20 2024-01-27 18:22:20.159 supervisord: enshrouded-server 0044:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
2024-01-27 11:22:20 2024-01-27 18:22:20.159 supervisord: enshrouded-server 0044:err:winediag:nodrv_CreateWindow L"The explorer process failed to start."
2024-01-27 11:22:20 2024-01-27 18:22:20.159 supervisord: enshrouded-server 0044:err:systray:initialize_systray Could not create tray window
Digging into the /var/log/supervisor
directory I see the following logs. The server starts and immediately shuts down.
# cat enshrouded-server-stdout---supervisor-13oyptgp.log
INFO - Running enshrouded-server
INFO - Shutting down enshrouded server with PID 160
INFO - Releasing PID file /var/run/enshrouded/enshrouded-server.pid
INFO - Shutdown complete
INFO - Running enshrouded-server
# cat enshrouded-server-stderr---supervisor-agi7ue50.log
0044:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
0044:err:winediag:nodrv_CreateWindow L"The explorer process failed to start."
0044:err:systray:initialize_systray Could not create tray window
I might have the issue. In your config you set the update cron without quotes.
UPDATE_CRON="*/30 * * * *"
My guess, the update cron starts every second and kills the server immediately. Not sure why it's working for me without the quotes though.
To get even more insights, you could add log_level=50
as an environment variable
I switched to the proton image and had the same result. Here's a full dump of the logs. Also I added quotes around the cron and add the log level to 50.
@Pacobart my logs seems to be similar. after that there is another could not create tray window and then it should log some cpu information. Is that correct?
Do you get the Game Version (SVN)
log? And how far ist the log going. This time it seems to run much further.
@Pacobart my logs seems to be similar. after that there is another could not create tray window and then it should log some cpu information. Is that correct?
Do you get the
Game Version (SVN)
log? And how far ist the log going. This time it seems to run much further.
I sent the logs from the time I started the container to the time I killed the container. It ran for 6 minutes and didn't go past the SetupDiInstallDevice
errors.
After restarting the container I get basically the same log showing the bottom error and then the following:
enshrouded-server | 2024-01-28 03:17:54,164 INFO reaped unknown pid 140 (exit status 0)
enshrouded-server | 2024-01-28 03:17:56,167 INFO reaped unknown pid 125 (exit status 0)
enshrouded-server | 2024-01-28 03:18:01,173 INFO success: enshrouded-server entered RUNNING state, process has stayed up for > than 10 seconds (startsecs)
enshrouded-server | 2024-01-28 03:18:01.174 supervisord: enshrouded-updater enshrouded-server: started
enshrouded-server | 2024-01-28 03:18:01,195 INFO exited: enshrouded-updater (exit status 0; expected)
enshrouded-server | 2024-01-28 03:18:01.195 supervisord: enshrouded-updater INFO - enshrouded-updater complete
hm, my guess there is still something wrong with the file permissions. The next step would be to move and create the logs files. Maybe it hangs there for some reason.
Pls check the owner and group of the ./game and ./game/server folder (ls -l
). And if the ./game folder is not the PUID user, than chown the files (chown -R PUID:PGID ./game
).
Can you shed more light on the following errors. I'm not familiar with how wine works but maybe wine isn't running? I've set the permissions to 777 for everyone, deleted the contents of the game folder and still have the same errors.
2024-01-28 10:49:24 2024-01-28 17:49:24.693 supervisord: enshrouded-server 0120:err:wineusb:DriverEntry Failed to initialize Unix library, status 0xc0000135.
2024-01-28 10:49:24 2024-01-28 17:49:24.693 supervisord: enshrouded-server 0120:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\wineusb": c0000135
2024-01-28 10:49:24 2024-01-28 17:49:24.696 supervisord: enshrouded-server 002c:err:setupapi:SetupDiInstallDevice Failed to start service L"wineusb" for device L"ROOT\\WINE\\WINEUSB", error 126.
2024-01-28 10:49:24 2024-01-28 17:49:24.698 supervisord: enshrouded-server 002c:err:setupapi:SetupDiInstallDevice Failed to control service L"wineusb" for device L"ROOT\\WINE\\WINEUSB", error 1062.
2024-01-28 10:49:25 2024-01-28 17:49:25.024 supervisord: enshrouded-server wine: configuration in L"/opt/enshrouded/server/steamapps/compatdata/2278520/pfx" has been updated.
You can ignore those errors, don't know what proton/wine is trying to do there. After some more wine messages, you should start to see
[enshrouded] Create logfile
...
[app] start creation step Init
[app] start creation step Init_Steamwork
...
[Session] 'PrepareGame' (up)!
...
[Session] 'HostOnline' (up)!
do you see any of those?
It doesn't get that far. It's like the server never actually starts. Is there a way I can just run the server without any supervisord and update logic?
Well you could use docker run ... mornedhels/enshrouded-server:latest bash
and start debugging manually.
You could also just start the docker compose wait for the bootstrap part and use docker compose exec -it enshrouded bash
. From there you could run supervisorctl stop enshrouded-updater and or enshrouded-server and run it manually.
The required startup commands can be found here: https://github.com/mornedhels/enshrouded-server/blob/main/scripts/proton/enshrouded-server#L32-L39
Before you tinker around with that. There is also a log folder. Maybe you get more information out of that.
@Pacobart Are you sure you have enough diskspace for the server to run? I ran into this myself aswell but came to the conclusion that my disk was simply too full for the server to expand itself.
Due to inactivity, I'm closing the issue. Feel free to reopen if you need more help.
Is there an existing issue for this?
Used image version
latest
Used docker compose file or docker command
docker run -d --name enshrouded \ --hostname enshrouded \ --restart=unless-stopped \ -p 15636-15637:15636-15637/udp \ -v ./game:/opt/enshrouded \ -e SERVER_NAME="samuliweb" \ -e SERVER_PASSWORD="password" \ -e UPDATE_CRON="/30 *" \ -e PUID=4711 \ -e PGID=4711 \ mornedhels/enshrouded-server:latest
What you expected to see, versus what you actually saw
expecting: Server starting having: endless loop
Logs from the container
Details
``` 2024-01-25 21:22:41.390 supervisord: enshrouded-server 00000348 svchost.exe 2024-01-25 21:22:41.390 supervisord: enshrouded-server #0110000034c 0 2024-01-25 21:22:41.390 supervisord: enshrouded-server #01100000358 0 2024-01-25 21:22:41.391 supervisord: enshrouded-server #0110000035c 0 wine_sechost_service 2024-01-25 21:22:41.391 supervisord: enshrouded-server 00000284 (D) Z:\opt\enshrouded\server\enshrouded_server.exe 2024-01-25 21:22:41.391 supervisord: enshrouded-server #0110000019c 0 2024-01-25 21:22:41.391 supervisord: enshrouded-server #0110000021c 1 NetworkSystem 2024-01-25 21:22:41.392 supervisord: enshrouded-server #01100000224 1 MessageSystem 2024-01-25 21:22:41.392 supervisord: enshrouded-server #01100000228 0 Task-default02 2024-01-25 21:22:41.392 supervisord: enshrouded-server #01100000230 0 Task-default03 2024-01-25 21:22:41.393 supervisord: enshrouded-server #01100000234 0 Task-default04 2024-01-25 21:22:41.393 supervisord: enshrouded-server #01100000240 -1 Task-background00 2024-01-25 21:22:41.393 supervisord: enshrouded-server #01100000244 -1 Task-background01 2024-01-25 21:22:41.394 supervisord: enshrouded-server #0110000024c -1 Task-background02 2024-01-25 21:22:41.394 supervisord: enshrouded-server #01100000250 -1 BackgroundTask 2024-01-25 21:22:41.394 supervisord: enshrouded-server #01100000258 0 2024-01-25 21:22:41.395 supervisord: enshrouded-server #01100000254 2 2024-01-25 21:22:41.395 supervisord: enshrouded-server #01100000260 0 2024-01-25 21:22:41.395 supervisord: enshrouded-server #01100000268 0 2024-01-25 21:22:41.396 supervisord: enshrouded-server #0110000026c 0 2024-01-25 21:22:41.396 supervisord: enshrouded-server #011000002a0 0 2024-01-25 21:22:41.396 supervisord: enshrouded-server #01100000198 0 2024-01-25 21:22:41.397 supervisord: enshrouded-server #011000002e8 1 NativeFileDevice 2024-01-25 21:22:41.397 supervisord: enshrouded-server #011000002f4 1 FileSystem 2024-01-25 21:22:41.397 supervisord: enshrouded-server #0110000027c 2 2024-01-25 21:22:41.398 supervisord: enshrouded-server #01100000288 1 P2pReceiveThread 2024-01-25 21:22:41.398 supervisord: enshrouded-server #01100000280 1 P2pSendThread 2024-01-25 21:22:41.398 supervisord: enshrouded-server #01100000278 1 Session 2024-01-25 21:22:41.399 supervisord: enshrouded-server #011000002f8 0 HttpClient 2024-01-25 21:22:41.399 supervisord: enshrouded-server #0110000029c 2 2024-01-25 21:22:41.399 supervisord: enshrouded-server #01100000338 -1 ResourceSystem 2024-01-25 21:22:41.400 supervisord: enshrouded-server #01100000330 -1 SaveData 2024-01-25 21:22:41.400 supervisord: enshrouded-server #01100000340 1 <== GameServer 2024-01-25 21:22:41.400 supervisord: enshrouded-server #0110000032c 0 2024-01-25 21:22:41.409 supervisord: enshrouded-server 00000204 explorer.exe 2024-01-25 21:22:41.409 supervisord: enshrouded-server #01100000208 0 2024-01-25 21:22:41.409 supervisord: enshrouded-server #01100000210 0 wine_rpcrt4_server 2024-01-25 21:22:41.410 supervisord: enshrouded-server System information: 2024-01-25 21:22:41.410 supervisord: enshrouded-server Wine build: wine-9.0 2024-01-25 21:22:41.410 supervisord: enshrouded-server Platform: x86_64 (guest: i386) 2024-01-25 21:22:41.410 supervisord: enshrouded-server Version: Windows 10 2024-01-25 21:22:41.410 supervisord: enshrouded-server Host system: Linux 2024-01-25 21:22:41.410 supervisord: enshrouded-server Host version: 6.7.1-060701-generic 2024-01-25 21:22:41,465 INFO reaped unknown pid 763 (exit status 0) 2024-01-25 21:22:41.464 supervisord: enshrouded-server INFO - Releasing PID file /var/run/enshrouded/enshrouded-server.pid 2024-01-25 21:22:41.468 supervisord: enshrouded-server INFO - Shutdown complete 2024-01-25 21:22:41,468 INFO exited: enshrouded-server (exit status 0; expected) 2024-01-25 21:22:41,472 INFO spawned: 'enshrouded-server' with pid 766 2024-01-25 21:22:41.492 supervisord: enshrouded-server INFO - Running enshrouded-server 2024-01-25 21:22:42.611 supervisord: enshrouded-server [holistic] Backup log to '/opt/enshrouded/server/logs/backup/enshrouded_server_2024-01-25T21-22-42.log'. 2024-01-25 21:22:42.612 supervisord: enshrouded-server [enshrouded] Create logfile 2024-01-25 21:22:42.612 supervisord: enshrouded-server enshrouded_server(detached HEAD) - version f797991cde92efb6d62aae4c677a00e3d6bfe9c2 (master) 2024-01-25 21:22:42.612 supervisord: enshrouded-server CPUs: 2024-01-25 21:22:42.612 supervisord: enshrouded-server Idx Id Group LogIdx CoreIdx LLCIdx NumaIdx EffClass 2024-01-25 21:22:42.612 supervisord: enshrouded-server 0 256 0 0 0 2 0 0 2024-01-25 21:22:42.612 supervisord: enshrouded-server 1 257 0 1 1 2 0 0 2024-01-25 21:22:42.612 supervisord: enshrouded-server 2 258 0 2 2 2 0 0 2024-01-25 21:22:42.612 supervisord: enshrouded-server 3 259 0 3 3 2 0 0 2024-01-25 21:22:42.612 supervisord: enshrouded-server CPU Types: 2024-01-25 21:22:42.612 supervisord: enshrouded-server Performance: 4 0000000000000000000000000000000000000000000000000000000000001111 2024-01-25 21:22:42.612 supervisord: enshrouded-server Efficient: 0 0000000000000000000000000000000000000000000000000000000000000000 2024-01-25 21:22:42.612 supervisord: enshrouded-server [task] TaskSystemSetup: 2024-01-25 21:22:42.612 supervisord: enshrouded-server [task] mainWorkerCount: 2 2024-01-25 21:22:42.612 supervisord: enshrouded-server [task] nextMainWorkerIndex: 1 2024-01-25 21:22:42.613 supervisord: enshrouded-server [task] Group 'default' worker:5 main:2 2024-01-25 21:22:42.613 supervisord: enshrouded-server [task] 0: Task-default00 0000000000000000000000000000000000000000000000000000000000000000 2024-01-25 21:22:42.613 supervisord: enshrouded-server [task] 1: Task-default01 0000000000000000000000000000000000000000000000000000000000000000 2024-01-25 21:22:42.613 supervisord: enshrouded-server [task] 2: Task-default02 0000000000000000000000000000000000000000000000000000000000001111 2024-01-25 21:22:42.613 supervisord: enshrouded-server [task] 3: Task-default03 0000000000000000000000000000000000000000000000000000000000001111 2024-01-25 21:22:42.613 supervisord: enshrouded-server [task] 4: Task-default04 0000000000000000000000000000000000000000000000000000000000001111 2024-01-25 21:22:42.613 supervisord: enshrouded-server [task] Group 'background' worker:3 main:0 2024-01-25 21:22:42.613 supervisord: enshrouded-server [task] 0: Task-background00 0000000000000000000000000000000000000000000000000000000000001111 2024-01-25 21:22:42.613 supervisord: enshrouded-server [task] 1: Task-background01 0000000000000000000000000000000000000000000000000000000000001111 2024-01-25 21:22:42.613 supervisord: enshrouded-server [task] 2: Task-background02 0000000000000000000000000000000000000000000000000000000000001111 2024-01-25 21:22:42.613 supervisord: enshrouded-server [app] start creation step Init 2024-01-25 21:22:42.613 supervisord: enshrouded-server [app] start creation step Init_Steamworks 2024-01-25 21:22:42.911 supervisord: enshrouded-server Setting breakpad minidump AppID = 1203620#015 2024-01-25 21:22:42.911 supervisord: enshrouded-server [app] start creation step Init_FileSystem 2024-01-25 21:22:42.911 supervisord: enshrouded-server SteamInternal_SetMinidumpSteamID: Caching Steam ID: 76561197960265728 [API loaded no]#015 2024-01-25 21:22:42.915 supervisord: enshrouded-server [app] start creation step Init_MountPackage 2024-01-25 21:22:42.921 supervisord: enshrouded-server +--"": 2024-01-25 21:22:42.921 supervisord: enshrouded-server | 2024-01-25 21:22:42.921 supervisord: enshrouded-server +--"": 2024-01-25 21:22:42.921 supervisord: enshrouded-server | 2024-01-25 21:22:42.921 supervisord: enshrouded-server +--"gamebuild": (#0) Archive -> '/gamebuild_path/enshrouded_server' 2024-01-25 21:22:42.921 supervisord: enshrouded-server | 2024-01-25 21:22:42.921 supervisord: enshrouded-server +--"gamebuild_path": (#1) Native -> 'Z:/opt/enshrouded/server/' 2024-01-25 21:22:42.921 supervisord: enshrouded-server [app] start creation step Init_Version 2024-01-25 21:22:42.922 supervisord: enshrouded-server Game Version (SVN): 487046 2024-01-25 21:22:42.922 supervisord: enshrouded-server [app] start creation step Init_UserSystem 2024-01-25 21:22:42.922 supervisord: enshrouded-server [user] Couldn't retrieve steam friends interface. 2024-01-25 21:22:42.922 supervisord: enshrouded-server [user] Couldn't retrieve steam user interface. 2024-01-25 21:22:42.922 supervisord: enshrouded-server [app] start creation step Init_OnlineSystem 2024-01-25 21:22:42.929 supervisord: enshrouded-server [OnlineProviderSteam] started transition from 'Uninitialized' to 'Initialized' (current='