[Check_mk (english)] Problem with a Kentix Multisensor (Crash dump)

Jonas_Neumann · October 3, 2019, 11:28am

Hi,

I’m having trouble getting our “Kentix MultiSensor-LAN” to work in our 1.5.0p22 CMK installation:

OMD[sitename]:~$ cmk --check-discovery kentix
UNKN - check failed - please submit a crash report!
Crash dump:\nH4sIAIXXlV0C/+1WW2/bNhT2834Fp5cmgaObb4mBPKTJ2iZdNmzBmiwXCDRFy4QlkiCp2E7R/75DydfVSBMsGzqA34vEc+N3SB4eEoX1yGd8KBr/GkJAt9u236jX7tTfTljJAZ04jBtRq9PutDqtbgj6qNOLew0UNv4DlNpghVDDLoEqsGFEb7X7ln6ezPL7P8FnjwhFvT7yOM6Y0HfcayJPzsxI8OSBKs0Et9rY7/lRF+2kdIjL3DTRJZUIHaA4jA6bKG7124f9KNpFd/z2/ckJOvBjP7y3oWjKzDwGgYlWwSU2Iw3iWy8Q0gSiSIP5fDqI/I4fyjj2wSUYsIpTZaGZoTpY24sgFwTnQc4GQR33KdOlUdzzH5l8nqnfe65dIHNs9nPGy2n8bB8Y7Zvxi8xFnr7IPp3xXODn+1j9vsRkjDOqn+Xl3dudnpLEzGR1mM54Sqc/KSWU9Sf2klnqyIiSKuHKQWFCBzCXPQm3354pIMU4GWBNgyoM45kvZxDsIIaAE4WlpGlSqZJhyYmdBgrclLqJbEBDpwZ+c8GzZG0sqRqm2GB0hFa+OyOhDccFbaI9rDIw29sbT+zfrs33RWRTpomA4z2r2bbidnO+EMlSVXGl6oERqoFIklGTWArJQrhGiEmcpopqIKVFqUDZRAXUJVt4EFt0IIRCo3Ybju48hZmmd94/Jh+FcQhUv+ZnE1DUlIrX5LlI6auQfw3KnQXlDVbb1nzhCwfpOyHfbS3Ib+FmU+B0kkDoosphYfN9sO9FPUv+K1KWNgRCljYUIFa40EZBPUOdooROKSkNXRXHzlaWWxOry0rmZcZ4UmuX2fRfng5cC8l8rYKN6ev84sNDm18pwZAmE2ZG0NmUptUVUnW+VVVsKnbmgRIiuKHcPL3UeoTV/NJLinH9o4Mx+LFpggsJtLgWyq5rN7Jdtpprq957A2su36AKfTSE5mB2oG3R2+h+N4jCpndv7/O17r/ox9a5arjJA4S3GjpLR+ePIrtq/cGvP2STi3fT9sXpW0JPjyd2/MssTX8+Ftl5POa/suNJ/Z+XN8UBjN8OriITnUebPnUMwq8/RenK/nB4U0xH6Yff80HxaVzN+aRvqE/YMR+8B99L0j1794Tt5eTj2Uk6+fP6/PHm6jfLqze8Do9stik1mOU21c/z+1qURpZm2cjQEPQ0RftI5hQODNLloGAGYVR1PaSoFMr8aGPZow5+vMxzGNmzZKPUW+Qt+8GiTW70hbo+Vs5MJySHpytVIBviXFMr5HYTE80LuSYtNdV/lxWYl7CJdSdeiVOqiWJy8V47qfhcfESnSypfwMqwwhKER3oYhVEUd3x4wYdte8GK+kzkvUV7f8B5WWWTM22gsuFVgGABkRgihXlGvS8/NBwcHBwcHBwcHBwcHBwcHBwcHBwcHBwcHBwcHF4JfwE+9U9JACgAAA==

Did anyone encounter the same problem? I have attached the Log file.

cmk_kentix (81.9 KB)

andreas-doehler · October 3, 2019, 12:21pm

Hi Jonas,

