SNMP Error, Agent OK

JanHalek · January 3, 2022, 10:01am

CMK version: 2.0.0p17 CRE
OS version: CentOS 7

Error message: [agent] Version: 1.2.6p12, OS: linux, [snmp] Cannot fetch system description OID .1.3.6.1.2.1.1.1.0. Please check your SNMP configuration. Possible reason might be: Wrong credentials, wrong SNMP version, Firewall rules, etc.CRIT , execution time 6.1 sec

Output of “cmk --debug -vvn hostname”:

Checkmk version 2.0.0p17
Try license usage history update.
Trying to acquire lock on /omd/sites/housing/var/check_mk/license_usage/next_run
Got lock on /omd/sites/housing/var/check_mk/license_usage/next_run
Trying to acquire lock on /omd/sites/housing/var/check_mk/license_usage/history.json
Got lock on /omd/sites/housing/var/check_mk/license_usage/history.json
Next run time has not been reached yet. Abort.
Releasing lock on /omd/sites/housing/var/check_mk/license_usage/history.json
Released lock on /omd/sites/housing/var/check_mk/license_usage/history.json
Releasing lock on /omd/sites/housing/var/check_mk/license_usage/next_run
Released lock on /omd/sites/housing/var/check_mk/license_usage/next_run
Loading autochecks from /omd/sites/housing/var/check_mk/autochecks/DURUM-KEBAB.mk
+ FETCHING DATA
  Source: SourceType.HOST/FetcherType.TCP
[cpu_tracking] Start [7fd7eec59d60]
Connecting via TCP to SOMEIP:6556 (20.0s timeout)
[TCPFetcher] Fetch with cache settings: DefaultAgentFileCache(base_path=PosixPath('/omd/sites/housing/tmp/check_mk/cache/DURUM-KEBAB'), max_age=MaxAge(checking=0, discovery=120, inventory=120), disabled=False, use_outdated=False, simulation=False)
Not using cache (Too old. Age is 107 sec, allowed is 0 sec)
[TCPFetcher] Execute data source
Reading data from agent
Output is not encrypted
Write data to cache file /omd/sites/housing/tmp/check_mk/cache/DURUM-KEBAB
Trying to acquire lock on /omd/sites/housing/tmp/check_mk/cache/DURUM-KEBAB
Got lock on /omd/sites/housing/tmp/check_mk/cache/DURUM-KEBAB
Releasing lock on /omd/sites/housing/tmp/check_mk/cache/DURUM-KEBAB
Released lock on /omd/sites/housing/tmp/check_mk/cache/DURUM-KEBAB
Closing TCP connection to SOMEIP:6556
[cpu_tracking] Stop [7fd7eec59d60 - Snapshot(process=posix.times_result(user=0.0, system=0.0, children_user=0.0, children_system=0.0, elapsed=0.08999999985098839))]
  Source: SourceType.HOST/FetcherType.SNMP
[cpu_tracking] Start [7fd7eedd8190]
[SNMPFetcher] Fetch with cache settings: SNMPFileCache(base_path=PosixPath('/omd/sites/housing/tmp/check_mk/data_source_cache/snmp/DURUM-KEBAB'), max_age=MaxAge(checking=0, discovery=120, inventory=120), disabled=False, use_outdated=False, simulation=False)
Not using cache (Does not exist)
[SNMPFetcher] Execute data source
No persisted sections loaded
  SNMP scan:
       Getting OID .1.3.6.1.2.1.1.1.0: Running 'snmpget -v1 -c SECRET -m "" -M "" -On -OQ -Oe -Ot SOMEIP .1.3.6.1.2.1.1.1.0'
ERROR: SNMP errorTimeout: No Response from SOMEIP.

failed.
[cpu_tracking] Stop [7fd7eedd8190 - Snapshot(process=posix.times_result(user=0.020000000000000018, system=0.0, children_user=0.0, children_system=0.0, elapsed=6.020000000484288))]
Cannot fetch system description OID .1.3.6.1.2.1.1.1.0. Please check your SNMP configuration. Possible reason might be: Wrong credentials, wrong SNMP version, Firewall rules, etc.

Hello,

I have problem with update from version 1.6p22 to 2.0.0p17.
Approximately 300 hosts gets two messages from Check_MK. One of them you can see above.

Next one is " [agent] Version: 1.6.0p20, OS: windows, [snmp] SNMP Error on 192.168.1.7: Timeout: No Response from 192.168.1.7 (Exit-Code: 1)CRIT , execution time 6.7 sec".

If I tried to turn off everything from “Monitoring agents” then check will go to OK, but it is not desirable solution. We have multiple hosts running SNMP and more hosts running agent. So any configurations to permanently disable SNMP is not desirable.

Why Check_MK checks SNMP even it is disabled in hosts settings? Is there any rule to block this functionality? The version of the agent is not important, it does the same for version 1.6.0pXX - even for Windows.

Thank you for your help
Jan

