[BlueOnyx:18811] Re: BlueOnyx server down

[Tom]

Chris Gebhardt - VIRTBIZ Internet <cobaltfacts at ...> writes:

> Uh oh!  Why did you reboot?  To fix the DNS server?
Because I was told to in the GUI, after logging in with my IP.
> What have you checked?  Have you looked in the messages log for lines 
> that include "named" in them?    Do this:
> 
> grep "named" /var/log/messages
> 
> Then paste the last, oh, 20 or so lines to us and maybe we can help 
find 
> where it's gone awry.
> 
Dec 16 16:00:06 ns systemd[1]: named-chroot.service: control process 
exited, code=exited status=1
Dec 16 16:00:06 ns systemd[1]: Unit named-chroot.service entered failed 
state.
Dec 16 16:00:06 ns systemd[1]: named-chroot.service failed.
Dec 16 16:00:06 ns systemctl[25124]: 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.
Dec 16 16:00:06 ns systemd[1]: Stopping Set-up/destroy chroot 
environment for named (DNS)...
Dec 16 16:00:06 ns systemd[1]: Stopped Set-up/destroy chroot environment 
for named (DNS).
Dec 16 16:15:07 ns systemd[1]: Starting Set-up/destroy chroot 
environment for named (DNS)...
Dec 16 16:15:07 ns systemd[1]: Started Set-up/destroy chroot environment 
for named (DNS).
Dec 16 16:15:07 ns bash: /etc/named.conf:36: open: 
/etc/named.conf.include: file not found
Dec 16 16:15:07 ns systemd[1]: named-chroot.service: control process 
exited, code=exited status=1
Dec 16 16:15:07 ns systemd[1]: Unit named-chroot.service entered failed 
state.
Dec 16 16:15:07 ns systemd[1]: named-chroot.service failed.
Dec 16 16:15:07 ns systemctl[28240]: 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.
Dec 16 16:15:07 ns systemd[1]: Stopping Set-up/destroy chroot 
environment for named (DNS)...
Dec 16 16:15:07 ns systemd[1]: Stopped Set-up/destroy chroot environment 
for named (DNS).