[Date Prev][Date Next]
Re: Help -- replication broken with 2.1 -> 2.2 Master upgrade!
On Wed, 7 Sep 2005, Quanah Gibson-Mount wrote:
--On Wednesday, September 07, 2005 1:49 PM -0400 Victor Danilchenko
We have upgraded our LDAP master to CentOS 4.1 (RHEL 4 derivative),
which includes openLDAP 2.2.13, and replication broke. The config file is
the same, with just some changes in the schema inclusion (the old DB was
dumped and reloaded without errors). The problem is that the master is
not writing the replogfile!
How can you consider OpenLDAP 2.2.13 a viable upgrade? Have you looked at the
numerous bugs fixed since the 2.2.13 release, several relating to slurpd?
No, I haven't, but it sounds like I should. Still, I find it
hard ot believe that an OpenLDAP version released with RHEL 4.1 simply
*does not replicate*, though I am open to that possibility.
I have just looked at the CHANGELOG for OpenLDAP 2.2.26, and I
see what you mean. Perhaps we will build 2.2.26 RPMs... should be rather
The relevant section of my slapd.conf:
bindmethod=simple credentials=secret starttls=yes
I stopped slurpd, successfully wrote an update to the master, and the
replication.log is empty. This configuration worked fine under RHL 9 with
OpenLDAP 2.1. I looked through the OpenLDAP 2.2 docs, the replcation
slapd.conf syntax seems to be the same; but replication log remains
empty, and its mtime unchanged, no matter what updates I write to the
Which replication log remains empty? The slapd replog, or the slurpd replog?
The one slapd is supposed to produce, and slurpd is supposed to
consume -- specified by replogfile directive. That file remains not only
empty, but even its mtime attribute remains unchanged. It's almost as if
the replica directives in slapd.conf simply don't exist, as far as slapd
| Victor Danilchenko + Unix: Your gun, Your bullet, |
| firstname.lastname@example.org | Your foot, Your choice. |
| CSCF | 5-4231 | MS: Same as Unix, BUT: No choice, |
+-----------------------+ and We Aim Higher. |