https://bugzilla.redhat.com/show_bug.cgi?id=681617
Description of problem: A replication initialisation which did not complete left an attribute in the agreement which confused the server on subsequent startups. The replication agreement in the dse.ldif contains nsds5BeginReplicaRefresh: start and on startup ... [01/Mar/2011:15:25:41 +0000] - Config Warning: - nsslapd-maxdescriptors: invalid value "8192", maximum file descriptors must range from 1 to 1024 (the current process limit). Server will use a setting of 1024. [01/Mar/2011:15:25:42 +0000] - Red Hat-Directory/8.2.4 B2011.028.1837 starting up [01/Mar/2011:15:25:43 +0000] - slapd started. Listening on All Interfaces port 389 for LDAP requests [01/Mar/2011:15:25:43 +0000] - Listening on All Interfaces port 636 for LDAPS requests [01/Mar/2011:15:30:06 +0000] NSMMReplicationPlugin - Total update aborted: Replication agreement for "agmt="cn=Rep2dir01" (dir01:389)" can not be updated while the replica is disabled
batch update to FUTURE milestone
set default ticket origin to Community
Added initial screened field value.
need to clone to RHEL BZ
I cannot reproduce the problem...
To stop the consumer initialization, usually, "nsds5beginreplicarefresh: cancel" is set to the agreement. The attribute value is left in the agreement, but it does not do any harm.
I manually replace "cancel" with "start" and restarted the server. Then, the consumer initialization is automatically restarted and completed. [..] - slapd started. Listening on All Interfaces port 389 for LDAP requests [..] NSMMReplicationPlugin - Beginning total update of replica "agmt="cn=aaa" (hostB:390)". [..] NSMMReplicationPlugin - Finished total update of replica "agmt="cn=aaa" (hostB:390)". Sent 50002 entries.
Set NEEDINFO in the original bz 681617, as well.
Since no one in the team successfully duplicated the problem and there is no new input, we are closing this ticket for now. Please feel free to reopen this bug if someone runs into this bug.
Metadata Update from @arubin: - Issue assigned to nhosoi - Issue set to the milestone: 1.3.0.rc1
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/63
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Invalid)
Login to comment on this ticket.