History not working after update

[RebeccaIlene]

Hi Team,

Recently we have updated to version 5.7.0.
After the update the history of all hosts and service are not showing up.
No latest history is shown either. When I check under notifications I can see the emails sent out but the history is empty.

Can someone please suggest what the issue is and how it can be fixed?

One other issue we have observed that ndo2db service is not found.

Has this caused the issue?

[root@host ~]# systemctl status ndo2db
Unit ndo2db.service could not be found.

Please find attached screenshot.

[scottwilkerson]

Recently we have updated to version 5.7.0.
After the update the history of all hosts and service are not showing up.
No latest history is shown either. When I check under notifications I can see the emails sent out but the history is empty.

Can someone please suggest what the issue is and how it can be fixed?

This was a bug found in 5.7.0 ans we released 5.7.1 yesterday that fixes this.

One other issue we have observed that ndo2db service is not found.

Has this caused the issue?

[root@host ~]# systemctl status ndo2db
Unit ndo2db.service could not be found.

5.7.0 removes the ndo2db service and it is replaced with ndo3 which is a direct connection to the DB no service necessary

[RebeccaIlene]

Thanks for the update. After updating to 5.7.1 we are able to view the history.

5.7.0 removes the ndo2db service and it is replaced with ndo3 which is a direct connection to the DB no service necessary

After the update Service now lost connectivity to Nagios.

Is this related? What can we do to fix it?

[RebeccaIlene]

In addition to this we have also observed that when we apply the configurations all service and host checks go into pending.

Will this effect the checks in any way? We have scheduled checks that run once a day and we don't want the checks to be missed because the configurations were applied at the same time.

[scottwilkerson]

Thanks for the update. After updating to 5.7.1 we are able to view the history.

Nice

After the update Service now lost connectivity to Nagios.

How was it connected? What exactly do you mean by "lost connectivity"

In addition to this we have also observed that when we apply the configurations all service and host checks go into pending.

Will this effect the checks in any way? We have scheduled checks that run once a day and we don't want the checks to be missed because the configurations were applied at the same time.

They show pending in the UI while the DB is being populated, but this doesn't affect actual monitoring or notifications

[RebeccaIlene]

We have observed another problem.
When we run apply configuration all host checks are going into pending and not updating until we restart all services from command line.

This has impacted us in a huge way as over the weekend the checks were down for 12 hours. The services were later restarted and the checks started working.

Please suggest what can be done to avid this. We make regular changes in the configuration and don't want to impact monitoring in anyway.

Service now is also integrated with XI and as XI wasn't working for 12 hours monitoring was down for 12 hours there were no tickers raised causing a huge impact for us.

[scottwilkerson]

When you say you need to restart the services after applying configuration, which services are you referring to?

[RebeccaIlene]

All services - httpd, crond, npcd, nagios, mod-gearman-worker, gearmand, postgresql, ramdisk, mariadb and snmptt.

This reoccurred thrice over the weekend. Can you please suggest what is causing this and a permanent fix for it?

[lmiltchev]

There is an issue with the Mod Gearman integration in Nagios XI 5.7.1 and some older systems that are still using postgres. These issues will be fixed in Nagios XI 5.7.2, which will be released this week.

[RebeccaIlene]

Thanks. Looking forward for the update.
Hope this will fix the issue.
Will update the case if issue persists after update.