14.02.2014 Views

ldapv3.pdf 7947KB Apr 17 2013 11:30:42 AM - mirror omadata

ldapv3.pdf 7947KB Apr 17 2013 11:30:42 AM - mirror omadata

ldapv3.pdf 7947KB Apr 17 2013 11:30:42 AM - mirror omadata

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

The Rejection Log<br />

The rejection log format is very similair to that of the replication log except that each<br />

transaction begins with the specification of the error that caused replication to fail.<br />

Sample Rejection Log Content<br />

ERROR: No such object<br />

replica: india-north.whitemice.org:389<br />

time: 1015245<strong>30</strong>3.0<br />

dn: cn=nt1000 Machine Account,ou=SystemAccounts,dc=Whitemice,dc=Org<br />

changetype: delete<br />

ERROR: Constraint violation<br />

replica: india-north.whitemice.org:389<br />

time: 1015245328.0<br />

dn: uid=NT1000$,ou=System Accounts,dc=whitemice,dc=org<br />

changetype: modify<br />

replace: uid<br />

uid: NT1000$<br />

-<br />

replace: uidNumber<br />

uidNumber: 525<br />

-<br />

The replica did not contain the<br />

object modified on the master.<br />

The slave and master must have<br />

been previously out of sync.<br />

Transactions are seperated<br />

by a single blank line.<br />

The modifcation requests<br />

violated the schema known to<br />

the slave or its structure.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!