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!
[root@albion nagios]# systemctl status nagios
● nagios.service - Nagios Network Monitoring
Loaded: loaded (/usr/lib/systemd/system/nagios.service; disabled; vendor preset: disabled)
Active: inactive (dead)
Docs: https://www.nagios.org/documentation/
I'm certain that it was set to "enabled" before the update, because I have Dev, Test, and 2xProd instances, all managed by Ansible, and the Prod systems are set to auto-reboot each week. The Prod systems have been in place for 2 years, so we'd have noticed if Nagios wasn't starting at boot time. Of course, I just used our playbook to reset it to "enabled", so our systems are fine.
Perhaps examine the .spec file for this RPM... it can certainly have a "vendor default" set to "disabled", but the expected behavior is that when I apply an update, it should remain "enabled", if it was set that way before the update.
Please let me know if you have any questions. Our systems are on CentOS7.
_______________________________________________
epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
