New hosts remain pending after upgrade to 5.7.3

[DennisPR]

I have reboot the server today (to add extra CPU's to the VM) and it seems that the ndo2db is running by default

Code: Select all

[root@localhost ~]# service ndo2db status
ndo2db (pid 3764) is running...
[root@localhost ~]# service ndo2db stop
Stopping ndo2db: done.
[root@localhost ~]# ps aux | grep ndo2db
root     19508  0.0  0.0 103320   860 pts/1    R+   01:02   0:00 grep ndo2db

[cdienger]

Run:

Code: Select all

systemctl disable ndo2db

and then reboot to verify that it doesn't start again.

[DennisPR]

Shouldn't ndo2db be running all the time ?
If I stop ndo2db Nagios doesn't execute services anymore

In what version of Nagios XI will this be fixed pls ?
At this time I am running XI 5.7.4 with ndoutils 5.6.14 and can't upgrade to 5.7.5 because I don't see any fixes about ndoutils in the 5.7.5 changelog ?

[cdienger]

The last profile I have shows this module is loaded:

Code: Select all

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

so the ndo2db process should no longer be needed with that. If you switch to using ndoutils instead, then the above line should be commented out and this line used instead:

Code: Select all

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

and in that case the ndo2db process should be run.

We're aiming for 5.8 to include fixes to the new ndo module.

[DennisPR]

I found the following lines in /usr/local/nagios/etc/nagios.cfg

Code: Select all

# NDOUtils module^M
# Commented out by NDO 'make install-broker-line' on Mon Oct 19 11:26:29 CEST 2020
#broker_module=/usr/local/nagios/bin/ndomod.o config_file=/usr/local/nagios/etc/ndomod.cfg^M
...
# Added by NDO 'make install-broker-line' on Mon Oct 19 11:26:29 CEST 2020
#broker_module=/usr/local/nagios/bin/ndo.so /usr/local/nagios/etc/ndo.cfg
broker_module=/usr/local/nagios/bin/ndomod.o config_file=/usr/local/nagios/etc/ndomod.cfg

19 October is the date that we excetuted the last Nagios XI update.
How do I determine what's best... Using the ndo module or service ?
Looks like the update script installed the module so I guess I need to turn off by running

Code: Select all

systemctl disable ndo2db

That's all I need to do ?

[cdienger]

The new module has had issues with not updating statuses so I would recommend the old method for now. I think there may have been some confusion with what steps were done when. To be clear - you're still seeing issues with the statuses not updating and nagios.cfg currently contains:

Code: Select all

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

?

If so, then that would mean the ndo2db is being used and what we'd suggest. In which case the ndo2db service should running.

Please provide a fresh profile so we can take a look a the current setup/logs.

[junkertf]

Hello,

Same issue here after upgrade from 5.6.8 to 5.7.5

Don't understand why let ppl do upgrade in these situation on the systems.
Eighter or, i can add it to the solution with my profiles.

Our TEST not produce the symptoms detailed in these Thread, and our PROD system produce it.
We decided to revert back our version to the originally working 5.6.8 version.

I post our profiles to cdinenger.

Thank you, best regards,

Ferenc

[cdienger]

XI 5.8 was released today and addresses the pending issue seen in 5.7.x releases.