https://bugzilla.redhat.com/show_bug.cgi?id=667943
Description of problem: Unable to restart the DS instance when the ds-logpipe.py script is not running and the Named pipe file is present. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 1. Configure access logs for named pipe. Set these access log attributes using ldapmodify. nsslapd-accesslog-maxlogsperdir: 1 nsslapd-accesslog-logexpirationtime: -1 nsslapd-accesslog-logrotationtime: -1 nsslapd-accesslog: /var/log/dirsrv/slapd-$inst_name/access.pipe nsslapd-accesslog-logbuffering: off 2. Stop DS instance and run ds-logpipe.py script to create the Named pipe file. 4. Kill the ds-logpipe.py script. 5. Restart the DS insatnce 6. Result: Hangs forever. Actual results: Restart hangs forever. Expected results: As per Rich's comments, "we should figure out a way to make the write timeout if writing to a pipe".
batch update moving tickets to future
set default ticket origin to Community
Added initial screened field value.
Metadata Update from @rmeggins: - Issue set to the milestone: FUTURE
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to None (was: Needs Review) - Issue close_status updated to: None - Issue set to the milestone: 1.4.4 (was: FUTURE)
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/198
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 - Issue status updated to: Closed (was: Open)