Bug 1103337
Summary: | find a way to remove replication plugin errors messages "changelog iteration code returned a dummy entry with csn %s, skipping ..." | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Marc Sauton <msauton> | |
Component: | 389-ds-base | Assignee: | Noriko Hosoi <nhosoi> | |
Status: | CLOSED ERRATA | QA Contact: | Sankar Ramalingam <sramling> | |
Severity: | high | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 6.5 | CC: | amsharma, jgalipea, msauton, nhosoi, nkinder, rmeggins | |
Target Milestone: | pre-dev-freeze | |||
Target Release: | 6.6 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | 389-ds-base-1.2.11.15-34.el6 | Doc Type: | Bug Fix | |
Doc Text: |
Cause: Message "changelog iteration code returned a dummy entry with csn %s, skipping ..." is coded as an error level, which should not be.
Consequence: Once the server runs into the state, the benign error is logged in the error log repeatedly.
Fix: Changed the log level to replication log level.
Result: Unless the log level is set to the replication log level, the message is not logged in the error log.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1108405 (view as bug list) | Environment: | ||
Last Closed: | 2014-10-14 07:55:12 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1108405 |
Description
Marc Sauton
2014-05-30 19:04:42 UTC
added upstream ticket https://fedorahosted.org/389/ticket/47809 find a way to remove replication plugin errors messages "changelog iteration code returned a dummy entry with csn %s, skipping ..." Is this error coming when the replication error log level is enabled? Can this be reproduced in QE environment? (In reply to Sankar Ramalingam from comment #3) > Is this error coming when the replication error log level is enabled? > Can this be reproduced in QE environment? I ran this test first: https://bugzilla.redhat.com/show_bug.cgi?id=1080185#c1 then checked the error log to make sure there is ... 1) no "changelog iteration code returned ..." message is loged, and 2) no duplicate of "Can't locate CSN 539946eb000b00020000 in the changelog" message. [root@dhcp201-155 export]# tail -f /var/log/dirsrv/slapd-M1/errors [14/Aug/2014:08:13:17 -0400] attrcrypt - No symmetric key found for cipher AES in backend repman, attempting to create one... [14/Aug/2014:08:13:17 -0400] attrcrypt - Key for cipher AES successfully generated and stored [14/Aug/2014:08:13:17 -0400] attrcrypt - No symmetric key found for cipher 3DES in backend repman, attempting to create one... [14/Aug/2014:08:13:17 -0400] attrcrypt - Key for cipher 3DES successfully generated and stored [14/Aug/2014:08:13:17 -0400] - slapd started. Listening on All Interfaces port 30100 for LDAP requests [14/Aug/2014:08:13:17 -0400] - Listening on All Interfaces port 30101 for LDAPS requests [14/Aug/2014:08:15:26 -0400] NSMMReplicationPlugin - agmt="cn=M1_to_M2" (dhcp201-155:30103): Replica has a different generation ID than the local data. [14/Aug/2014:08:15:27 -0400] NSMMReplicationPlugin - agmt="cn=M1_to_M4" (dhcp201-155:30107): Replica has a different generation ID than the local data. [14/Aug/2014:08:16:57 -0400] NSMMReplicationPlugin - Beginning total update of replica "agmt="cn=M1_to_M2" (dhcp201-155:30103)". [14/Aug/2014:08:17:02 -0400] NSMMReplicationPlugin - Finished total update of replica "agmt="cn=M1_to_M2" (dhcp201-155:30103)". Sent 160 entries. ^C [root@dhcp201-155 export]# rpm -qa | grep 389 389-admin-debuginfo-1.1.34-1.el6.x86_64 389-ds-base-1.2.11.15-39.el6.x86_64 389-ds-base-debuginfo-1.2.11.15-36.el6.x86_64 389-adminutil-1.1.17-1.el6.x86_64 389-adminutil-debuginfo-1.1.17-1.el6.x86_64 389-ds-base-libs-1.2.11.15-39.el6.x86_64 389-console-1.1.7-1.el6.noarch Hence Verified. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-1385.html |