[GH-ISSUE #272] [LGSM] cronjob calls of tf2server monitor, fn_tmuxcheck fails #231

New issue

Closed

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

kerem commented

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

Owner

Originally created by @JHiemenz on GitHub (Jan 21, 2015).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/272

Hello sir,

Not sure how this should get classified, it isn't really a 'bug' with any of your code, but perhaps some documenting of more prerequisites for users wanting to use cron entries, at least on some systems.
I noticed the following behavior under Ubuntu-14.04.1-LTS-64bit

When setting up cronjobs for the user, the PATH environment is bare for scripts called via cron. The instance of 'tf2server monitor' was always outputting "Tmux is not installed' messages to my logs and then attempting to restart, even though tmux is installed (/usr/local/bin/tmux) and the server was running. A quick test showed me that the PATH under cron was only '/usr/bin:/bin', which is quite bare, when the Ubuntu tmux package is installed to /usr/local/bin

The solution I took was when setting up the cron entries, to set the PATH at the top of the crontab file.

So, my crontab entries are now looking like this:

USER=tf2server
PATH=/home/tf2server/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
0 5 * * *  /home/tf2server/tf2server update-restart > /dev/null 2>&1
*/5 * * * * /home/tf2server/tf2server monitor > /dev/null 2>&1

I suppose setting PATH inside the tf2server script would also work, but since this issue is more of a system related item, I think fixing it in crontab is better than changing the tf2server script unnecessarily. Perhaps some extra documentation .. or a test for tmux that will write out full path to tmux into the fn calls?

Originally created by @JHiemenz on GitHub (Jan 21, 2015). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/272 Hello sir, Not sure how this should get classified, it isn't really a 'bug' with any of your code, but perhaps some documenting of more prerequisites for users wanting to use cron entries, at least on some systems. I noticed the following behavior under Ubuntu-14.04.1-LTS-64bit When setting up cronjobs for the user, the PATH environment is bare for scripts called via cron. The instance of 'tf2server monitor' was always outputting "Tmux is not installed' messages to my logs and then attempting to restart, even though tmux is installed (/usr/local/bin/tmux) and the server was running. A quick test showed me that the PATH under cron was only '/usr/bin:/bin', which is quite bare, when the Ubuntu tmux package is installed to /usr/local/bin The solution I took was when setting up the cron entries, to set the PATH at the top of the crontab file. So, my crontab entries are now looking like this: ``` USER=tf2server PATH=/home/tf2server/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games 0 5 * * * /home/tf2server/tf2server update-restart > /dev/null 2>&1 */5 * * * * /home/tf2server/tf2server monitor > /dev/null 2>&1 ``` I suppose setting PATH inside the tf2server script would also work, but since this issue is more of a system related item, I think fixing it in crontab is better than changing the tf2server script unnecessarily. Perhaps some extra documentation .. or a test for tmux that will write out full path to tmux into the fn calls?

kerem

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

closed this issue
added the
type: bug
label

kerem commented

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

Author

Owner

@dgibbs64 commented on GitHub (Jan 22, 2015):

This should be easy to resolve within the script itself. Should be a simple if statement. I will write a fix for this soon.

@dgibbs64 commented on GitHub (Jan 22, 2015): This should be easy to resolve within the script itself. Should be a simple if statement. I will write a fix for this soon.

kerem commented

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

Author

Owner

@dgibbs64 commented on GitHub (Apr 17, 2015):

I have made some changes that should reduce the chance of issues.

@dgibbs64 commented on GitHub (Apr 17, 2015): I have made some changes that should reduce the chance of issues.

kerem commented

2026-02-27 02:00:17 +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.