Hi, Sorry but it took me a while to get into this monitoring app. All problems are solved now and everything is running just fine ! :-) Just wanted to say thanks everyone for help.
In case other people get into the same situation as i with crash reports after upgrading from very old check_mk revisions to the latest stable one. As Andreas mentioned, the problem was related to the check files in the folder 'local/share/check_mk/checks'. That one was full of the problematic if64, netapp,oid..and other files which generated tons of crash logs on the monitoring system. After moving away the files to a tmp folder, re-running discovery 'Tabula Rasa' & Services' all issues are gone. As i still received handful of errors, i updated old client check_mk agents, ilo on blade server as also firmware on our wifi network which i monitor as well. System is happy again :-) personal rule for the future: - Don't forget to clone actual monitoring page first. So you have a fresh backup to test the upgrade. - Check files in local/share/check_mk/checks and verify if they are compatible with latest check_mk revision - else move them away ( for testing ) - Read crash logs carefully in /var/check_mk/crashed_checks/ - they might already guide you to the problem and solution - Test if firmware or newer check_mk agent on client side fix the issue Best regards, Henrik 2017-03-13 22:12 GMT+01:00 Andreas Döhler <[email protected]>: > This is no problem with the "force if64 check type" settings. > > @Henrik you installed a package with the check "if64_neighbor" and this > check replaces the normal interface check. > Remove this plugin from your local structure and take a look at your > disabled check types settings. > > Best regards > Andreas > > Jarek Nowak <[email protected]> schrieb am Mo., 13. März 2017 um 18:20 Uhr: > >> in my actual check_mk version (1.2.8p14) there is an "force if instead of >> if64" rule in the rulesets (search for if64 there), but as far as i recall >> there was an previous rule (in earlier versions) which stated the opposite. >> As stated before, i would suggest to delete and re-inventorize one >> problematic host, for trying weathe the problem is persistent, before >> ruling if64 type out, use the rule option as last resort. >> this problem may vanish after software/firmware update either, so recheck >> that after updating when you use that ruleset. >> >> w/ regards >> Jarek >> >> 2017-03-13 17:27 GMT+01:00 Jarek Nowak <[email protected]>: >> >> as far as i recall there was an option in the rulesets for >> (interface)discovery, ive encountered similar Problems after upgrading omd >> 1.10 to an (homebrew) omd Edition where i patched in an upstream Check_mk >> (git) Edition and that rules where implemented. Ill check weather i can >> find it, when I'm home. >> >> Am 13.03.2017 16:37 schrieb "Henrik Schöpel" <[email protected]>: >> >> Hi Jarek, >> >> Couldn't find any information how to >> >> 2017-03-09 20:56 GMT+01:00 Jarek Nowak <[email protected]>: >> >> did you try to re-discover all (failing ) devices? as far as i remember >> you needed to explizitly chose if64 type checks in erlier versions. >> >> Am 09.03.2017 09:11 schrieb "Henrik Schöpel" <[email protected]>: >> >> Hi, >> >> I have a pretty strange problem since i upgraded check_mk version >> 1.2.6p16 to the latest stable revision ( 1.2.8p18 ). >> >> Upgrade went smooth but now i get bombed with lot of 'UNKNOWN - check >> failed' errors. Error seem to be if64 related as i can see that in the web >> interface. I only see this one mostly on our Network devices but also >> handful of servers. It would be really great if someone maybe have an idea >> to get this problem fixed. >> >> The crashlog is super long so i would like to paste just a few lines. If >> needed, i can post the whole one. >> >> >> >> >> Crash Type check >> Time 2017-03-09 07:48:20 >> Operating System el7 >> Check_MK Version 1.2.8p18 >> Python Version 2.7.5 (default, Nov 6 2016, 00:28:07) [GCC 4.8.5 >> 20150623 (Red Hat 4.8.5-11)] >> Exception >> >> TypeError (if64_scan_function() takes exactly 2 arguments (1 given)) >> >> Traceback >> >> File "/omd/sites/monitoring/share/check_mk/modules/discovery.py", line >> 260, in check_discovery >> ipaddress=ipaddress) >> >> File "/omd/sites/monitoring/share/check_mk/modules/discovery.py", line >> 865, in get_host_services >> return get_node_services(hostname, ipaddress, use_caches, >> do_snmp_scan, on_error) >> >> File "/omd/sites/monitoring/share/check_mk/modules/discovery.py", line >> 890, in get_node_services >> services = get_discovered_services(hostname, ipaddress, use_caches, >> do_snmp_scan, on_error) >> >> File "/omd/sites/monitoring/share/check_mk/modules/discovery.py", line >> 874, in get_discovered_services >> new_items = discover_services(hostname, None, use_caches, >> do_snmp_scan, on_error, ipaddress) >> >> File "/omd/sites/monitoring/share/check_mk/modules/discovery.py", line >> 602, in discover_services >> check_types = snmp_scan(hostname, ipaddress, on_error) >> >> File "/omd/sites/monitoring/share/check_mk/modules/discovery.py", line >> 704, in snmp_scan >> result = scan_function(oid_function) >> >> Local Variables >> >> {'basename': 'if64_neighbor', >> 'check': {'check_function': <function check_if64_neighbor at 0x27e4de8>, >> 'default_levels_variable': 'if_default_levels', >> 'extra_sections': [], >> 'group': 'if', >> 'handle_empty_info': False, >> 'handle_real_time_checks': False, >> 'has_perfdata': True, >> 'includes': ['if.include', 'cdp_lldp_dulpex.include'], >> 'inventory_function': <function inventory_if64_neighbor at >> 0x292cc80>, >> 'node_info': True, >> 'parse_function': None, >> 'service_description': 'Interface %s', >> 'snmp_info': [('.1.3.6.1.2.1', >> ['Max recursion depth reached', >> 'Max recursion depth reached', >> 'Max recursion depth reached', >> 'Max recursion depth reached', >> 'Max recursion depth reached', >> 'Max recursion depth reached', >> 'Max recursion depth reached', >> 'Max recursion depth reached', >> 'Max recursion depth reached', >> 'Max recursion depth reached', >> 'Max recursion depth reached', >> 'Max recursion depth reached', >> 'Max recursion depth reached', >> 'Max recursion depth reached', >> 'Max recursion depth reached', >> 'Max recursion depth reached', >> 'Max recursion depth reached', >> 'Max recursion depth reached', >> 'Max recursion depth reached', >> 'Max recursion depth reached']), >> ('.1.0.8802.1.1.2.1.4.1.1', >> ['Max recursion depth reached', >> 'Max recursion depth reached', >> 'Max recursion depth reached', >> 'Max recursion depth reached']), >> ('.1.3.6.1.4.1.9.9.23.1.2.1.1', >> ['Max recursion depth reached', >> 'Max recursion depth reached', >> 'Max recursion depth reached', >> 'Max recursion depth reached'])], >> 'snmp_scan_function': <function if64_scan_function at >> 0x292cde8>}, >> >> _______________________________________________ >> omd-users mailing list >> [email protected] >> http://lists.mathias-kettner.de/mailman/listinfo/omd-users >> >> >> >> >> >> -- >> Henrik Schöpel >> >> https://www.xing.com/profile/Henrik_Schoepel >> http://www.mobygames.com/developer/sheet/view/developerId,260068/ >> >> >> _______________________________________________ >> omd-users mailing list >> [email protected] >> http://lists.mathias-kettner.de/mailman/listinfo/omd-users >> > -- Henrik Schöpel https://www.xing.com/profile/Henrik_Schoepel http://www.mobygames.com/developer/sheet/view/developerId,260068/
_______________________________________________ omd-users mailing list [email protected] http://lists.mathias-kettner.de/mailman/listinfo/omd-users
