[BlueOnyx:18821] Re: BlueOnyx server down

[Tom]

Tom <wcstaff at ...> writes:

I pulled an all-nighter and read a lot and tried to find a solution. I 
read that it is possible to do a YUM Downgrade, but did not do it. Will 
a YUM Downgrade possibly fix the problem?
I only see where I can only pick the full last ID# from the history 
list. I'm assuming, since a YUM update caused the problem, there may be 
a way to reverse and repair. Admittedly this is out of my league.
 
Here are the last 20 or so entries from my "/var/log/messages" this 
morning:
----------------------------------
Dec 17 07:15:06 ns systemd[1]: named-chroot.service failed.
Dec 17 07:15:06 ns systemctl[29882]: 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 17 07:15:06 ns systemd[1]: Stopping Set-up/destroy chroot 
environment for named (DNS)...
Dec 17 07:15:06 ns systemd[1]: Stopped Set-up/destroy chroot environment 
for named (DNS).
Dec 17 07:30:06 ns systemd[1]: Starting Set-up/destroy chroot 
environment for named (DNS)...
Dec 17 07:30:06 ns systemd[1]: Started Set-up/destroy chroot environment 
for named (DNS).
Dec 17 07:30:06 ns bash: /etc/named.conf:36: open: 
/etc/named.conf.include: file not found
Dec 17 07:30:06 ns systemd[1]: named-chroot.service: control process 
exited, code=exited status=1
Dec 17 07:30:06 ns systemd[1]: Unit named-chroot.service entered failed 
state.
Dec 17 07:30:06 ns systemd[1]: named-chroot.service failed.
Dec 17 07:30:06 ns systemctl[440]: 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 17 07:30:06 ns systemd[1]: Stopping Set-up/destroy chroot 
environment for named (DNS)...
Dec 17 07:30:06 ns systemd[1]: Stopped Set-up/destroy chroot environment 
for named (DNS).
Dec 17 07:45:06 ns systemd[1]: Starting Set-up/destroy chroot 
environment for named (DNS)...
Dec 17 07:45:06 ns systemd[1]: Started Set-up/destroy chroot environment 
for named (DNS).
Dec 17 07:45:07 ns bash: /etc/named.conf:36: open: 
/etc/named.conf.include: file not found
Dec 17 07:45:07 ns systemd[1]: named-chroot.service: control process 
exited, code=exited status=1
Dec 17 07:45:07 ns systemd[1]: Unit named-chroot.service entered failed 
state.
Dec 17 07:45:07 ns systemd[1]: named-chroot.service failed.
Dec 17 07:45:07 ns systemctl[3742]: 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 17 07:45:07 ns systemd[1]: Stopping Set-up/destroy chroot 
environment for named (DNS)...
Dec 17 07:45:07 ns systemd[1]: Stopped Set-up/destroy chroot environment 
for named (DNS).
-------------------------------
And "systemctl status named-chroot.service" results:
-------------------
● named-chroot.service - Berkeley Internet Name Domain (DNS)
   Loaded: loaded (/usr/lib/systemd/system/named-chroot.service; 
disabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2015-12-17 08:00:07 EST; 
13min ago
  Process: 7222 ExecStartPre=/bin/bash -c if [ ! 
"$DISABLE_ZONE_CHECKING" == "yes" ]; then /usr/sbin/named-checkconf -z 
/etc/named.conf; else echo "Checking of zone files is disabled"; fi 
(code=exited, status=1/FAILURE)

Dec 17 08:00:07 ns bash[7222]: /etc/named.conf:36: open: 
/etc/named.conf.include: file not found
-------------------

Thanks in advance
Tom