starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-25 14:15:59 +03:00

[GH-ISSUE #540] ARK server update stopping after one try #438

New issue

Closed

opened 2026-02-27 02:01:26 +03:00 by kerem · 6 comments

kerem commented

2026-02-27 02:01:26 +03:00

Owner

Originally created by @M-D-M on GitHub (Dec 3, 2015).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/540

Having this problem consistently with either update or force-update -- any ideas? I can run it again and again but it just downloads a little bit more each time:

steamuser@steamvm:/storage$ ./arkserver force-update
[  OK  ] Update ark-server: Updating arkserver
Redirecting stderr to '/home/steamuser/Steam/logs/stderr.txt'
[  0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation
-- type 'quit' to exit --
Loading Steam API...OK.

Connecting anonymously to Steam Public...Logged in OK
Waiting for license info...OK
 Update state (0x3) reconfiguring, progress: 0.00 (0 / 0)
 Update state (0x61) downloading, progress: 0.27 (79322774 / 29011247757)
Error! App '376030' state is 0x402 after update job.
CWorkThreadPool::~CWorkThreadPool: work complete queue not empty, 8 items discarded.
CWorkThreadPool::~CWorkThreadPool: work processing queue not empty: 386 items discarded.
steamuser@steamvm:/storage

Originally created by @M-D-M on GitHub (Dec 3, 2015). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/540 Having this problem consistently with either update or force-update -- any ideas? I can run it again and again but it just downloads a little bit more each time: ``` steamuser@steamvm:/storage$ ./arkserver force-update [ OK ] Update ark-server: Updating arkserver Redirecting stderr to '/home/steamuser/Steam/logs/stderr.txt' [ 0%] Checking for available updates... [----] Verifying installation... Steam Console Client (c) Valve Corporation -- type 'quit' to exit -- Loading Steam API...OK. Connecting anonymously to Steam Public...Logged in OK Waiting for license info...OK Update state (0x3) reconfiguring, progress: 0.00 (0 / 0) Update state (0x61) downloading, progress: 0.27 (79322774 / 29011247757) Error! App '376030' state is 0x402 after update job. CWorkThreadPool::~CWorkThreadPool: work complete queue not empty, 8 items discarded. CWorkThreadPool::~CWorkThreadPool: work processing queue not empty: 386 items discarded. steamuser@steamvm:/storage ```

kerem

2026-02-27 02:01:26 +03:00

closed this issue
added the
type: bug

info: steamcmd
labels

kerem commented

2026-02-27 02:01:27 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Dec 9, 2015):

This is a bug with SteamCMD I recommend a Google around for this one to see it you find anything. Validation may possibly resolve this though. Let me know if you find anything :-)

@dgibbs64 commented on GitHub (Dec 9, 2015): This is a bug with SteamCMD I recommend a Google around for this one to see it you find anything. Validation may possibly resolve this though. Let me know if you find anything :-)

kerem commented

2026-02-27 02:01:27 +03:00

Author

Owner

@M-D-M commented on GitHub (Dec 9, 2015):

Nope -- been googling about it for months now. Nobody seems to have anything but questions. I have my own script that validates as well -- doesn't fix the problem. I eventually had to make a script that just re-runs the same command over and over again if the previous one fails, just to get it to work, however, this constant stop/restart method means an update takes HOURS, sometimes days, instead of 30min or so for people who don't have this problem:

$updateArkCmd

while [ $? -ne 0 ]
do
    $updateArkCmd
done

@M-D-M commented on GitHub (Dec 9, 2015): Nope -- been googling about it for months now. Nobody seems to have anything but questions. I have my own script that validates as well -- doesn't fix the problem. I eventually had to make a script that just re-runs the same command over and over again if the previous one fails, just to get it to work, however, this constant stop/restart method means an update takes HOURS, sometimes days, instead of 30min or so for people who don't have this problem: ``` $updateArkCmd while [ $? -ne 0 ] do $updateArkCmd done ```

kerem commented

2026-02-27 02:01:27 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Dec 10, 2015):

Could be an issue with your server maybe the dependencies required for steamcmd are damaged. It's worth trying on a fresh install

@dgibbs64 commented on GitHub (Dec 10, 2015): Could be an issue with your server maybe the dependencies required for steamcmd are damaged. It's worth trying on a fresh install

kerem commented

2026-02-27 02:01:27 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Dec 16, 2015):

I could do with finding out a list of error codes for SteamCMD e.g 0x402 This may help figure out the issues such as this. Then I could write error handling in a bit better

@dgibbs64 commented on GitHub (Dec 16, 2015): I could do with finding out a list of error codes for SteamCMD e.g 0x402 This may help figure out the issues such as this. Then I could write error handling in a bit better

kerem commented

2026-02-27 02:01:27 +03:00

Author

Owner

@UltimateByte commented on GitHub (Jan 7, 2016):

I've been googleing this. The vast majority of people getting this error just need to restart the process until it works. Could be due to some packet loss. You'd better re-run a "validate" after such a painful download though.

Closing this, feel free to re-open if needed.

Have a nice admin time !

@UltimateByte commented on GitHub (Jan 7, 2016): I've been googleing this. The vast majority of people getting this error just need to restart the process until it works. Could be due to some packet loss. You'd better re-run a "validate" after such a painful download though. Closing this, feel free to re-open if needed. Have a nice admin time !

kerem commented

2026-02-27 02:01:27 +03:00

Author

Owner

@lock[bot] commented on GitHub (Jul 19, 2018):

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock[bot] commented on GitHub (Jul 19, 2018): This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.