[GH-ISSUE #544] [GMOD] Attempting graceful shutdown on every restart #439

Closed
opened 2026-02-27 02:01:27 +03:00 by kerem · 7 comments
Owner

Originally created by @UltimateByte on GitHub (Dec 9, 2015).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/544

Hi there,

Setting up new gmod servers.
On every ./gmodserver restart, "i get Attempting graceful shutdown:1 :2 :3 ..." and it never ends. I have to do ctrl + c. Then if i do ./gmodserver console, i can see the server actually rebooted.
Any idea of what's going on ?

Originally created by @UltimateByte on GitHub (Dec 9, 2015). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/544 Hi there, Setting up new gmod servers. On every ./gmodserver restart, "i get Attempting graceful shutdown:1 :2 :3 ..." and it never ends. I have to do ctrl + c. Then if i do ./gmodserver console, i can see the server actually rebooted. Any idea of what's going on ?
kerem 2026-02-27 02:01:27 +03:00
Author
Owner

@UltimateByte commented on GitHub (Dec 12, 2015):

I've seen this : https://github.com/dgibbs64/linuxgsm/issues/508

Seems not to be enough for a proper shutdown.
I don't really get why it does that.

<!-- gh-comment-id:164127906 --> @UltimateByte commented on GitHub (Dec 12, 2015): I've seen this : https://github.com/dgibbs64/linuxgsm/issues/508 Seems not to be enough for a proper shutdown. I don't really get why it does that.
Author
Owner

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

The server should force a shutdown after 30 seconds if a graceful shutdown was not successful.

<!-- gh-comment-id:166011951 --> @dgibbs64 commented on GitHub (Dec 19, 2015): The server should force a shutdown after 30 seconds if a graceful shutdown was not successful.
Author
Owner

@UltimateByte commented on GitHub (Dec 19, 2015):

I've never waited 30s yet, always ctrl + C to end it. Any idea of why is it doing a graceful shutdown ? It does it with the latest version of lgsm, but not ot the previous one (got many servers on the same machine).

<!-- gh-comment-id:166016956 --> @UltimateByte commented on GitHub (Dec 19, 2015): I've never waited 30s yet, always ctrl + C to end it. Any idea of why is it doing a graceful shutdown ? It does it with the latest version of lgsm, but not ot the previous one (got many servers on the same machine).
Author
Owner

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

Yeah a graceful shutdown is designed to give the server time to correctly turn off. All LGSM does is send the quit command to the server which is a lot cleaner than simply killing the process. Commonly as graceful shutdown only takes a few seconds. But im guessing that your garrys mod server is taking a long time or not responding to the quit command.

Maybe try opening up the console in on terminal and stopping the server in another to see what happens.

<!-- gh-comment-id:166159952 --> @dgibbs64 commented on GitHub (Dec 20, 2015): Yeah a graceful shutdown is designed to give the server time to correctly turn off. All LGSM does is send the quit command to the server which is a lot cleaner than simply killing the process. Commonly as graceful shutdown only takes a few seconds. But im guessing that your garrys mod server is taking a long time or not responding to the quit command. Maybe try opening up the console in on terminal and stopping the server in another to see what happens.
Author
Owner

@UltimateByte commented on GitHub (Dec 21, 2015):

OK thanks for the info.

You put me on the way.
The "quit" command orders a restart and makes a segmentation fault...
http://image.noelshack.com/fichiers/2015/52/1450664450-quit.png
GARRY !!!!!!!!
-________-

Waiting for a fix, we can add -norestart to launch option, then the graceful period is only 2 seconds. The downside is that it takes longer to restart the server with the crontab monitor than with an instant restart.

<!-- gh-comment-id:166171246 --> @UltimateByte commented on GitHub (Dec 21, 2015): OK thanks for the info. You put me on the way. The "quit" command orders a restart and makes a segmentation fault... http://image.noelshack.com/fichiers/2015/52/1450664450-quit.png GARRY !!!!!!!! -________- Waiting for a fix, we can add -norestart to launch option, then the graceful period is only 2 seconds. The downside is that it takes longer to restart the server with the crontab monitor than with an instant restart.
Author
Owner

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

Conclusion from gmod's github : that issue happens only when you're using a collection, even on windows. It should be fixed at the next gmod update.

<!-- gh-comment-id:168491119 --> @UltimateByte commented on GitHub (Jan 3, 2016): Conclusion from gmod's github : that issue happens only when you're using a collection, even on windows. It should be fixed at the next gmod update.
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.

<!-- gh-comment-id:406332575 --> @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.
Sign in to join this conversation.
No labels
Atomic
Epic
cannot reproduce
command: backup
command: console
command: debug
command: details
command: fast-dl
command: install
command: mods
command: monitor
command: post-details
command: restart
command: send
command: start
command: stop
command: update
command: update-lgsm
command: validate
command: wipe
distro: AlmaLinux
distro: Arch Linux
distro: CentOS
distro: Debian
distro: Fedora
distro: RedHat
distro: Rocky Linux
distro: Ubuntu
distro: openSUSE
engine: goldsrc
engine: source
game: 7 Days to Die
game: ARMA 3
game: Ark: Survival Evolved
game: Assetto Corsa
game: Avorion
game: BATTALION: Legacy
game: Barotrauma
game: Battalion 1944
game: Battlefield 1942
game: Black Mesa: Deathmatch
game: Blade Symphony
game: Call of Duty 2
game: Call of Duty 4
game: Call of Duty: United Offensive
game: Counter-Strike 1.6
game: Counter-Strike 2
game: Counter-Strike: Global Offensive
game: Counter-Strike: Source
game: Day of Infamy
game: Dayz
game: Death Match Classic
game: Don't Starve Together
game: ET: Legacy
game: Eco
game: Factorio
game: Factorio
game: Garry's Mod
game: Half-Life
game: Hurtword
game: Insurgecy
game: Insurgecy
game: Insurgency: Sandstorm
game: Just Cause 3
game: Killing Floor
game: Killing Floor 2
game: Left 4 Dead 2
game: Minecraft
game: Minecraft Bedrock
game: Mordhau
game: Multi Theft Auto
game: Mumble
game: Natural Selection 2
game: No More Room in Hell
game: Pavlov VR
game: Post Scriptum
game: Project Zomboid
game: Quake 3
game: QuakeWorld
game: Red Orchestra: Ostfront 41-45
game: Return to Castle Wolfenstein
game: Rising World
game: Rust
game: San Andreas Multiplayer
game: Satisfactory
game: Soldat
game: Soldier of Fortune 2
game: Squad
game: Squad 44
game: Starbound
game: Stationeers
game: Sven Co-op
game: Team Fortress 2
game: Teamspeak 3
game: Teeworlds
game: Terraria
game: The Front
game: Unreal Tournament 2004
game: Unreal Tournament 3
game: Unreal Tournament 99
game: Unturned
game: Valheim
game: Wurm Unlimited
game: Zombie Master Reborn
game: label missing
good first issue
help wanted
info: alerts
info: dependency
info: docker
info: docs
info: email
info: query
info: steamcmd
info: systemd
info: tmux
info: website
info: website
needs more info
outcome: duplicate
outcome: issue resolved
outcome: issue resolved
outcome: issue unresolved
outcome: pr accepted
outcome: pr rejected
outcome: unconfirmed
outcome: wontfix
outcome: wrong forum
potential-duplicate
priority
pull-request
type: bug
type: feature
type: feature
type: feature request
type: game server request
type: refactor
waiting response
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/LinuxGSM#439
No description provided.