Arch (32bit/64bit): x86_64
Install method : Manual, monitor (remote) only.
Database being used (sqlite, mysql): MySQL
If manual install; web server used: Remote on an IIS Server
Steps to reproduce issue:
- Boot VPS
- Press the 'Start' button on a CS:GO Server
Any troubleshooting steps you've tried.:
- Checked permissions of all files, tried killing ugccmon processes in htop, but to no avail, manual kills of spawned CS:GO server processes
Relevant log entries and/or event viewer messages.:
Code: Select all
11/12/2015 00:38:58 UGCCMon shutting down. It may take a few minutes for the monitor to finalize and shutdown.
11/12/2015 00:45:03 UGCCMon Started (1.791) | Dbtype=mysql | Interval=60000ms
11/12/2015 00:45:03 OS: Linux
11/12/2015 00:45:04 Using config file: ugccmon.cfg
11/12/2015 00:45:04 Running as user: root
11/12/2015 00:45:06 Remote mode enabled. ID=2, Port=64842
11/12/2015 00:45:06 Starting CPU/Memory Monitor thread
11/12/2015 00:45:06 Starting process crash monitor/advanced monitoring thread, firstbootpause: 30
11/12/2015 00:45:06 Starting auto updater thread
11/12/2015 00:45:06 Starting timed restarts thread
11/12/2015 00:45:06 Starting FTP Server on port 3338. Using PASV data ports: 2000-65535
11/12/2015 00:45:06 -+-+-| Monitor Initialized |-+-+-
11/12/2015 00:45:07 Server has crashed three times in a short period of time, setting nostart to prevent crash/restart looping on server 15
11/12/2015 00:45:07 Home path: /home/ugcc
11/12/2015 00:45:10 CPU monitoring is disabled on linux, we will continue to monitor memory usage.
11/12/2015 00:45:10 No servers have resource monitoring enabled, shutting down resource monitoring thread.
11/12/2015 00:47:07 Remote Start Request Received for id: 15 SUCCESS
11/12/2015 00:47:07 Server id 15 is not running--restarting.
11/12/2015 00:47:07 Attempting to start id: 15...SUCCESS
11/12/2015 00:48:16 Error sending crash report
421 Downstream server error
11/12/2015 00:49:17 Server has crashed three times in a short period of time, setting nostart to prevent crash/restart looping on server 15
11/12/2015 00:49:51 Remote Start Request Received for id: 15 SUCCESS
11/12/2015 00:50:17 Server id 15 is not running--restarting.
11/12/2015 00:50:17 Attempting to start id: 15...SUCCESS
11/12/2015 00:51:22 Error sending crash report
421 Downstream server error
11/12/2015 00:52:23 Server has crashed three times in a short period of time, setting nostart to prevent crash/restart looping on server 15
Working Directory - /home/dgclan/servers/CSGO/CSGO-A
Server Executable - /home/dgclan/servers/CSGO/CSGO-A/srcds_run
Command Line Arguments - -usercon +game_type 0 +game_mode 0 -maxplayers 10 +map de_dust2 +rcon_password "testing" -condebug
Hidden Command Line Arguments - -console -game csgo +ip 23.88.103.141 -port 27015
Kill Child Processes - On
Dependencies Follow Server - On
Dependencies Wait Time - 30
Query address - 23.88.103.141
Display address - 23.88.103.141
Game server port - 27015
Query Port - 0
Secondary query port - 0
RCON Port - 0
Restart on Crash and at System Startup - On
Alert users on crash - On
Enable advanced monitoring - On
Prevent Crash Loops - On
Enable maximum player monitoring - 0
Server startup time - 5
The server does NOT show that it is started on the main screen, and no query information is displayed. Running the command with the parameters by hand via ssh from the ugcc user account works without a problem. Remote monitor connection tests are completed successfully. Thoughts/help? I'm not sure if this is something right under my nose or not. Think/thought that I crossed all of the obvious stuff off the checklist, so to speak. Multiple IPs on the server. Monitor is run off of the main server IP address, while the game server is off of the first Virtual NIC. CS:GO processes spawn out of control with no wait (3 seconds, maybe 5-10 seconds per? If that?) while the ugccmon processes seem to be fixed, but unkillable (using SIGTERM in htop F9, along with multiple 'service ugccmon stop' commands, which apparantly do nothing). This is on Ubuntu 14.04 on a Xen VPS. Processes all spawn as root, but neither the root account nor sudo can kill them.
