named: the working directory is not writable

[Richard G]

I've seen this error for the first time, however it might be there longer.
Can this be fixed and how?

As far as I know, the rights and owner are oke, this is my /slaves directory under /var/named

drwxrwx--- 2 named named 4096 Jan 20 17:33 slaves

Looks writable to me.
Any clues?

 

[nobaloney]

Have you tried writing to it as the same user who owns the files in it?

Jeff

 

[Richard G]

I don't know if it means something or if it's important. Got 2 other servers also with Centos on it (1 of them has Cpanel), all have the same error.
There are no files present in the slaves directory.
This is what the logs exactly says:
Mar 24 17:57:18 server2 named[2853]: the working directory is not writable

Or it must be the named directory itself:
drwxr-xr-x 5 root named 4096 Mar 27 04:24 named/
Grouprights here are not writable, but root is the only one making files under that directory anyway. So I wonder if this needs to be writable by named.

 

[nobaloney]

The only servers for which we need anything in /var/named/slaves do NOT run DirectAdmin; they're slave nameservers. The ownership and rights are:

# ls -ald /var/named/slaves
drwxrwx---    3 named    named        4096 Oct 26  2008 /var/named/slaves
#

The ownership and rights for /var/named are:

# ls -ald /var/named
drwxr-x---    4 root     named      118784 Mar 22 23:03 /var/named
#

To which logfile are you referring?

Jeff

 

[Richard G]

It's not a slave server, just a DirectAdmin server.

The logfile i'm referring to is the /var/log/messages file. The notice is only visible in the logfile when named is restarted.

 

[nobaloney]

You can most likely ignore it since you don't need to refer to your slaves directory if you're not running as a slave nameserver. It's really not worth further investigation since BIND doesn't put anything into the slaves directory by itself; you have to set it up to do so.

Jeff

 

[Richard G]

Oke, I don't need to worry then, thank you for your support!