starred/LinuxGSM

Fork 0

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

[GH-ISSUE #4316] [Bug]: Command_Monitor.sh not working properly as Cron Job #2704

New issue

Closed

opened 2026-02-27 03:04:50 +03:00 by kerem · 11 comments

kerem commented

2026-02-27 03:04:50 +03:00

Owner

Originally created by @Royel-Payne on GitHub (Sep 23, 2023).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/4316

User story

Command_Monitor not working properly as Cron Job after latest update

Game

Rust

Linux distro

Ubuntu 22.04, Ubuntu 20.04

Command

command: monitor

Further information

LGSM Monitor is no longer restarting game server after an update-lgsm was done on 9-17-23. This was working properly before a scheduled task to update-lgsm was done. (0 0 * * 0 /home/rustserver/rustserver update-lgsm > /dev/null 2>&1)

This is being run as a cron job. (*/5 * * * * /home/rustserver/rustserver monitor > /dev/null 2>&1)

When ran from CLI (./rustserver monitor) this functions as expected but when running as a Cron job this fails.

Log files are included

Relevant log output

Sep 22 17:40:03.430 rustserver: MONITOR: INFO: Checking installer: CHECKING
Sep 22 17:40:04.437 rustserver: MONITOR: PASS: Checking installer: LinuxGSM is installing
Sep 22 17:40:04.447 rustserver: MONITOR: INFO: LinuxGSM version: v23.5.2
Sep 22 17:40:04.449 rustserver: MONITOR: PASS: core_exit.sh exiting with code: 0
Sep 22 17:45:03.154 rustserver: MONITOR: INFO: Checking installer: CHECKING
Sep 22 17:45:04.161 rustserver: MONITOR: PASS: Checking installer: LinuxGSM is installing
Sep 22 17:45:04.172 rustserver: MONITOR: INFO: LinuxGSM version: v23.5.2
Sep 22 17:45:04.175 rustserver: MONITOR: PASS: core_exit.sh exiting with code: 0
Sep 22 17:50:02.892 rustserver: MONITOR: INFO: Checking installer: CHECKING
Sep 22 17:50:03.899 rustserver: MONITOR: PASS: Checking installer: LinuxGSM is installing
Sep 22 17:50:03.912 rustserver: MONITOR: INFO: LinuxGSM version: v23.5.2
Sep 22 17:50:03.915 rustserver: MONITOR: PASS: core_exit.sh exiting with code: 0
Sep 22 17:55:03.625 rustserver: MONITOR: INFO: Checking installer: CHECKING
Sep 22 17:55:04.633 rustserver: MONITOR: PASS: Checking installer: LinuxGSM is installing
Sep 22 17:55:04.644 rustserver: MONITOR: INFO: LinuxGSM version: v23.5.2
Sep 22 17:55:04.646 rustserver: MONITOR: PASS: core_exit.sh exiting with code: 0
Sep 22 18:00:03.377 rustserver: MONITOR: INFO: Checking installer: CHECKING
Sep 22 18:00:04.385 rustserver: MONITOR: PASS: Checking installer: LinuxGSM is installing
Sep 22 18:00:04.396 rustserver: MONITOR: INFO: LinuxGSM version: v23.5.2
Sep 22 18:00:04.399 rustserver: MONITOR: PASS: core_exit.sh exiting with code: 0
Sep 22 18:05:03.102 rustserver: MONITOR: INFO: Checking installer: CHECKING
Sep 22 18:05:04.109 rustserver: MONITOR: PASS: Checking installer: LinuxGSM is installing
Sep 22 18:05:04.120 rustserver: MONITOR: INFO: LinuxGSM version: v23.5.2
Sep 22 18:05:04.123 rustserver: MONITOR: PASS: core_exit.sh exiting with code: 0
Sep 22 18:10:02.873 rustserver: MONITOR: INFO: Checking installer: CHECKING
Sep 22 18:10:03.881 rustserver: MONITOR: PASS: Checking installer: LinuxGSM is installing
Sep 22 18:10:03.897 rustserver: MONITOR: INFO: LinuxGSM version: v23.5.2
Sep 22 18:10:03.900 rustserver: MONITOR: PASS: core_exit.sh exiting with code: 0

Steps to reproduce

Run command_monitor.sh as Cron job
Stop/Restart server from Rcon
Wait for Cron job to run, server should be restarted but does not succeed
View log files

Originally created by @Royel-Payne on GitHub (Sep 23, 2023). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/4316 ### User story Command_Monitor not working properly as Cron Job after latest update ### Game Rust ### Linux distro Ubuntu 22.04, Ubuntu 20.04 ### Command command: monitor ### Further information LGSM Monitor is no longer restarting game server after an update-lgsm was done on 9-17-23. This was working properly before a scheduled task to update-lgsm was done. (0 0 * * 0 /home/rustserver/rustserver update-lgsm > /dev/null 2>&1) This is being run as a cron job. (*/5 * * * * /home/rustserver/rustserver monitor > /dev/null 2>&1) When ran from CLI (./rustserver monitor) this functions as expected but when running as a Cron job this fails. Log files are included ### Relevant log output ```shell Sep 22 17:40:03.430 rustserver: MONITOR: INFO: Checking installer: CHECKING Sep 22 17:40:04.437 rustserver: MONITOR: PASS: Checking installer: LinuxGSM is installing Sep 22 17:40:04.447 rustserver: MONITOR: INFO: LinuxGSM version: v23.5.2 Sep 22 17:40:04.449 rustserver: MONITOR: PASS: core_exit.sh exiting with code: 0 Sep 22 17:45:03.154 rustserver: MONITOR: INFO: Checking installer: CHECKING Sep 22 17:45:04.161 rustserver: MONITOR: PASS: Checking installer: LinuxGSM is installing Sep 22 17:45:04.172 rustserver: MONITOR: INFO: LinuxGSM version: v23.5.2 Sep 22 17:45:04.175 rustserver: MONITOR: PASS: core_exit.sh exiting with code: 0 Sep 22 17:50:02.892 rustserver: MONITOR: INFO: Checking installer: CHECKING Sep 22 17:50:03.899 rustserver: MONITOR: PASS: Checking installer: LinuxGSM is installing Sep 22 17:50:03.912 rustserver: MONITOR: INFO: LinuxGSM version: v23.5.2 Sep 22 17:50:03.915 rustserver: MONITOR: PASS: core_exit.sh exiting with code: 0 Sep 22 17:55:03.625 rustserver: MONITOR: INFO: Checking installer: CHECKING Sep 22 17:55:04.633 rustserver: MONITOR: PASS: Checking installer: LinuxGSM is installing Sep 22 17:55:04.644 rustserver: MONITOR: INFO: LinuxGSM version: v23.5.2 Sep 22 17:55:04.646 rustserver: MONITOR: PASS: core_exit.sh exiting with code: 0 Sep 22 18:00:03.377 rustserver: MONITOR: INFO: Checking installer: CHECKING Sep 22 18:00:04.385 rustserver: MONITOR: PASS: Checking installer: LinuxGSM is installing Sep 22 18:00:04.396 rustserver: MONITOR: INFO: LinuxGSM version: v23.5.2 Sep 22 18:00:04.399 rustserver: MONITOR: PASS: core_exit.sh exiting with code: 0 Sep 22 18:05:03.102 rustserver: MONITOR: INFO: Checking installer: CHECKING Sep 22 18:05:04.109 rustserver: MONITOR: PASS: Checking installer: LinuxGSM is installing Sep 22 18:05:04.120 rustserver: MONITOR: INFO: LinuxGSM version: v23.5.2 Sep 22 18:05:04.123 rustserver: MONITOR: PASS: core_exit.sh exiting with code: 0 Sep 22 18:10:02.873 rustserver: MONITOR: INFO: Checking installer: CHECKING Sep 22 18:10:03.881 rustserver: MONITOR: PASS: Checking installer: LinuxGSM is installing Sep 22 18:10:03.897 rustserver: MONITOR: INFO: LinuxGSM version: v23.5.2 Sep 22 18:10:03.900 rustserver: MONITOR: PASS: core_exit.sh exiting with code: 0 ``` ### Steps to reproduce 1. Run command_monitor.sh as Cron job 2. Stop/Restart server from Rcon 3. Wait for Cron job to run, server should be restarted but does not succeed 4. View log files

kerem

2026-02-27 03:04:50 +03:00

closed this issue
added the
type: bug

command: monitor

distro: Ubuntu

command: install

game: Rust

command: update-lgsm
labels

kerem commented

2026-02-27 03:04:51 +03:00

Author

Owner

@jonathan-robertson commented on GitHub (Sep 23, 2023):

This is also happening to me; also using Ubuntu; hearing the version of Ubuntu does not seem to matter.

For what it's worth, I'm using LinuxGSM to manage 7 Days to Die.

@jonathan-robertson commented on GitHub (Sep 23, 2023): This is also happening to me; also using Ubuntu; hearing the version of Ubuntu does not seem to matter. For what it's worth, I'm using LinuxGSM to manage 7 Days to Die.

kerem commented

2026-02-27 03:04:51 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Sep 23, 2023):

