Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I have compiled Bind 9.8 on Debian, and am having difficulty getting the daemon to load. Output of more /var/log/daemon.log | grep named is as follows (I have isolated the problem to the following lines):-

Jul  3 00:54:07 server1 named[850]: /etc/bind/named.conf.options:2: change directory
to'/var/cache/bind' failed: file not found
Jul  3 00:54:07 server1 named[850]: /etc/bind/named.conf.options:2: parsing failed
Jul  3 00:54:07 server1 named[850]: loading configuration: file not found
Jul  3 00:54:07 server1 named[850]: exiting (due to fatal error)

EDIT:- Bind 9.7 was installed from the debian repos prior to compiling and installing 9.8, and was removed by aptitude --purge remove bind9

Regards, Jack Hunt

share|improve this question
1  
Seriously? You can't work this out from the error messages you posted? (change directory to'/var/cache/bind' failed: file not found => "Maybe I should create the directory it wants?")... I'm just asking for a little effort here. –  voretaq7 Jul 3 '12 at 0:38
1  
And place what in it exactly? If it is looking for a file or files to use in this directory, then what is the point in merely creating an empty directory! –  VisionIncision Jul 3 '12 at 0:49

2 Answers 2

named.conf.options is a Debianism, and /var/cache/bind is the directory that it has configured by default. That's from your old package install.

Clarify what you did when you compiled and installed the software. Where did the binaries end up, where did the config files end up, and are you certain that your init script is starting the new version?

share|improve this answer
    
Hi, after installing, the binaries ended up in /usr/local/sbin verified by ./named -v –  VisionIncision Jul 3 '12 at 0:45
    
I think I have made an error, as the logs were initially moaning about /etc/named.conf not existing, so I symlinked named.conf from /etc/bind. This, I assumed was where the new installation placed its config files. Thanks. –  VisionIncision Jul 3 '12 at 0:47
    
How would I verify that my init scripts are starting the correct version? –  VisionIncision Jul 3 '12 at 1:04
1  
@VisionIncision Well, where did the init script come from? I don't believe the BIND source install includes an init script or default config files. The Debian ones should work, but you might need to tweak them to be appropriate to your install. –  Shane Madden Jul 3 '12 at 1:12
    
Ok, I am sorry if this is frustrating, but am I right in understanding that you mean the different bind9 scripts in the rc*.d directories? If so, I was under the impression that these would have been set by the source install. If this is not the case, then I assume that they are from the old install. I have not attempted to use BIND before, as you can probably tell. So I am not sure what exactly would require tweaking. Thanks for the help, much appreciated. –  VisionIncision Jul 3 '12 at 1:17

Check if the /var/cache/bind exists and if the bind user has the right permission to access it.

share|improve this answer
    
Thanks for the response, no /var/cache/bind does not exist. –  VisionIncision Jul 3 '12 at 0:11

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.