On 11/15/2014 10:30 AM, Ivanov Andrey (M.) wrote:
we've migrated our production systems to 389ds version 22.214.171.124. Everything seems
fine now, the only new messages i see in error logs (several times per day) are
[15/Nov/2014:03:58:43 +0100] - replica_generate_next_csn: opcsn=5466c164000000010000
<= basecsn=5466c164000000020000, adjusted opcsn=5466c164000100010000
[15/Nov/2014:10:38:38 +0100] - replica_generate_next_csn: opcsn=54671f1f000000010000
<= basecsn=54671f1f000000030000, adjusted opcsn=54671f1f000100010000
Are these only information messages that can be safely ignored or they may be a
manifestation of some potential problem?
This looks ok to me, and the message should not be a fatal message. The
code handles this correctly by incrementing the sequence number and
updating the generator. In practice it should be very difficult to get
the generator to generate a CSN like this. Are all of these machines
running in VMs? If so, what is the hypervisor? How many of these do
you see per day?
In source code (./ldap/servers/plugins/replication/repl5_replica.c)
it looks like a serious one (SLAPI_LOG_FATAL):
slapi_log_error (SLAPI_LOG_FATAL, NULL,
"opcsn=%s <= basecsn=%s, adjusted opcsn=%s\n",
opcsnstr, basecsnstr, opcsn2str);
It should not be FATAL. Please file a ticket.
389 users mailing list