Subject: Re: up2date has hijacked my server
gaijin@gci.net
Date: Tue Apr 08 2003 - 17:23:49 AKDT
Try specifying kill -15 <pid>, or kill -9 <pid>.
Think of it like this:
kill <pid> Pretty please, go away?
kill -15 <pid> Go Away and Take Your Mess With You!
kill -9 <pid> *BLAM* Now I must clean up the mess
The first two give the process the opportunity to perform
a proper closure.
The last will kill it without properly closing files, freeing
memory, etc.
On Tue, 8 Apr 2003 enderak@gci.net wrote:
>
> Hey all. I ssh'd into my server today and noticed
> that my cpu was pegged at 100% for some reason.
> Looking at 'top' and 'ps ax' it says that up2date
> has been using almost all my cpu for over a month
> now (50785 minutes = 35 days!)
>
> Various outputs are as follows:
>
> top:
> PID USER PRI NI SIZE RSS SHARE STAT %CPU
> %MEM TIME COMMAND
> 22991 root 25 0 5380 1568 1504 R 98.9
> 1.2 50789m up2date
>
> ps ax:
> PID TTY STAT TIME COMMAND
> 22991 ? R 50786:19 /usr/bin/python -u
> /usr/sbin/up2date
>
> I've tried 'kill 22991', 'killall up2date', and
> 'killall python' all several times, but it just
> won't die. Aside from rebooting, is there anything
> I can do here?
>
> Thanks,
> Justin
>
>
>
> ---------
> To unsubscribe, send email to <aklug-request@aklug.org>
> with 'unsubscribe' in the message body.
>
---------
To unsubscribe, send email to <aklug-request@aklug.org>
with 'unsubscribe' in the message body.
This archive was generated by hypermail 2a23 : Tue Apr 08 2003 - 17:23:52 AKDT