Red Hat Bugzilla – Bug 52317
slurpd replication fails
Last modified: 2007-04-18 12:36:12 EDT
Description of Problem:
slurpd fails to replicate to slave servers.
Version-Release number of selected component (if applicable):
Never, ever replicates data in 'normal' (not-single shot) mode
Steps to Reproduce:
1. Setup master LDAP server and slave server (config works with 2.0.7)
2. Make change to master server
Change does not propagate
Slave server should be updated
Upgrading to OpenLDAP 2.0.11 on RedHat 7.1 causes slurpd to fail to update
slave servers. After upgrading a configuration which correctly updated
slave nodes using slurpd no longer generates updates.
Using single-shot mode works correctly
i.e. slurpd -r <replog file> -o
Correctly performs the update. However when I run:
slurpd -d -1
I see that the config file is correctly parsed and I see the copies of the
slapd replog file being made correctly however I see no output from the
update thread until I ctrl-C the daemon when I get:
begin replication thread for white-clued0.fnal.gov:389
end replication thread for white-clued0.fnal.gov:389
The replica configuration I have works correctly with 2.0.7 its only when I
upgraded to 2.0.11 that I noticed this problem. I can post the config if
its helpful. As far as I can tell it seems that the threads in 2.0.11 are
somehow not running (but I know next to nothing about thread programming!).
The RPM I am using is the official update to OpenLDAP 2.0.11-8.
I'll second this; I'm seeing the *exact* same thing in
openldap-servers-2.0.11-8. slurpd compiled from the stock openldap 2.0.11-stable
(20010524) works as it should.
openldap-servers-2.0.11-8.i386.rpm slurpd broken
openldap-servers-2.0.7-14.i386.rpm slurpd works
openldap-2.0.11.tar.gz (20010524) slurpd works
I can reproduce this at will by upgrading/downgrading from/to the RPM versions
I can't for the life of me figure out what caused this breakage; the source in
the 2.0.11-8 RPM is the 20010524 stable release, which works fine for me with
vanilla build flags. The patches in the 2.0.11-8 RPM don't seem to touch
anything important, so my only guess is that the build flags are triggering
Is this fixed by openldap-servers-2.0.18-2.i386.rpm from rawhide?
Yes, openldap-2.0.18-2 from rawhide *does* fix this.
2.0.11-13 fixes this problem for me as well
This bug should be marked as RESOLVED/RAWHIDE or RESOLVED/FIXED. (The 2.0.22-1
errata release might have fixed it, too.)