Send inn-workers mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.isc.org/mailman/listinfo/inn-workers
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of inn-workers digest..."


Today's Topics:

   1. ovdb instability with Berkeley DB5/6 ([email protected])


----------------------------------------------------------------------

Message: 1
Date: Thu, 12 Sep 2019 17:56:04 -0400
From: [email protected]
To: [email protected]
Subject: ovdb instability with Berkeley DB5/6
Message-ID: <[email protected]>
Content-Type: text/plain


I have an INN environment that I updated recently.  I got it stable, but
I figured I would post my experience in case there's something I can do
to help.  Otherwise, maybe my experience will help anyone else having
this issue.

Env: FreeBSD 12 - amd64, INN 2.6.3

The trouble came when using 'makehistory -O -x -F' to build my ovdb.  I
started with the precompiled Berkeley DB 5.3 from the FreeBSD ports
system.  I couldn't get it to be stable.  At first, I had mmap on.  That
was very unstable.  It would die and corrupt the DB.  It wouldn't
recover.  Then I turned on shared memory instead.  Things were slightly
more stable, but it would eventually hang.  When I did an 'ovdb_stat
-t', I would see there was a single transaction running.  I tried lots
of other parameters randomly.  I figure I have pretty good coverage of
them at this point.

My experience was about the same with BDB 6.2.

I finally switched back to BDB 4.8, which is EoL.  With that and shared
memory, it was stable enough to build ovdb (about 20 hours).  Everything
looks good so far.

I was upgrading from 2.5.3 and I can't remember what version of BDB I
was using way back then.  It was probably another 4.x version.  That was
rock solid for years.  Hopefully I've gotten it back into a good state.

If this happens again, do folks have thoughts on how to debug it?

-boogles


------------------------------

Subject: Digest Footer

_______________________________________________
inn-workers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-workers


------------------------------

End of inn-workers Digest, Vol 115, Issue 1
*******************************************

Reply via email to