I don't have #5 (sleepycat#14657) nor the unofficial http://www.stanford.edu/services/directory/openldap/configuration/patches/db... patch. As for the official one, I'm not sure about its relevance to the actual SEGV due to the "recovery...fail" comment. In other words, though it may be impacting the ability of alock/db_recover to do its thing, that's just a side effect of the unclean shutdown which is the real bug here to my view.

The region size patch is interesting, but I will tell you that the database in question has

set_cachesize 0 200000000 0

and it (to a glance) looks like that only impacts the gig column, which I have as zero anyway.

I can tell you that stop/starts weren't an issue with 2.3.32 and the same Sleepycat binaries...not that I stop/start often as a rule of thumb. (I am lately; we're implementing ando's {RADIUS} module.) But two identical traces on two different boxes caught my eye.

On Thu, 26 Apr 2007, Quanah Gibson-Mount wrote:

----- richton@nbcs.rutgers.edu wrote:

...

Full_Name: Aaron RIchton Version: 2.3.35 OS: Solaris 9 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (128.6.30.206)

BDB 4.2.52. I've had a couple (different) machines SEGV on slapd shutdown. Both had identical stack traces:

Wierd, I've been running hdb on my servers for nearly a year without such an issue. Did this just start with 2.3.35?

Also, what patches do you have applied to BDB 4.2.52. I'm up to 6 now.

http://www.stanford.edu/services/directory/openldap/configuration/bdb-build-notes.html

5 are direct from sleepycat:

http://www.oracle.com/technology/products/berkeley-db/db/update/4.2.52/patch.4.2.52.html

with the last one there possibly impacting you if you don't have it?

--Quanah

-- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc

---

Zimbra :: the leader in open source messaging and collaboration