I did a 389 install using yum and setup-ds-admin.pl on Fedora 21.
I can't get my slapd server to start when the machine boots. It is enabled and can be started manually but will not start when the server starts. Ideas?
[root@binf2 slapd-binf2]# systemctl status dirsrv@binf2.service â dirsrv@binf2.service - 389 Directory Server binf2. Loaded: loaded (/usr/lib/systemd/system/dirsrv@.service; enabled) Active: active (running) since Mon 2015-07-13 13:57:49 EDT; 38min ago Process: 1445 ExecStart=/usr/sbin/ns-slapd -D /etc/dirsrv/slapd-%i -i /var/run/dirsrv/slapd-%i.pid -w /var/run/dirsrv/slapd-%i.startpid (code=exited, status=0/SUCCESS) Main PID: 1446 (ns-slapd) CGroup: /system.slice/system-dirsrv.slice/dirsrv@binf2.service ââ1446 /usr/sbin/ns-slapd -D /etc/dirsrv/slapd-binf2 -i /var/run/dirsrv/slapd-binf2.pid -w /var/run/dirsrv/slapd-binf2.startpid
There are no errors in /var/log/dirsrv/slapd-binf2/errors.
Enabling the individual dirsrv'at sign'binf2.service did not work but enabling the dirsrv target did so that works for me.
Metadata Update from @mryanfda: - Issue set to the milestone: N/A
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/1552
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: Invalid)
Login to comment on this ticket.