Nagios Support Forum

I have recently upgraded Nagios from 5.6.5 to 5.7.5. The application was upgraded using the offline install. What I am experiencing is that it seems to take forever (not really, but minutes in some cases) to put a new service in. Also there are times that the application freezes for a while once services starts running. Am I doing something wrong??? Please let me know.

Often this is due to a corrupt MySQL table. Try running the back repair script, and let me know if that is successful. Run the following as root from the terminal. See here for complete instructions: run the database repair

If you PM me a system profile I can diagnose further. Get one by going to Admin (top menu) => System Profile (in the left menu), then clicking the blue button.

If you're unable to generate the the profile through the web interface, please try generating it from the command line by running these commands as root: Then send me the resulting /usr/local/nagiosxi/var/components/profile.zip file.
If the profile script fails, please include the ENTIRE output.

I ran the database repair command but am still getting slow response when I try to add a service. I also collected the profile.zip file, but am unable to forward it as it contains server, ip address, and user information that my employer has deemed not to leave the company. It will take me a while to sanitize this. Is there some data I can eliminate to quicken me sending this to you?

Also, just to let you know, we currently monitor 177 servers with approximately 2200 services. The Nagios server is a 4 core processor with 8 GB of RAM. Does this server need more resources?

Another thing that I just thought of is that my original Nagios XI (5.6.5) server was on a non-FIPS RedHat 7 server. My latest Nagios XI server (5.7.5) is on a FIPS Redhat 7 server. Could this be causing the problems I am observing?

What seems to be happening is that we get literally thousands of the following message by doing a tail -f /var/log/messages. ->

ndo2db: Warning: queue send error, retrying...

After this message stops Nagios XI works again. This usually takes between 7 and 10 minutes.

ndo2db shouldn't be running if you upgraded to 5.7.x. ndo2db is our older technology that basically listens on a UNIX socket for database inserts, then handles the actual insertion into the database. It has limits, being that it runs into issues when it tries to insert more than the database can handle. In newer versions (Nagios XI 5.7.0 and later), this was replaced by just writing directly to the database from the Nagios worker threads. In addition to being able to handle more database inserts, this resulted in an overall performance boost, too.

If you PM me a system profile I can diagnose further. Get one by going to Admin (top menu) => System Profile (in the left menu), then clicking the blue button.

The problem seems to be with Nagvis. It appears that Nagvis uses the no2db service. Is there a way of configuring Nagvis to use something else? We have spent a large amount of time getting this to work in our environment.

Received NagiosConfigFiles.zip. I sent you a message about it, but I'll reply here too for posterity.

dchurch wrote:Unfortunately this is not a system profile, and doesn't tell me anything about how NagViz is configured.

Get a system profile zip by going to Admin (top menu) => System Profile (in the left menu), then clicking the blue button.

If you're unable to generate the the profile through the web interface, please try generating it from the command line by running these commands as root:

Code: Select all

rm -rf /usr/local/nagiosxi/var/components/profile*
/usr/local/nagiosxi/scripts/components/getprofile.sh SUPPORT

Then send me the resulting /usr/local/nagiosxi/var/components/profile.zip file.
If the profile script fails, please include the ENTIRE output.

Any word on the file I PMed to you? I'm trying to figure out why when I add a new service and apply it, I have to wait upwards of 10 minutes before I can use Nagios again.