Directory

Checking for reverse doesn't work, eg.:

#check_dns_host.pl -H 8.8.8.8.in-addr.arpa -Q REVERSE -W 1000 -C 1000

DNS OK! QUERYRETURNCODE=(NOERROR => 8.8.8.8.in-addr.arpa) ANSWERS=(0) QUERY_RETURNVAL=() ELAPSED=(8 ms) | DurationMS=8

Reverse checks always return ANSWERS=(0).

Forward seems to work fine.

Thanks for your tool. I needed something to replace the default check_dns because I need to verify the existence of a PTR record.

Unfortunately your tool does what I want it to do. It says "DNS OK" when no PTR is returned, because the tool only checks for errors instead of checking if an actually record is returned.

Very good work. This plugin does exactly what it needs to. There is little I can add to this review other that it is just working.

You do need some Perl libraries and the Nagios plugin libraries to be able to use the plugin, but it should be no problem to install them.

Plugin works great, but has compatibility issues with latest version of rsnapshot. "interval" is now deprecated and replaced by "retain". So the plugin needs some updating.

The plugin itself works just great. There is however a minor issue. In my case the plugin identifies itself to the remote server with ' HELO localhost.localdomain'. My server does not accept this is as part of antispam solution.

The fix is to add "Hello=>'your.nagios.server'" to the new class instance definition:

$smtp = Net::SMTP->new($smtp_server, Port=>$smtp_port, Timeout=>$timeout,Debug=>$smtp_debug, Hello=>'nagios.example.com');

This plugin was exactly what I was looking for, because we sometimes have Apache machines that reached their MaxClients settings.

However, out of the box this plugin does not work as expected. The script counts the number of 'dots' on the /server-status/ page. The number of dots is the number of ServerLimit minus in use slots.

However, ServerLimit is 256 by default and MaxClients is 150 by default. So if your server is full (MaxClients reached) this module believes there are still 256-150 = 106 open slots available, but that is not true.

To resolve this you have to set your CRITICAL level to atleast 106 or adjust Apache.

Also, this module returns 'WARNING' when Apache is down. I believe this should be 'CRITICAL'. If your Apache is unresponsive due to MaxClients reached, the module will return WARNING instead of CRITICAL while your service is nonresponsive.