On Tue, Apr 05, 2011 at 10:33:24AM +0200, Olivier PAVILLA wrote:
> Apr 5 06:28:38 luz2 slapd[21213]: syncrepl_message_to_entry: rid=008
> mods check (objectClass: value #4 invalid per syntax)
> Apr 5 06:28:38 luz2 slapd[21213]: do_syncrepl: rid=008 retrying
> Apr 5 06:38:38 luz2 slapd[21213]: do_syncrep2: rid=008
> LDAP_RES_INTERMEDIATE - SYNC_ID_SET
[snip]
> Apr 5 06:38:50 luz2 slapd[21213]: syncrepl_message_to_entry: rid=008
> mods check (objectClass: value #4 invalid per syntax)
> Apr 5 06:38:50 luz2 slapd[21213]: do_syncrepl: rid=008 retrying
>
> Someone or anyone could tell me what's wrong?
> I didn't change anything on my server for several months. So suddenly I
> got those lines. Who can explain to me?
The "objectClass: value #4 invalid per syntax" indicates
that your consumer (slave) slapd doesn't have the correct
schemas installed, and doesn't recognize an objectClass
of an entry that the provder (master) is sending. This
is causing the synchronization to fail, but is easily
fixed: just install the necessary schemas on the consumer.
The SYNC_ID_SET messages in this case are the provider
telling the consumer what entries it has, so the consumer
can delete entries not present on the provider. This is
normal operation in some situations. It shouldn't happen
too often if you specify a sufficient sessionlog size on
the provider.
--
Chris Mikkelson | Setting delivery schedules is easy enough using the
cmikk@qwest.net | I Ching, astrology, psychic hotlines, or any of the
| well-known scatomantic and necromantic methodologies.
| Meeting your prophetic deadlines, though, is another
| bowl of entrails. -- Stan Kelly-Bootle
Attachment:
pgpk3b8Ua8QtG.pgp
Description: PGP signature