Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 8): Bug 1836428
Description of problem: Requesting an Enhancement to ds-replcheck monitoring tool. The customer is getting periodic ldap.TIMEOUT errors between East coast & West coast servers. We have increased timeouts for Directory Server replication, and are not having any data or replication issues, but the reporting tool does not also allow them to increase any ldap communication/query wait times. Version-Release number of selected component (if applicable): actual Directory Server version unknown, in use with IdM, we assume a 10.something 389-ds-base-1.3.9.1-13.el7_7.x86_64 How reproducible: periodic issue Steps to Reproduce: 1. run ds-replcheck periodically Actual results: Performing online report... Connecting to servers... Validating suffix ... Gathering Master's RUV... Gathering Replica's RUV... Start searching and comparing... Traceback (most recent call last): File "/usr/bin/ds-replcheck", line 1394, in <module> main() File "/usr/bin/ds-replcheck", line 1386, in main do_online_report(opts, OUTPUT_FILE) File "/usr/bin/ds-replcheck", line 1138, in do_online_report r_rtype, r_rdata, r_rmsgid, r_rctrls = replica.result3(replica_msgid) File "/usr/lib64/python2.7/site-packages/ldap/ldapobject.py", line 469, in result3 resp_ctrl_classes=resp_ctrl_classes File "/usr/lib64/python2.7/site-packages/ldap/ldapobject.py", line 476, in result4 ldap_result = self._ldap_call(self._l.result4,msgid,all,timeout,add_ctrls,add_intermediates,add_extop) File "/usr/lib64/python2.7/site-packages/ldap/ldapobject.py", line 99, in _ldap_call result = func(*args,**kwargs) ldap.TIMEOUT
Metadata Update from @mreynolds: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1836428
Metadata Update from @mreynolds: - Issue assigned to mreynolds
Metadata Update from @mreynolds: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Issue set to the milestone: 1.3.10 (was: 0.0 NEEDS_TRIAGE) - Issue tagged with: CLI, RFE
https://pagure.io/389-ds-base/pull-request/51103
Commit c350ddc relates to this ticket
c32469c..6102669 389-ds-base-1.4.3 -> 389-ds-base-1.4.3
1076fce..a267875 389-ds-base-1.4.2 -> 389-ds-base-1.4.2
9c545b9..8c8b1aa 389-ds-base-1.4.1 -> 389-ds-base-1.4.1
Metadata Update from @mreynolds: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Commit b1e4f5f relates to this ticket
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/4155
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: fixed)
Login to comment on this ticket.