Issue after upgrade to 5.7.2 version

[bseuser]

Hi,

We recently upgraded Nagios to 5.7.2 from 5.6.12. We are facing issues after upgrading to 5.7.2, for example, when we create a new check and the check is showing pending status for a long time and the "force an immediate check" also didn't help and the Next check date showing some weird date i.e., 1970-xx-xx.

I tried to repair the database but no luck and I followed https://support.nagios.com/forum/viewto ... 16&t=59388 forum but no luck.

So, I want to know is it be possible to restore/rollback it from "configure snapshot" to the previous successfully day snapshot or we need to go step by step following https://support.nagios.com/forum/viewto ... 16&t=59202 this?

Below are the broken in GUI:
-----------------------------------
--> Last check and Next check contents are not updating
--> If I add a new host using CCM and apply configuration it's not showing up in GUI, and the same with configuring wizard as well.
--> When I click "force an immediate check." It showing command executed successfully but not turns to green/warning/critical, still showing pending in grey color.
--> And checks are showing some weird date example 1970-08-20 date instead of the current date.

Thanks,

[benjaminsmith]

Hi,

I would recommend downgrading to the previous version of ndoutils. Restart the services and if you're still having trouble, please send us your system profile.

Downgrade Instructons (Local Database)

Code: Select all

systemctl stop nagios
cd /tmp
rm -rf /tmp/nagiosxi
wget https://assets.nagios.com/downloads/nagiosxi/5/xi-5.6.14.tar.gz
tar zxf xi-5.6.14.tar.gz
cd /tmp/nagiosxi/subcomponents/ndoutils
./install
systemctl enable ndo2db

Then edit your /usr/local/nagios/etc/nagios.cfg and make sure this line is uncommented:

Code: Select all

broker_module=/usr/local/nagios/bin/ndomod.o config_file=/usr/local/nagios/etc/ndomod.cfg

Make sure this line is commented:

Code: Select all

#broker_module=/usr/local/nagios/bin/ndo.so /usr/local/nagios/etc/ndo.cfg

Then start the nagios service:

Code: Select all

systemctl start nagios

Thanks, Benajmin

To send us your system profile.
Login to the Nagios XI GUI using a web browser.
Click the "Admin" > "System Profile" Menu
Click the "Download Profile" button
Save the profile.zip file and share in a private message or upload it to the post/ticket, and then reply to this post to bring it up in the queue.

[bseuser]

I followed the steps, no luck. Still, the new creation checks are showing weird date i.e., 1970-01-01. I sent you the system profile in a private message. Attached the screenshot for your reference.

Request you kindly provide us with the solution.

[benjaminsmith]

Hi,

Looking over the profile, it looks like ndo was not downgraded yet. It is still loading the newer ndo3 broker module.

# Added by NDO 'make install-broker-line' on Thu Aug 27 03:28:51 EDT 2020
broker_module=/usr/local/nagios/bin/ndo.so /usr/local/nagios/etc/ndo.cfg

You'll want to comment out that line and uncomment the following.

Code: Select all

broker_module=/usr/local/nagios/bin/ndomod.o config_file=/usr/local/nagios/etc/ndomod.cfg

And then restart the nagios service.

Code: Select all

systemctl start nagios

The time settings are correct, and the last check result is showing a recent date.

Code: Select all

[1598847714] SERVICE ALERT: batfs0802.mathworks.com;BaTFS REST API;CRITICAL;SOFT;1;connect to address 172.30.212.102 and port 8082: Connection refused

Recently, there was a similar case related to SNMP trap time calculations, is that happening across all checks and services or only passive check results such as SNMP traps. If so, can you send me the following configuration file. Thank you.

Code: Select all

/etc/snmp/snmptt.conf

[bseuser]

Thanks, after downgrading the ndoutils to 5.6.14 now the Next check and Last check field is updating with the correct date.
But, I observer after the click on "Force an immediate check" it showing command executed successfully and it is taking some little bit long time to update the status.
Is this know issue in 5.7.2 version?

Thanks.

[benjaminsmith]

HI,

But, I observer after the click on "Force an immediate check" it showing command executed successfully and it is taking some little bit long time to update the status.

Typically, downgrading would help that issue. The dashlet is only going to refresh at specific times depending on how the dashlet refresh rate settings; go to Admin > System Config > Performance Settings > Dashlets to check.

Try refreshing the page shortly after you force an immediate check to see if it updates. Otherwise, force an immediate check and watch the following log for any errors.

Code: Select all

tail -f /usr/local/nagiosxi/var/cmdsubsys.log

[bseuser]

Hi,

I updated the Nagios XI from 5.7.2 to 5.7.3 version in our dev instance.
I am doing testing for failure modes which we observe in 5.7.2.

1. By using Bulk Host Cloning and Import option, I see still the Last check filed shows some wired date i.e., 1970-01-01. Attached the screenshot for your reference.
2. The force immediate check works fine in 5.7.3, and the last check and next check fields are updating.
3. When I create a new check by using CCM, I see the same the last check filed shows some wired date i.e., 1970-01-01 and when I ran/click on force immediate checks its updating the current date.

Please see the attached screenshot for your reference and help us to fix problem.

Thank You..

[bseuser]

Any update on my query?

[benjaminsmith]

Hi,

Do you know if you are running ndo2db or ndo3 on the upgraded version (5.7.3)? If you're not sure, please send the lastest profile since upgrading.

Please try to re-start the nagios process and then let the system run for about 10-15 minutes and attach the full nagios log to the thread.

Code: Select all

/usr/local/nagios/var/nagios.log

[bseuser]

Hi,

I said in my previous message, I installed it in our dev instances.
Yes, it's ndo3 running in our dev instance.
I send you the profile in PM for your reference.

Thanks,