Page 3 of 4
Re: Lost all what was in Scheduled Downtime after upgrade
Posted: Fri Sep 25, 2020 8:19 am
by steph007
To recap the problem
mysqld run at 100%+ CPU as soon as I put Host or Service in Scheduled Downtime.
When mysqld run high in CPU, Force Check of Service have big delay to run and all regular check are delay. Not 10 sec. Can be 10 minutes or more!
Re: Lost all what was in Scheduled Downtime after upgrade
Posted: Fri Sep 25, 2020 3:46 pm
by benjaminsmith
Hi
@Steph007,
We have a bug report submitted for an issue with scheduled downtime brokering on startup in ndo3 (new database backend). This will be fixed in the next maintenance release.
Sorry about the inconvenience, but if this is a production server, I would recommend downgrading to the previous version again.
Benjamin
Re: Lost all what was in Scheduled Downtime after upgrade
Posted: Mon Sep 28, 2020 9:26 am
by steph007
Donwgrading to the previous version?!! 5.7.2?!!
Or you talk about NDO?
I prefer just donwgrading NDO again like I did in 5.7.2. Can I with version 5.7.3?
Re: Lost all what was in Scheduled Downtime after upgrade
Posted: Tue Sep 29, 2020 9:59 am
by benjaminsmith
Hi,
Sorry for the confusion, that's right - downgrading NDO again as before.
For a standard installation ( without offloaded databases), the steps are as follows.
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:
Re: Lost all what was in Scheduled Downtime after upgrade
Posted: Tue Sep 29, 2020 3:06 pm
by steph007
I did the rollback of NDO.
Look good for now.
Really waiting for a real fix.
Re: Lost all what was in Scheduled Downtime after upgrade
Posted: Wed Sep 30, 2020 11:26 am
by benjaminsmith
Hi,
Thanks for being flexible. If you want to check back in a week or so I can give you an update on what's happening with the next release.
Best Regards,
Benjamin
Re: Lost all what was in Scheduled Downtime after upgrade
Posted: Tue Oct 20, 2020 1:28 pm
by steph007
Hi,
With the release of the new version 5.7.4, how are you confident that my problem will be fixed?
Re: Lost all what was in Scheduled Downtime after upgrade
Posted: Wed Oct 21, 2020 11:15 am
by benjaminsmith
HI,
We did fix the issue with scheduled downtime on startup, here's the changelog.
NDO - 3.0.4
-----------
- Fixed issue with downtime brokering on startup
- Fixed logging of failed queries for WRITE_HOSTS/WRITE_SERVICES/WRITE_CONTACTS
- Fixed blank host/service status rows that may get added during a hard restart
However, since this system did have issues with check results not updating and you had to downgrade multiple times, I would recommend holding off until the next release. We're still seeing a few issues check results not coming in, especially on Cent 6 systems.
Benjamin
Re: Lost all what was in Scheduled Downtime after upgrade
Posted: Wed Oct 21, 2020 1:29 pm
by steph007
Can I update to 5.7.4 and roolback again NDO right after?
I'm asking because I'm actually planing migrate NagiosXI to centos7.
Since the new centos image I downloaded is already at 5.7.4 I need also to be at 5.7.4 to do the backup/restore procedure of NagiosXI.
So, another question, does the backup/restore of NagiosXI will get NDO config once restore on the new centoos7 image?
Re: Lost all what was in Scheduled Downtime after upgrade
Posted: Wed Oct 21, 2020 3:40 pm
by benjaminsmith
Hi,
Can I update to 5.7.4 and rollback again NDO right after?
Yeah, you can roll back NDO without causing any issues. In fact, if you downgraded, it should just leave the previous version running to avoid impacting those systems that had to downgrade.
If you installed a fresh 5.7.4 system it will be using ndo3, but just run the downgrade again and then change the broker module line as shown in the instructions, then run the restore script.
If you run into any troubles running the restore on the new VM, just let us know, and we can assist you.
Benjamin