it’s better to do a “cmk --debug -vv --check-discovery kentix”

Now you get a readable message.

Best regards

Andreas

···

Am Do., 3. Okt. 2019 um 13:28 Uhr schrieb Jonas Neumann cmk@tschanness.de:

Hi,

I’m having trouble getting our “Kentix MultiSensor-LAN” to work in our 1.5.0p22 CMK installation:

OMD[sitename]:~$ cmk --check-discovery kentix
UNKN - check failed - please submit a crash report!
Crash dump:\nH4sIAIXXlV0C/+1WW2/bNhT2834Fp5cmgaObb4mBPKTJ2iZdNmzBmiwXCDRFy4QlkiCp2E7R/75DydfVSBMsGzqA34vEc+N3SB4eEoX1yGd8KBr/GkJAt9u236jX7tTfTljJAZ04jBtRq9PutDqtbgj6qNOLew0UNv4DlNpghVDDLoEqsGFEb7X7ln6ezPL7P8FnjwhFvT7yOM6Y0HfcayJPzsxI8OSBKs0Et9rY7/lRF+2kdIjL3DTRJZUIHaA4jA6bKG7124f9KNpFd/z2/ckJOvBjP7y3oWjKzDwGgYlWwSU2Iw3iWy8Q0gSiSIP5fDqI/I4fyjj2wSUYsIpTZaGZoTpY24sgFwTnQc4GQR33KdOlUdzzH5l8nqnfe65dIHNs9nPGy2n8bB8Y7Zvxi8xFnr7IPp3xXODn+1j9vsRkjDOqn+Xl3dudnpLEzGR1mM54Sqc/KSWU9Sf2klnqyIiSKuHKQWFCBzCXPQm3354pIMU4GWBNgyoM45kvZxDsIIaAE4WlpGlSqZJhyYmdBgrclLqJbEBDpwZ+c8GzZG0sqRqm2GB0hFa+OyOhDccFbaI9rDIw29sbT+zfrs33RWRTpomA4z2r2bbidnO+EMlSVXGl6oERqoFIklGTWArJQrhGiEmcpopqIKVFqUDZRAXUJVt4EFt0IIRCo3Ybju48hZmmd94/Jh+FcQhUv+ZnE1DUlIrX5LlI6auQfw3KnQXlDVbb1nzhCwfpOyHfbS3Ib+FmU+B0kkDoosphYfN9sO9FPUv+K1KWNgRCljYUIFa40EZBPUOdooROKSkNXRXHzlaWWxOry0rmZcZ4UmuX2fRfng5cC8l8rYKN6ev84sNDm18pwZAmE2ZG0NmUptUVUnW+VVVsKnbmgRIiuKHcPL3UeoTV/NJLinH9o4Mx+LFpggsJtLgWyq5rN7Jdtpprq957A2su36AKfTSE5mB2oG3R2+h+N4jCpndv7/O17r/ox9a5arjJA4S3GjpLR+ePIrtq/cGvP2STi3fT9sXpW0JPjyd2/MssTX8+Ftl5POa/suNJ/Z+XN8UBjN8OriITnUebPnUMwq8/RenK/nB4U0xH6Yff80HxaVzN+aRvqE/YMR+8B99L0j1794Tt5eTj2Uk6+fP6/PHm6jfLqze8Do9stik1mOU21c/z+1qURpZm2cjQEPQ0RftI5hQODNLloGAGYVR1PaSoFMr8aGPZow5+vMxzGNmzZKPUW+Qt+8GiTW70hbo+Vs5MJySHpytVIBviXFMr5HYTE80LuSYtNdV/lxWYl7CJdSdeiVOqiWJy8V47qfhcfESnSypfwMqwwhKER3oYhVEUd3x4wYdte8GK+kzkvUV7f8B5WWWTM22gsuFVgGABkRgihXlGvS8/NBwcHBwcHBwcHBwcHBwcHBwcHBwcHBwcHBwcHF4JfwE+9U9JACgAAA==

Did anyone encounter the same problem? I have attached the Log file.

