Weird SNMP error message after upgrade to 2.3.0

CMK version:
2.3.0
OS version:
Ubuntu 22.04 with latest updates
Error message:

Output of “cmk --debug -vvn hostname”: (If it is a problem with checks or plugins)

value store: synchronizing
Trying to acquire lock on /omd/sites/CBS/tmp/check_mk/counters/ava19-as1.belfla.be
Got lock on /omd/sites/CBS/tmp/check_mk/counters/ava19-as1.belfla.be
value store: loading from disk
Releasing lock on /omd/sites/CBS/tmp/check_mk/counters/ava19-as1.belfla.be
Released lock on /omd/sites/CBS/tmp/check_mk/counters/ava19-as1.belfla.be
Checkmk version 2.3.0
+ FETCHING DATA
  Source: SourceInfo(hostname='ava19-as1.belfla.be', ipaddress='10.198.254.8', ident='snmp', fetcher_type=<FetcherType.SNMP: 7>, source_type=<SourceType.HOST: 1>)
[cpu_tracking] Start [7f5ac6941ca0]
Read from cache: SNMPFileCache(ava19-as1.belfla.be, path_template=/omd/sites/CBS/tmp/check_mk/data_source_cache/snmp/{mode}/{hostname}, max_age=MaxAge(checking=0, discovery=450.0, inventory=450.0), simulation=False, use_only_cache=False, file_cache_mode=6)
Not using cache (does not exist)
[cpu_tracking] Stop [7f5ac6941ca0 - Snapshot(process=posix.times_result(user=0.0, system=0.0, children_user=0.0, children_system=0.0, elapsed=0.0))]
  Source: SourceInfo(hostname='ava19-as1.belfla.be', ipaddress='10.198.254.8', ident='piggyback', fetcher_type=<FetcherType.PIGGYBACK: 4>, source_type=<SourceType.HOST: 1>)
[cpu_tracking] Start [7f5ac5baa870]
Read from cache: NoCache(ava19-as1.belfla.be, path_template=/dev/null, max_age=MaxAge(checking=0.0, discovery=0.0, inventory=0.0), simulation=False, use_only_cache=False, file_cache_mode=1)
No piggyback files for 'ava19-as1.belfla.be'. Skip processing.
No piggyback files for '10.198.254.8'. Skip processing.
Get piggybacked data
[cpu_tracking] Stop [7f5ac5baa870 - Snapshot(process=posix.times_result(user=0.0, system=0.0, children_user=0.0, children_system=0.0, elapsed=0.0))]
[cpu_tracking] Start [7f5ac646f470]
+ PARSE FETCHER RESULTS
  HostKey(hostname='ava19-as1.belfla.be', source_type=<SourceType.HOST: 1>)  -> Add sections: []
Received no piggyback data
CDP Neighbor GigabitEthernet0/1 AVA18-AS1 PEND Check plug-in received no monitoring data
CPU utilization 1    PEND Check plug-in received no monitoring data
FAN chassis 1        PEND Check plug-in received no monitoring data
Interface FastEthernet0/1 PEND Check plug-in received no monitoring data
Interface FastEthernet0/13 PEND Check plug-in received no monitoring data
Interface FastEthernet0/2 PEND Check plug-in received no monitoring data
Interface FastEthernet0/23 PEND Check plug-in received no monitoring data
Interface GigabitEthernet0/1 PEND Check plug-in received no monitoring data
Memory I/O           PEND Check plug-in received no monitoring data
Memory Processor     PEND Check plug-in received no monitoring data
Power internal power supply 1 PEND Check plug-in received no monitoring data
SNMP Info            PEND Check plug-in received no monitoring data
Uptime               PEND Check plug-in received no monitoring data
No piggyback files for 'ava19-as1.belfla.be'. Skip processing.
No piggyback files for '10.198.254.8'. Skip processing.
[cpu_tracking] Stop [7f5ac646f470 - Snapshot(process=posix.times_result(user=0.010000000000000231, system=0.0, children_user=0.0, children_system=0.0, elapsed=0.010000001639127731))]
[snmp] UnpicklingError("invalid load key, '\\x00'.")(!!), [piggyback] Success (but no data found for this host), Missing monitoring data for all plugins(!), execution time 0.0 sec | execution_time=0.010 user_time=0.010 system_time=0.000 children_user_time=0.000 children_system_time=0.000 cmk_time_snmp=0.000 cmk_time_agent=0.000

This happens with a significant numbers of hosts out of the 1500 monitored. I have no idea how to fix this.

Hi,

did you have any errors in your Update Log?

You can try to delete the files of one of the affected hosts here and discover it again : /omd/sites/<your site>/var/check_mk/persisted_sections/snmp/

I did not notice many errors in the update log, but… I might have missed that.

That said: deleting the persistent file enables me to re-add the host. So at least now I have a fix :slight_smile:

Now I have to find the hosts that have the issue, delete the files and re-add them. But that’s acceptable. At least we can fix them!

Thank you Andre! Much obliged

1 Like