On Tuesday 08 November 2005 19:43, Ben Beuchler wrote: > I'm using OpenLDAP 2.26 on Ubuntu linux. Replication appears to be > working in that when I first fired up the secondary server it pulled > across the full database and if I modify an entry on the primary > server, the modification is properly sync'd to the secondary. > However, if I add a new entry to the primary, the CPU load on the > primary immediately jumps to 100% and stops responding. As this is a > production server, I haven't been able to wait to see how long this > state lasts. If I shut down the secondary server and add the new > entry to the primary, it is sync'd as soon as I start the secondary > back up. > > This is the syncrepl section from the secondary config: > > syncrepl rid=42 > provider=ldaps://ldap.mcad.edu > type=refreshAndPersist > searchbase="dc=ldap,dc=mcad,dc=edu" > filter="(objectclass=*)" > scope=sub > updatedn="cn=replicant,dc=bindaccts,dc=ldap,dc=mcad,dc=edu" > bindmethod=simple > binddn="cn=syncclient,dc=bindaccts,dc=ldap,dc=mcad,dc=edu" > credentials=<snip> There is no updatedn option for sycnrepl .... > > And the sessionlog entry from the primary server: > > sessionlog 1 100 > > Any thoughts on why this might be happening? Are you indexing the entryCSN and entryUUID attributes? But, upgrading at least the provider to 2.3.x is probably a good idea. Regards, Buchan -- Buchan Milne ISP Systems Specialist B.Eng,RHCE(803004789010797),LPIC-2(LPI000074592)
Attachment:
pgp0j8AnODckI.pgp
Description: PGP signature