On Thu, 2025-10-09 at 16:33 -0400, Rob Crittenden via FreeIPA-users wrote: > > > pki-tomcatd@pki-tomcat is timing itself out.
I don't think it is: Oct 08 13:19:46 server.interlinx.bc.ca ipa-pki-wait-running[1760]: ipa-pki-wait-running: Reached end of wait timeout 600, giving up So it does seem to be waiting the increased 600s timeout. > Increasing the > startup_timeout in /etc/ipa/*.conf is not sufficient. The systemd > start > timeout needs to be updated as well (blame the systemd folks, not > us). Indeed, it was. But I have already addressed that: # cat /etc/systemd/system/[email protected]/override.conf [Service] TimeoutStartSec=2400 But again, I want to stop guessing at how long the timeout needs to be and look in the journal at the (mysterious, to me) service that is providing the queried CA endpoint to see how long it's actually taking to start using the systemd log messages. So which systemd unit is providing the queried CA endpoint? Cheers, b. -- _______________________________________________ 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
