[BlueOnyx:19098] Re: DNS not starting

Gregg K greggk1 at cox.net
Wed Feb 3 10:27:42 -05 2016


> Hi all,
> 
> > Fix:
> >
> > /usr/sausalito/sbin/cced.init restart
> > systemctl restart named-chroot
> 
> Yeah, that's the fix. I also just published a YUM update for 5209R which
will
> prevent this from happening again.

I'm seeing this issue again today.  I follow the instructions above, and
this is the result:
Job for named-chroot.service failed because the control process exited with
error code. See "systemctl status named-chroot.service" and "journalctl -xe"
for details.

I then look at my messages to see what happened, and this is what is in
there:
Feb  3 08:24:21 main named[17760]: automatic empty zone:
1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
Feb  3 08:24:21 main named[17760]: automatic empty zone: D.F.IP6.ARPA
Feb  3 08:24:21 main named[17760]: automatic empty zone: 8.E.F.IP6.ARPA
Feb  3 08:24:21 main named[17760]: automatic empty zone: 9.E.F.IP6.ARPA
Feb  3 08:24:21 main named[17760]: automatic empty zone: A.E.F.IP6.ARPA
Feb  3 08:24:21 main named[17760]: automatic empty zone: B.E.F.IP6.ARPA
Feb  3 08:24:21 main named[17760]: automatic empty zone:
8.B.D.0.1.0.0.2.IP6.ARPA
Feb  3 08:24:21 main named[17760]: command channel listening on
127.0.0.1#953
Feb  3 08:24:21 main named[17760]: command channel listening on ::1#953
Feb  3 08:24:21 main named[17760]: isc_stdio_open 'data/named.run' failed:
file not found
Feb  3 08:24:21 main named[17760]: configuring logging: file not found
Feb  3 08:24:21 main named[17760]: loading configuration: file not found
Feb  3 08:24:21 main named[17760]: exiting (due to fatal error)
Feb  3 08:24:21 main systemd: named-chroot.service: control process exited,
code=exited status=1
Feb  3 08:24:21 main systemd: Failed to start Berkeley Internet Name Domain
(DNS).
Feb  3 08:24:21 main systemd: Unit named-chroot.service entered failed
state.
Feb  3 08:24:21 main systemd: named-chroot.service failed.
Feb  3 08:24:21 main systemd: Stopping Set-up/destroy chroot environment for
named (DNS)...
Feb  3 08:24:21 main systemd: Stopped Set-up/destroy chroot environment for
named (DNS).

It looks like it's not finding the config file?
Should I uninstall and reinstall the whole thing?

Gregg




More information about the Blueonyx mailing list