Description of problem: "named" service doesn't start on Fedora 17 Version-Release number of selected component (if applicable): bind-9.9.0-4.fc17.x86_64 How reproducible: Always. Steps to Reproduce: selinux is disabled bind-chroot is not installed Call "systemctl start named.service" Actual results: "systemctl start named.service" hangs, and after some waiting tells that service unit failed. /var/log/messages contains the following message: May 30 21:32:13 home systemd[1]: PID file /run/named/named.pid not readable (yet?) after start. May 30 21:32:33 home named[4083]: shutting down May 30 21:32:33 home named[4083]: stopping command channel on 127.0.0.1#953 May 30 21:32:33 home named[4083]: stopping command channel on ::1#953 May 30 21:32:33 home named[4083]: no longer listening on 127.0.0.1#53 May 30 21:32:33 home named[4083]: no longer listening on 192.168.1.2#53 May 30 21:32:33 home named[4083]: no longer listening on 192.168.66.1#53 May 30 21:32:33 home named[4083]: exiting Expected results: named should start and continue to run Additional info: I couldn't find directory /run/named, and systemd-tmpfiles --create ... doesn't help because /etc/tmpfiles.d/named has only one line: "d /var/run/named 0755 named named -" named creates its' PID file as /var/run/named/named.pid by default (that's what "man named" told me) and the default /etc/named.conf doesn't have option "pid-file" The solution was: 1. add "d /run/named 0755 named named -" into /etc/tmpfiles.d so it should be d /var/run/named 0755 named named - d /run/named 0755 named named - 2. add pid-file "/run/named.pid"; option into default named.conf
Ough, sorry that's not a bind bug! Something goes wrong so /run and /var/run isn't the same after last update, that's more a systemd issue :-(