*/5 * * * * /home/gmodserver/gmodserver monitor > /dev/null 2>&1 The result is the server still doesn't auto restart thanks to server query after a crash/freeze of the server that is not detected by SRCDS and so doesn't auto restart.Ĭould it be the crontab monitor function that fails ?Ġ 5 * * * /home/gmodserver/gmodserver update-restart > /dev/null 2>&1
![gmod file exists gmod file exists](https://ponysfm.com/system/images/imgs/000/001/156/full/7b75e862676b849d428cf580b51f7dc2.png)
#Gmod file exists manual
But a after some time (my guess is after a crash), the manual monitor function doesn't work anymore. The weird thing is : Right after the server started, the monitor function is OK.
![gmod file exists gmod file exists](https://pm1.narvii.com/6549/99ce8ee4dd349fa4e119182bd64aaa0d96edf95e_hq.jpg)
I've seen your answers there #171 (comment)Ĭould you please telle me where is the lock file located, so i check the permissions on it ? (with ls -l ) If you need to update-restart, think about making a simple restart after that. Temporary fix : change automatic update-restart by a simple restart. I'm a bit lost here, any help would be very appreciated.ĮDIT/TEMPORARY FIX : Issue caused by the update-restart function that breaks the lock file that is used to tell the monitor function that the server is started and that it can process to monitoring (so if you stop the server, monitor doesn't automatically relaunches it). So what ? Does the script auto-closes now ? Monitoring gmod-server: No lock file found: Monitor disabled Now, after a server crash : the automatic monitor still doesn't work, and the manual one says that. The automatic monitor didn't work at all with the previous version, but the manual one worked all the time. Thanks for the console being smooth now (first thing i noticed). I had an old version of the script, and updated it recently.