db->put: Invalid argument?

Alex Kiernan alexk at demon.net
Tue Jul 10 08:12:17 UTC 2001


Alex Kiernan <alexk at demon.net> writes:

> Ron Jarrell <jarrell at solaris.cc.vt.edu> writes:
> 
> > At 08:17 AM 7/9/01 +0100, Alex Kiernan wrote:
> > 
> > >
> > >If you're willing to try I've some patches against Berkeley DB which I
> > >hope will help to identify the problem.
> > 
> > So long as they won't eat my performance, I'd be willing to give it a shot.
> > Might be a few days before I could schedule the time to recompile the library,
> > rebuild INN, and swap it into place though.  Hasn't happened again since that
> > second occurrence though.
> > 
> 
> It shouldn't be too bad (its a getpid() per mutex lock & unlock). If
> you do get it to fail, can you pick one of the blocked processes and
> print out mutexp->lockedby & unlockedby. Then look and see if those
> processes are still running & if so what they are.
> 

Something else which would be useful to print (and has just occurred
to me) would be mutexp->locked (heck lets just print *mutexp & have
done with it!)

-- 
Alex Kiernan, Principal Engineer, Development, Thus PLC


More information about the inn-workers mailing list