Thanks for the info. I am reviewing a couple of bugs relating to monitor. I will try and replicate this as well

@dgibbs64 commented on GitHub (Sep 23, 2023): Thanks for the info. I am reviewing a couple of bugs relating to monitor. I will try and replicate this as well

kerem commented

2026-02-27 03:04:51 +03:00

Author

Owner

@Royel-Payne commented on GitHub (Sep 23, 2023):

Thanks!

Let me know if you need anything else, I'll be glad to provide more info if you need.

@Royel-Payne commented on GitHub (Sep 23, 2023): Thanks! Let me know if you need anything else, I'll be glad to provide more info if you need.

kerem commented

2026-02-27 03:04:51 +03:00

Author

Owner

@TheBambino commented on GitHub (Sep 23, 2023):

I am also having this issue. Same OS. Latest update.

@TheBambino commented on GitHub (Sep 23, 2023): I am also having this issue. Same OS. Latest update.

kerem commented

2026-02-27 03:04:51 +03:00

Author

Owner

@aStonePenguin commented on GitHub (Sep 24, 2023):

Same problem with Debian 12

@aStonePenguin commented on GitHub (Sep 24, 2023): Same problem with Debian 12

kerem commented

2026-02-27 03:04:51 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Sep 25, 2023):

So this is a fun bug to identify. It appears to only happen with cron or watch. Bash appears to just stop running. I will continue doing tests until I find the issue. A hotfix will go out once fixed

