Yes, check the errors log file liek mentioned, and/or the systemd 's dirsrv status , and/or journalctl -r --unit=dirsrv@\*
Without logs, I will just speculate the ns-slapd daemon needed the key file password at restart, and was waiting at a prompt, then eventually timed out.
if this is the case, check the admin guide at either
9.4.1.4. Starting Directory Server Without a Password File
or
9.4.1.5. Creating a Password File for Directory Server
Thanks,
M.
On Wed, Apr 18, 2018 at 10:23 AM, Paul Whitney <paul.whitney@xxxxxxx> wrote:
Hi Jeremy,I would look at the /var/log/dirsrv/admin-serv/error and /var/log/dirsrv/slapd-config/ errors files to see what is preventing you from starting the services. I am following the Red Hat Directory Server 10 Admin Guide under section 9.4.1.2. So far I have been able to create the certificates and database and getting the certs imported to the proper locations. My issue happens when I attempt to restart the services. The service eventually just times out trying to restart and I get a message "the server could not be restarted". I end up losing the changes I had just made in the console. I have tried to review my settings to be sure I didn't overlook something and everything seems to be ok. What logs should I be reviewing to see why the service isn't restarting properly?
_______________________________________________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org
_______________________________________________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org
_______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
