Shagz
New Member
Hmmmm...ok, so the server *didn't* come back up after it crashed?
K, checked the log, and Plankeye's cron job *did* attempt to bring the server back up, however it crashed *bad* when it did...
And it's still crashing it seems. The cron job attempts to start the server and then it freaks out, posting the above crash to the log.
But if I delete the log file and the *.pid (making sure to do a ps -ef to see if ut's not already running), and start the thing by hand, it goes up just fine. If I kill the server and let the cron job take over, it crashes every time.
Plank, can you e-mail me the contents of your cron job? There might be something wrong in the way it's starting up the server.
PS - Plank, you haven't patched the server up with the last few patches, have you?
K, checked the log, and Plankeye's cron job *did* attempt to bring the server back up, however it crashed *bad* when it did...
[b said:Quote[/b] ]Mutators UT2Vote43.UT2Vote,UAdminModV095b.UAdminMod
<------------------------ Starting UT2Vote43 ------------------------>
----------------------------------------
UAdminMod loading...
Opening user log ../UserLogs/UAdminMod.log
Signal: SIGSEGV [segmentation fault]
Aborting.
Crash information will be saved to your logfile.
Developer Backtrace:
[ 1] /usr/ut2004/System/ucc-bin [0x84a5171]
[ 2] /lib/tls/libpthread.so.0 [0x400368f8]
[ 3] /usr/ut2004/System/ucc-bin [0x844c864]
[ 4] /usr/ut2004/System/ucc-bin [0x842f224]
etc...
And it's still crashing it seems. The cron job attempts to start the server and then it freaks out, posting the above crash to the log.
But if I delete the log file and the *.pid (making sure to do a ps -ef to see if ut's not already running), and start the thing by hand, it goes up just fine. If I kill the server and let the cron job take over, it crashes every time.
Plank, can you e-mail me the contents of your cron job? There might be something wrong in the way it's starting up the server.

PS - Plank, you haven't patched the server up with the last few patches, have you?