Just a quick thought - have you top'd the system to see what process is
causing the prob.
Assuming you have shell access (ssh or the like), just 'top' - it'll
show all the running processes sorted by CPU usage (example below). Find
the culprit and then kill the process id (PID)
HTH
Jeff
Example top output..
bash-2.05b$ top
00:43:38 up 2:28, 2 users, load average: 0.00, 0.11, 0.13
83 processes: 82 sleeping, 1 running, 0 zombie, 0 stopped
CPU states: 9.2% user 2.7% system 0.0% nice 0.0% iowait 88.0%
idle
Mem: 1030932k av, 659544k used, 371388k free, 0k shrd, 42720k
buff
509268k actv, 82232k in_d, 4960k in_c
Swap: 1052216k av, 4020k used, 1048196k free 419520k
cached
PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU
COMMAND
2474 root 15 0 286M 30M 5956 S 0.9 2.9 6:11 0 X
1 root 15 0 476 452 424 S 0.0 0.0 0:04 0 init
2 root 15 0 0 0 0 SW 0.0 0.0 0:00 0
keventd
3 root 15 0 0 0 0 SW 0.0 0.0 0:00 0 kapmd
4 root 34 19 0 0 0 SWN 0.0 0.0 0:00 0
ksoftirqd_CPU
9 root 25 0 0 0 0 SW 0.0 0.0 0:00 0
bdflush
5 root 15 0 0 0 0 SW 0.0 0.0 0:00 0 kswapd
6 root 15 0 0 0 0 SW 0.0 0.0 0:00 0
kscand/DMA
On Tue, 2003-12-30 at 00:33, Timothy Stone wrote:
> List,
>
> I need help. I have an unknown process that has suddenly starting
> hogging the CPU on my staging server (RH8).
>
> I came back from the screensaver, pressed ALT-F2 to open a
> gnome-terminal. Pressed F1 to get a help window (I wanted to look
> something up). As the help window opened, I moused over to a mozilla
> window and clicked the close widget.
>
> Everything froze at that point. The HDD spun up, and it has been going
> for 3 hours now. I'm very worried. I get some GUI response, the mouse
> seems to be tracking, albeit very slowly like a flip-book cartoon. But
> keyboard and mouse clicks are being consumed or ignored.
>
> How can I arrest a haywire process that is potentially consuming 99% of
> the CPU?
>
> CTRL-ALT-Delete is not responding. I just looked up some stuff on the
> mailing list archives for "process hog" and "process hogging CPU" and
> see that X might be the culprit. I'm considering a trip to work to test
> CTRL-Backspace to arrest X, but this might not work as I'm not sure
> about the keyboard.
>
> The box is responding to ping. But that could be the NIC and unrelated
> to the OS.
>
> Thoughts? I'm desperate enough to hit the power button. This is very
> upsetting as the HDD may fail if it continues much longer.
>
> Tim
>
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
