xvfb-run: error: Xvfb failed to start

ewoudje commented 5 months ago

As specified above, after restarting the container it suddenly doesn't boot anymore with this error.

Updating V-Rising Dedicated Server files...

Redirecting stderr to '/root/Steam/logs/stderr.txt'
Logging directory: '/root/Steam/logs'
[  0%] Checking for available updates...
[----] Verifying installation...
UpdateUI: skip show logoSteam Console Client (c) Valve Corporation - version 1716242337
-- type 'quit' to exit --
Loading Steam API...OK
"@sSteamCmdForcePlatformType" = "windows"

Connecting anonymously to Steam Public...OK
Waiting for client config...OK
Waiting for user info...OK
 Update state (0x3) reconfiguring, progress: 0.00 (0 / 0)
 Update state (0x5) verifying install, progress: 22.48 (414043981 / 1842233665)
 Update state (0x5) verifying install, progress: 45.19 (832483919 / 1842233665)
 Update state (0x5) verifying install, progress: 67.95 (1251817481 / 1842233665)
 Update state (0x5) verifying install, progress: 90.45 (1666209893 / 1842233665)
Success! App '1829350' fully installed.
steam_appid: 1604030
Keeping only the latest 30 log files
Creating /vrising/data/20240523-0818-VRisingServer.log
Launching ARM V Rising

xvfb-run: error: Xvfb failed to start

gogoout commented 5 months ago

Which environment are you running on? Are you building image yourself or pulling from docker hub? I recently change the xvfb command to xvfb-run to solve one of my failed to restart problem. The latest version works for my instance.

ewoudje commented 5 months ago

Im pulling from docker hub. The server is oracle linux on oracle cloud. It worked the first couple of times.

But ive found out that it seems destroying the container and making it again fixes the issue.

gogoout commented 5 months ago

Seems this error is caused by xvfb not get killed when container stops. I have pushed a new version which hopefully would fix this.

gogoout / vrising-server-arm64

xvfb-run: error: Xvfb failed to start #1