Auerbach, Steven via FreeIPA-users wrote: > A storage subsystem failure below our virtualization layer caused a hard > crash of our 2^nd IPA Master. It will not start back up. > > $ Systemctl status –l ipa > > ● ipa.service - Identity, Policy, Audit > > Loaded: loaded (/usr/lib/systemd/system/ipa.service; enabled; vendor > preset: disabled) > > Active: failed (Result: exit-code) since Fri 2021-08-06 15:47:24 EDT; > 3 days ago > > Process: 1554 ExecStart=/usr/sbin/ipactl start (code=exited, > status=1/FAILURE) > > Main PID: 1554 (code=exited, status=1/FAILURE) > > > > Aug 06 15:46:46 ipa04.fbog.local systemd[1]: Starting Identity, Policy, > Audit... > > Aug 06 15:47:24 ipa04.fbog.local ipactl[1554]: Failed to start Directory > Service: Command '/bin/systemctl start [email protected]' > returned non-zero exit status 1 > > Aug 06 15:47:24 ipa04.fbog.local ipactl[1554]: Starting Directory Service > > Aug 06 15:47:24 ipa04.fbog.local systemd[1]: ipa.service: main process > exited, code=exited, status=1/FAILURE > > Aug 06 15:47:24 ipa04.fbog.local systemd[1]: Failed to start Identity, > Policy, Audit. > > Aug 06 15:47:24 ipa04.fbog.local systemd[1]: Unit ipa.service entered > failed state. > > Aug 06 15:47:24 ipa04.fbog.local systemd[1]: ipa.service failed. > > > > Multiple OS restarts do not clear this. There must be a pid file > somewhere to delete. Not sure where to look in documentation or a > meaningful search expression for researching the web. > > Help?
You need to look in the 389-ds error log for details, /var/log/dirsrv/slapd-FBOG-LOCAL/errors rob _______________________________________________ FreeIPA-users mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/[email protected] Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
