Re: [hlds_linux] Crashing L4D2 fork killing entire machine
Just had this happen again with all tf2 servers, after forcing a hard-reset i went through the logs and found that every srcds_i486 process had seg faulted throwing tons of: kernel: srcds_i486[18318]: segfault at e99b02b8 ip f6e9adbb sp ffd10ad0 error 4 in materialsystem_i486.so[f6e05000+171000] kernel: srcds_i486[20803] general protection ip:10528178 sp:fff9352c error:0 kernel: srcds_i486[593]: segfault at fc9f04a8 ip f6eebdbb sp ffd61b30 error 4 in materialsystem_i486.so[f6e56000+171000] kernel: srcds_i486[2654] trap invalid opcode ip:e6e8640 sp:ffed145c error:0 Is the solution is to create some kind of script to check for runaway processes and kill them? On Tue, Dec 22, 2009 at 1:46 AM, Andrew Armstrong and...@mammoth.com.auwrote: Not sure if this is the cause, but I was just in a game and someone decided to exploit something on the Concert map finale. He managed to spawn stacks of grenade launchers. Everyone's ping then started to go up and everyone began to warp around, I just left the game. I'd suspect he would have sent that server to high CPU usage since everything began to lag and degrade. May or may not be the reason for what you're seeing. - Andrew -Original Message- From: hlds_linux-boun...@list.valvesoftware.com [mailto:hlds_linux-boun...@list.valvesoftware.com] On Behalf Of Joshua Smith Sent: Tuesday, 22 December 2009 4:17 AM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] Crashing L4D2 fork killing entire machine Just wondering if anyone has tracked down a possible cause for this yet? Is it related to setting sched_fifo? whenever this happens there seems to be no logs and being locked out of ssh ive never seen what is actually happening. On Sat, Dec 12, 2009 at 12:10 PM, Vaughan Reid vau...@gmail.com wrote: SIGINT and SIGKILL are not commands, they are methods of killing processes used by programmers. Off the top of my head a SIGKILL can be done by using this command: kill -9 pid And a SIGINT is just a normal kill: kill pid Best to try and use the second one first as it will try to gracefully close the process. If that doesn't work try the first. pid is obviously the process id of the game server you are trying to get rid off. On Sun, Dec 13, 2009 at 6:38 AM, Saint K. sai...@specialattack.net wrote: I just had another forked server goin mental on me. I tried the SIGKILL and SIGINT commands but they don't work (command not found). Where am I suppose to execute these commands? Cheers, -Original Message- From: hlds_linux-boun...@list.valvesoftware.com [mailto: hlds_linux-boun...@list.valvesoftware.com] On Behalf Of Milton Ngan Sent: Monday, November 30, 2009 12:39 AM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] Crashing L4D2 fork killing entire machine If you guys are running the servers with -debug (which doesn't currently do anything useful in -fork mode) or crash dumps enabled you should send a SIGABRT (-6) to the process to get it to dump a core file. It will also kill the fork as well. SIGKILL should be used as a last resort if SIGINT (standard kill) doesn't do anything. With regards to -debug and -fork, I have a Perl script that I run alongside srcds_run to achieve desired behavior. I need to re-write this to be more portable so that it can be shipped. -Original Message- From: hlds_linux-boun...@list.valvesoftware.com [mailto: hlds_linux-boun...@list.valvesoftware.com] On Behalf Of riemers Sent: Saturday, November 28, 2009 11:49 AM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] Crashing L4D2 fork killing entire machine I've seen a process with 100% too, i've also seen a server which was full for like 2 hours on the same map. At that point i check it out, and it seemed the 4 survivor bots where playing against the infected bots, over and over again. Somehow still pretty funny.. On Sat, 28 Nov 2009 20:13:44 +0100, Saint K. sai...@specialattack.net wrote: I have had this issue twice up till now, and it's rather disturbing. What happened is that a L4D2 fork gets in a crashing mode of some kind where it continuously puts 100% CPU load on a single core. I've seen these sort of crashes perhaps around 10 times so far. 8 times I've spotted it soon enough to kill -9 pid the process, and 2 times I've been too late and it been in such a state for several hours before it will entirely kill off the machine. The machine will only reply to icmp and nothing else (ssh, http, ftp, gameservers etc). This worries me a bit, because I do not have any reason to assume something is broken on OS or hardware level. Regards, Saint K. ___ To unsubscribe, edit your list preferences
Re: [hlds_linux] Crashing L4D2 fork killing entire machine
Not sure if this is the cause, but I was just in a game and someone decided to exploit something on the Concert map finale. He managed to spawn stacks of grenade launchers. Everyone's ping then started to go up and everyone began to warp around, I just left the game. I'd suspect he would have sent that server to high CPU usage since everything began to lag and degrade. May or may not be the reason for what you're seeing. - Andrew -Original Message- From: hlds_linux-boun...@list.valvesoftware.com [mailto:hlds_linux-boun...@list.valvesoftware.com] On Behalf Of Joshua Smith Sent: Tuesday, 22 December 2009 4:17 AM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] Crashing L4D2 fork killing entire machine Just wondering if anyone has tracked down a possible cause for this yet? Is it related to setting sched_fifo? whenever this happens there seems to be no logs and being locked out of ssh ive never seen what is actually happening. On Sat, Dec 12, 2009 at 12:10 PM, Vaughan Reid vau...@gmail.com wrote: SIGINT and SIGKILL are not commands, they are methods of killing processes used by programmers. Off the top of my head a SIGKILL can be done by using this command: kill -9 pid And a SIGINT is just a normal kill: kill pid Best to try and use the second one first as it will try to gracefully close the process. If that doesn't work try the first. pid is obviously the process id of the game server you are trying to get rid off. On Sun, Dec 13, 2009 at 6:38 AM, Saint K. sai...@specialattack.net wrote: I just had another forked server goin mental on me. I tried the SIGKILL and SIGINT commands but they don't work (command not found). Where am I suppose to execute these commands? Cheers, -Original Message- From: hlds_linux-boun...@list.valvesoftware.com [mailto: hlds_linux-boun...@list.valvesoftware.com] On Behalf Of Milton Ngan Sent: Monday, November 30, 2009 12:39 AM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] Crashing L4D2 fork killing entire machine If you guys are running the servers with -debug (which doesn't currently do anything useful in -fork mode) or crash dumps enabled you should send a SIGABRT (-6) to the process to get it to dump a core file. It will also kill the fork as well. SIGKILL should be used as a last resort if SIGINT (standard kill) doesn't do anything. With regards to -debug and -fork, I have a Perl script that I run alongside srcds_run to achieve desired behavior. I need to re-write this to be more portable so that it can be shipped. -Original Message- From: hlds_linux-boun...@list.valvesoftware.com [mailto: hlds_linux-boun...@list.valvesoftware.com] On Behalf Of riemers Sent: Saturday, November 28, 2009 11:49 AM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] Crashing L4D2 fork killing entire machine I've seen a process with 100% too, i've also seen a server which was full for like 2 hours on the same map. At that point i check it out, and it seemed the 4 survivor bots where playing against the infected bots, over and over again. Somehow still pretty funny.. On Sat, 28 Nov 2009 20:13:44 +0100, Saint K. sai...@specialattack.net wrote: I have had this issue twice up till now, and it's rather disturbing. What happened is that a L4D2 fork gets in a crashing mode of some kind where it continuously puts 100% CPU load on a single core. I've seen these sort of crashes perhaps around 10 times so far. 8 times I've spotted it soon enough to kill -9 pid the process, and 2 times I've been too late and it been in such a state for several hours before it will entirely kill off the machine. The machine will only reply to icmp and nothing else (ssh, http, ftp, gameservers etc). This worries me a bit, because I do not have any reason to assume something is broken on OS or hardware level. Regards, Saint K. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux No virus found in this incoming message. Checked by AVG - www.avg.com Version: 9.0.709 / Virus Database: 270.14.87/2534 - Release Date: 11/29/09 20:31:00 ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo
Re: [hlds_linux] Crashing L4D2 fork killing entire machine
Just wondering if anyone has tracked down a possible cause for this yet? Is it related to setting sched_fifo? whenever this happens there seems to be no logs and being locked out of ssh ive never seen what is actually happening. On Sat, Dec 12, 2009 at 12:10 PM, Vaughan Reid vau...@gmail.com wrote: SIGINT and SIGKILL are not commands, they are methods of killing processes used by programmers. Off the top of my head a SIGKILL can be done by using this command: kill -9 pid And a SIGINT is just a normal kill: kill pid Best to try and use the second one first as it will try to gracefully close the process. If that doesn't work try the first. pid is obviously the process id of the game server you are trying to get rid off. On Sun, Dec 13, 2009 at 6:38 AM, Saint K. sai...@specialattack.net wrote: I just had another forked server goin mental on me. I tried the SIGKILL and SIGINT commands but they don't work (command not found). Where am I suppose to execute these commands? Cheers, -Original Message- From: hlds_linux-boun...@list.valvesoftware.com [mailto: hlds_linux-boun...@list.valvesoftware.com] On Behalf Of Milton Ngan Sent: Monday, November 30, 2009 12:39 AM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] Crashing L4D2 fork killing entire machine If you guys are running the servers with -debug (which doesn't currently do anything useful in -fork mode) or crash dumps enabled you should send a SIGABRT (-6) to the process to get it to dump a core file. It will also kill the fork as well. SIGKILL should be used as a last resort if SIGINT (standard kill) doesn't do anything. With regards to -debug and -fork, I have a Perl script that I run alongside srcds_run to achieve desired behavior. I need to re-write this to be more portable so that it can be shipped. -Original Message- From: hlds_linux-boun...@list.valvesoftware.com [mailto: hlds_linux-boun...@list.valvesoftware.com] On Behalf Of riemers Sent: Saturday, November 28, 2009 11:49 AM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] Crashing L4D2 fork killing entire machine I've seen a process with 100% too, i've also seen a server which was full for like 2 hours on the same map. At that point i check it out, and it seemed the 4 survivor bots where playing against the infected bots, over and over again. Somehow still pretty funny.. On Sat, 28 Nov 2009 20:13:44 +0100, Saint K. sai...@specialattack.net wrote: I have had this issue twice up till now, and it's rather disturbing. What happened is that a L4D2 fork gets in a crashing mode of some kind where it continuously puts 100% CPU load on a single core. I've seen these sort of crashes perhaps around 10 times so far. 8 times I've spotted it soon enough to kill -9 pid the process, and 2 times I've been too late and it been in such a state for several hours before it will entirely kill off the machine. The machine will only reply to icmp and nothing else (ssh, http, ftp, gameservers etc). This worries me a bit, because I do not have any reason to assume something is broken on OS or hardware level. Regards, Saint K. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux No virus found in this incoming message. Checked by AVG - www.avg.com Version: 9.0.709 / Virus Database: 270.14.87/2534 - Release Date: 11/29/09 20:31:00 ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Crashing L4D2 fork killing entire machine
We've wrote a script now to check for faulty L4D2 processes. Once one is detected it will send a kill -6. According to Milton this should produce a coredump, alltho I haven't been able to find one yet in my L4D2 dir, and the logging shows at least 2 instances where it occurred. So far we're still in the blind. Saint K. -Original Message- From: hlds_linux-boun...@list.valvesoftware.com [mailto:hlds_linux-boun...@list.valvesoftware.com] On Behalf Of Joshua Smith Sent: Monday, December 21, 2009 6:17 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] Crashing L4D2 fork killing entire machine Just wondering if anyone has tracked down a possible cause for this yet? Is it related to setting sched_fifo? whenever this happens there seems to be no logs and being locked out of ssh ive never seen what is actually happening. On Sat, Dec 12, 2009 at 12:10 PM, Vaughan Reid vau...@gmail.com wrote: SIGINT and SIGKILL are not commands, they are methods of killing processes used by programmers. Off the top of my head a SIGKILL can be done by using this command: kill -9 pid And a SIGINT is just a normal kill: kill pid Best to try and use the second one first as it will try to gracefully close the process. If that doesn't work try the first. pid is obviously the process id of the game server you are trying to get rid off. On Sun, Dec 13, 2009 at 6:38 AM, Saint K. sai...@specialattack.net wrote: I just had another forked server goin mental on me. I tried the SIGKILL and SIGINT commands but they don't work (command not found). Where am I suppose to execute these commands? Cheers, -Original Message- From: hlds_linux-boun...@list.valvesoftware.com [mailto: hlds_linux-boun...@list.valvesoftware.com] On Behalf Of Milton Ngan Sent: Monday, November 30, 2009 12:39 AM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] Crashing L4D2 fork killing entire machine If you guys are running the servers with -debug (which doesn't currently do anything useful in -fork mode) or crash dumps enabled you should send a SIGABRT (-6) to the process to get it to dump a core file. It will also kill the fork as well. SIGKILL should be used as a last resort if SIGINT (standard kill) doesn't do anything. With regards to -debug and -fork, I have a Perl script that I run alongside srcds_run to achieve desired behavior. I need to re-write this to be more portable so that it can be shipped. -Original Message- From: hlds_linux-boun...@list.valvesoftware.com [mailto: hlds_linux-boun...@list.valvesoftware.com] On Behalf Of riemers Sent: Saturday, November 28, 2009 11:49 AM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] Crashing L4D2 fork killing entire machine I've seen a process with 100% too, i've also seen a server which was full for like 2 hours on the same map. At that point i check it out, and it seemed the 4 survivor bots where playing against the infected bots, over and over again. Somehow still pretty funny.. On Sat, 28 Nov 2009 20:13:44 +0100, Saint K. sai...@specialattack.net wrote: I have had this issue twice up till now, and it's rather disturbing. What happened is that a L4D2 fork gets in a crashing mode of some kind where it continuously puts 100% CPU load on a single core. I've seen these sort of crashes perhaps around 10 times so far. 8 times I've spotted it soon enough to kill -9 pid the process, and 2 times I've been too late and it been in such a state for several hours before it will entirely kill off the machine. The machine will only reply to icmp and nothing else (ssh, http, ftp, gameservers etc). This worries me a bit, because I do not have any reason to assume something is broken on OS or hardware level. Regards, Saint K. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux No virus found in this incoming message. Checked by AVG - www.avg.com Version: 9.0.709 / Virus Database: 270.14.87/2534 - Release Date: 11/29/09 20:31:00 ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences
Re: [hlds_linux] Crashing L4D2 fork killing entire machine
This is about as frustrating as not having multi-threaded TF2 servers! On Mon, 2009-12-21 at 19:59 +0100, Saint K. wrote: We've wrote a script now to check for faulty L4D2 processes. Once one is detected it will send a kill -6. According to Milton this should produce a coredump, alltho I haven't been able to find one yet in my L4D2 dir, and the logging shows at least 2 instances where it occurred. So far we're still in the blind. Saint K. -Original Message- From: hlds_linux-boun...@list.valvesoftware.com [mailto:hlds_linux-boun...@list.valvesoftware.com] On Behalf Of Joshua Smith Sent: Monday, December 21, 2009 6:17 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] Crashing L4D2 fork killing entire machine Just wondering if anyone has tracked down a possible cause for this yet? Is it related to setting sched_fifo? whenever this happens there seems to be no logs and being locked out of ssh ive never seen what is actually happening. On Sat, Dec 12, 2009 at 12:10 PM, Vaughan Reid vau...@gmail.com wrote: SIGINT and SIGKILL are not commands, they are methods of killing processes used by programmers. Off the top of my head a SIGKILL can be done by using this command: kill -9 pid And a SIGINT is just a normal kill: kill pid Best to try and use the second one first as it will try to gracefully close the process. If that doesn't work try the first. pid is obviously the process id of the game server you are trying to get rid off. On Sun, Dec 13, 2009 at 6:38 AM, Saint K. sai...@specialattack.net wrote: I just had another forked server goin mental on me. I tried the SIGKILL and SIGINT commands but they don't work (command not found). Where am I suppose to execute these commands? Cheers, -Original Message- From: hlds_linux-boun...@list.valvesoftware.com [mailto: hlds_linux-boun...@list.valvesoftware.com] On Behalf Of Milton Ngan Sent: Monday, November 30, 2009 12:39 AM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] Crashing L4D2 fork killing entire machine If you guys are running the servers with -debug (which doesn't currently do anything useful in -fork mode) or crash dumps enabled you should send a SIGABRT (-6) to the process to get it to dump a core file. It will also kill the fork as well. SIGKILL should be used as a last resort if SIGINT (standard kill) doesn't do anything. With regards to -debug and -fork, I have a Perl script that I run alongside srcds_run to achieve desired behavior. I need to re-write this to be more portable so that it can be shipped. -Original Message- From: hlds_linux-boun...@list.valvesoftware.com [mailto: hlds_linux-boun...@list.valvesoftware.com] On Behalf Of riemers Sent: Saturday, November 28, 2009 11:49 AM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] Crashing L4D2 fork killing entire machine I've seen a process with 100% too, i've also seen a server which was full for like 2 hours on the same map. At that point i check it out, and it seemed the 4 survivor bots where playing against the infected bots, over and over again. Somehow still pretty funny.. On Sat, 28 Nov 2009 20:13:44 +0100, Saint K. sai...@specialattack.net wrote: I have had this issue twice up till now, and it's rather disturbing. What happened is that a L4D2 fork gets in a crashing mode of some kind where it continuously puts 100% CPU load on a single core. I've seen these sort of crashes perhaps around 10 times so far. 8 times I've spotted it soon enough to kill -9 pid the process, and 2 times I've been too late and it been in such a state for several hours before it will entirely kill off the machine. The machine will only reply to icmp and nothing else (ssh, http, ftp, gameservers etc). This worries me a bit, because I do not have any reason to assume something is broken on OS or hardware level. Regards, Saint K. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux No virus found in this incoming message. Checked by AVG - www.avg.com Version: 9.0.709 / Virus Database: 270.14.87/2534 - Release Date: 11/29/09 20:31:00
Re: [hlds_linux] Crashing L4D2 fork killing entire machine
Dear Mr. f0rkz, Please don't hijack treads. Create your own. It's so easy. -Original Message- From: hlds_linux-boun...@list.valvesoftware.com [mailto:hlds_linux-boun...@list.valvesoftware.com] On Behalf Of f0rkz Sent: Monday, December 21, 2009 8:05 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] Crashing L4D2 fork killing entire machine This is about as frustrating as not having multi-threaded TF2 servers! On Mon, 2009-12-21 at 19:59 +0100, Saint K. wrote: We've wrote a script now to check for faulty L4D2 processes. Once one is detected it will send a kill -6. According to Milton this should produce a coredump, alltho I haven't been able to find one yet in my L4D2 dir, and the logging shows at least 2 instances where it occurred. So far we're still in the blind. Saint K. -Original Message- From: hlds_linux-boun...@list.valvesoftware.com [mailto:hlds_linux-boun...@list.valvesoftware.com] On Behalf Of Joshua Smith Sent: Monday, December 21, 2009 6:17 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] Crashing L4D2 fork killing entire machine Just wondering if anyone has tracked down a possible cause for this yet? Is it related to setting sched_fifo? whenever this happens there seems to be no logs and being locked out of ssh ive never seen what is actually happening. On Sat, Dec 12, 2009 at 12:10 PM, Vaughan Reid vau...@gmail.com wrote: SIGINT and SIGKILL are not commands, they are methods of killing processes used by programmers. Off the top of my head a SIGKILL can be done by using this command: kill -9 pid And a SIGINT is just a normal kill: kill pid Best to try and use the second one first as it will try to gracefully close the process. If that doesn't work try the first. pid is obviously the process id of the game server you are trying to get rid off. On Sun, Dec 13, 2009 at 6:38 AM, Saint K. sai...@specialattack.net wrote: I just had another forked server goin mental on me. I tried the SIGKILL and SIGINT commands but they don't work (command not found). Where am I suppose to execute these commands? Cheers, -Original Message- From: hlds_linux-boun...@list.valvesoftware.com [mailto: hlds_linux-boun...@list.valvesoftware.com] On Behalf Of Milton Ngan Sent: Monday, November 30, 2009 12:39 AM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] Crashing L4D2 fork killing entire machine If you guys are running the servers with -debug (which doesn't currently do anything useful in -fork mode) or crash dumps enabled you should send a SIGABRT (-6) to the process to get it to dump a core file. It will also kill the fork as well. SIGKILL should be used as a last resort if SIGINT (standard kill) doesn't do anything. With regards to -debug and -fork, I have a Perl script that I run alongside srcds_run to achieve desired behavior. I need to re-write this to be more portable so that it can be shipped. -Original Message- From: hlds_linux-boun...@list.valvesoftware.com [mailto: hlds_linux-boun...@list.valvesoftware.com] On Behalf Of riemers Sent: Saturday, November 28, 2009 11:49 AM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] Crashing L4D2 fork killing entire machine I've seen a process with 100% too, i've also seen a server which was full for like 2 hours on the same map. At that point i check it out, and it seemed the 4 survivor bots where playing against the infected bots, over and over again. Somehow still pretty funny.. On Sat, 28 Nov 2009 20:13:44 +0100, Saint K. sai...@specialattack.net wrote: I have had this issue twice up till now, and it's rather disturbing. What happened is that a L4D2 fork gets in a crashing mode of some kind where it continuously puts 100% CPU load on a single core. I've seen these sort of crashes perhaps around 10 times so far. 8 times I've spotted it soon enough to kill -9 pid the process, and 2 times I've been too late and it been in such a state for several hours before it will entirely kill off the machine. The machine will only reply to icmp and nothing else (ssh, http, ftp, gameservers etc). This worries me a bit, because I do not have any reason to assume something is broken on OS or hardware level. Regards, Saint K. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Crashing L4D2 fork killing entire machine
Not really sure how this is a hijack, but ok! On Mon, 2009-12-21 at 21:01 +0100, Saint K. wrote: Dear Mr. f0rkz, Please don't hijack treads. Create your own. It's so easy. -Original Message- From: hlds_linux-boun...@list.valvesoftware.com [mailto:hlds_linux-boun...@list.valvesoftware.com] On Behalf Of f0rkz Sent: Monday, December 21, 2009 8:05 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] Crashing L4D2 fork killing entire machine This is about as frustrating as not having multi-threaded TF2 servers! On Mon, 2009-12-21 at 19:59 +0100, Saint K. wrote: We've wrote a script now to check for faulty L4D2 processes. Once one is detected it will send a kill -6. According to Milton this should produce a coredump, alltho I haven't been able to find one yet in my L4D2 dir, and the logging shows at least 2 instances where it occurred. So far we're still in the blind. Saint K. -Original Message- From: hlds_linux-boun...@list.valvesoftware.com [mailto:hlds_linux-boun...@list.valvesoftware.com] On Behalf Of Joshua Smith Sent: Monday, December 21, 2009 6:17 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] Crashing L4D2 fork killing entire machine Just wondering if anyone has tracked down a possible cause for this yet? Is it related to setting sched_fifo? whenever this happens there seems to be no logs and being locked out of ssh ive never seen what is actually happening. On Sat, Dec 12, 2009 at 12:10 PM, Vaughan Reid vau...@gmail.com wrote: SIGINT and SIGKILL are not commands, they are methods of killing processes used by programmers. Off the top of my head a SIGKILL can be done by using this command: kill -9 pid And a SIGINT is just a normal kill: kill pid Best to try and use the second one first as it will try to gracefully close the process. If that doesn't work try the first. pid is obviously the process id of the game server you are trying to get rid off. On Sun, Dec 13, 2009 at 6:38 AM, Saint K. sai...@specialattack.net wrote: I just had another forked server goin mental on me. I tried the SIGKILL and SIGINT commands but they don't work (command not found). Where am I suppose to execute these commands? Cheers, -Original Message- From: hlds_linux-boun...@list.valvesoftware.com [mailto: hlds_linux-boun...@list.valvesoftware.com] On Behalf Of Milton Ngan Sent: Monday, November 30, 2009 12:39 AM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] Crashing L4D2 fork killing entire machine If you guys are running the servers with -debug (which doesn't currently do anything useful in -fork mode) or crash dumps enabled you should send a SIGABRT (-6) to the process to get it to dump a core file. It will also kill the fork as well. SIGKILL should be used as a last resort if SIGINT (standard kill) doesn't do anything. With regards to -debug and -fork, I have a Perl script that I run alongside srcds_run to achieve desired behavior. I need to re-write this to be more portable so that it can be shipped. -Original Message- From: hlds_linux-boun...@list.valvesoftware.com [mailto: hlds_linux-boun...@list.valvesoftware.com] On Behalf Of riemers Sent: Saturday, November 28, 2009 11:49 AM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] Crashing L4D2 fork killing entire machine I've seen a process with 100% too, i've also seen a server which was full for like 2 hours on the same map. At that point i check it out, and it seemed the 4 survivor bots where playing against the infected bots, over and over again. Somehow still pretty funny.. On Sat, 28 Nov 2009 20:13:44 +0100, Saint K. sai...@specialattack.net wrote: I have had this issue twice up till now, and it's rather disturbing. What happened is that a L4D2 fork gets in a crashing mode of some kind where it continuously puts 100% CPU load on a single core. I've seen these sort of crashes perhaps around 10 times so far. 8 times I've spotted it soon enough to kill -9 pid the process, and 2 times I've been too late and it been in such a state for several hours before it will entirely kill off the machine. The machine will only reply to icmp and nothing else (ssh, http, ftp, gameservers etc). This worries me a bit, because I do not have any reason to assume something is broken on OS or hardware level. Regards, Saint K. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Crashing L4D2 fork killing entire machine
I just had another forked server goin mental on me. I tried the SIGKILL and SIGINT commands but they don't work (command not found). Where am I suppose to execute these commands? Cheers, -Original Message- From: hlds_linux-boun...@list.valvesoftware.com [mailto:hlds_linux-boun...@list.valvesoftware.com] On Behalf Of Milton Ngan Sent: Monday, November 30, 2009 12:39 AM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] Crashing L4D2 fork killing entire machine If you guys are running the servers with -debug (which doesn't currently do anything useful in -fork mode) or crash dumps enabled you should send a SIGABRT (-6) to the process to get it to dump a core file. It will also kill the fork as well. SIGKILL should be used as a last resort if SIGINT (standard kill) doesn't do anything. With regards to -debug and -fork, I have a Perl script that I run alongside srcds_run to achieve desired behavior. I need to re-write this to be more portable so that it can be shipped. -Original Message- From: hlds_linux-boun...@list.valvesoftware.com [mailto:hlds_linux-boun...@list.valvesoftware.com] On Behalf Of riemers Sent: Saturday, November 28, 2009 11:49 AM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] Crashing L4D2 fork killing entire machine I've seen a process with 100% too, i've also seen a server which was full for like 2 hours on the same map. At that point i check it out, and it seemed the 4 survivor bots where playing against the infected bots, over and over again. Somehow still pretty funny.. On Sat, 28 Nov 2009 20:13:44 +0100, Saint K. sai...@specialattack.net wrote: I have had this issue twice up till now, and it's rather disturbing. What happened is that a L4D2 fork gets in a crashing mode of some kind where it continuously puts 100% CPU load on a single core. I've seen these sort of crashes perhaps around 10 times so far. 8 times I've spotted it soon enough to kill -9 pid the process, and 2 times I've been too late and it been in such a state for several hours before it will entirely kill off the machine. The machine will only reply to icmp and nothing else (ssh, http, ftp, gameservers etc). This worries me a bit, because I do not have any reason to assume something is broken on OS or hardware level. Regards, Saint K. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux No virus found in this incoming message. Checked by AVG - www.avg.com Version: 9.0.709 / Virus Database: 270.14.87/2534 - Release Date: 11/29/09 20:31:00 ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Crashing L4D2 fork killing entire machine
SIGINT and SIGKILL are not commands, they are methods of killing processes used by programmers. Off the top of my head a SIGKILL can be done by using this command: kill -9 pid And a SIGINT is just a normal kill: kill pid Best to try and use the second one first as it will try to gracefully close the process. If that doesn't work try the first. pid is obviously the process id of the game server you are trying to get rid off. On Sun, Dec 13, 2009 at 6:38 AM, Saint K. sai...@specialattack.net wrote: I just had another forked server goin mental on me. I tried the SIGKILL and SIGINT commands but they don't work (command not found). Where am I suppose to execute these commands? Cheers, -Original Message- From: hlds_linux-boun...@list.valvesoftware.com [mailto: hlds_linux-boun...@list.valvesoftware.com] On Behalf Of Milton Ngan Sent: Monday, November 30, 2009 12:39 AM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] Crashing L4D2 fork killing entire machine If you guys are running the servers with -debug (which doesn't currently do anything useful in -fork mode) or crash dumps enabled you should send a SIGABRT (-6) to the process to get it to dump a core file. It will also kill the fork as well. SIGKILL should be used as a last resort if SIGINT (standard kill) doesn't do anything. With regards to -debug and -fork, I have a Perl script that I run alongside srcds_run to achieve desired behavior. I need to re-write this to be more portable so that it can be shipped. -Original Message- From: hlds_linux-boun...@list.valvesoftware.com [mailto: hlds_linux-boun...@list.valvesoftware.com] On Behalf Of riemers Sent: Saturday, November 28, 2009 11:49 AM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] Crashing L4D2 fork killing entire machine I've seen a process with 100% too, i've also seen a server which was full for like 2 hours on the same map. At that point i check it out, and it seemed the 4 survivor bots where playing against the infected bots, over and over again. Somehow still pretty funny.. On Sat, 28 Nov 2009 20:13:44 +0100, Saint K. sai...@specialattack.net wrote: I have had this issue twice up till now, and it's rather disturbing. What happened is that a L4D2 fork gets in a crashing mode of some kind where it continuously puts 100% CPU load on a single core. I've seen these sort of crashes perhaps around 10 times so far. 8 times I've spotted it soon enough to kill -9 pid the process, and 2 times I've been too late and it been in such a state for several hours before it will entirely kill off the machine. The machine will only reply to icmp and nothing else (ssh, http, ftp, gameservers etc). This worries me a bit, because I do not have any reason to assume something is broken on OS or hardware level. Regards, Saint K. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux No virus found in this incoming message. Checked by AVG - www.avg.com Version: 9.0.709 / Virus Database: 270.14.87/2534 - Release Date: 11/29/09 20:31:00 ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Crashing L4D2 fork killing entire machine
Unfortunately I had a fork messing up again last night when I was asleep, with as result that the machine requires a reboot this morning because its not accessible. Does anyone by any chance have a way to check the L4D2 processes for any process being stuck in 100% load, and send the kill signal to the process as suggested by VALVe to create the crashdump file? Cheers, -Original Message- From: hlds_linux-boun...@list.valvesoftware.com [mailto:hlds_linux-boun...@list.valvesoftware.com] On Behalf Of Pavilus Zirovski Sent: Monday, November 30, 2009 10:22 AM To: hlds_linux@list.valvesoftware.com Subject: Re: [hlds_linux] Crashing L4D2 fork killing entire machine It's happening about 3-4 times per month for me on 32bit Gentoo hosting TF2 servers only. Im not using -debug in startup line. I am using default preempt kernel (not realtime), but i was using realtime priority scheduler on srcds processes. I think maybe that is the problem. Now i removed resched.sh script from crontab, cause i thought that maybe it happens at some specific moments when cpu overload is very high and rescheduling script changes realtime priority of all srcds_processes (chrt -f -p 98 processid), but im not sure. Now i change realtime priority manually only. Server hasnt crashed for about 2 weeks for now, but i think it might crash any time. This has been frustrating for me as well, cause i lost all remote accesses to server, all processes start to hang one by one and cpu usage is maximized (all taken by one srcds process) at that moment till i lost connection from server at all and i have to call my hosting company so they could physically restart server. At first i thought it was because of some hardware failure or something but now seeing that others have the same problem then im not sure. I hope someone could give some more clues.. I'll give this a shot when I see it happening again. Btw, my OS is Linux Debian Lenny 64-bit with kernel 2.6.30, default compiled. Cheers, -Original Message- From: hlds_linux-boun...@list.valvesoftware.com [mailto: hlds_linux-boun...@list.valvesoftware.com]http://mail.inbox.lv/horde/imp/compose.php?to=hlds_linux-bounces%40list.valvesoftware.com%5Dthismailbox=INBOXstart=1On Behalf Of Milton Ngan Sent: Monday, November 30, 2009 12:39 AM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] Crashing L4D2 fork killing entire machine If you guys are running the servers with -debug (which doesn't currently do anything useful in -fork mode) or crash dumps enabled you should send a SIGABRT (-6) to the process to get it to dump a core file. It will also kill the fork as well. SIGKILL should be used as a last resort if SIGINT (standard kill) doesn't do anything. With regards to -debug and -fork, I have a Perl script that I run alongside srcds_run to achieve desired behavior. I need to re-write this to be more portable so that it can be shipped. -Original Message- From: hlds_linux-boun...@list.valvesoftware.com [mailto: hlds_linux-boun...@list.valvesoftware.com]http://mail.inbox.lv/horde/imp/compose.php?to=hlds_linux-bounces%40list.valvesoftware.com%5Dthismailbox=INBOXstart=1On Behalf Of riemers Sent: Saturday, November 28, 2009 11:49 AM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] Crashing L4D2 fork killing entire machine I've seen a process with 100% too, i've also seen a server which was full for like 2 hours on the same map. At that point i check it out, and it seemed the 4 survivor bots where playing against the infected bots, over and over again. Somehow still pretty funny.. On Sat, 28 Nov 2009 20:13:44 +0100, Saint K. sai...@specialattack.net wrote: I have had this issue twice up till now, and it's rather disturbing. What happened is that a L4D2 fork gets in a crashing mode of some kind where it continuously puts 100% CPU load on a single core. I've seen these sort of crashes perhaps around 10 times so far. 8 times I've spotted it soon enough to kill -9 pid the process, and 2 times I've been too late and it been in such a state for several hours before it will entirely kill off the machine. The machine will only reply to icmp and nothing else (ssh, http, ftp, gameservers etc). This worries me a bit, because I do not have any reason to assume something is broken on OS or hardware level. Regards, Saint K. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux No virus found in this incoming message. Checked by AVG - www.avg.com Version: 9.0.709 / Virus Database: 270.14.87/2534 - Release Date: 11/29/09 20:31:00
Re: [hlds_linux] Crashing L4D2 fork killing entire machine
I can confirm the 100% cpu usage by one process. It does not respond anymore, but it uses the whole cpu. Any workaround for this? I have had this issue twice up till now, and it's rather disturbing. What happened is that a L4D2 fork gets in a crashing mode of some kind where it continuously puts 100% CPU load on a single core. I've seen these sort of crashes perhaps around 10 times so far. 8 times I've spotted it soon enough to kill -9 pid the process, and 2 times I've been too late and it been in such a state for several hours before it will entirely kill off the machine. The machine will only reply to icmp and nothing else (ssh, http, ftp, gameservers etc). This worries me a bit, because I do not have any reason to assume something is broken on OS or hardware level. Regards, Saint K. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Crashing L4D2 fork killing entire machine
At 04:21 AM 11/30/2009, Pavilus Zirovski wrote: It's happening about 3-4 times per month for me on 32bit Gentoo hosting TF2 servers only. Im not using -debug in startup line. I am using default preempt kernel (not realtime), but i was using realtime priority scheduler on srcds processes. I think maybe that is the problem. Now i removed resched.sh script from crontab, cause i thought that maybe it happens at some specific moments when cpu overload is very high and rescheduling script changes realtime priority of all srcds_processes (chrt -f -p 98 processid), but im not sure. Now i change realtime priority manually only. Server hasnt crashed for about 2 weeks for now, but i think it might crash any time. This has been frustrating for me as well, cause i lost all remote accesses to server, all processes start to hang one by one and cpu usage is maximized (all taken by one srcds process) at that moment till i lost connection from server at all and i have to call my hosting company so they could physically restart server. At first i thought it was because of some hardware failure or something but now seeing that others have the same problem then im not sure. I hope someone could give some more clues.. TBH you don't need SCHED_FIFO, you only need SCHED_RR. Gameservers are not time sensitive enough to justify running them at the same priority as, say, the network packet scheduler. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Crashing L4D2 fork killing entire machine
At 04:21 AM 11/30/2009, Pavilus Zirovski wrote: It's happening about 3-4 times per month for me on 32bit Gentoo hosting TF2 servers only. Im not using -debug in startup line. I am using default preempt kernel (not realtime), but i was using realtime priority scheduler on srcds processes. I think maybe that is the problem. Now i removed resched.sh script from crontab, cause i thought that maybe it happens at some specific moments when cpu overload is very high and rescheduling script changes realtime priority of all srcds_processes (chrt -f -p 98 processid), but im not sure. Now i change realtime priority manually only. Server hasnt crashed for about 2 weeks for now, but i think it might crash any time. This has been frustrating for me as well, cause i lost all remote accesses to server, all processes start to hang one by one and cpu usage is maximized (all taken by one srcds process) at that moment till i lost connection from server at all and i have to call my hosting company so they could physically restart server. At first i thought it was because of some hardware failure or something but now seeing that others have the same problem then im not sure. I hope someone could give some more clues.. TBH you don't need SCHED_FIFO, you only need SCHED_RR. Gameservers are not time sensitive enough to justify running them at the same priority as, say, the network packet scheduler. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Crashing L4D2 fork killing entire machine
Do you realy need chrt on l4d and l4d2? In my opinion no. Unlike the other source games it is limited to tick 30 and fps max. You can not change this values. So where is the point using chrt? I use it only for games like tf2 dods css and never had the problem you described. Gary Stanley schrieb: At 04:21 AM 11/30/2009, Pavilus Zirovski wrote: It's happening about 3-4 times per month for me on 32bit Gentoo hosting TF2 servers only. Im not using -debug in startup line. I am using default preempt kernel (not realtime), but i was using realtime priority scheduler on srcds processes. I think maybe that is the problem. Now i removed resched.sh script from crontab, cause i thought that maybe it happens at some specific moments when cpu overload is very high and rescheduling script changes realtime priority of all srcds_processes (chrt -f -p 98 processid), but im not sure. Now i change realtime priority manually only. Server hasnt crashed for about 2 weeks for now, but i think it might crash any time. This has been frustrating for me as well, cause i lost all remote accesses to server, all processes start to hang one by one and cpu usage is maximized (all taken by one srcds process) at that moment till i lost connection from server at all and i have to call my hosting company so they could physically restart server. At first i thought it was because of some hardware failure or something but now seeing that others have the same problem then im not sure. I hope someone could give some more clues.. TBH you don't need SCHED_FIFO, you only need SCHED_RR. Gameservers are not time sensitive enough to justify running them at the same priority as, say, the network packet scheduler. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Crashing L4D2 fork killing entire machine
I'll give this a shot when I see it happening again. Btw, my OS is Linux Debian Lenny 64-bit with kernel 2.6.30, default compiled. Cheers, -Original Message- From: hlds_linux-boun...@list.valvesoftware.com [mailto:hlds_linux-boun...@list.valvesoftware.com] On Behalf Of Milton Ngan Sent: Monday, November 30, 2009 12:39 AM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] Crashing L4D2 fork killing entire machine If you guys are running the servers with -debug (which doesn't currently do anything useful in -fork mode) or crash dumps enabled you should send a SIGABRT (-6) to the process to get it to dump a core file. It will also kill the fork as well. SIGKILL should be used as a last resort if SIGINT (standard kill) doesn't do anything. With regards to -debug and -fork, I have a Perl script that I run alongside srcds_run to achieve desired behavior. I need to re-write this to be more portable so that it can be shipped. -Original Message- From: hlds_linux-boun...@list.valvesoftware.com [mailto:hlds_linux-boun...@list.valvesoftware.com] On Behalf Of riemers Sent: Saturday, November 28, 2009 11:49 AM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] Crashing L4D2 fork killing entire machine I've seen a process with 100% too, i've also seen a server which was full for like 2 hours on the same map. At that point i check it out, and it seemed the 4 survivor bots where playing against the infected bots, over and over again. Somehow still pretty funny.. On Sat, 28 Nov 2009 20:13:44 +0100, Saint K. sai...@specialattack.net wrote: I have had this issue twice up till now, and it's rather disturbing. What happened is that a L4D2 fork gets in a crashing mode of some kind where it continuously puts 100% CPU load on a single core. I've seen these sort of crashes perhaps around 10 times so far. 8 times I've spotted it soon enough to kill -9 pid the process, and 2 times I've been too late and it been in such a state for several hours before it will entirely kill off the machine. The machine will only reply to icmp and nothing else (ssh, http, ftp, gameservers etc). This worries me a bit, because I do not have any reason to assume something is broken on OS or hardware level. Regards, Saint K. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux No virus found in this incoming message. Checked by AVG - www.avg.com Version: 9.0.709 / Virus Database: 270.14.87/2534 - Release Date: 11/29/09 20:31:00 ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Crashing L4D2 fork killing entire machine
It's happening about 3-4 times per month for me on 32bit Gentoo hosting TF2 servers only. Im not using -debug in startup line. I am using default preempt kernel (not realtime), but i was using realtime priority scheduler on srcds processes. I think maybe that is the problem. Now i removed resched.sh script from crontab, cause i thought that maybe it happens at some specific moments when cpu overload is very high and rescheduling script changes realtime priority of all srcds_processes (chrt -f -p 98 processid), but im not sure. Now i change realtime priority manually only. Server hasnt crashed for about 2 weeks for now, but i think it might crash any time. This has been frustrating for me as well, cause i lost all remote accesses to server, all processes start to hang one by one and cpu usage is maximized (all taken by one srcds process) at that moment till i lost connection from server at all and i have to call my hosting company so they could physically restart server. At first i thought it was because of some hardware failure or something but now seeing that others have the same problem then im not sure. I hope someone could give some more clues.. I'll give this a shot when I see it happening again. Btw, my OS is Linux Debian Lenny 64-bit with kernel 2.6.30, default compiled. Cheers, -Original Message- From: hlds_linux-boun...@list.valvesoftware.com [mailto: hlds_linux-boun...@list.valvesoftware.com]http://mail.inbox.lv/horde/imp/compose.php?to=hlds_linux-bounces%40list.valvesoftware.com%5Dthismailbox=INBOXstart=1On Behalf Of Milton Ngan Sent: Monday, November 30, 2009 12:39 AM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] Crashing L4D2 fork killing entire machine If you guys are running the servers with -debug (which doesn't currently do anything useful in -fork mode) or crash dumps enabled you should send a SIGABRT (-6) to the process to get it to dump a core file. It will also kill the fork as well. SIGKILL should be used as a last resort if SIGINT (standard kill) doesn't do anything. With regards to -debug and -fork, I have a Perl script that I run alongside srcds_run to achieve desired behavior. I need to re-write this to be more portable so that it can be shipped. -Original Message- From: hlds_linux-boun...@list.valvesoftware.com [mailto: hlds_linux-boun...@list.valvesoftware.com]http://mail.inbox.lv/horde/imp/compose.php?to=hlds_linux-bounces%40list.valvesoftware.com%5Dthismailbox=INBOXstart=1On Behalf Of riemers Sent: Saturday, November 28, 2009 11:49 AM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] Crashing L4D2 fork killing entire machine I've seen a process with 100% too, i've also seen a server which was full for like 2 hours on the same map. At that point i check it out, and it seemed the 4 survivor bots where playing against the infected bots, over and over again. Somehow still pretty funny.. On Sat, 28 Nov 2009 20:13:44 +0100, Saint K. sai...@specialattack.net wrote: I have had this issue twice up till now, and it's rather disturbing. What happened is that a L4D2 fork gets in a crashing mode of some kind where it continuously puts 100% CPU load on a single core. I've seen these sort of crashes perhaps around 10 times so far. 8 times I've spotted it soon enough to kill -9 pid the process, and 2 times I've been too late and it been in such a state for several hours before it will entirely kill off the machine. The machine will only reply to icmp and nothing else (ssh, http, ftp, gameservers etc). This worries me a bit, because I do not have any reason to assume something is broken on OS or hardware level. Regards, Saint K. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Crashing L4D2 fork killing entire machine
If you guys are running the servers with -debug (which doesn't currently do anything useful in -fork mode) or crash dumps enabled you should send a SIGABRT (-6) to the process to get it to dump a core file. It will also kill the fork as well. SIGKILL should be used as a last resort if SIGINT (standard kill) doesn't do anything. With regards to -debug and -fork, I have a Perl script that I run alongside srcds_run to achieve desired behavior. I need to re-write this to be more portable so that it can be shipped. -Original Message- From: hlds_linux-boun...@list.valvesoftware.com [mailto:hlds_linux-boun...@list.valvesoftware.com] On Behalf Of riemers Sent: Saturday, November 28, 2009 11:49 AM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] Crashing L4D2 fork killing entire machine I've seen a process with 100% too, i've also seen a server which was full for like 2 hours on the same map. At that point i check it out, and it seemed the 4 survivor bots where playing against the infected bots, over and over again. Somehow still pretty funny.. On Sat, 28 Nov 2009 20:13:44 +0100, Saint K. sai...@specialattack.net wrote: I have had this issue twice up till now, and it's rather disturbing. What happened is that a L4D2 fork gets in a crashing mode of some kind where it continuously puts 100% CPU load on a single core. I've seen these sort of crashes perhaps around 10 times so far. 8 times I've spotted it soon enough to kill -9 pid the process, and 2 times I've been too late and it been in such a state for several hours before it will entirely kill off the machine. The machine will only reply to icmp and nothing else (ssh, http, ftp, gameservers etc). This worries me a bit, because I do not have any reason to assume something is broken on OS or hardware level. Regards, Saint K. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Crashing L4D2 fork killing entire machine
I'm having this same error like 2 times per month, with srcds/hlds servers. I can only ping the machine but ssh, http, ftp won't work. People can join to the gameservers but they get freeze at mapchange for about 30mins. Sometimes I got luck and I manage to access to SSH. I checked the system load and it was 100+. 'reboot' command wasn't working so i did a 'killall hlds_i686 srcds_i686 srcds_i486' and the machine got unstuck and all worked fine again. strange, isn't it? I think that the problem is related to giving RT priority to the gameservers or maybe the kernel config (i'm using the one in fragaholics.de wiki in CentOS) -Rodrigo Joshua Smith escribió: I have experienced this EXACT behavior on several machines, all running debian lenny 64bit. I stopped running the forks after it started taking entire machines down. On Sat, Nov 28, 2009 at 11:48 AM, riemers riem...@binkey.nl wrote: I've seen a process with 100% too, i've also seen a server which was full for like 2 hours on the same map. At that point i check it out, and it seemed the 4 survivor bots where playing against the infected bots, over and over again. Somehow still pretty funny.. On Sat, 28 Nov 2009 20:13:44 +0100, Saint K. sai...@specialattack.net wrote: I have had this issue twice up till now, and it's rather disturbing. What happened is that a L4D2 fork gets in a crashing mode of some kind where it continuously puts 100% CPU load on a single core. I've seen these sort of crashes perhaps around 10 times so far. 8 times I've spotted it soon enough to kill -9 pid the process, and 2 times I've been too late and it been in such a state for several hours before it will entirely kill off the machine. The machine will only reply to icmp and nothing else (ssh, http, ftp, gameservers etc). This worries me a bit, because I do not have any reason to assume something is broken on OS or hardware level. Regards, Saint K. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
[hlds_linux] Crashing L4D2 fork killing entire machine
I have had this issue twice up till now, and it's rather disturbing. What happened is that a L4D2 fork gets in a crashing mode of some kind where it continuously puts 100% CPU load on a single core. I've seen these sort of crashes perhaps around 10 times so far. 8 times I've spotted it soon enough to kill -9 pid the process, and 2 times I've been too late and it been in such a state for several hours before it will entirely kill off the machine. The machine will only reply to icmp and nothing else (ssh, http, ftp, gameservers etc). This worries me a bit, because I do not have any reason to assume something is broken on OS or hardware level. Regards, Saint K. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Crashing L4D2 fork killing entire machine
I've seen a process with 100% too, i've also seen a server which was full for like 2 hours on the same map. At that point i check it out, and it seemed the 4 survivor bots where playing against the infected bots, over and over again. Somehow still pretty funny.. On Sat, 28 Nov 2009 20:13:44 +0100, Saint K. sai...@specialattack.net wrote: I have had this issue twice up till now, and it's rather disturbing. What happened is that a L4D2 fork gets in a crashing mode of some kind where it continuously puts 100% CPU load on a single core. I've seen these sort of crashes perhaps around 10 times so far. 8 times I've spotted it soon enough to kill -9 pid the process, and 2 times I've been too late and it been in such a state for several hours before it will entirely kill off the machine. The machine will only reply to icmp and nothing else (ssh, http, ftp, gameservers etc). This worries me a bit, because I do not have any reason to assume something is broken on OS or hardware level. Regards, Saint K. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Crashing L4D2 fork killing entire machine
I have experienced this EXACT behavior on several machines, all running debian lenny 64bit. I stopped running the forks after it started taking entire machines down. On Sat, Nov 28, 2009 at 11:48 AM, riemers riem...@binkey.nl wrote: I've seen a process with 100% too, i've also seen a server which was full for like 2 hours on the same map. At that point i check it out, and it seemed the 4 survivor bots where playing against the infected bots, over and over again. Somehow still pretty funny.. On Sat, 28 Nov 2009 20:13:44 +0100, Saint K. sai...@specialattack.net wrote: I have had this issue twice up till now, and it's rather disturbing. What happened is that a L4D2 fork gets in a crashing mode of some kind where it continuously puts 100% CPU load on a single core. I've seen these sort of crashes perhaps around 10 times so far. 8 times I've spotted it soon enough to kill -9 pid the process, and 2 times I've been too late and it been in such a state for several hours before it will entirely kill off the machine. The machine will only reply to icmp and nothing else (ssh, http, ftp, gameservers etc). This worries me a bit, because I do not have any reason to assume something is broken on OS or hardware level. Regards, Saint K. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
