[oi-dev] Anybody else running named on OI

[Till Wegmüller]

Hi Gary

Looks like a config error to me.

Your named was trying to run in the working directory /root as user
named. That of course will not work :)

Once a package has been installed it's config is not updated by the
distribution, as most people run their own config and IPS's behaviour
tends to break configs more than helping make things work.

Whats the content of named.conf? What does /usr/sbin/named-checkconf say
about config errors?

Hope this helps
Till

On 18.10.20 01:26, Gary Mills wrote:
> After a recent OI update and reboot, I found that the nameserver no
> longer ran.  The service log showed:
> 
>     dns-server: Executing: /usr/sbin/named  -u named in '/root'
>     dns-server : start failed! Check syslog for further information.
> 
> The messages log said:
> 
>     Aug  2 19:29:17 qtpie named[1937]: [ID 873579 daemon.error] the working directory is not writable
>     Aug  2 19:29:17 qtpie named[1937]: [ID 873579 daemon.crit] loading configuration: permission denied
>     Aug  2 19:29:17 qtpie named[1937]: [ID 873579 daemon.crit] exiting (due to fatal error)
> 
> The service is: svc:/network/dns/server:default .  It's bind version
> 9.16.0, if that matters.
> 
> My configuration file is /etc/named.conf, the default, with zone files
> in /var/named .  Apparently, it was attempting to run named as user
> named, starting in /root .  named's home directory, /var/chroot/named,
> does not exist.  Creating that directory did not help.
> 
> I had to delete the options/user property value from the service to
> get it to work.  Now it runs as root, without the `-u named' option.
> This is not ideal.  Are any of you running named in the default
> configuration?  How did you accomplish this?
> 
>