On 10/19/18 6:49 AM, Z D via FreeIPA-users wrote:
Hi there,
This is el7.3 running ipa-server 4.4.0 release 12.0.1.el7.
After reboot I couldn't start ipa service via systemctl, hence I run
"ipactl start --ignore-service-failures" and this was kind of
successful. I still have some discrepancies, and looking for
troubleshooting ideas.
1. "systemctl status ipa.service" reads that service failed
2. "systemctl status pki-tomcatd.target" reads that PKI Tomcat Server
is running.
Hi,
The PKI service status can be found using "systemctl status
pki-tomcatd(a)pki-tomcat.service".
More details on the differences between targets and units can be found
in the man pages for systemd.unit(5) and systemd.target(5).
3.
# ipactl status
Directory Service: RUNNING
krb5kdc Service: RUNNING
kadmin Service: RUNNING
named Service: RUNNING
ipa_memcached Service: RUNNING
httpd Service: RUNNING
ipa-custodia Service: RUNNING
ntpd Service: RUNNING
pki-tomcatd Service: STOPPED <---- !!
ipa-otpd Service: RUNNING
ipa-dnskeysyncd Service: RUNNING
ipa: INFO: The ipactl command was successful
To troubleshoot, you can have a look at the output of
# systemctl status pki-tomcatd(a)pki-tomcat.service
and the logs in /var/log/pki/pki-tomcat/ca/debug.
I would start by checking if some certificates expired with getcert list
(check the status, should be MONITORING, and the expires: <date>).
HTH,
flo
Well, why pki-tomcatd reads 'stopped' and how to make systemctl to
recognize that ipa service is running, thanks in advance,
Zarko
_______________________________________________
FreeIPA-users mailing list -- freeipa-users(a)lists.fedorahosted.org
To unsubscribe send an email to freeipa-users-leave(a)lists.fedorahosted.org
Fedora Code of Conduct:
https://getfedora.org/code-of-conduct.html
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedorahosted.org/archives/list/freeipa-users@lists.fedoraho...