Thanks guys for the responses. So I was missing the overlay declaration in the slapd.conf file but now I'm running into another problem that no else seems to have either. Here are the log messages:
Sep 12 10:46:35 ldap3 slapd[27342]: syncrepl_entry: rid=001 LDAP_RES_SEARCH_ENTRY(LDAP_SYNC_ADD) Sep 12 10:46:35 ldap3 slapd[27342]: dn_callback : entries have identical CSN dc=example,dc=com 20080623052654.050277Z#000000#000#000000 Sep 12 10:46:35 ldap3 slapd[27342]: syncrepl_entry: rid=001 be_search (0) Sep 12 10:46:35 ldap3 slapd[27342]: syncrepl_entry: rid=001 dc=example,dc=com Sep 12 10:46:35 ldap3 slapd[27342]: syncrepl_entry: rid=001 entry unchanged, ignored (dc=example,dc=com) Sep 12 10:46:35 ldap3 slapd[27342]: syncrepl_entry: rid=001 LDAP_RES_SEARCH_ENTRY(LDAP_SYNC_ADD) Sep 12 10:46:35 ldap3 slapd[27342]: syncrepl_entry: rid=001 be_search (0) Sep 12 10:46:35 ldap3 slapd[27342]: syncrepl_entry: rid=001 cn=admin,dc=example,dc=com Sep 12 10:46:35 ldap3 slapd[27342]: Entry (cn=admin,dc=example,dc=com): object class 'simpleSecurityObject' requires attribute 'userPassword' Sep 12 10:46:35 ldap3 slapd[27342]: entry failed schema check: object class 'simpleSecurityObject' requires attribute 'userPassword' Sep 12 10:46:35 ldap3 slapd[27342]: null_callback : error code 0x41 Sep 12 10:46:35 ldap3 slapd[27342]: syncrepl_entry: rid=001 be_modify (65) Sep 12 10:46:35 ldap3 slapd[27342]: syncrepl_entry: rid=001 be_modify failed (65) Sep 12 10:46:35 ldap3 slapd[27342]: do_syncrepl: rid=001 retrying The "rootdn" and "rootpw" are set so I'm not sure which password would be missing. Also, the weird thing is that replication worked for a while, I only ever populated one server and it was replicated over to the consumer even without the overlay declaration. Scott On Fri, Sep 12, 2008 at 9:41 AM, Howard Chu <[EMAIL PROTECTED]> wrote: > Brett @Google wrote: >> >> check that you have not forgotten "overlay syncrepl" on the master >> that is printing that error > > overlay syncprov, and the error is printed on the consumer, not the master. > >> that's one case where i've seen this error, does not mean it's your >> problem though.. >> >> i interpret that message as meaning it's getting a client request to >> do syncrepl, but the server is saying it does not know what syncrepl >> is. if not that could be a configuration issue do do with syncrepl ? > > It means the consumer sent a syncrepl request but didn't get any sync info > in the reply. It almost always means there was no syncprov overlay > configured on the master. >> >> Cheers >> Brett >> >> On Fri, Sep 12, 2008 at 2:25 PM, Scott Briggs<[EMAIL PROTECTED]> wrote: >>> >>> Hi, I'm trying to figure out a problem I'm having with an ldap server >>> that stopped replicating with log entries like: >>> >>> do_syncrep2: rid=002 got search entry without Sync State control >>> do_syncrepl: rid=001 retrying >>> >>> So can anyone tell me what "got search entry without sync state >>> control" means? I could only find 1 other reference to someone who >>> had this error but nothing was mentioned about what this means. I'm >>> running openldap ver. 2.4.9 in a multimaster setup (2 servers) on >>> Ubuntu hardy. Thanks. >>> >>> Scott >>> >> > > > -- > -- Howard Chu > CTO, Symas Corp. http://www.symas.com > Director, Highland Sun http://highlandsun.com/hyc/ > Chief Architect, OpenLDAP http://www.openldap.org/project/ >