@dgibbs64 commented on GitHub (Sep 25, 2023): So this is a fun bug to identify. It appears to only happen with cron or watch. Bash appears to just stop running. I will continue doing tests until I find the issue. A hotfix will go out once fixed

kerem commented

2026-02-27 03:04:51 +03:00

Author

Owner

@Royel-Payne commented on GitHub (Sep 25, 2023):

Well I'm glad to hear it's fun! :)

Thanks for your time, I'm sure we all greatly appreciate the hard work you put into this project.

Good luck finding the solution. I'll keep my eye out for any updates.

@Royel-Payne commented on GitHub (Sep 25, 2023): Well I'm glad to hear it's fun! :) Thanks for your time, I'm sure we all greatly appreciate the hard work you put into this project. Good luck finding the solution. I'll keep my eye out for any updates.

kerem commented

2026-02-27 03:04:51 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Sep 26, 2023):

Found the issue. cron uses a different environment to the default bash one (sh) and it is missing the $USER variable. So I added code to set the $USER variable if missing. Hopfully that should now fix the issue. Please update linuxgsm and let me know :)

@dgibbs64 commented on GitHub (Sep 26, 2023): Found the issue. cron uses a different environment to the default bash one (sh) and it is missing the $USER variable. So I added code to set the $USER variable if missing. Hopfully that should now fix the issue. Please update linuxgsm and let me know :)

kerem commented

2026-02-27 03:04:51 +03:00

Author

Owner

@Royel-Payne commented on GitHub (Sep 26, 2023):

Thanks man, I'll update and let you know the results shortly.

@Royel-Payne commented on GitHub (Sep 26, 2023): Thanks man, I'll update and let you know the results shortly.

kerem commented

2026-02-27 03:04:51 +03:00

Author

Owner

@Royel-Payne commented on GitHub (Sep 26, 2023):

Tested and it looks to be working.

Thanks so much for getting this resolved.

@Royel-Payne commented on GitHub (Sep 26, 2023): Tested and it looks to be working. Thanks so much for getting this resolved.

kerem commented

2026-02-27 03:04:51 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 30, 2024):

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 (Sep 30, 2024): 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:55:40 +03:00

[PR #2704] [MERGED] fix(details): catch error should ifconfig.co fail #3750