starred/LinuxGSM

Fork 0

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

[GH-ISSUE #1558] Can't monitor/start servers #1217

New issue

Closed

opened 2026-02-27 02:55:56 +03:00 by kerem · 5 comments

kerem commented

2026-02-27 02:55:56 +03:00

Owner

Originally created by @shavitush on GitHub (Aug 2, 2017).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1558

That's since a server reboot. Had to change hardware..

Ubuntu Server 16.04

hns@dedi:~$ ./csgoserver start
[ERROR ] Fix csgo-server: Applying botprofile.db fix: Counter-Strike: Global Offensive
[ERROR ] Fix csgo-server: Applying valve.rc fix: Counter-Strike: Global Offensive
[  OK  ] Starting csgo-server: LinuxGSM
hns@dedi:~$ ./csgoserver monitor
[ERROR ] Monitor csgo-server: Checking session: FAIL
[ INFO ] Stopping csgo-server: LinuxGSM is already stopped
[ERROR ] Fix csgo-server: Applying botprofile.db fix: Counter-Strike: Global Offensive
[ERROR ] Fix csgo-server: Applying valve.rc fix: Counter-Strike: Global Offensive
[  OK  ] Starting csgo-server: LinuxGSM

And the server doesn't start. It all used to be fine, including the botprofile.db/valve.rc fixes..

csgo-server-script.log:

Aug 02 19:15:17 csgo-server: START: PASS: Started LinuxGSM
Aug 02 19:15:17 csgo-server: START: PASS: command_start.sh exiting with code: 0
Aug 02 19:20:02 csgo-server: UPDATE LinuxGSM: INFO: Updating LinuxGSM
Aug 02 19:20:03 csgo-server: MONITOR: ERROR: SteamCMD is currently checking for updates
Aug 02 19:20:04 csgo-server: MONITOR: ERROR: command_monitor.sh exiting with code: 2
Aug 02 19:20:18 csgo-server: MONITOR: ERROR: SteamCMD is currently checking for updates
Aug 02 19:20:19 csgo-server: MONITOR: ERROR: command_monitor.sh exiting with code: 2
Aug 02 19:20:45 csgo-server: UPDATE LinuxGSM: PASS: Updating functions
Aug 02 19:20:45 csgo-server: UPDATE LinuxGSM: PASS: command_update_linuxgsm.sh exiting with code: 0

I've tried to update LGSM and validate the game files, it's still broken.

Originally created by @shavitush on GitHub (Aug 2, 2017). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1558 That's since a server reboot. Had to change hardware.. Ubuntu Server 16.04 ``` hns@dedi:~$ ./csgoserver start [ERROR ] Fix csgo-server: Applying botprofile.db fix: Counter-Strike: Global Offensive [ERROR ] Fix csgo-server: Applying valve.rc fix: Counter-Strike: Global Offensive [ OK ] Starting csgo-server: LinuxGSM hns@dedi:~$ ./csgoserver monitor [ERROR ] Monitor csgo-server: Checking session: FAIL [ INFO ] Stopping csgo-server: LinuxGSM is already stopped [ERROR ] Fix csgo-server: Applying botprofile.db fix: Counter-Strike: Global Offensive [ERROR ] Fix csgo-server: Applying valve.rc fix: Counter-Strike: Global Offensive [ OK ] Starting csgo-server: LinuxGSM ``` And the server doesn't start. It all used to be fine, including the botprofile.db/valve.rc fixes.. csgo-server-script.log: ``` Aug 02 19:15:17 csgo-server: START: PASS: Started LinuxGSM Aug 02 19:15:17 csgo-server: START: PASS: command_start.sh exiting with code: 0 Aug 02 19:20:02 csgo-server: UPDATE LinuxGSM: INFO: Updating LinuxGSM Aug 02 19:20:03 csgo-server: MONITOR: ERROR: SteamCMD is currently checking for updates Aug 02 19:20:04 csgo-server: MONITOR: ERROR: command_monitor.sh exiting with code: 2 Aug 02 19:20:18 csgo-server: MONITOR: ERROR: SteamCMD is currently checking for updates Aug 02 19:20:19 csgo-server: MONITOR: ERROR: command_monitor.sh exiting with code: 2 Aug 02 19:20:45 csgo-server: UPDATE LinuxGSM: PASS: Updating functions Aug 02 19:20:45 csgo-server: UPDATE LinuxGSM: PASS: command_update_linuxgsm.sh exiting with code: 0 ``` I've tried to update LGSM and validate the game files, it's still broken.

kerem closed this issue

2026-02-27 02:55:56 +03:00

kerem commented

2026-02-27 02:55:56 +03:00

Author

Owner

@Froster2406 commented on GitHub (Aug 2, 2017):

I got the same problem since the newest csgo update (02.08.2017). Can't update the server because every time the update starts the server gets in a sort of idle status for about 10 minutes and tries to download the update but fails and gets stuck in an infinite loop afterwards.

Log from the console

gameserver@FrostBolt:~/compMatchServer$ ./csgoserver update
[  OK  ] Update competitive-server: Checking for update: Server logs: Update requested

Applying update...
[  OK  ] Update competitive-server: Updating FrostBolt.ch - 5v5 Competitive Server | 128 Tick
Redirecting stderr to '/home/gameserver/Steam/logs/stderr.txt'
Looks like steam didn't shutdown cleanly, scheduling immediate update check
[  0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation
-- type 'quit' to exit --
Loading Steam API...threadtools.cpp (1905) : Assertion Failed: No space left on device
OK.

Connecting anonymously to Steam Public...Logged in OK
Waiting for user info...OK
 Update state (0x3) reconfiguring, progress: 0.00 (0 / 0)
 Update state (0x5) validating, progress: 0.00 (0 / 0)
 Update state (0x5) validating, progress: 0.00 (0 / 0)
 Update state (0x5) validating, progress: 0.00 (0 / 0)
 Update state (0x5) validating, progress: 0.00 (0 / 0)
 Update state (0x5) validating, progress: 0.00 (0 / 0)

@Froster2406 commented on GitHub (Aug 2, 2017): I got the same problem since the newest csgo update (02.08.2017). Can't update the server because every time the update starts the server gets in a sort of idle status for about 10 minutes and tries to download the update but fails and gets stuck in an infinite loop afterwards. Log from the console ``` gameserver@FrostBolt:~/compMatchServer$ ./csgoserver update [ OK ] Update competitive-server: Checking for update: Server logs: Update requested Applying update... [ OK ] Update competitive-server: Updating FrostBolt.ch - 5v5 Competitive Server | 128 Tick Redirecting stderr to '/home/gameserver/Steam/logs/stderr.txt' Looks like steam didn't shutdown cleanly, scheduling immediate update check [ 0%] Checking for available updates... [----] Verifying installation... Steam Console Client (c) Valve Corporation -- type 'quit' to exit -- Loading Steam API...threadtools.cpp (1905) : Assertion Failed: No space left on device OK. Connecting anonymously to Steam Public...Logged in OK Waiting for user info...OK Update state (0x3) reconfiguring, progress: 0.00 (0 / 0) Update state (0x5) validating, progress: 0.00 (0 / 0) Update state (0x5) validating, progress: 0.00 (0 / 0) Update state (0x5) validating, progress: 0.00 (0 / 0) Update state (0x5) validating, progress: 0.00 (0 / 0) Update state (0x5) validating, progress: 0.00 (0 / 0) ```

kerem commented

2026-02-27 02:55:56 +03:00

Author

Owner

@shavitush commented on GitHub (Aug 7, 2017):

My server ran out of disk space while updating servers and it basically broke the whole thing.. fixed by deleting all of them and reinstalling.

@shavitush commented on GitHub (Aug 7, 2017): My server ran out of disk space while updating servers and it basically broke the whole thing.. fixed by deleting all of them and reinstalling.

kerem commented

2026-02-27 02:55:56 +03:00

Author

Owner

@Froster2406 commented on GitHub (Aug 7, 2017):

My server ran out of disk space while updating servers and it basically broke the whole thing.. fixed by deleting all of them and reinstalling.

Does still not work for my side, since i got over 1.5 TByte of free space. I will edit this comment if i find a fix.

@Froster2406 commented on GitHub (Aug 7, 2017): > My server ran out of disk space while updating servers and it basically broke the whole thing.. fixed by deleting all of them and reinstalling. Does still not work for my side, since i got over 1.5 TByte of free space. I will edit this comment if i find a fix.

kerem commented

2026-02-27 02:55:57 +03:00

Author

Owner

@shavitush commented on GitHub (Aug 7, 2017):

@Froster2406 you should create your own issue then!

@shavitush commented on GitHub (Aug 7, 2017): @Froster2406 you should create your own issue then!

kerem commented

2026-02-27 02:55:57 +03:00

Author

Owner

@lock[bot] commented on GitHub (Aug 7, 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 (Aug 7, 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.