>> Quanah Gibson-Mount <quanah(a)zimbra.com> schrieb am
02.09.2014 um 18:42 in
--On Tuesday, September 02, 2014 9:24 AM +0200 Francesco Malvezzi
> On provider all ok. Provider is mirrormode and other mirror side is ok.
> The accesslog-based syncrepl on a consumer was stuck. Neither the modify
> nor the other next modifies were propagated.
Recently I had a similar problem with accesslog:
When trying to create two additional indexes for the acesslog database, slapd did not
finish, and it stopped processing requests. It could not be shutdown either (it said it
would wait for outstanding commands to finish, but they never finished). Badly I could not
query the monitoring database either while in that state...
In the end it turned out that the problem was not local at all: After stopping the other
replicating slapds and rebuilding their databases from the master (slapcat/slapadd) and
restarting them, I could add the additional indexes on the initial node.
Indication of the problem was that the databases were not identical (it's a bit tricky
to find out, because you cannot really diff slapcats from different servers as the order
of entries differs).
It was an old slapd with bdb on SLES11 SP3...
What openldap version?
Zimbra :: the leader in open source messaging and collaboration