HP-UX Directory Server Administrator Guide HP-UX Directory Server Version 8.1 (5900-3098, May 2013)

access";allow (read, search, compare)(userdn = "ldap:///anyone");)
-
add: aci
aci: (target="ldap:///dc=example,dc=com")(targetattr!="userPassword")
(targetfilter="(!(nsds5ReplConflict=*))")(version 3.0;acl
"Anonymous read-search access";allow (read, search, compare)
(userdn="ldap:///anyone");)
-
The new ACI filters out all entries that contain the nsds5ReplConflict attribute from search
results.
For more information on the ldapmodify command, see “Managing Entries from the Command
line” (page 111) and the HP-UX Directory Server configuration, command, and file reference.
8.19 Troubleshooting replication-related problems
This section lists some error messages, explains possible causes, and offers remedies.
It is possible to get more debugging information for replication by setting the errors log level to
8192, which is replication debugging. See “Troubleshooting replication-related problems” (page
388).
To change the errors log level to 8192, run the following ldapmodify command:
dn: cn=config
changetype: modify
replace: nsslapd-errorlog-level
nsslapd-errorlog-level: 8192
Because log level is additive, running the above command will result in excessive messages in the
errors log. So, use it judiciously.
To turn off replication debugging log, set the same attribute to 0.
The cl-dump.pl script, which is explained in detail in the HP-UX Directory Server configuration,
command, and file reference can also help troubleshoot replication-related problems. Depending
on the usage options, the script can selectively dump a particular replica:
• Dump the contents of a replication-change-log file and in-memory variables purge
RUV and maxRUV.
• grep and interpret change sequence numbers (CSNs) in the changelog.
• Get the base-64 encoded changelog from the Directory Server, then decode the changelog.
Many common replication problems are described in Table 42 (page 388).
Table 42 Replication errors
RemedyImpactReasonError/symptom
Ignore this message if it
occurs before the consumer is
The local supplier will not
replicate any data to the
consumer.
The consumer specified at
the beginning of this
message has not been
agmt=%s (%s:%d) Replica
has a different generation ID
than the local data.
initialized. Otherwise,
reinitialize the consumer if the(successfully) initialized yet,
message is persistent. In aor it was initialized from a
different root supplier. multi-master environment, all
the servers should be
initialized only once from a
root supplier, directly or
indirectly. For example, M1
initializes M2 and M4, M2
then initializes M3, and so
on. The important thing to
note is that M2 must not start
initializing M3 until M2's own
initialization is done (check
the total update status from
388 Managing Replication