#47809 find a way to remove replication plugin errors messages "changelog iteration code returned a dummy entry with csn %s, skipping ..."
Closed: wontfix None Opened 9 years ago by msauton.

Sometimes, when trying to resolve replication issues, we end up with a newer message flooding the errors log from the replication plug-in:
"
changelog iteration code returned a dummy entry with csn 5385ee18000000070000, skipping ...
"
and there is no way to get rid of this messages that keeps filling the errors log file.

this is a report to find a way to try suppress this message when not necessary, in
ldap/servers/plugins/replication/windows_inc_protocol.c
ldap/servers/plugins/replication/repl5_inc_protocol.c

examples:

RHDS 9.1 RHEL 6.5 with
389-ds-base-1.2.11.15-30.el6_5.x86_64
[29/May/2014:12:29:09 -0400] agmt="cn=ds1-xp" (ds1:636) - Can't locate CSN 5385e594000000070000 in the changelog (DB rc=-30988). The consumer may need to be reinitialized.
[29/May/2014:12:29:09 -0400] NSMMReplicationPlugin - agmt="cn=ds1-xp" (ds1:636): changelog iteration code returned a dummy entry with csn 5385ee18000000070000, skipping ...

RHEL 6.4 and IPA 3 with:
389-ds-base-1.2.11.15-20.el6_4.x86_64
ipa-server-3.0.0-26.el6_4.4.x86_64
[05/Feb/2014:09:22:36 -0800] agmt="cn=meTods1.example.com" (ds1:389) - Can't locate CSN 5244d0b8000100040000 in the changelog (DB rc=-30988). The consumer may need to be reinitialized.
[05/Feb/2014:09:22:36 -0800] NSMMReplicationPlugin - agmt="cn=meTods1.example.com" (ds1:389): changelog iteration code returned a dummy entry with csn 52d42b20000000320000, skipping ...

other example:

[18/Oct/2011:13:09:57 +0000] NSMMReplicationPlugin - agmt="cn=srvAtosrvB" (srvB:389): changelog iteration code returned a dummy entry with csn 4e9d7bc2000000080000, skipping ...


Description:
1) Can't locate CSN %s in the changelog (DB rc=%d).
Print the message once per one missing CSN.
2) changelog iteration code returned a dummy entry with csn %s, skipping ...
Downgrade the log level to replication log level (SLAPI_LOG_REPL).

Thanks for reviewing the patch, Rich!

Pushed to master:
0fe78df..6a1b10d master -> master
commit 6a1b10d

Pushed to 389-ds-base-1.3.2:
3e5c14a..ddca54d 389-ds-base-1.3.2 -> 389-ds-base-1.3.2
commit ddca54d

Pushed to 389-ds-base-1.3.1:
cc38a66..e50653f 389-ds-base-1.3.1 -> 389-ds-base-1.3.1
commit e50653fffab5036e2027f99f9d2b2bf70f498e2e

Pushed to 389-ds-base-1.2.11:
cb8471b..b4248f8 389-ds-base-1.2.11 -> 389-ds-base-1.2.11
commit b4248f8

Metadata Update from @nhosoi:
- Issue assigned to nhosoi
- Issue set to the milestone: 1.2.11.30

7 years ago

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/1140

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Fixed)

3 years ago

Login to comment on this ticket.

Metadata