Sean McLennan via FreeIPA-users wrote: >> The 404's you see are because the CA didn't successfully start but >> tomcat did. So there is no registered servlet associated with the URI. > > Oh—just for future reference, is there somewhere that can be seen (aside from > ipa-healthcheck)? ipactl status shows everything running...
Right. We can't easily test whether the applications within tomcat are running via systemd IIRC. Best we can do is see if tomcat is running. A simple way is: ipa cert-show 1. As long as it doesn't return an error the communication is working. This also exercises the RA cert. >> There are two replication agreements. One for the IPA data >> (ipa-replica-manage) and one for the PKI data (ipa-csreplica-manage). > > Ah! Also good to know—I did not realize. > >> I'd try the force-sync command first to see if you can kickstart >> replication. If that fails then a re-init is probably in order. > > The force-sync did not work, but re-init did and everything seems to be OK > now. OK. Glad you're back up and running again. 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, report it: https://pagure.io/fedora-infrastructure/new_issue
