Sounds like the process that cron is invoking died with exit 1. That
means it crashed.
But, this still does not really mean anything useful.
Is this a single-core system, or multi-CPUs?
What I would suggest is that you open up two or three extra ssh sessions
over to your host, raise the priority or even real-time to ssh and the
shell to prevent them getting hung up when whatever bad thing happens
happens. Then, you can figure out what is using up all of your system
resources.
This isn't really a srcds thing anymore. Srcds should not be able to
take your whole system down unless you were doing something really bad.
Maybe you've got a nice resource fork going on and you don't know it.
Try removing the redirect to /dev/null on that script. If the mailer is
setup right, you should get an email with the output. That might help
you understand what is going on too.
You might set up a process that records system stats to a file every one
second and just let it run in the background while you try and get your
system to fail again. It might show something helpful after you reboot.
Mike Johansen wrote:
Dec 11 05:15:01 server56258 /USR/SBIN/CRON[3083]: (srcds) CMD (cd
/home/srcds&& ./start1.sh update>/dev/null 2>&1)
Dec 11 05:15:09 server56258 /USR/SBIN/CRON[3071]: (CRON) error (grandchild
#3081 failed with exit status 1)
--
# Jesse Molina
# Mail = [email protected]
# Page = [email protected]
# Cell = 1.602.323.7608
# Web = http://www.opendreams.net/jesse/
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
