Nagios Support Forum

Posted: **Tue Jan 08, 2019 4:37 am**

Dear support,
we have an offline installation on Red Hat 6.7.
We upgraded from 5.4.13 to 5.5.7 on 17 December, when 5.5.8 was not available in offline repo.

We are encountering issues when we "apply configuration" in CCM:
if we do not wait at least 30 minutes between actions, monitoring engine not start.

On CLI, we stop nagios (/etc/init.d/nagios stop), then we tried nagios in foreground (/usr/local/nagios/bin/nagios /usr/local/nagios/etc/nagios.cfg) and we received "Segmentation fault".

We found a not-acceptable solution: renaming /usr/local/nagios/var/retention.dat

We are using these files:
/etc/init.d/nagios from rpm
/usr/local/nagios/etc/nagios.cfg from rpm, but we modified these 2 lines for compatibility:

Code: Select all

service_perfdata_file_template=DATATYPE::SERVICEPERFDATA\tTIMET::$TIMET$\tHOSTNAME::$HOSTNAME$\tSERVICEDESC::$SERVICEDESC$\tSERVICEPERFDATA::$SERVICEPERFDATA$\tSERVICECHECKCOMMAND::$SERVICECHECKCOMMAND$\tHOSTSTATE::$HOSTSTATE$\tHOSTSTATETYPE::$HOSTSTATETYPE$\tSERVICESTATE::$SERVICESTATE$\tSERVICESTATETYPE::$SERVICESTATETYPE$\tSERVICEOUTPUT::$SERVICEOUTPUT$
host_perfdata_file_template=DATATYPE::HOSTPERFDATA\tTIMET::$TIMET$\tHOSTNAME::$HOSTNAME$\tHOSTPERFDATA::$HOSTPERFDATA$\tHOSTCHECKCOMMAND::$HOSTCHECKCOMMAND$\tHOSTSTATE::$HOSTSTATE$\tHOSTSTATETYPE::$HOSTSTATETYPE$\tHOSTOUTPUT::$HOSTOUTPUT$

We are waiting your feedback.

Thank you for your support

Posted: **Tue Jan 08, 2019 10:42 am**

5.5.8 is now available in the offline repository and contains an upgrade to ndoutils which resolved an issue that is what you describe

Code: Select all

- Fixed issue with specific configurations in ndoutils causing Core to crash by updating ndoutils to 2.1.3 -JO

Posted: **Tue Jan 08, 2019 11:10 am**

Looking further in other issues, we found that some services are stuck in SOFT state.
To avoid notification storming, last time we deleted retention.dat, we restored manually "last_hard_state" in some services, but we are not sure that there is a correlation between stuck services and "manually fixed" ones.

With 5.5.8 these issues will be solved?

Or will we have to follow the workaround found at https://support.nagios.com/forum/viewto ... 66#p271152 ?

Thank you for your support

Posted: **Tue Jan 08, 2019 12:22 pm**

Some of them are resolved, however there is another fix in final testing for stuck SOFT states that will likely be released next week.

Posted: **Tue Jan 08, 2019 12:30 pm**

We need to ask authorization to proceed to management and we can not upgrade too many times on the same month.
We want open a change request to upgrade to 5.5.8 to fix ndoutils issues.
Should we add workaround found at https://support.nagios.com/forum/viewto ... 66#p271152 or add rollback to Nagios Core 4.2.4 ?

Thank you for your support

Posted: **Tue Jan 08, 2019 2:53 pm**

If you cannot wait until the beginning of next week for the next release, the most stable would be to roll back to 4.2.4 however that may not be possible if you cannot compile on your offline server.

Nagios Support Forum

[5.5.7] Segmentation fault after upgrade

[5.5.7] Segmentation fault after upgrade

Re: [5.5.7] Segmentation fault after upgrade

Re: [5.5.7] Segmentation fault after upgrade

Re: [5.5.7] Segmentation fault after upgrade

Re: [5.5.7] Segmentation fault after upgrade

Re: [5.5.7] Segmentation fault after upgrade