r.sander · January 3, 2022, 10:13am

Please post the top section of the output from cmk -D HOSTNAME.

JanHalek · January 3, 2022, 10:27am

Addresses:              SOMEIP
Tags:                   [Autodiscovery:NO], [address_family:ip-v4-only], [agent:all-agents], [criticality:prod], [hostgroups:non-hostgroup], [ip-v4:ip-v4], [networking:lan], [piggyback:auto-piggyback], [servicegroups:non-servicegroup], [site:housing], [snmp:snmp], [snmp_ds:no-snmp], [tcp:tcp]
Labels:                 [cpu:monitoring], [fs:monitoring], [host:upandown], [http:monitoring], [period:helpdesk]
Host groups:            check_mk
Contact groups:         check-mk-notify, hosting_company, our_notify
Agent mode:             Normal Checkmk agent, all configured special agents
Type of agent:
  TCP: SOMEIP:6556
  SNMP (Community: ‘SECRET’, Bulk walk: no, Port: 161, Backend: Classic)
  Process piggyback data from /omd/sites/housing/tmp/check_mk/piggyback/DURUM-KEBAB
Services:
  checktype      item  params                                                                                                                                                                                                                                                                                                                                                                                                   description       groups
  -------------- ----- -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ----------------- ------
  cpu_loads      None  (5.0, 10.0)                                                                                                                                                                                                                                                                                                                                                                                              CPU load
  kernel_util    None  {'util': (80.0, 90.0)}                                                                                                                                                                                                                                                                                                                                                                                   CPU utilization
  df             /     {'levels': (90.0, 92.0), 'magic_normsize': 20, 'levels_low': (50.0, 60.0), 'trend_range': 24, 'trend_perfdata': True, 'show_levels': 'onmagic', 'inodes_levels': (10.0, 5.0), 'show_inodes': 'onlow', 'show_reserved': False}                                                                                                                                                                            Filesystem /
  df             /boot {'levels': (90.0, 92.0), 'magic_normsize': 20, 'levels_low': (50.0, 60.0), 'trend_range': 24, 'trend_perfdata': True, 'show_levels': 'onmagic', 'inodes_levels': (10.0, 5.0), 'show_inodes': 'onlow', 'show_reserved': False}                                                                                                                                                                            Filesystem /boot
  lnx_if         2     {'errors': {'both': ('perc', (0.01, 0.1))}, 'speed': None, 'state': None}                                                                                                                                                                                                                                                                                                                                Interface 2
  mem_linux      None  {'levels_virtual': ('perc_used', (80.0, 90.0)), 'levels_total': ('perc_used', (120.0, 150.0)), 'levels_shm': ('perc_used', (30.0, 35.0)), 'levels_pagetables': ('perc_used', (8.0, 16.0)), 'levels_committed': ('perc_used', (130.0, 150.0)), 'levels_commitlimit': ('perc_free', (20.0, 10.0)), 'levels_vmalloc': ('abs_free', (52428800, 31457280)), 'levels_hardwarecorrupted': ('abs_used', (1, 1))} Memory
  chrony         None  {'ntp_levels': (10, 200.0, 500.0), 'alert_delay': (1800, 3600)}                                                                                                                                                                                                                                                                                                                                          NTP Time
  cpu_threads    None  {'levels': (2000, 4000)}                                                                                                                                                                                                                                                                                                                                                                                 Number of threads
  postfix_mailq        {'deferred': (10, 20), 'active': (200, 300)}                                                                                                                                                                                                                                                                                                                                                             Postfix Queue
  tcp_conn_stats None  {}                                                                                                                                                                                                                                                                                                                                                                                                       TCP Connections
  uptime         None  {}

robin.gierse · January 3, 2022, 11:47am

For the love of Cthulhu! Use code blocks, I beg you!

r.sander · January 3, 2022, 12:41pm

There is still SNMP configured. Have you activated your changes?

JanHalek · January 3, 2022, 12:52pm

Yes, I have

Thank you,
Jan

JanHalek · January 7, 2022, 6:31am

Anyone with recommendations?

andreas-doehler · January 7, 2022, 8:30am

I think i see the problem.

, [snmp:snmp], [snmp_ds:no-snmp], [tcp:tcp]

SNMP host should look like this for example

, [snmp:snmp], [snmp_ds:snmp-v2]

agent host has this tags

, [snmp_ds:no-snmp], [tcp:tcp]

In your case the extra [snmp:snmp] leads to the SNMP calls.

Now the why. I think that in your 1.6 installation the host tag “agent” was modified.
If this tag was modified manually before the upgrade to 2.0 then it is a little bit broken after the upgrade.
This can only be fixed manually on the command line. Attention backup the host tag file before modifying.

JanHalek · January 7, 2022, 8:57am

I have already discovered that just few minutes after my last reply.
We will try to fix this.

Thank you for your help and have a nice day,
Jan

system · January 7, 2023, 8:57am

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.