[Date Prev][Date Next]
Re: Binlogs Growing umlimited
On Thu, 12 Jul 2012, Thomas Spycher wrote:
I've recently noticed that the bin logs of the bdb backend are growing
1. what could happen with the server, which makes it only being able to
read of its own db?
2. why are the bin logs are growing so dramatically?
I'm not entirely sure what you're referring to when something is only
"able to read of its own db" (is the backend going read-only? what
messages are you seeing? etc.) but given the context perhaps you're
experiencing timeouts from a large log sync. Berkeley DB transaction logs
grow without bound under the default configuration, and you might not be
checkpointing writes in back-bdb (which could explain your curious restart
behavior). Get started with:
and the slapd-bdb man page for details on transaction logs, checkpoints
and so forth. You might also want to check that you're running a sane
version of Berkeley DB (with patches as may be appropriate) and of
OpenLDAP itself (2.4.31 is latest as of this writing).