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 statu
> 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...
> There are two
Sean McLennan via FreeIPA-users wrote:
>> You don't say what distribution or release you are running.
>
> Apologies—I meant to add that and then got distracted. They are both CentoOS
> Stream 9 running 4.9.8 (master) and 4.10.0 (replica). I was actually
> surprised they aren't the same version—I
> You don't say what distribution or release you are running.
Apologies—I meant to add that and then got distracted. They are both CentoOS
Stream 9 running 4.9.8 (master) and 4.10.0 (replica). I was actually surprised
they aren't the same version—I'm not sure how that happened TBH.
> I'd
> reco
Sean McLennan via FreeIPA-users wrote:
> Similar to a number of other posts, I have a server on which pki-tomcatd
> won't start.
>
> I just have two servers; a master and replica. I haven't upgraded anything
> recently. The problem started two days ago when the server certificates
> renewed. Th
