[GH-ISSUE #3105] Unclear of cronjob ran #2193

New issue

Closed

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

kerem commented

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

Owner

Originally created by @b1kks3r on GitHub (Nov 20, 2020).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/3105

Hi guys,

I am working on multiple gameservers but of course first I want to make sure the configuration and first server are running perfectly. That's not the case for my cronjob.

When I typ (as root) grep cron /var/log/syslog | tail -1
Nov 20 08:40:27 DS5146 crontab[171832]: (root) END EDIT (root)

I expected to see some lines about the csgoserver.

Below I'll show only relevant data.

Server details
Master server: listed
Status: ONLINE

Script details
User: csgoserver
Location: /home/csgoserver
Config file: /home/csgoserver/serverfiles/csgo/cfg/csgoserver.cfg

I am trying to setup the cronjobs (root) and this is how I did it;

Login as root

crontab -e
*/5 * * * * su - csgoserver -c '/home/csgoserver/csgoserver monitor' > /dev/null 2>&1
*/30 * * * * su - csgoserver -c '/home/csgoserver/csgoserver update' > /dev/null 2>&1
30 4 * * * su - csgoserver -c '/home/csgoserver/csgoserver force-update' > /dev/null 2>&1
0 0 * * 0 su - csgoserver -c '/home/csgoserver/csgoserver update-lgsm' > /dev/null 2>&1

check if my changes are saved with crontab -l and they do appear

systemctl status cron
systemctl status cron
● cron.service - Regular background program processing daemon Loaded: loaded (/lib/systemd/system/cron.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2020-11-20 07:43:36 UTC; 53min ago
Docs: man:cron(8)
Main PID: 158787 (cron)
Tasks: 19 (limit: 38283)
Memory: 208.8M
CGroup: /system.slice/cron.service
├─120079 tmux new-session -d -x 80 -y 23 -s csgoserver ./srcds_run -game csgo -usercon -strictportbind -i>
├─120080 sh -c ./srcds_run -game csgo -usercon -strictportbind -ip 0.0.0.0 -port 27015 +clientport 27005 >
├─120081 /bin/sh ./srcds_run -game csgo -usercon -strictportbind -ip 0.0.0.0 -port 27015 +clientport 2700>
├─120088 ./srcds_linux -game csgo -usercon -strictportbind -ip 0.0.0.0 -port 27015 +clientport 27005 +tv_>
└─158787 /usr/sbin/cron -f

Originally created by @b1kks3r on GitHub (Nov 20, 2020). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/3105 Hi guys, I am working on multiple gameservers but of course first I want to make sure the configuration and first server are running perfectly. That's not the case for my cronjob. **When I typ (as root) grep cron /var/log/syslog | tail -1** `Nov 20 08:40:27 DS5146 crontab[171832]: (root) END EDIT (root)` I expected to see some lines about the csgoserver. **Below I'll show only relevant data.** **Server details** `Master server: listed` `Status: ONLINE` **Script details** `User: csgoserver` `Location: /home/csgoserver` `Config file: /home/csgoserver/serverfiles/csgo/cfg/csgoserver.cfg` I am trying to setup the cronjobs (root) and this is how I did it; **Login as root** **crontab -e** `*/5 * * * * su - csgoserver -c '/home/csgoserver/csgoserver monitor' > /dev/null 2>&1` `*/30 * * * * su - csgoserver -c '/home/csgoserver/csgoserver update' > /dev/null 2>&1` `30 4 * * * su - csgoserver -c '/home/csgoserver/csgoserver force-update' > /dev/null 2>&1` `0 0 * * 0 su - csgoserver -c '/home/csgoserver/csgoserver update-lgsm' > /dev/null 2>&1` **check if my changes are saved with crontab -l and they do appear** **systemctl status cron** `systemctl status cron` `● cron.service - Regular background program processing daemon Loaded: loaded (/lib/systemd/system/cron.service; enabled; vendor preset: enabled)` ` Active: active (running) since Fri 2020-11-20 07:43:36 UTC; 53min ago` ` Docs: man:cron(8)` ` Main PID: 158787 (cron)` ` Tasks: 19 (limit: 38283)` ` Memory: 208.8M` ` CGroup: /system.slice/cron.service` `├─120079 tmux new-session -d -x 80 -y 23 -s csgoserver ./srcds_run -game csgo -usercon -strictportbind -i>` `├─120080 sh -c ./srcds_run -game csgo -usercon -strictportbind -ip 0.0.0.0 -port 27015 +clientport 27005 >` `├─120081 /bin/sh ./srcds_run -game csgo -usercon -strictportbind -ip 0.0.0.0 -port 27015 +clientport 2700>` `├─120088 ./srcds_linux -game csgo -usercon -strictportbind -ip 0.0.0.0 -port 27015 +clientport 27005 +tv_>` `└─158787 /usr/sbin/cron -f`

kerem closed this issue

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

kerem commented

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

Author

Owner

@h3o66 commented on GitHub (Nov 20, 2020):

All what lgsm does, even the executed cron jobs should be logged in log/script/csgoserver-script.log

Also I would search different for the logs in the messages log:
grep csgo /var/log/messages | tail -n 10

@h3o66 commented on GitHub (Nov 20, 2020): All what lgsm does, even the executed cron jobs should be logged in `log/script/csgoserver-script.log` Also I would search different for the logs in the messages log: `grep csgo /var/log/messages | tail -n 10`

kerem commented

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

Author

Owner

@b1kks3r commented on GitHub (Nov 20, 2020):

Ubuntu no longer uses the /var/log/messages file by default. The same information is available in the file /var/log/syslog. So, the following command showed me where I was looking for!
grep csgo /var/log/syslog | tail -n 10

@b1kks3r commented on GitHub (Nov 20, 2020): Ubuntu no longer uses the /var/log/messages file by default. The same information is available in the file /var/log/syslog. So, the following command showed me where I was looking for! `grep csgo /var/log/syslog | tail -n 10`

kerem commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Nov 21, 2021):

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

@github-actions[bot] commented on GitHub (Nov 21, 2021): This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

kerem referenced this issue

2026-02-27 03:54:59 +03:00

[PR #2279] [MERGED] fix(fix): re-add fix_tf2 and minor fix refactor #3568

kerem referenced this issue

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

[PR #2289] [MERGED] fix(fix): re-add fix_tf2 and minor fix refactor #3572