PID file ... not readable (yet?)

Greg Hudson ghudson at
Sun Nov 5 09:57:30 EST 2017

On 11/05/2017 05:36 AM, Jaap Winius wrote:
>    systemd[1]: krb5-kdc.service: PID file /run/ \
>      not readable (yet?) after start: No such file or directory

Does everything seem to work aside from this warning message being
produced, or is there an accompanying problem?

There can be a very brief window of time between krb5kdc exiting on
startup and its child process writing the pid file.  That window is
normal for traditional Unix daemon programs (because of the way the
daemon() function works) and isn't a problem as long as nothing wants to
restart the KDC service in the first second of its life.  But it might
be enough for systemd to complain.

More information about the Kerberos mailing list