starred/LinuxGSM

Fork 0

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

[GH-ISSUE #171] Server Monitor #136

New issue

Closed

opened 2026-02-27 01:59:44 +03:00 by kerem · 10 comments

kerem commented

2026-02-27 01:59:44 +03:00

Owner

Originally created by @uGamers on GitHub (Sep 16, 2014).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/171

I set up monitor crontab.
I run the server with this command ./csserver restart
I even tried ./csserver start <Still nothing<

I get this error [K[[0;36m INFO [0;39m] Monitoring DMM: No lock file found: Monitor disabled
To enable monitor run /home/cs16/counterstrikeservers/DMM/csserver start

I have a lock file next to the csserver that it makes when the server is started.

The info in the csserver is as followed.

Directories

rootdir="$(cd "$(dirname "${BASH_SOURCE[0]}" )" && pwd )"
selfname="$0"
lockselfname=$(echo ".${servicename}.lock")
filesdir="${rootdir}/serverfiles"
systemdir="${filesdir}/cstrike"
executabledir="${filesdir}"
executable="./hlds_run"
servercfgdir="${systemdir}"
servercfg="server.cfg"
servercfgfullpath="${servercfgdir}/${servercfg}"
defaultcfg="${servercfgdir}/server.cfg"
backupdir="backups"
steamclient="${rootdir}/steamcmd/linux32/steamclient.so"

Is there something im doing wrong or is this a bug?

Thanks Mark

Originally created by @uGamers on GitHub (Sep 16, 2014). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/171 I set up monitor crontab. I run the server with this command ./csserver restart I even tried ./csserver start <Still nothing< I get this error [K[[0;36m INFO [0;39m] Monitoring DMM: No lock file found: Monitor disabled To enable monitor run /home/cs16/counterstrikeservers/DMM/csserver start I have a lock file next to the csserver that it makes when the server is started. The info in the csserver is as followed. # Directories rootdir="$(cd "$(dirname "${BASH_SOURCE[0]}" )" && pwd )" selfname="$0" lockselfname=$(echo ".${servicename}.lock") filesdir="${rootdir}/serverfiles" systemdir="${filesdir}/cstrike" executabledir="${filesdir}" executable="./hlds_run" servercfgdir="${systemdir}" servercfg="server.cfg" servercfgfullpath="${servercfgdir}/${servercfg}" defaultcfg="${servercfgdir}/server.cfg" backupdir="backups" steamclient="${rootdir}/steamcmd/linux32/steamclient.so" Is there something im doing wrong or is this a bug? Thanks Mark

kerem closed this issue

2026-02-27 01:59:44 +03:00

kerem commented

2026-02-27 01:59:44 +03:00

Author

Owner

@Scarsz commented on GitHub (Sep 16, 2014):

Be sure your user has write access to that folder as a check

@Scarsz commented on GitHub (Sep 16, 2014): Be sure your user has write access to that folder as a check

kerem commented

2026-02-27 01:59:45 +03:00

Author

Owner

@uGamers commented on GitHub (Sep 16, 2014):

Yes they do.

@uGamers commented on GitHub (Sep 16, 2014): Yes they do.

kerem commented

2026-02-27 01:59:45 +03:00

Author

Owner

@Scarsz commented on GitHub (Sep 17, 2014):

Mind doing a new install (or just a different directory) and pasting in the install log?

@Scarsz commented on GitHub (Sep 17, 2014): Mind doing a new install (or just a different directory) and pasting in the install log?

kerem commented

2026-02-27 01:59:45 +03:00

Author

Owner

@uGamers commented on GitHub (Sep 17, 2014):

Where will the install log be?

@uGamers commented on GitHub (Sep 17, 2014): Where will the install log be?

kerem commented

2026-02-27 01:59:45 +03:00

Author

Owner

@Scarsz commented on GitHub (Sep 17, 2014):

./csserver install | tee install.log

@Scarsz commented on GitHub (Sep 17, 2014): `./csserver install | tee install.log`

kerem commented

2026-02-27 01:59:45 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Sep 17, 2014):

something is stopping the lock file being created for some reason. I think we might need to add something on server start to check the lock file does exist and if not create a warning. Might be able to even identify some reasons why its not working e.g permissions etc.

@dgibbs64 commented on GitHub (Sep 17, 2014): something is stopping the lock file being created for some reason. I think we might need to add something on server start to check the lock file does exist and if not create a warning. Might be able to even identify some reasons why its not working e.g permissions etc.

kerem commented

2026-02-27 01:59:45 +03:00

Author

Owner

@uGamers commented on GitHub (Sep 17, 2014):

The lock file is being created but when i crash the server on purpose it does not run the the crontab job i have set.

crontab -e
*/5 * * * * /home/cs16/counterstrikeservers/random/csserver monitor > /dev/null 2>&1

Also your
fn_parms(){
parms="-game cstrike -strictportbind -ip ${ip} -port ${port} +clientport ${clientport} +map ${defaultmap} -maxplayers ${maxplayers}"
}

should be?
fn_parms(){
parms="-game cstrike -strictportbind +ip ${ip} -port ${port} +clientport ${clientport} +map ${defaultmap} -maxplayers ${maxplayers}"
}

not -ip but +ip?

The first part of csserver exec

steamuser="anonymous"
steampass=""

Start Variables

defaultmap="de_dust2"
maxplayers="32"
port="27030"
clientport="27005"
ip="192.223.26.228"

https://developer.valvesoftware.com/wiki/Command_Line_Options#Command-line_parameters_2

fn_parms(){
parms="-game cstrike -strictportbind +ip ${ip} -port ${port} +clientport ${clientport} +map ${defaultmap} -maxplayers ${maxplayers}"
}

Advanced Variables

Steam

appid="90"

Server Details

servicename="random"
gamename="Counter Strike 1.6"
engine="goldsource"

Directories

rootdir="$(cd "$(dirname "${BASH_SOURCE[0]}" )" && pwd )"
selfname="$0"
lockselfname=$(echo ".${servicename}.lock")
filesdir="${rootdir}/serverfiles"
systemdir="${filesdir}/cstrike"
executabledir="${filesdir}"
executable="./hlds_run"
servercfgdir="${systemdir}"
servercfg="${servicename}.cfg"
servercfgfullpath="${servercfgdir}/${servercfg}"
defaultcfg="${servercfgdir}/server.cfg"
backupdir="backups"
steamclient="${rootdir}/steamcmd/linux32/steamclient.so"

Server Details

servername=$(grep -s hostname "${servercfgfullpath}"|sed 's/hostname //g'|sed 's/"//g')
rcon=$(grep -s rcon_password "${servercfgfullpath}"|sed 's/rcon_password //g'|sed 's/"//g')

Logging

logdays="7"
gamelogdir="${systemdir}/logs"
scriptlogdir="${rootdir}/log/script"
consolelogdir="${rootdir}/log/console"

scriptlog="${scriptlogdir}/${servicename}-script.log"
consolelog="${consolelogdir}/${servicename}-console.log"
emaillog="${scriptlogdir}/${servicename}-email.log"

scriptlogdate="${scriptlogdir}/${servicename}-script-$(date '+%d-%m-%Y-%H-%M-%S').log"
consolelogdate="${consolelogdir}/${servicename}-console-$(date '+%d-%m-%Y-%H-%M-%S').log"

@uGamers commented on GitHub (Sep 17, 2014): The lock file is being created but when i crash the server on purpose it does not run the the crontab job i have set. crontab -e */5 \* \* \* \* /home/cs16/counterstrikeservers/random/csserver monitor > /dev/null 2>&1 Also your fn_parms(){ parms="-game cstrike -strictportbind -ip ${ip} -port ${port} +clientport ${clientport} +map ${defaultmap} -maxplayers ${maxplayers}" } should be? fn_parms(){ parms="-game cstrike -strictportbind +ip ${ip} -port ${port} +clientport ${clientport} +map ${defaultmap} -maxplayers ${maxplayers}" } not -ip but +ip? The first part of csserver exec # Steam login steamuser="anonymous" steampass="" # Start Variables defaultmap="de_dust2" maxplayers="32" port="27030" clientport="27005" ip="192.223.26.228" # https://developer.valvesoftware.com/wiki/Command_Line_Options#Command-line_parameters_2 fn_parms(){ parms="-game cstrike -strictportbind +ip ${ip} -port ${port} +clientport ${clientport} +map ${defaultmap} -maxplayers ${maxplayers}" } #### Advanced Variables # Steam appid="90" # Server Details servicename="random" gamename="Counter Strike 1.6" engine="goldsource" # Directories rootdir="$(cd "$(dirname "${BASH_SOURCE[0]}" )" && pwd )" selfname="$0" lockselfname=$(echo ".${servicename}.lock") filesdir="${rootdir}/serverfiles" systemdir="${filesdir}/cstrike" executabledir="${filesdir}" executable="./hlds_run" servercfgdir="${systemdir}" servercfg="${servicename}.cfg" servercfgfullpath="${servercfgdir}/${servercfg}" defaultcfg="${servercfgdir}/server.cfg" backupdir="backups" steamclient="${rootdir}/steamcmd/linux32/steamclient.so" # Server Details servername=$(grep -s hostname "${servercfgfullpath}"|sed 's/hostname //g'|sed 's/"//g') rcon=$(grep -s rcon_password "${servercfgfullpath}"|sed 's/rcon_password //g'|sed 's/"//g') # Logging logdays="7" gamelogdir="${systemdir}/logs" scriptlogdir="${rootdir}/log/script" consolelogdir="${rootdir}/log/console" scriptlog="${scriptlogdir}/${servicename}-script.log" consolelog="${consolelogdir}/${servicename}-console.log" emaillog="${scriptlogdir}/${servicename}-email.log" scriptlogdate="${scriptlogdir}/${servicename}-script-$(date '+%d-%m-%Y-%H-%M-%S').log" consolelogdate="${consolelogdir}/${servicename}-console-$(date '+%d-%m-%Y-%H-%M-%S').log"

kerem commented

2026-02-27 01:59:45 +03:00

Author

Owner

@uGamers commented on GitHub (Sep 18, 2014):

My Guess is that Monitor is broke via crontab or just dont work at all idk ive tried everything i could think of for 3 days still nothing.

@uGamers commented on GitHub (Sep 18, 2014): My Guess is that Monitor is broke via crontab or just dont work at all idk ive tried everything i could think of for 3 days still nothing.

kerem commented

2026-02-27 01:59:45 +03:00

Author

Owner

@UltimateByte commented on GitHub (Sep 18, 2014):

Did you try a machine reboot after setting the crontab ?
Also, check your server logfiles to see if the crontab actyally sends a monitor command to the script. It's located in your root script folder into log/script. You should see monitor occurrences.

@UltimateByte commented on GitHub (Sep 18, 2014): Did you try a machine reboot after setting the crontab ? Also, check your server logfiles to see if the crontab actyally sends a monitor command to the script. It's located in your root script folder into log/script. You should see monitor occurrences.

kerem commented

2026-02-27 01:59:45 +03:00

Author

Owner

@lock[bot] commented on GitHub (Jul 20, 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 20, 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.