Corey Devenport via FreeIPA-users wrote:
> Corey Devenport via FreeIPA-users wrote:
>
> From getcert-list(1):
>
> NEED_GUIDANCE
> An unhandled error was encountered while attempting to contact the CA,
> or there is the service has just been told to monitor a certificate
> which does not exist and for which it has no location specified for
> storing a key pair that could be used to generate a signing request to
> obtain one.
>
> I'd check the journal for errors. It's safe to assume the cert exists in
> the database if the CA is operational.
>
> The tracking looks right. Restarting certmonger may refresh its status.
> It could be leftover from when the CA wasn't working.
>
> rob
There don't seem to be any errors in the journal...
I restarted certmonger and the status remains the same.
I'm still unable to perform any certificate operation from the webUI or through the
CLI. I get the same error of "Unable to communicate with CMS (403)"
That means the CA isn't running which could also explain the NEED_GUIDANCE.
Look in the ca debug log for details but you have to read top-down and
not bottom up.
rob