Crit Snmp Error On
Contents |
- check_mk service: CRIT - SNMP Error in 6.0 sec - possible to increase critical time limit? Next message: [Check_mk (english)] SNMP host - check_mk service: CRIT - SNMP Error in 6.0 cacti snmp error sec - possible to increase critical time limit? Messages sorted by: [ date
Snmp Error Cacti Centos
] [ thread ] [ subject ] [ author ] Nope - those errors do not look like timeouts on the snmp error 222 nagios side. Sorry. In fact, from what you have posted here, Im not sure why you think it's a timeout error? 7.5 seconds and 11.5 seconds are within the default timeouts. This is really snmp error index an error being returned from the clients. My advice would be to change the max_check_attempts to something greater then 1, so it will retry a few times before notifying you. To do that, you would do something like: extra_service_config['max_check_attempts"] = [ ("2", ALL_HOSTS, "Check_MK"), ] To change it to 2 tries, for instance. I also set my ping hosts to allow a few failures before notifying; extra_service_config['max_check_attempts"] = [
Snmp Error No Response Received
("3", ALL_HOSTS, "PING"), ] This slows down how quickly you get notified, but is well worth it to me to get rid of the majority of false alarms. Scott -----Original Message----- From: checkmk-en-bounces at lists.mathias-kettner.de [mailto:checkmk-en-bounces at lists.mathias-kettner.de] On Behalf Of Chris C Sent: Thursday, March 24, 2011 9:01 AM To: checkmk-en at lists.mathias-kettner.de Subject: Re: [Check_mk (english)] SNMP host - check_mk service: CRIT - SNMP Error in 6.0 sec - possible to increase critical time limit? Hm. Are you sure I should be looking at the Nagios side of the house. I'm trying to resolve issues like this.... 2011-03-24 08:07:30 SERVICE ALERT netapp Check_MK HARD OK - Agent version (unknown), execution time 7.5 sec 2011-03-24 08:06:34 SERVICE ALERT netapp Check_MK HARD CRIT - SNMP Error on 172.16.10.44, execution time 11.5 sec The netapp host is an snmp bulkwalk based based host. The netapp host is under heavier load during this tmie because of filer side ndmp backups and client side filesystem backups. Snmp is a low priority process on the filer so execution times will be slower. Is there a way to make an adjustment so I don't get an alert on the slower execution time? Thanks, /Chris C On Thu, Mar 24,
Hi everyone,I know this post was from awhile ago but I would like to ask the question again.Is it possible to increase the execution time limit for tcp agents snmp error 223 andsnmp based checks?My Nagios / Check_mk host has 210 hosts and 3200 services. snmp error 2007 Hosts thatare strictly snmp are using bulkwalk. I don't get a lot of falsealarms maybe less than 10
Snmp Error 2
per night but that is 10 less alerts that myguys get.Thanks!/Chris C Lander, Scott 2011-03-24 12:50:55 UTC PermalinkRaw Message Look around in your nagios.cfg file for something like# TIMEOUT VALUES# These http://lists.mathias-kettner.de/pipermail/checkmk-en/2011-March/002778.html options control how much time Nagios will allow various# types of commands to execute before killing them off. Options# are available for controlling maximum time allotted for# service checks, host checks, event handlers, notifications, the# ocsp command, and performance data commands. All values are in# seconds.service_check_timeout=900host_check_timeout=30event_handler_timeout=30notification_timeout=30ocsp_timeout=5perfdata_timeout=5-----Original Message-----From: checkmk-en-***@lists.mathias-kettner.de [mailto:checkmk-en-***@lists.mathias-kettner.de] On Behalf Of Chris CSent: Thursday, March 24, 2011 8:45 AMTo: checkmk-***@lists.mathias-kettner.deSubject: Re: [Check_mk http://checkmk-en.mathias-kettner.narkive.com/KQlQFKZs/check-mk-english-snmp-host-check-mk-service-crit-snmp-error-in-6-0-sec-possible-to-increase (english)] SNMP host - check_mk service: CRIT - SNMP Error in 6.0 sec - possible to increase critical time limit?Hi everyone,I know this post was from awhile ago but I would like to ask the question again.Is it possible to increase the execution time limit for tcp agents andsnmp based checks?My Nagios / Check_mk host has 210 hosts and 3200 services. Hosts thatare strictly snmp are using bulkwalk. I don't get a lot of falsealarms maybe less than 10 per night but that is 10 less alerts that myguys get.Thanks!/Chris C_______________________________________________checkmk-en mailing listcheckmk-***@lists.mathias-kettner.dehttp://lists.mathias-kettner.de/mailman/listinfo/checkmk-en------------------------------------------------------------------------------------This e-mail message is intended only for the personal use of the recipient(s) named above. If you are not an intended recipient, you may not review, copy or distribute this message. If you have received this communication in error, please notify the Hearst Service Center (***@hearstsc.com) immediately by email and delete the original message.------------------------------------------------------------------------------------ Chris C 2011-03-24 13:00:49 UTC PermalinkRaw Message Hm. Are you sure I should be looking at the Nagios side of the house.I'm trying to resolve issues like this....2011-03-24 08:07:30 SERVICE ALERT netapp Check_MK HARD OK - Agentversion (unknown), exe
Members Icinga PNP Icinga Exchange Monitoring Plugins NagVis Undone Threads Go to Page Bottom Sitemap monitoring-portal.org » Forum https://monitoring-portal.org/index.php?thread/21306-service-check-mk-crit-snmp-error-debug-log/ » Addons & Plugins » Check_MK » Service check_mk CRIT - https://support.nagios.com/forum/viewtopic.php?f=7&t=33209 SNMP Error & debug_log This site uses cookies. By continuing to browse this site, you are agreeing to our use of cookies. More details Your browser has JavaScript disabled. If you would like to use all features of this site, it is mandatory snmp error to enable JavaScript. jerico Beginner Posts 25 Number of hosts 300 Number of services 3000 Operating Systems Ubuntu Server 12.04 1 Service check_mk CRIT - SNMP Error & debug_log Jan 14th 2011, 8:52am Hallo Zusammen Bei meiner Installation überwache ich das IBM Blade Center mittels check_mk. Die Inventur der checks funktionierte ohne Probleme: check_mk snmp error 2 --checks=blade_bays,blade_blades,blade_blowers,blade_health,blade_mediatray,blade_misc,blade_powerfan,blade_powermod,ibm_imm_health -I BC2_AMM Auf den Blade Centers habe ich nun ca. zwischen 40 und 50 checks die mittels snmp überwacht werden. Mein Problem ist, dass der check_snmp service regelmässig mit folgenden Fehlermeldung auftaucht: CRIT - SNMP Error in 11.2 sec. Scheint als wenn der Wert des "Service check duration" einen bestimmten Wert überschreitet ein CRIT Alarm auslöst. Gibt es eine Möglichkeit dies zu tunen bzw. anzupassen. Dann habe ich noch ein zweites Problem. Habe einen snmp check bei dem mir folgender Fehler ausgegeben wird: UNKNOWN - invalid output from agent, invalid check parameters or error in implementation of check blade_bays. Please set debug_log to a filename in main.mk for enabling exception logging. Wenn ich im /etch/check_mk/main.mk folgende Zeile eintrage: debug_log = "/var/log/check_mk_debug.log", passiert leider noch nichts. Meine eingesetzte Version ist: check_mk 1.1.9i3 Vielen Dank für entsrpechende Tips und Tricks jerico Quote Report Content Go to Page Top jerico Beginner Posts 25 Number of hosts 300 Number of services 3000 Operating Syst
• All times are UTC - 6 hours [ DST ] Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group