[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Unkillable processes?



On Wednesday 16 July 2003 21:32, Bradley M Alexander wrote:
> Today I noticed a number of processes, normal housekeeping stuff, like
> anacron, run-parts, etc that are in a sleeping state, but can't be killed.
> I'm starting to wonder if the reason I can only get about 30 days or less
> out of the firewall is that the process table fills up and things slow to a
> crawl.
>
> Not only can the processes be killed (with a kill -9 as root), but if I
> start a process, it seems at the moment that I cannot kill any hung process
> (for instance, requesting a man page did not ever display said page, so I
> tried to control-c out of it, and was unsuccessful.
>
> A few of the processes showing up now are
>
> root      4659  0.0  0.7  1348  696 ?        S    Jul15   0:00 anacron -s
> root      7260  0.0  0.5  1308  496 ?        SN   Jul15   0:00 run-parts
> --repor
> t /etc/cron.daily
> root      5164  0.0  1.0  2040  984 ?        SN   Jul15   0:00 /bin/sh
> /etc/cron
> .daily/find
> root      7177  0.0  1.0  2076 1028 ?        SN   Jul15   0:00 /bin/sh
> /usr/bin/
> updatedb
> root     19375  0.0  1.0  2076  972 ?        SN   Jul15   0:00 /bin/sh
> /usr/bin/updatedb
> root     13227  0.0  0.5  7160  488 ?        SN   Jul15   0:00 sort -f
> root     13092  0.0  0.2  1188  284 ?        SN   Jul15   0:00
> /usr/lib/locate/frcode
> storm    26028  0.0  0.6  1964  576 pts/1    D    14:21   0:00 man ps

Assuming that everything else works, I'd think it's dud memory. Try running 
memtest86 for some time. That's the only thing that made my always-on boxes 
misbehave up to now.

An alternative idea would be that you're running an extremely funky kernel 
(early 2.4 series perhaps?) that could need upgrading.

-- 
Got Backup?



Reply to: