SOLVED - Re: Bind failing to start on new 9.9.4 server

Robert Moskowitz rgm at htt-consult.com
Thu Feb 9 15:50:20 UTC 2017


File permission problems.

On 02/09/2017 10:38 AM, Ray Bellis wrote:
> On 09/02/2017 15:32, Robert Moskowitz wrote:
>
>> Now doing it 'right' and seeing:
>>
>> 09-Feb-2017 09:59:52.191 could not open file '/run/named/named.pid':
>> Permission denied
>> 09-Feb-2017 09:59:52.192 generating session key for dynamic DNS
>> 09-Feb-2017 09:59:52.192 could not open file '/run/named/session.key':
>> Permission denied
>> 09-Feb-2017 09:59:52.193 could not create /run/named/session.key
>> 09-Feb-2017 09:59:52.193 failed to generate session key for dynamic DNS:
>> permission denied
>> 09-Feb-2017 09:59:52.193 sizing zone task pool based on 21 zones
>>
>> so perhaps some permissions problems?  I am su as root.
> Are you specifying the '-u <user>' flag to named, and does that user
> have read / write permissions to /run/named ?
>
> [ also, does the config specify use of chroot? ]
>
>> then after all the auto zones:
>>
>> ...
>>
>> Now why am I getting network unreachable?  I can ping out to a lot of
>> addrs.
>

When I rsynced all my backed up zone files, I then had to chown in 
/var/named.

Well, I set /var/named/data to root:named, this made named create

/var/named/data/named.run as root:named, which then named could not 
write to!

did a chown to named:named, rm the bad named.run, restarted named, and 
all is working.

nits

They get you every time.

Thanks for the help.


Bob




More information about the bind-users mailing list