starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-25 06:05:57 +03:00

[GH-ISSUE #465] Doesnt restart by cron #384

New issue

Closed

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

kerem commented

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

Owner

Originally created by @ghost on GitHub (Jul 30, 2015).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/465

Hello, I tried making so, that the server restarts everytime 5AM inside cron, syslog said the command ran successfully, but the server didnt restart(atleast the server logs dont say so), but when I run the command manually, it works fine, even gets logged. this is what I got in crontab:

0 5 * * * su - user '/path/to/server restart' > /dev/null 2>&1

Originally created by @ghost on GitHub (Jul 30, 2015). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/465 Hello, I tried making so, that the server restarts everytime 5AM inside cron, syslog said the command ran successfully, but the server didnt restart(atleast the server logs dont say so), but when I run the command manually, it works fine, even gets logged. this is what I got in crontab: ``` 0 5 * * * su - user '/path/to/server restart' > /dev/null 2>&1 ```

kerem closed this issue

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

kerem commented

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

Author

Owner

@dgibbs64 commented on GitHub (Jul 30, 2015):

I cannot see anything wrong with that cronjob. I recommend testing by creating cronjobs to run a couple of mins after you set it and test.

@dgibbs64 commented on GitHub (Jul 30, 2015): I cannot see anything wrong with that cronjob. I recommend testing by creating cronjobs to run a couple of mins after you set it and test.

kerem commented

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

Author

Owner

@ghost commented on GitHub (Jul 31, 2015):

I did that already multiple times before too, it still said that the cron was successfull(syslog said so in ubuntu) but the server didnt restart at all, and it wasnt logged.

Again, cron said it was successful:

Jul 31 05:00:01 185 CRON[29114]: (root) CMD (su - USER '/server/gmodserver update-restart' > /dev/null 2>&1)
Jul 31 05:00:01 185 CRON[29115]: (root) CMD (su - USER '/server/gmodserver restart' > /dev/null 2>&1)

Edit:
Also tried a shellscript which I used on my foxedbot:

/server/restart.sh:

su USER
cd /server/
./gmodserver restart

crontab:

0 5 * * * /server/restart.sh  > /dev/null 2>&1

but it didnt work. log still says it ran, but server didnt restart.

Also, I'd like to ask, why theres no screen socket of the server when I do "screen -l",

and when I go into the server console, I cannot detach at all(CTRL b+d), the only way for me to detach is exiting putty, any help?

@ghost commented on GitHub (Jul 31, 2015): I did that already multiple times before too, it still said that the cron was successfull(syslog said so in ubuntu) but the server didnt restart at all, and it wasnt logged. Again, cron said it was successful: ``` Jul 31 05:00:01 185 CRON[29114]: (root) CMD (su - USER '/server/gmodserver update-restart' > /dev/null 2>&1) Jul 31 05:00:01 185 CRON[29115]: (root) CMD (su - USER '/server/gmodserver restart' > /dev/null 2>&1) ``` Edit: Also tried a shellscript which I used on my foxedbot: /server/restart.sh: ``` su USER cd /server/ ./gmodserver restart ``` crontab: ``` 0 5 * * * /server/restart.sh > /dev/null 2>&1 ``` but it didnt work. log still says it ran, but server didnt restart. Also, I'd like to ask, why theres no screen socket of the server when I do "screen -l", and when I go into the server console, I cannot detach at all(CTRL b+d), the only way for me to detach is exiting putty, any help?

kerem commented

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

Author

Owner

@dgibbs64 commented on GitHub (Jul 31, 2015):

It's Ctrl+b, d not ctrl, b+d many people type the command wrong.

I recommend trying your bash script with another command. E.g time
sh

#/bin/bash
date > /tmp/date

If that doesn't work there is some thing wrong with cron. The script is used by a lot of people without issue so its more likely some issue on your server

LGSM also uses tmux not screen.

@dgibbs64 commented on GitHub (Jul 31, 2015): It's Ctrl+b, d not ctrl, b+d many people type the command wrong. I recommend trying your bash script with another command. E.g time sh #/bin/bash date > /tmp/date If that doesn't work there is some thing wrong with cron. The script is used by a lot of people without issue so its more likely some issue on your server LGSM also uses tmux not screen.

kerem commented

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

Author

Owner

@dgibbs64 commented on GitHub (Jul 31, 2015):

Also to ensure you have not made an error make sure you follow the instructions to the letter and test to rule out user error ;-)

@dgibbs64 commented on GitHub (Jul 31, 2015): Also to ensure you have not made an error make sure you follow the instructions to the letter and test to rule out user error ;-)

kerem commented

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

Author

Owner

@ghost commented on GitHub (Aug 1, 2015):

some scripts of be worked without #bin/bash, but I reupdated it, which didnt work on root, crontab works fine on user though, I guess I have to use that.

I also could swear the server was running with screen, sorry, since my friend had on his server the console automaticly in screen, so I literally press CTRL + b - let go - and then d? because that didnt work for me either.

@ghost commented on GitHub (Aug 1, 2015): some scripts of be worked without #bin/bash, but I reupdated it, which didnt work on root, crontab works fine on user though, I guess I have to use that. I also could swear the server was running with screen, sorry, since my friend had on his server the console automaticly in screen, so I literally press CTRL + b - let go - and then d? because that didnt work for me either.

kerem commented

2026-02-27 02:01:11 +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.