Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1450901
Description of problem: ======================== When the "nsslapd-localuser" is incorrect, there is no message in the errors log. Version-Release number of selected component (if applicable): ============================================================== # ns-slapd -D /etc/dirsrv/slapd-vm-idm-027/ -V | head -2 389 Project 389-Directory/1.3.6.1 B2017.125.237 How reproducible: ================== Steps to Reproduce: 1. Stop the RHDS instance 2. Edit the dse.ldif file and set the "nsslapd-localuser" to a non-existing user # grep "nsslapd-localuser" dse.ldif nsslapd-localuser: dirsrv123 # # getent passwd | grep dirsrv dirsrv:x:389:389:user for 389-ds-base:/usr/share/dirsrv:/sbin/nologin # 3. Try to start the RHDS instance. It will fail with no message in the errors log: # start-dirsrv Starting instance "vm-idm-027" Job for dirsrv@vm-idm-027.service failed because the control process exited with error code. See "systemctl status dirsrv@vm-idm-027.service" and "journalctl -xe" for details. # Actual results: ================= No message in the errors log. Expected results: ================== Log a meaningful error message. Additional info: ================= # systemctl status dirsrv@vm-idm-027.service ? dirsrv@vm-idm-027.service - 389 Directory Server vm-idm-027. Loaded: loaded (/usr/lib/systemd/system/dirsrv@.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Mon 2017-05-15 16:52:23 IST; 9s ago Process: 2231 ExecStart=/usr/sbin/ns-slapd -D /etc/dirsrv/slapd-%i -i /var/run/dirsrv/slapd-%i.pid (code=exited, status=0/SUCCESS) Process: 2435 ExecStartPre=/usr/sbin/ds_systemd_ask_password_acl /etc/dirsrv/slapd-%i/dse.ldif (code=exited, status=2) Main PID: 2231 (code=exited, status=0/SUCCESS) May 15 16:52:23 vm-idm-027.XXX systemd[1]: Starting 389 Directory Server vm-idm-027.... May 15 16:52:23 vm-idm-027.XXX ds_systemd_ask_password_acl[2435]: setfacl: Option -m: Invalid argument near character 3 May 15 16:52:23 vm-idm-027.XXX systemd[1]: dirsrv@vm-idm-027.service: control process exited, code=exited status=2 May 15 16:52:23 vm-idm-027.XXX systemd[1]: Failed to start 389 Directory Server vm-idm-027.. May 15 16:52:23 vm-idm-027.XXX systemd[1]: Unit dirsrv@vm-idm-027.service entered failed state. May 15 16:52:23 vm-idm-027.XXX systemd[1]: dirsrv@vm-idm-027.service failed.
Metadata Update from @mreynolds: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1450901
Metadata Update from @mreynolds: - Custom field type adjusted to defect - Issue set to the milestone: 1.3.7.0 (was: 0.0 NEEDS_TRIAGE)
Metadata Update from @mreynolds: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Issue set to the milestone: 1.4.2 (was: 1.3.7.0)
Metadata Update from @vashirov: - Issue priority set to: minor - Issue set to the milestone: 1.4.3 (was: 1.4.2)
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/2314
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)
Login to comment on this ticket.