Nagios Support Forum

What version of NSClient are you using? If memory serves, NSC.ini is the 3.x-type ini file, and NSClient 3.x is probably not what you want.

That said, the error looks like you have a networking issue. Firewall, perhaps?

Is there perhaps another service also checking memory?

What version of Core is this? If memory serves, there are some different notification options in different versions.

Can you upload the check_dhcp you are using? Plugins can be named anything, so support will need to see the actual code to know for sure they are giving you the proper documentation, should documentation exist. Did you try a -h flag on the plugin to see if it had help?

My suspicion is these were events in MySQL (or Postgres). Restarting the database might have done it, but you might have needed to clear the queues. I will leave it to someone in support to give you the info on clearing the queues.

What MTA are you using? If you are using postfix or sendmail, if you do a web search for 'mail queue' without the quotes then you will see results.

I have not kept up with the newest features, so someone from support can correct me, but I do not believe Nagios itself does any actual queuing.

Not really a Core issue, but wasn't sure where to put it.

If you go to the top right of exchange.nagios.org and press the "+" as seen below you end up at Feel free to close once you've passed it along to Ludmil (or whomever).

Thanks for sharing! Are we ready to lock this one up?

As long as the service has some hosts when you re-enable, it should work.

Why not just use NSClient .4.4? That works for you, correct? Here's the previous thread: https://support.nagios.com/forum/viewtopic.php?t=47359

By default, on many OSes, the access.conf is completely commented out. Do you have anything related to apache in there? Anything about apache in the sudoers?