innd stops responding

[Gary Thandi]

By snapshot, do you mean the truss I ran? Are you suggesting keeping the
truss running until a failure? The only bad part is that truss is very
verbose and creates a rather large file. Not sure if I'd be able to run the
command and have enough disk space. 

Are there any good ovdb resources, someon could point me to as a start?


-----Original Message-----
From: Alex Kiernan <alex.kiernan at gmail.com>
To: Gary Thandi <gary.thandi at 360.net>
CC: inn-workers at isc.org <inn-workers at isc.org>
Sent: Mon Jul 19 06:50:19 2004
Subject: Re: innd stops responding

On Mon, 19 Jul 2004 06:42:48 -0700, Gary Thandi <gary.thandi at 360.net> wrote:
> 
> yes.  i've had to resort to stopping and starting all news processes every
> 60 minutes.
> 

Try getting a snapshot - I know Heath's made some fixes to the ovdb
code, but I've not tried those.

Certainly the behaviour you're seeing is typical for ovdb on Solaris;
I'm not sure if anyone's addressed the way nnrpd does termination yet,
but last time I looked it seemed like if you took a signal at the
wrong moment, nnrpd would try and make calls into ovdb (and hence
BerkeleyDB) in a re-entrant fashion, which isn't supported (not
unreasonably) by BerkeleyDB.

-- 
Alex Kiernan