Re: [Nagios-users] How to check Internet access and/or DNS?
On 24/01/06, Marc Haber <[EMAIL PROTECTED]> wrote: > On a second thought, how do I check DNS? I mean, even with the > Internet down, my local DNS servers probably can correctly serve DNS > records for my local network which they're authoritative for. So, does > it make sense to check the DNS servers once for an external host (like > www.nagios.org) and once for an internal host, resulting in two > services being checked on the DNS server? Just do checks for a few DNS entries - your ISP's website, your externally hosted website, your internal website, nagios.org... If most of these go down at the same time as your web check to google.com, you know there's something bad happening :) Brian. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 ___ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
[Nagios-users] Possible bug - limit on number of config objects?
Hi all, OS: Debian Linux 3.1 Nagios version: 2.0b6 Compile options: --prefix=/usr/local/nagios I've hit an "interesting" issue. CGIs are reporting that they cannot read object configuration data, however, permissions are fine. The "only" thing that changed was the addition of more hosts and services to monitor. The nagios daemons appear to be running fine, there are no useful error messages that I can find. I currently have the following numbers being monitored in nagios: 2691 "define host"s 2673 "define hostextinfo"s 2783 "define service"s When we reduce the numbers by a few hundred, the CGIs work fine, so I'm thinking there's a hardlimit in the CGIs. Any ideas? The error reported is: "Whoops! Error: Could not read object configuration data!" I could not find any useful error messages in any logfile." Here is the output of: /usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg Nagios 2.0b6 Copyright (c) 1999-2005 Ethan Galstad (http://www.nagios.org) Last Modified: 11-30-2005 License: GPL Reading configuration data... Running pre-flight check on configuration data... Checking services... Checked 2777 services. Checking hosts... Checked 2687 hosts. Checking host groups... Checked 22 host groups. Checking service groups... Checked 16 service groups. Checking contacts... Checked 1 contacts. Checking contact groups... Checked 1 contact groups. Checking service escalations... Checked 13 service escalations. Checking service dependencies... Checked 0 service dependencies. Checking host escalations... Checked 0 host escalations. Checking host dependencies... Checked 0 host dependencies. Checking commands... Checked 32 commands. Checking time periods... Checked 4 time periods. Checking extended host info definitions... Checked 2672 extended host info definitions. Checking extended service info definitions... Checked 0 extended service info definitions. Checking for circular paths between hosts... Checking for circular host and service dependencies... Checking global event handlers... Checking obsessive compulsive processor commands... Checking misc settings... Total Warnings: 0 Total Errors: 0 Things look okay - No serious problems were detected during the pre-flight check Thanks, Brian. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 ___ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
