[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Replication problem - More Info

I have been tracing through the slurpd code and it would appear that my
replication thread is being fired off correctly AND that thread is finding
replication records that need to be sent to the replica. The area it appears to
be stopping at is in ri.c in the Ri_process function at around line 62:
    while ( !sglob->slurpd_shutdown &&
            (( re = rq->rq_gethead( rq )) == NULL ))
>From what I can tell, the replication threads are not progressing past this

Any ideas why??

> I am running OpenLDAP 2.0.11 on RedHat 7.1 and I am trying to get replication
> working from one master to a single replica. I have added a replication entry
> the master's slapd.conf which looks like this:
> <snip>
> replogfile      /var/lib/ldap/slapd.replog
> replica host=slavehost.somedomain.com:389
>         binddn="cn=root,dc=somedomain,dc=com"
>         bindmethod=simple
>         credentials=secretpassword
> <snip>
> In the replica's slapd.conf file I have an updatedn entry like so:
> <snip>
> updatedn        "cn=root,dc=somedomain,dc=com"
> <snip>
> When I start the master server, slurpd starts up as expected. When I alter an
> entry on the master, the slapd.replog file is written with the change. Slurpd
> then copies this change to replica/slurpd.replog and deletes the entry from
> slapd.replog.
> This is where it stops. The change is never sent to the slave??
> if I run slurpd in debug mode, I see no messages to indicate any error.
> I see no connection to the replica from the master in the replica's log file.
> If I stop the running slurpd and do a oneshot run of slurpd over the
> replica/slurpd.replog file, it successfully sends the changes to the replica.
> Any ideas what might be preventing slurpd from sending the changes through to
> the replica automatically?
> How long should I have to wait before the changes are sent?
> Thanks
> Roland