Home > DNS > Named: the working directory is not writable

Named: the working directory is not writable

October 26, 2008 Posted by KP

If I do:
# tail -f /var/log/messages &
# rndc reload

I will get the error message:

named: the working directory is not writable.

The error message was caused by ‘rndc reload’, ‘/etc/rc.d/named restart’ has no such error. I tried to change named directory to group writable, which doesn’t solve the problem, moreover, bind will detect the change and gives another error message.

Anyway, I don’t think this is a real error. Trying to fix it makes things worse, I ignored it.



Related Posts:

Filed Under: DNS

8 Comments to “Named: the working directory is not writable”

  1. ALan Says:

    Had the same issue – did you ever discover what this was – as you say it doesn’t seem to effect the way the system works.

  2. FreeBSD Newbie Says:

    No, some pages claimed the problem disappeared after they changed the directory permission, but it didn’t work for me.

  3. Gitsnik Says:

    I just came across this working out some slave domain issues and changing the directory permission alone wasn’t enough:

    # cd /etc/namedb/
    # chown -R bind:wheel *
    # chmod -R g+w *
    # chmod -R g+r *

    Got rid of it for me. Note that it wasn’t just correcting the permissions on the one folder, had to be all the files as well.

    Might also want to check that bind is able to write to the /etc/namedb/rndc.key file.

    That’s what worked for me, on a recently updated to 6.4-STABLE server.

  4. bill fiore Says:

    the above did not wort for me – freebsd 8.0-beta2 amd64

  5. TNT4BRAIN Says:

    Had the same issue on Fedora Core 12. Solved successfully – just changed the permissions on /var/named/chroot/var/named to 0660.

  6. Rizki Anto Says:

    for freeBSD 8.0 :
    #cd /etc/namedb
    #chmod -R bind:wheel *

    then restart named
    #/etc/rc.d/named restart

    it’s work

  7. Rizki Anto Says:

    sorry i’m wrong
    should be :
    chown -R bind:wheel *

    sorrryyyy

  8. vds Says:

    in /var/log/messages:
    named[1727]: client (ip addr)#56183: error sending response: not enough free resources
    It is a lot of them, ~200 in second.
    What is it? About what resources there is a speech?
    thanks

Leave a Comment

(required)
(will not be published, required)

* Copy this password:

* Type or paste password here:






Archives

Links