Hi all,
this is my official request for help from all of you with experience setting up a Linux dedicated server.
Symptoms:
Whenever I start the Linux UT3 ded. server, a period of time passes after which the CPU is hogged, and the entire OS becomes unresponsive, and I have to restart the server *physically*. The period of time can be anything from 30secs to 10 minutes into a match.
Steps taken:
* During tests I run server with only critical processes running on the server
* I have used the standard UT3 server configs for testing
* I have set up hardware monitoring graphs (Munin) and checked spikes in I/O, temperatures, interrupts, etc.
* I have checked logs for backtraces, weird IRQ events, whatever .. without luck.
Question:
What are good steps to take in order to troubleshoot this?
Server info:
* Debian testing ("lenny")
* Pentium 4 2.4GHz, 1GB RAM
* Ded. 40/40Mbit connection
* UT3 v1.2 (with Webadmin v0.9)
Anyone? What the h*ck is going on?
this is my official request for help from all of you with experience setting up a Linux dedicated server.
Symptoms:
Whenever I start the Linux UT3 ded. server, a period of time passes after which the CPU is hogged, and the entire OS becomes unresponsive, and I have to restart the server *physically*. The period of time can be anything from 30secs to 10 minutes into a match.
Steps taken:
* During tests I run server with only critical processes running on the server
* I have used the standard UT3 server configs for testing
* I have set up hardware monitoring graphs (Munin) and checked spikes in I/O, temperatures, interrupts, etc.
* I have checked logs for backtraces, weird IRQ events, whatever .. without luck.
Question:
What are good steps to take in order to troubleshoot this?
Server info:
* Debian testing ("lenny")
* Pentium 4 2.4GHz, 1GB RAM
* Ded. 40/40Mbit connection
* UT3 v1.2 (with Webadmin v0.9)
Code:
root@isildur:~# uname -a Linux isildur 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686 pentium4 i386 GNU/Linux

Comment