Brian J. Murrell via FreeIPA-users wrote:
> I've been experiencing certmonger taking (too) long to start up and
> systemd ends up giving up on it:
>
> Mar 25 08:47:41 server.interlinx.bc.ca systemd[1]: Starting Certificate
> monitoring and PKI enrollment...
> Mar 25 08:49:24 server.interlinx.bc.c
On Mon, 2018-03-26 at 10:30 -0400, Rob Crittenden via FreeIPA-users
wrote:
> Brian J. Murrell via FreeIPA-users wrote:
> > I've been experiencing certmonger taking (too) long to start up and
> > systemd ends up giving up on it:
> >
> > Mar 25 08:47:41 server.interlinx.bc.ca systemd[1]: Starting
>
Brian J. Murrell via FreeIPA-users wrote:
> On Mon, 2018-03-26 at 10:30 -0400, Rob Crittenden via FreeIPA-users
> wrote:
>> Brian J. Murrell via FreeIPA-users wrote:
>>> I've been experiencing certmonger taking (too) long to start up and
>>> systemd ends up giving up on it:
>>>
>>> Mar 25 08:47:41
On Mon, 2018-03-26 at 14:50 -0400, Rob Crittenden via FreeIPA-users
wrote:
>
> Sure looks like the problem is in the selfsign CA. Can you start
> certmonger from the command-line in debug mode to see if there is any
> indication why?
>
> # certmonger -d 9 -n
2018-03-26 15:09:42 [10537] Starting
On Mon, 2018-03-26 at 15:19 -0400, Brian J. Murrell via FreeIPA-users
wrote:
> On Mon, 2018-03-26 at 14:50 -0400, Rob Crittenden via FreeIPA-users
> wrote:
> >
> > Sure looks like the problem is in the selfsign CA. Can you start
> > certmonger from the command-line in debug mode to see if there is
