If supported can the nagios-4.0.8 package be update to 4.1.1
I would like to see this also. My logs are getting filled with:
09:55:07 nagios Worker 19660: Unknown jobtype: 9
09:55:07 nagios wproc: Unknown job type: 9
09:55:10 nagios Worker 19661: Unknown jobtype: 10
09:55:10 nagios wproc: Unknown job type: 10
which is fixed in 4.1.0:
While you're at it, could you please resolve BUG#1084934 as well? This also affects the version of Nagios in EPEL7, FWIW.
nagios-4.2.4-2.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-0f3297a19b
nagios-4.2.4-2.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-0f3297a19b
nagios-4.2.4-2.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.
This is the second time that Nagios in EPEL7 was updated to another major version, introducing a lot of disruptive changes. The update to 4.0.8 already broke several things (e.g. PNP4Nagios plugin), this update also changes the directory layout and location of several files, rendering existing 4.0.8 installations in a broken state during update.
This is in violation of the package policies for EPEL - https://fedoraproject.org/wiki/EPEL_Updates_Policy
"All updates should strive to avoid situations that require manual intervention to keep the package functioning after update."
"Major updates with changes to user experience are to be avoided."
As the member of a project that depends on a stable version of Nagios in EPEL,
this repeated breaking of Nagios causes a lot of confusion and headache on our end and for our users.
This bug is an auto tracking bug and so we will continue the discussion on how to fix this in https://bugzilla.redhat.com/show_bug.cgi?id=1427895
I will also be discussing it at todays EPSCO meeting on how to get it fixed.
It's kind of a catch 22. It needs to be stable, but there also needs to be an upgrade path or at the very least, somebody needs to backport security fixes. If given between an upgrade breaking Nagios or having a major security hole due to a bug in an older release, I tend to lean towards at least having an option to apply a possibly breaking update to resolve the security issue.