BIND 9.14.0: unable to set effective uid to 0: Operation not permitted

Gasoo gasoo at bluewin.ch
Thu Mar 28 13:40:19 UTC 2019


Hello

I build my own bind9 RPM for RHEL6 and RHEL7.
With the new version I get two errors when starting named.

Mar 25 16:41:56 dnsserver named[1348]: using default UDP/IPv4 port 
range: [1024, 65535]
Mar 25 16:41:56 dnsserver named[1348]: listening on IPv4 interface lo, 
127.0.0.1#53
Mar 25 16:41:56 dnsserver named[1348]: listening on IPv4 interface eth0, 
192.168.10.100#53
Mar 25 16:41:56 dnsserver named[1348]: unable to set effective uid to 0: 
Operation not permitted
Mar 25 16:41:56 dnsserver named[1348]: generating session key for 
dynamic DNS
Mar 25 16:41:56 dnsserver named[1348]: unable to set effective uid to 0: 
Operation not permitted
Mar 25 16:41:56 dnsserver named[1348]: sizing zone task pool based on 10 
zones

 From what I understand, the process named is running as user named already.
After it writes /var/run/named/named.pid, it tries to set the uid back to 0.
The same again after /var/run/named/session.key is written.

Bind is running in a chroot environment and the files are created with 
the uid/gid of named.
As far as I can see, everything is working fine.

Why does named want to set the uid of itself back to 0?
Has anyone seen this as well?


Kind Regards
Stephan


More information about the bind-users mailing list