Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1394000
Description of problem: If you attempt to run dbmon.sh on a DS server with nsslapd-require-secure-binds: on, dbmon.sh fails to connect. There probably should be an option to use TLS. Version-Release number of selected component (if applicable): 389-ds-base-1.3.5.10-11.el7.x86_64 How reproducible: always Steps to Reproduce: Set cn=config attribute nsslapd-require-secure-binds=on and run dbmon.sh Actual results: VERBOSE=2 /usr/sbin/dbmon.sh Thu Nov 10 19:29:13 UTC 2016 ldap_bind: Confidentiality required (13) additional info: Operation requires a secure connection awk: cmd. line:84: fatal: division by zero attempted
Metadata Update from @mreynolds: - Issue set to the milestone: 1.3.6.0
Metadata Update from @mreynolds: - Issue assigned to mreynolds
<img alt="0001-Issue-49065-dbmon.sh-fails-if-you-have-nsslapd-requi.patch" src="/389-ds-base/issue/raw/files/7f0509925c6b3eebecbc3104148fe46d8565214b4d7922eca17fd26cb528a742-0001-Issue-49065-dbmon.sh-fails-if-you-have-nsslapd-requi.patch" />
Metadata Update from @mreynolds: - Custom field origin adjusted to RHCust (was: Community) - Custom field reviewstatus adjusted to review - Issue close_status updated to: None
Looks good to me, ack
Metadata Update from @firstyear: - Custom field reviewstatus adjusted to ack (was: review)
13e89e5..eef2ee8 master -> master
Metadata Update from @mreynolds: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
3f4c67f..f057563 389-ds-base-1.3.5 -> 389-ds-base-1.3.5
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/2124
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.