Take the 2-minute tour ×
Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems.. It's 100% free, no registration required.
Feb 24 15:54:34 ns1 named[20308]: all zones loaded
Feb 24 15:54:34 ns1 named[20308]: running
Feb 24 15:54:34 ns1 systemd[1]: PID file /var/run/named/named.pid not readable (yet?) after start.
Feb 24 15:56:03 ns1 systemd[1]: named.service operation timed out. Terminating.
Feb 24 15:56:03 ns1 named[20308]: shutting down
Feb 24 15:56:03 ns1 named[20308]: stopping command channel on 0.0.0.0#953
Feb 24 15:56:03 ns1 named[20308]: exiting

I have tried renaming to named.service as mentioned here: named does't start when using systemctl

share|improve this question
    
what does ls -l /var/run/named/ show –  X Tian Feb 24 at 16:33
    
@XTian # ls -l /var/run/named/ total 4 -rw------- 1 named named 102 Feb 24 15:25 session.key –  SavageCore Feb 24 at 16:36

1 Answer 1

up vote 1 down vote accepted

This looks to be a bug. See this ticket titled: Bug 984764 - bind-chroot-9.9.3-3.P1.fc19.x86_64 failed to start.

The fix is to add this to your named.conf file:

pid-file      "/var/run/named/named.pid";

There are additional tips in the ticket with respect to getting your system back into a state where you can successfully run Bind afterwards.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.