HP3000-L Archives

December 2006, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
John MacLerran <[log in to unmask]>
Reply To:
John MacLerran <[log in to unmask]>
Date:
Tue, 19 Dec 2006 15:50:28 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (24 lines)
Hello everyone,
I apologize if you've received this twice, but I forgot to put [HP3000-L] in
the header.

We have a runaway process on our box (N4000 4-way 440MHz, mpe 7.5, PP2).
We've tried to do an abortjob on it, but that didn't kill it.  Then, we
tried an abortproc on the specific PIN, and received the message: "There is
already an ABORT pending for pin "902". (CIWARN 11015)". In SOS, the process
that is still alive is the son process, and the father process is reported
as not being active. Grasping at straws, I did a kill -9 on the son's PIN in
the posix shell, but that didn't do anything.

Is there anything else I can try, or do we need to reboot the box? Is there
anything I can do to suspend that process so it won't consume resources?
I've already dropped it to the lowest it can go in the E queue, but it still
consumes disc i/o and cpu cycles.

Thanks!
John MacLerran
[log in to unmask]

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2