It is Linux. Unfortunately, it's always the production instances
that hang, and I can't leave them that way while I poke around.
Especially since it seems to be load related and so usually happens
at the busiest times of the day. I don't really know how to use
gdb; if there is something quick I can do that can be examined
offline, let me know and I will try it.
janine
On Oct 3, 2005, at 11:15 AM, Dossy Shiobara wrote:
On 2005.10.03, Janine Sisk <[EMAIL PROTECTED]> wrote:
It's pretty tough to track down the cause since once it happens nsd
is totally unresponsive and doesn't give any clues as to what
happened.
If you're running on Solaris, you might want to capture the "pstack"
output of the process.
On Linux, you could attach with gdb and try to get a backtrace.
-- Dossy
--
Dossy Shiobara [EMAIL PROTECTED] | http://dossy.org/
Panoptic Computer Network http://panoptic.com/
"He realized the fastest way to change is to laugh at your own
folly -- then you can let go and quickly move on." (p. 70)
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to
<[EMAIL PROTECTED]> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the
Subject: field of your email blank.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]>
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.
