| View previous topic :: View next topic |
| Author |
Message |
ktsaou
Tux's lil' helper
Joined: 10 Jul 2003
Posts: 80
|
 Posted: Sun Dec 07, 2014 2:09 am Post subject: bind under systemd cannot create /var/run/named |
 |
|
Hi,
I just switched from openrc to systemd.
For some reason bind complains that it cannot create the directory /var/run/named. It says: permission denied.
My /var/run is a symlink to /run.
I also have similar errors from freshclam.
Any ideas what is happening? |
|
| Back to top |
|
 |
ktsaou
Tux's lil' helper
Joined: 10 Jul 2003
Posts: 80
|
| Posted: Sun Dec 07, 2014 5:12 pm Post subject: |
|
|
ok got it.
systemd is not ready for general use in gentoo.
Almost all services have their issues under systemd.
Switched back to openrc. |
|
| Back to top |
|
|
gerdesj
l33t
Joined: 29 Sep 2005
Posts: 621
Location: Yeovil, Somerset, UK
|
| Posted: Tue Dec 09, 2014 1:03 am Post subject: |
|
|
systemd is ready for general use. I'll agree with you that some packages have not been ported yet but systemd units are easy to write or scraped from another distro.
I have just emerged bind onto my laptop and it simply started and worked so would you like to have another go?
| Code: |
# ls -l /var
...
lrwxrwxrwx 1 root root 4 Feb 27 2014 run -> /run
|
| Code: |
# ls -l /
...
drwxr-xr-x 34 root root 1020 Dec 9 00:51 run
|
| Code: |
# ls -l /var/run
...
drwxr-xr-x 2 named named 40 Dec 9 00:51 named
|
What does ls -l /var/run give on your system for named ?
Cheers
Jon |
|
| Back to top |
|
|
weust
n00b
Joined: 28 Feb 2014
Posts: 26
|
| Posted: Thu Jan 01, 2015 5:44 pm Post subject: |
|
|
Same issue here.
Not sure what you mean with "..give on your system for named", but I got this when using ls -l /var/run:
| Code: | # ls -l /var/run
lrwxrwxrwx 1 root root 4 Apr 15 2014 /var/run -> /run |
|
|
| Back to top |
|
|
weust
n00b
Joined: 28 Feb 2014
Posts: 26
|
| Posted: Thu Jan 01, 2015 5:58 pm Post subject: |
|
|
I went ahead and did it a bit dirty, but at least I don't get errors anymore.
Before, when I (re)started named, I got this:
| Quote: | couldn't mkdir '/run/named': Permission denied
generating session key for dynamic DNS
couldn't mkdir '/var/run/named': Permission denied
could not create /var/run/named/session.key
failed to generate session key for dynamic DNS: permission denied |
I then, as root, created /run/named. That give the following error:
| Quote: | Could not open '/run/named/named.pid'.
Please check file and directory permissions or reconfigure the filename.
could not open file '/run/named/named.pid': Permission denied
generating session key for dynamic DNS
Could not open '/var/run/named/session.key'.
Please check file and directory permissions or reconfigure the filename.
could not open file '/var/run/named/session.key': Permission denied
could not create /var/run/named/session.key
failed to generate session key for dynamic DNS: permission denied |
I then did a chmod 777 /run/named on the /run/named, and no more errors:
| Quote: | | generating session key for dynamic DNS |
No doubt it's not right what I did, as it should be able to create and place the files there itself, but for my home usage it's fine.
Now just to figure out why, after the recent named update, it takes about five minuted for some sites to resolve while others are fine. |
|
| Back to top |
|
|
|
Networking & Security
