CentOS 7.x troubleshooting 389-DS issues
From Notes_Wiki
<yambe:breadcrumb>CentOS_7.x_389DS|CentOS 7.x 389DS</yambe:breadcrumb>
CentOS 7.x troubleshooting 389-DS issues
389-ds fails to start after force reboot
After force reboot if 389 fails to restart with following log lines in journalctl:
journalctl -xe | grep -v named | grep systemd | tail -50 May 01 16:25:01 server4.rishivalley.org systemd[1]: dirsrv@server4.service: main process exited, code=exited, status=1/FAILURE May 01 16:25:01 server4.rishivalley.org systemd[1]: Failed to start 389 Directory Server server4.. -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel May 01 16:25:01 server4.rishivalley.org systemd[1]: Unit dirsrv@server4.service entered failed state. May 01 16:25:01 server4.rishivalley.org systemd[1]: dirsrv@server4.service failed. May 01 16:25:15 server4.rishivalley.org systemd[1]: Cannot add dependency job for unit microcode.service, ignoring: Unit is not loaded properly: Invalid argument. May 01 16:25:15 server4.rishivalley.org systemd[1]: Starting 389 Directory Server server4.... -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel May 01 16:25:15 server4.rishivalley.org ds_systemd_ask_password_acl[22991]: grep: /etc/dirsrv/slapd-server4/dse.ldif: No such file or directory May 01 16:25:15 server4.rishivalley.org systemd[1]: dirsrv@server4.service: main process exited, code=exited, status=1/FAILURE May 01 16:25:15 server4.rishivalley.org systemd[1]: Failed to start 389 Directory Server server4.. -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel May 01 16:25:15 server4.rishivalley.org systemd[1]: Unit dirsrv@server4.service entered failed state. May 01 16:25:15 server4.rishivalley.org systemd[1]: dirsrv@server4.service failed.
Note grep: /etc/dirsrv/slapd-server4/dse.ldif: No such file or directory then as per https://www.redhat.com/archives/freeipa-users/2014-April/msg00330.html use following commands to resolve the issue:
cd /etc/dirsrv/slapd-MYINSTANCE cp -p dse.ldif.startOK dse.ldif
Note as per above link:
- bak2db is only for the actual database data files (e.g. the files in /var/lib/dirsrv/slapd-MYINSTANCE/db)
Other useful references:
- https://www.redhat.com/archives/freeipa-users/2012-August/msg00129.html
- https://access.redhat.com/documentation/en-US/Red_Hat_Directory_Server/8.0/html/Administration_Guide/Backing_Up_and_Restoring_Data-Restoring_a_Single_Database.html
- https://forums.fedoraforum.org/showthread.php?301716-389-ds-Unit-dirsrv-service-failed-to-load-no-such-file-or-directory
<yambe:breadcrumb>CentOS_7.x_389DS|CentOS 7.x 389DS</yambe:breadcrumb>
