[Freeipa-users] Re: Request failed with status 500: Non-2xx response from CA REST API: 500. - pki-tomcatd fails to start

2017-09-12 Thread Rob Crittenden via FreeIPA-users
Winfried de Heiden wrote: > Hi all, > > Yes, there was a discrepancy in de certificates and was fixed by using > https://floblanc.wordpress.com/2017/09/11/troubleshooting-freeipa-pki-tomcatd-fails-to-start/. > > Thanks for that! > > Now, getcert ist still shows errors. The certmonger logs shows:

[Freeipa-users] Re: Request failed with status 500: Non-2xx response from CA REST API: 500. - pki-tomcatd fails to start

2017-09-12 Thread Winfried de Heiden via FreeIPA-users
Hi all, Yes, there was a discrepancy in de certificates and was fixed by using https://floblanc.wordpress.com/2017/09/11/troubleshooting-freeipa-pki-tomcatd-fails-to-start/. Thanks for that! Now, getcert ist still shows errors. The certmonger

[Freeipa-users] Re: Request failed with status 500: Non-2xx response from CA REST API: 500. - pki-tomcatd fails to start

2017-09-12 Thread Florence Blanc-Renaud via FreeIPA-users
On 09/12/2017 09:10 AM, Winfried de Heiden via FreeIPA-users wrote: Hi all, I'll try my using the link provided. However: what is causing "CA_UNREACHABLE"? Request ID '20170129002017':     status: CA_UNREACHABLE     ca-error: Server at https://ipa.blabla.bla/ipa/xml failed request, will re

[Freeipa-users] Re: Request failed with status 500: Non-2xx response from CA REST API: 500. - pki-tomcatd fails to start

2017-09-12 Thread Winfried de Heiden via FreeIPA-users
Hi all, I'll try my using the link provided. However: what is causing "CA_UNREACHABLE"? Request ID '20170129002017':     status: CA_UNREACHABLE     ca-error: Server at https://ipa.blabla.bla/ipa/xml failed request, will retry: 4035 (RPC f