Nagios Support Forum

I believe I can probably add an update on the ndo2db problem machine I have and include today's profile zip for analysis. From our discussion during the conference, I had a cron entry to bounce nagios then ndo2db at 07:15AM every morning as a band aid. I have changed it to only bounce the ndo2db process and am monitoring for the results.

Thanks for the profile!

I had a cron entry to bounce nagios then ndo2db at 07:15AM every morning as a band aid.

Let us know how this is working for you.

Update, so far, our morning bounce of the ndo2db process only is working to keep the process stable and monitoring queue balanced.

Thanks for the feedback! Eric has been looking into this. We will get back to you as soon as we find out what is causing the issue.

Just checking in to see if you have any updates on this problem? I migrated my problem Nagios VM to the same hardware my other Nagios VMs that do not have the problem but no luck. The problem continued on different hardware.

We're still pushing hard on NDO changes. ndomod is largely done with updates, and ndo2db is being worked on as we speak. We will definitely be letting you know as soon as a testable change is in place!

Well, my problem child server with the frequent ndo2db problem is to the point it will stop scheduled checks in NagiosXI within 1 or 2 hours. I could really use any beta, untested, patch you have if available. Thanks, Marcus

Hey Marcus, we will let you know when/if something of use may be available for testing. Glad to hear you're willing to help test!

Emergency question to everyone seeing this issue: everyone with this issue virtual? I'm about to give the heck up and tell my boss to order a new blade that will only have RHEL and Nagios, no VM of any sort. I had to babysit my nagios all weekend and as ndo either stated hogging CPU or nagios schedule just stopped, I had to restart the service. Today my server is in such bad shape I finally had to just reboot and now its still acting all crazy. I can't wait til Wednesday night when I plan to offload DB and ndo, but not sure if that's going to help at this point!

I know how you feel. Fortunately for me, my problem server is not my primary nagios system but is critical for my network team. It only has 2500 monitors and plenty of hardware to spare. I'm considering rebuilding another image myself. Meanwhile, since the problem only impacts nagiosXI, I have the users working from the Thruk interface (which is basically nagios core) so the problem is transparent to them. While I'm not recommending this by any means, I have cronned a restart of the ndo2db process every 10 mins to keep the nagiosXI interface updated. This is just a band aid until I find a permanent fix or a patch for this problem is released.