Nagios Support Forum

We, the Dutch, would say Now breaks my wooden shoe! I am very surprised, yesterday I installed the server on SLES12 SP3 x64, and the feared error did not show itself all night. My assumption is that the bug is confined to openSUSE 42.3 (x86_64) only. To be honest, for now my problem is solved. But s...

We were on 4.3.3 only for a day or two, just for the test. I moved us back to 4.3.4 after the conclusion was drawn. I'm not familiar with the standard procedures, why would I want to move this to Github? I will of course, if required to get to a solution ;) Edit: The setup has been running on CentOS...

Great idea! I'm curious if the bug persists on another OS. The weekend would be a great test. I have chosen Centos 7 x64 for this test. I'll get on it right away. Update 14:15 CEST: It's not easy, lot's of checks are broken because of NRPE version conflicts, missing perl modules and what not. I'm fi...

Maybe you can an idea of our workload based on the performance information?

dwhitfield thank you. The io-wait times in top are 0, I guess a ramdisk would not be able to lower that? Since we're on Nagios Core the system isn't using ndo2db out of the box, and ours is currently not using that module. Is there any way to let Nagios handle this error? Just by discarding the che...

This is what happend the last 24 hours. - Memory usage went down to around 10% - CPU load as reported by VMWare hovers little under 20% - CPU ready time hovers between 1200 and 1600 ms. Counting the errors in the nagios logfiles results in: - 3870 IO broker registration failures. - 1489 checks that ...

dwhitfield not yet, I would like to see if the tips provided actually resolve the issue. spkane that's great news, I'll double the resources on the VM and see what happens. Although I'm not sure if that would improve our problem since the CPU load hovers around 35-40% according to VMWare. And the m...

I've set debug to -1. This is a fragment of the old setting: 2017-09-08 9:15:05 [1504854905.450313] [016.0] [pid=60058] Attempting to run scheduled check of host 'Eduarte [helicon.educus.nl]': check options=0, latency=0.000000 2017-09-08 9:15:05 [1504854905.450322] [016.0] [pid=60058] archives nagio...

I'm affraid I can't discover a pattern of any kind. I've been chewing on this for over a week now. What I noticed is that Nagios has to be running for a few hours before a major failure occurs. I have done some juggling with the logfiles of last few days. The result is that checks that get executed ...

Success! [1504784358] Event broker module 'NERD' deinitialized successfully. [1504784362] Nagios 4.3.3 starting... (PID=60058) [1504784362] Local time is Thu Sep 07 13:39:22 CEST 2017 [1504784362] LOG VERSION: 2.0 [1504784362] qh: Socket '/usr/local/nagios/var/rw/nagios.qh' successfully initialized ...