https://bugzilla.redhat.com/show_bug.cgi?id=754474
Description of problem: slapd process exits when put the database on read only mode while updates are coming to the server. Version-Release number of selected component (if applicable): 389 1.2.0 How reproducible: Sometime Steps to Reproduce: 1. Put the database on readonly mode while the updates are coming to the server. 2. 3. Actual results: "ns-salpd" process exits. Expected results: Additional info:
0001-Ticket-13-slapd-process-exits-when-put-the-database-.patch 0001-Ticket-13-slapd-process-exits-when-put-the-database-.patch
To ssh://git.fedorahosted.org/git/389/ds.git 19f290d..9fd4e09 master -> master commit changeset:9fd4e09/389-ds-base Author: Rich Megginson rmeggins@redhat.com Date: Wed Feb 1 14:01:52 2012 -0700 Reviewed by: mreynolds (Thanks!) Branch: master Fix Description: Make the log level REPL instead of FATAL - get rid of the assert Platforms tested: RHEL6 x86_64 Flag Day: no Doc impact: no
Added initial screened field value.
Metadata Update from @rmeggins: - Issue assigned to rmeggins - Issue set to the milestone: 1.2.10.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/13
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.