Page 1 of 1
Service check very sloowly updated
Posted: Mon Aug 17, 2020 9:01 am
by CBoekhuis
After upgrade from 5.6.14 to 5.7.2 we see some unwanted behavior.
Example :
I've enabled a service check created a few weeks ago , end Apply configuration. The check showed up after minutes (normally a few seconds) and showed a Duration of 18xxx : 1-1-1970. Also running a manual Force check took 5-15 minutes to show up with result in GUI.
This happens after applying the configuration.
Gr,
Christian
Re: Service check very sloowly updated
Posted: Tue Aug 18, 2020 11:24 am
by cdienger
I'd like to get a profile from the XI server which can be generated under Admin > System Config > System Profile > Download Profile.
I'd also like to get a copy of a the database that has the current configuration. If the default database is being used then this can be done from the command line with:
Code: Select all
mysqldump -uroot -pnagiosxi nagiosql > nagiosql.sql
If the database has been offloaded to another machine then you'll need to modify the commands slightly to look like:
Code: Select all
mysqldump -h database_host_ip -uusername -ppassword nagiosql > nagiosql.sql
If you're not sure about the credentials or database server IP you can review /usr/local/nagiosxi/html/config.inc.php. A copy of this is also included in the profile so we can review it if necessary.
Please PM both the nagiosql.sql file and the profile to me.
Re: Service check very sloowly updated
Posted: Tue Aug 18, 2020 2:49 pm
by CBoekhuis
Requested files send in PM's.
I've also posted another issue reguarding a SQL error . Maybe the issues are related
Re: Service check very sloowly updated
Posted: Wed Aug 19, 2020 1:41 pm
by cdienger
Thanks for the heads up. The two issues may be related but for now we'll treat them as separate.
I did see some timeouts occurring with some of the checks. This may explain why it is taking so long to update after a forced check. I'd like you to enable some more debugging by editing nagios.cfg found under Configure > Core Config Manager > CCM Admin > Core Configs, and setting the max_debug_file_size, debug_level and debug_verbosity:
Code: Select all
debug_level=16
debug_verbosity=2
max_debug_file_size=10000000
Then save the changes and apply the config and the force another check for the service. Please note the host and service name and approximately how long it takes for it to update. Once it does, gather /usr/local/nagios/var/nagios.debug and then revert the changes back.
Re: Service check very sloowly updated
Posted: Wed Aug 19, 2020 2:50 pm
by CBoekhuis
PM with attachment send
Re: Service check very sloowly updated
Posted: Thu Aug 20, 2020 9:09 am
by tgriep
Follow this instructions to downgrade to ndoutils to see if this helps the objects to update quicker..
Code: Select all
service nagios stop
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
./init.sh
cd /tmp/nagiosxi/subcomponents/ndoutils
./install
chkconfig ndo2db on
service ndo2db start
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:
Run the Apply Config and see if the statuses and Objects are updated quicker.
Re: Service check very sloowly updated
Posted: Sat Aug 22, 2020 2:27 am
by CBoekhuis
Hi, also this issue seems to be resolved.
Thanks for your great help.
Re: Service check very sloowly updated
Posted: Mon Aug 24, 2020 8:04 am
by scottwilkerson
CBoekhuis wrote:Hi, also this issue seems to be resolved.
Thanks for your great help.
Great!
Locking thread