At the risk of smelling like a thread hijack; I’m experiencing the same issue
on one server (Fedora 25), but on all others it’s fine. I don’t think this is a
‘normal’ issue that should be ‘fixed’ by restarting named-pkcs11 all the time.
I tend to check for known issues (and solutions) on this issue from time to
time, but there doesn’t seem to be a standard issue with a standard solution
for this case (yet?).
I suppose the FreeIPA team would like a ticket, some logs, maybe some core
dumps or gdb outputs, but I’d create my own message thread or ticket and not
bother you here ;-)
> On 26 May 2017, at 19:11, Sigbjorn Lie via FreeIPA-users
> <firstname.lastname@example.org> wrote:
> I have experienced named stopping unexpectedly from time to time. After
> moving to RHEL 7 the I made use of a handy feature in systemd,
> “Restart=always”, to make sure named is kept alive.
> This has kept named alive for me, and I was wondering if this perhaps would
> be a useful addition to the default "named-pkcs11.service” shipped in RHEL?
> The changes I have done is to copy the file
> /usr/lib/systemd/system/named-pkcs11.service to
> /etc/systemd/system/named-pkcs11.service, and adding the following to
> [service] section:
> The underlying issue of why named is crashing would of course also needs to
> be investigated separately.
> What do you think?
> FreeIPA-users mailing list -- email@example.com
> To unsubscribe send an email to freeipa-users-le...@lists.fedorahosted.org
FreeIPA-users mailing list -- firstname.lastname@example.org
To unsubscribe send an email to freeipa-users-le...@lists.fedorahosted.org