Interpreting Error Messages And Symptoms - Red Hat DIRECTORY SERVER 7.1 - ADMINISTRATOR Administrator's Manual

Interpreting Error Messages and Symptoms

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 error
log level to , which is replication debugging. For details on error log level,
8192
check the Red Hat Directory Server Configuration, Command, and File Reference.
To change the error log level to
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 error log. So, use it judiciously.
To turn off replication debugging log, set the same attribute to
Error Message:
agmt=%s (%s:%d) Replica has a different generation ID than the local
data
Reason: The consumer specified at the beginning of this message has not been
(successfully) initialized yet, or it was initialized from a different root supplier.
Impact: The local supplier will not replicate any data to the consumer.
Remedy: Ignore this message if it occurs before the consumer is initialized.
Otherwise, reinitialize the consumer if the message is persistent. In a
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 the M1's Console or M1 or M2's error log). Also, M2 should
not initialize M1 back.
, run the following
8192
Troubleshooting Replication-Related Problems
command:
ldapmodify
.
0
Chapter 8 Managing Replication 369