checkmk-en mailing list

checkmk-en@lists.mathias-kettner.de

Manage your subscription or unsubscribe

https://lists.mathias-kettner.de/cgi-bin/mailman/listinfo/checkmk-en

Jonas_Neumann · October 3, 2019, 1:29pm

Hi Andreas,

I’ve checked our device and it seems to be a very old firmware. I’ll see if I can update it and check back. If someone wants to extend the check for old devices the MIBs are on the end of this mail.

The traceback is:

Traceback (most recent call last):
File “/omd/sites/SITENAME/bin/cmk”, line 96, in
exit_status = modes.call(o, a, opts, args)
File “/omd/sites/SITENAME/lib/python/cmk_base/modes/init.py”, line 80, in call
return mode.handler_function(*handler_args)
File “/omd/sites/SITENAME/lib/python/cmk_base/modes/check_mk.py”, line 1412, in mode_check_discovery
return discovery.check_discovery(hostname, ipaddress=None)
File “/omd/sites/SITENAME/lib/python/cmk_base/checking.py”, line 82, in wrapped_check_func
status, infotexts, long_infotexts, perfdata = check_func(hostname, *args, **kwargs)
File “/omd/sites/SITENAME/lib/python/cmk_base/discovery.py”, line 324, in check_discovery
services = _get_host_services(hostname, ipaddress, sources, multi_host_sections, on_error=“raise”)
File “/omd/sites/SITENAME/lib/python/cmk_base/discovery.py”, line 1020, in _get_host_services
return _get_node_services(hostname, ipaddress, sources, multi_host_sections, on_error)
File “/omd/sites/SITENAME/lib/python/cmk_base/discovery.py”, line 1025, in _get_node_services
services = _get_discovered_services(hostname, ipaddress, sources, multi_host_sections, on_error)
File “/omd/sites/SITENAME/lib/python/cmk_base/discovery.py”, line 1063, in _get_discovered_services
new_items = _discover_services(hostname, ipaddress, sources, multi_host_sections, on_error)
File “/omd/sites/SITENAME/lib/python/cmk_base/discovery.py”, line 717, in _discover_services
for item, paramstring in _execute_discovery(multi_host_sections, hostname, ipaddress, check_plugin_name, on_error):
File “/omd/sites/SITENAME/lib/python/cmk_base/discovery.py”, line 916, in _execute_discovery
check_plugin_name, for_discovery=True)
File “/omd/sites/SITENAME/lib/python/cmk_base/data_sources/host_sections.py”, line 146, in get_section_content
nodes_of_clustered_service)
File “/omd/sites/SITENAME/lib/python/cmk_base/data_sources/host_sections.py”, line 204, in _get_section_content
section_content = self._update_with_parse_function(section_content, section_name)
File “/omd/sites/SITENAME/lib/python/cmk_base/data_sources/host_sections.py”, line 299, in _update_with_parse_function
return parse_function(section_content)
File “/omd/sites/SITENAME/share/check_mk/checks/kentix_amp_sensors”, line 61, in parse_kentix_amp_sensors
‘temp’ : float(line[1])/10,

What I found was that our Sensor does not report on the OIDs that CMK “wants”. kentix_amp_sensors expects the OID .1.3.6.1.4.1.37954.1.2.7.2.0:

OMD[SITENAME]:~$ snmpget -v2c -c public IPADDR .1.3.6.1.4.1.37954.1.2.7.2.0
SNMPv2-SMI::enterprises.37954.1.2.7.2.0 = No Such Instance currently exists at this OID

But we can get it from:

snmpget -v2c -c public IPADDR enterprises.37954.1.1.1.1.0

SNMPv2-SMI::enterprises.37954.1.1.1.1.0 = INTEGER: 25

For what it’s worth here the relevant OIDS:

Temperature is 25, Humidity is 26, Dewpoint 4, CO2 is 0, Motion is 0. The other vaulues are Min/Max (and then Alarm On/off I guess).

