db->put: Invalid argument?
jarrell at solaris.cc.vt.edu
Mon Jul 9 07:45:25 UTC 2001
At 08:17 AM 7/9/01 +0100, Alex Kiernan wrote:
>Ron Jarrell <jarrell at solaris.cc.vt.edu> writes:
>> At 09:14 AM 7/6/01 +0100, Alex Kiernan wrote:
>> >Alex Kiernan <alexk at demon.net> writes:
>> >> Well patched kernel too? I'm trying to figure why I'm not seeing the
>> >> problem anymore (and I was in the past with some regularity).
>> >OK, its happened here overnight. Its not the one I thought I'd seen
>> >before, its a new one.
>> >When it happens again can you break into it with dbx (or gdb), and
>> >print out mutexp->mutex.lock.owner64; for the one I have here it looks
>> >like junk:
>> >mutexp->mutex.lock.owner64 = ff000001
>> Yea, I can give that a shot. Hopefully now that I'm looking for something,
>> it'll never happen again :-).
>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.
More information about the inn-workers