On Tue, 17 Apr 2018, Neil MacGregor wrote: > Hi folks, we are giant fans of your work! Here's an idea on > how to make it better. > > We received an update to Nagios on Friday, last week: > [root@albion ~]# rpm -q --last nagios > nagios-4.3.4-5.el7.x86_64 Fri 13 Apr 2018 04:21:00 AM MDT > > After a reboot, Nagios didn't automatically restart. It's > apparent the service has been "disabled" after the upgrade. > That's unexpected! It may be 'apparent', but this assumption is not accurate Yes -- you will need to read and correct the changed syntax (updated and more current against upstream) You may 'pre-flight' the files thus: # /usr/sbin/nagios -v /etc/nagios/nagios.cfg locally and particularly I needed to tweak the DNS checking in: /etc/nagios/objects/dns.cfg The detail which is returned by the suggested systemd viewing suggestion is insufficiently long, and most people do not reach back further (there are systemd options to do so, but ...). Also, 'grepping' /var/log/messsages into a | less also helps But I find best the 'preflighting' approach permits progressively seeing, solving, and then seeing the next issue -- Russ herrold _______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
