[BlueOnyx:18816] Re: BlueOnyx server down

Tom wcstaff at webcoast.com
Wed Dec 16 18:19:57 -05 2015


Hi Chris,

>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.
> 
Here are the last 20+ entries from "/var/log/messages".
---------------
Dec 16 18:00:07 ns systemd[1]: named-chroot.service failed.
Dec 16 18:00:07 ns systemctl[17735]: 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 18:00:07 ns systemd[1]: Stopping Set-up/destroy chroot 
environment for named (DNS)...
Dec 16 18:00:07 ns systemd[1]: Stopped Set-up/destroy chroot environment 
for named (DNS).
Dec 16 18:03:55 ns systemctl[18502]: Removed symlink 
/etc/systemd/system/multi-user.target.wants/named.service.
Dec 16 18:04:11 ns systemctl[18732]: Created symlink from 
/etc/systemd/system/multi-user.target.wants/named.service to 
/usr/lib/systemd/system/named.service.
Dec 16 18:04:11 ns systemd[1]: Starting Set-up/destroy chroot 
environment for named (DNS)...
Dec 16 18:04:11 ns systemd[1]: Started Set-up/destroy chroot environment 
for named (DNS).
Dec 16 18:04:11 ns bash: /etc/named.conf:36: open: 
/etc/named.conf.include: file not found
Dec 16 18:04:11 ns systemd[1]: named-chroot.service: control process 
exited, code=exited status=1
Dec 16 18:04:11 ns systemd[1]: Unit named-chroot.service entered failed 
state.
Dec 16 18:04:11 ns systemd[1]: named-chroot.service failed.
Dec 16 18:04:11 ns systemctl[18753]: 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 18:04:11 ns systemd[1]: Stopping Set-up/destroy chroot 
environment for named (DNS)...
Dec 16 18:04:11 ns systemd[1]: Stopped Set-up/destroy chroot environment 
for named (DNS).
Dec 16 18:05:32 ns systemd[1]: Starting Set-up/destroy chroot 
environment for named (DNS)...
Dec 16 18:05:32 ns systemd[1]: Started Set-up/destroy chroot environment 
for named (DNS).
Dec 16 18:05:32 ns bash: /etc/named.conf:36: open: 
/etc/named.conf.include: file not found
Dec 16 18:05:32 ns systemd[1]: named-chroot.service: control process 
exited, code=exited status=1
Dec 16 18:05:32 ns systemd[1]: Unit named-chroot.service entered failed 
state.
Dec 16 18:05:32 ns systemd[1]: named-chroot.service failed.
Dec 16 18:05:32 ns systemctl[19110]: 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 18:05:32 ns systemd[1]: Stopping Set-up/destroy chroot 
environment for named (DNS)...
Dec 16 18:05:32 ns systemd[1]: Stopped Set-up/destroy chroot environment 
for named (DNS).
--------------------
I apologize in advance for the many posts. But I'm stumped. The best I 
can tell is it happened around 6:00am EST this morning, because I get 
regular emails from DFIX and that's when they stopped. 
Thanks in advance
Tom





More information about the Blueonyx mailing list