OMD[informatics]:~$ snmpbulkwalk -v2c -c public 10.1.6.194 enterprises.37954.1.1
SNMPv2-SMI::enterprises.37954.1.1.1.1.0 = INTEGER: 25
SNMPv2-SMI::enterprises.37954.1.1.1.2.0 = INTEGER: 15
SNMPv2-SMI::enterprises.37954.1.1.1.3.0 = INTEGER: 27
SNMPv2-SMI::enterprises.37954.1.1.1.4.0 = INTEGER: 0
SNMPv2-SMI::enterprises.37954.1.1.1.5.0 = STRING: “Temperature alarm”
SNMPv2-SMI::enterprises.37954.1.1.1.6.0 = INTEGER: 1
SNMPv2-SMI::enterprises.37954.1.1.2.1.0 = INTEGER: 26
SNMPv2-SMI::enterprises.37954.1.1.2.2.0 = INTEGER: 10
SNMPv2-SMI::enterprises.37954.1.1.2.3.0 = INTEGER: 80
SNMPv2-SMI::enterprises.37954.1.1.2.4.0 = INTEGER: 0
SNMPv2-SMI::enterprises.37954.1.1.2.5.0 = STRING: “Humidity alarm”
SNMPv2-SMI::enterprises.37954.1.1.2.6.0 = INTEGER: 1
SNMPv2-SMI::enterprises.37954.1.1.3.1.0 = INTEGER: 4
SNMPv2-SMI::enterprises.37954.1.1.3.2.0 = INTEGER: 2
SNMPv2-SMI::enterprises.37954.1.1.3.3.0 = INTEGER: 0
SNMPv2-SMI::enterprises.37954.1.1.3.4.0 = STRING: “Dewpoint alarm”
SNMPv2-SMI::enterprises.37954.1.1.3.6.0 = INTEGER: 1
SNMPv2-SMI::enterprises.37954.1.1.4.1.0 = INTEGER: 0
SNMPv2-SMI::enterprises.37954.1.1.4.2.0 = INTEGER: 10
SNMPv2-SMI::enterprises.37954.1.1.4.3.0 = INTEGER: 0
SNMPv2-SMI::enterprises.37954.1.1.4.4.0 = STRING: “CO alarm”
SNMPv2-SMI::enterprises.37954.1.1.4.6.0 = INTEGER: 1
SNMPv2-SMI::enterprises.37954.1.1.5.1.0 = INTEGER: 0
SNMPv2-SMI::enterprises.37954.1.1.5.2.0 = INTEGER: 30
SNMPv2-SMI::enterprises.37954.1.1.5.3.0 = INTEGER: 0
SNMPv2-SMI::enterprises.37954.1.1.5.4.0 = STRING: “Motion alarm”
SNMPv2-SMI::enterprises.37954.1.1.5.6.0 = INTEGER: 1
SNMPv2-SMI::enterprises.37954.1.1.6.1.0 = INTEGER: 0
SNMPv2-SMI::enterprises.37954.1.1.6.2.0 = STRING: “dig input 1”
SNMPv2-SMI::enterprises.37954.1.1.7.1.0 = INTEGER: 0
SNMPv2-SMI::enterprises.37954.1.1.7.2.0 = STRING: “dig input 2”
SNMPv2-SMI::enterprises.37954.1.1.8.1.0 = INTEGER: 7
SNMPv2-SMI::enterprises.37954.1.1.9.1.0 = INTEGER: 3
SNMPv2-SMI::enterprises.37954.1.1.10.1.0 = INTEGER: 20
SNMPv2-SMI::enterprises.37954.1.1.11.1.0 = INTEGER: 60

andreas-doehler · October 4, 2019, 8:41pm

Hi Jonas,

wenn ich mir die Daten und den Kentix Check so anschaue dann wäre das Firmware Update der erste Schritt.

Falls danach die Daten sich nicht geändert haben sieht es eher nach einem anderen Modell von Kentix aus.

Dann hilft nur komplett neuen Check erstellen.

Die bisher vorhandenen Kentix Checks sind ja auch für zwei unterschiedliche Geräte Typen schon.

Gruß