Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

couldn't open pid file '/var/run/named/named.pid' : Permission denied

1,992 views
Skip to first unread message

Andy Eccles

unread,
Jul 20, 2001, 4:55:34 PM7/20/01
to
This is the error I see when I tail the /var/log/messages after typing named
at the command shell.

Can anyone assist? I don't think there is a named.pid file in that dir. How
do I create one?


Thanks

Andy

andye...@hotmail.com

Ashley Kitto

unread,
Jul 20, 2001, 6:17:57 PM7/20/01
to

In message <sA067.1786$Vc1.6...@news2-win.server.ntlworld.com>, "Andy Eccles"
writes:

>This is the error I see when I tail the /var/log/messages after typing named
>at the command shell.
>
>Can anyone assist? I don't think there is a named.pid file in that dir. How
>do I create one?

Make sure that named has write permissions on the /var/run/named directory,
or point the named.conf pid-file option to a directory in which the named
process does have write permissions.
If you're running setuid, the user that bind is setuid to should have write
privileges, otherwise, root should have write privileges.

The named.conf pid-file option, if needed, should go in your options statement
as per this example:

options {
...
pid-file "/var/run/named/named.pid";
...
};

Ashley Kitto
Nominum Training and Support
http://www.nominum.com

Jean-Philippe Morin

unread,
Jul 20, 2001, 10:00:45 PM7/20/01
to

>>This is the error I see when I tail the /var/log/messages after typing named
>>at the command shell.
>>
>>Can anyone assist? I don't think there is a named.pid file in that dir. How
>>do I create one?
>
>Make sure that named has write permissions on the /var/run/named directory,
>or point the named.conf pid-file option to a directory in which the named
>process does have write permissions.
>If you're running setuid, the user that bind is setuid to should have write
>privileges, otherwise, root should have write privileges.
>
>The named.conf pid-file option, if needed, should go in your options statement
>as per this example:
>
>options {
>...
>
pid-file "/var/run/named/named.pid";
>...
>};

I have the same problem. I added the line in named.conf, but nothing change.
I did ls -l for my directory /var/run/named/
drwxr-xr-x 2 named named 1024 jui 20 21:25 named/

So I don't understand why he doesn't have the permission.

jp


Frederick Czajka

unread,
Jul 23, 2001, 10:30:27 AM7/23/01
to

Try a ls -ld on /var/run and see what your perms are there.

Frederick

On 20 Jul 2001 19:00:45 -0700, Jean-Philippe Morin

Jean-Philippe Morin

unread,
Jul 26, 2001, 8:24:22 PM7/26/01
to

>Try a ls -ld on /var/run and see what your perms are there.
>
>Frederick

ls -ld /var/run

drwxr-xr-x 4 root root 1024 jui 24 21:34 /var/run/

something wrong ?

Michael Kjorling

unread,
Jul 26, 2001, 8:50:51 PM7/26/01
to

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'll have to admit - I haven't read this entire thread. Seems like I
missed quite a few interesting posts by being off the list for too
long.

But what the user named is running as (whatever it is, `named' in my
case to keep it completely separate) is write permissions to
/var/run/named/ - or wherever the PID file should be put. Also note
that this holds true for any other directories it has to write to. (I
don't think it needs write access to the directories above it,
though.)

$ ls -ld /var/named
drwxrwx--- 5 michael named 4096 Jul 25 02:21 /var/named


Michael Kjörling


On Jul 26 2001 20:14 -0400, Jean-Philippe Morin wrote:

> ls -ld /var/run
>
> drwxr-xr-x 4 root root 1024 jui 24 21:34 /var/run/
>
> something wrong ?

- --
Michael Kjörling - mic...@kjorling.com - PGP: 8A70E33E
Manager Wolf.COM -- Programmer -- Network Administrator
"We must be the change we wish to see" (Mahatma Gandhi)

^..^ Support the wolves in Norway -- go to ^..^
\/ http://home.no.net/ulvelist/protest_int.htm \/

***** Please only send me emails which concern me *****

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7YLe8KqN7/Ypw4z4RAlXyAKCKikLv3IAIgzxF5D00hdobGhgMGwCg7Qj3
noB7HradgBuax22shncOoqQ=
=Qo9v
-----END PGP SIGNATURE-----


Avery Brooks

unread,
Aug 9, 2001, 3:10:42 AM8/9/01
to

I was getting this same error and I changed the permissions on the named
directory.. It works fine for me now, you might want to try a few chmod levels
... I don't remember which one worked for me.

Hope this helps

Avery

0 new messages