Re: Replication problem

[Mark Adamson <adamson@andrew.cmu.edu>]

1)  Did replication suddenly "cease" on Saturday Sept 9, say around 9:47pm?
If so, you hit the "S1G" bug. Check your slurpd.status file and if all of
the timestamps are around 999999999, stop slurpd and edit that file to
bump all the timestamps to 1000000000 (1 billion) and restart slurpd.

2) This should be posted to the software or bugs bboard, as this bboard is
for discussion of the development of OpenLDAP.


-Mark Adamson
 Carnegie Mellon



On Wed, 19 Sep 2001, Salgado, Fabian wrote:

>
>
> -----Original Message-----
> From: Salgado, Fabian
> Sent: Wednesday, September 19, 2001 10:54 AM
> To: 'OpenLDAP-devel@OpenLDAP.org'
> Subject: Replication problem
>
> Help!
>
> All of the sudden replication seized to function. Upon running slurpd in
> debug mode I get:
>
> new work in /usr/local/etc/openldap/slurprep.log
> copy replog "/usr/local/etc/openldap/slurprep.log" to
> "/usr/local/etc/openldap/t
> mp//replica/slurpd.replog"
> Replica 192.168.2.21:389, skip repl record for
> CN=14,DC=VOIP,DC=NETCARRIER,DC=CO
> M (old)
> Replica 192.168.2.18:389, skip repl record for
> CN=14,DC=VOIP,DC=NETCARRIER,DC=CO
> M (old)
> Replica 192.168.2.21:389, skip repl record for
> cn=15,dc=voip,dc=netcarrier,dc=co
> m (old)
> Replica 192.168.2.18:389, skip repl record for
> cn=15,dc=voip,dc=netcarrier,dc=co
> m (old)
>
> This happens for records which are already in the log file and those that
> are modified as slurpd is running.
>
> Any assistance would be greatly appreciated.
>
> Thanks,
>
> Fabian
>