csgoserver: Path Errors

[DreamDemon]

On following your cron jobs, they fire off but do not work. The problem is within the path variable.

cgaclan@ubuntu14lts-node0:/srv/steam$ /srv/steam/csgoserver start
[ .... ] Starting csgo-server: --CGA--War3 CS:GO Test Server/srv/steam/csgoserver: line 616: /rv/steam/csgoserver.lock: No such file or directory
[ OK ] Starting csgo-server: --CGA--War3 CS:GO Test Server

As you can see, the pathing gets chopped. The lockfile also doesn't get created if using the command from cron.

[DreamDemon]

As an additional note, this behavior can be seen both on Ubuntu x86_64 & CentOS 7.x x86_64.
For specifics on CentOS, I followed the directions to the letter.
http://danielgibbs.co.uk/scripts/csgoserver/#Automation

Direct Example:
[csgoserver@192-168-0-146 ~]$ /home/csgoserver/csgoserver monitor
[ INFO ] Monitoring csgo-server: No lock file found: Monitor disabled
[csgoserver@192-168-0-146 ~]$ ./csgoserver monitor
[ OK ] Monitoring csgo-server: Checking session: OK
[ OK ] Monitoring csgo-server: Querying port: 192.168.0.146:27015: OK
[csgoserver@192-168-0-146 ~]$

[dgibbs64]

Seems really odd. All the script foes is create a file when you run ./csgoserver start and remove it when you run ./csgoserver stop. If this file is not present monitor will not run. Its really basic. My guess is that for some reason the lockfile is not being created when the server is started.

[DreamDemon]

The lockfile gets created when run within the directory ( ./csgoserver) but when you do a full path it doesn't ( /srv/steam/csgserver). I suspect it has something to do with the way the variable is set for the directory information.

[dgibbs64]

Thanks for the info. I will check this out

[dgibbs64]

I have a fix for this issue and will be in the next release. Thanks for reporting this :D

[DreamDemon]

I have additional information that may help you. After your close of this I still saw the pathing problem where it wouldnt work with cron ( ubuntu 14 x86_64). I got a request from an admin to install another server which I did under CentOS 6 x86_64. Under CentOS, it works fine under cron.

[lock]

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.