[Date Prev][Date Next]
Re: slapd crashing "randomly?"
On Feb 6, 2007, at 1:35 PM, matthew sporleder wrote:
On 2/6/07, firstname.lastname@example.org <email@example.com> wrote:
I want to start this message by saying, what I'm about to describe is
completely vague and I don't expect to get a solution response. ;)
Basically, I'm out of ideas and am looking for some suggestions as
to debug the issue I'm running into.
Starting about half a year ago, slapd started "just dieing" out of
blue. Not a think in the logs shows up to indicate what might
it. The last query that I see in the logs before a crash always
be nothing special. I don't even see a core dump being generated
then that may just be because I don't have the proper setup to get
dump at this time. We were running the last 2.2 and upgraded to the
latest release of 2.3 to make sure it wasn't an "old version" issue.
Unfortunately, slapd still dies a fair amount on us. It appears
fairly unpredictable. I've seen it crash within 1 minute of
slapd (then a subsequent startup 'takes' just fine). I've seen it
when there were a number of network issues going on. I've seen it
out of the blue when nothing appeared to be going on. I don't
the drive space to turn on max debug logging 24/7 until the problem
We're thinking about setting up something to watch all of the network
traffic going to one of the boxes until it dies. (assuming we can
something with the resources to do that)
That all said... since I have nothing solid to present, do you
any suggestions of what would be the best way to track down what's
on? I'm literally out of ideas unless my berkeley db config is
causing the problem or something like that.
I apologize for the vagueness. =/ Any ideas/suggestions?
After the crash, is your bdb environment clean, or is it needing a
Depending on your OS, you could watch the pid all the time and trap
the last signals received, last files accessed, etc, and that wouldn't
take tons of resources.
The BDB environment is indeed unclean after the crash. Though, as of
2.3 it appears to auto-db_recover most of the time if someone else
starts up slapd before doing the recover.
You could try turning on max debugging and simply rotate a lot more
often. (every n minutes or even seconds) This way you could
definitely keep the -last- transactions and just not worry about the
Unfortnately we also use those logs for analysis. =/ But I might go
that route depending on how things go!