Removed, recreated, but still the issue persists. I’m not sure why it’s calling the agent_vsphere upon diagnostics: just added the new host, specified the IP, and went for the testing phase. On the host, I did call the agent register which succeeded:
RcyJSnqM3oWfSEA5aB8gfV7qaZLkswc1nmWcIvnI1dy9EUiZ1w==
-----END CERTIFICATE-----
Issued by:
Site 'monitoring' local CA
Issued to:
monitoring
Validity:
From Sun, 08 Jan 2023 08:37:32 +0000
To Fri, 11 May 3021 08:37:32 +0000
Do you want to establish this connection? [Y/n]
> Y
C:\Program Files (x86)\checkmk\service>
But when testing on the monitoring site, it still returns the same error
API Error:Error running automation call <tt>diag-host</tt>: Your request timed out after 110 seconds. This issue may be related to a local configuration problem or a request which works with a too large number of objects. But if you think this issue is a bug, please send a crash report.
And when calling the cmk debug, it still defaults to the agent_vsphere for some reason…
OMD[monitoring]:/opt/omd/versions/2.1.0p18.cre/bin$ cmk --debug -vvI monolithone
Discovering services and host labels on: monolithone
monolithone:
+ FETCHING DATA
Source: SourceType.HOST/FetcherType.PROGRAM
[cpu_tracking] Start [7fdd98a405e0]
[ProgramFetcher] Fetch with cache settings: DefaultAgentFileCache(monolithone, base_path=/omd/sites/monitoring/tmp/check_mk/data_source_cache/special_vsphere, max_age=MaxAge(checking=0, discovery=120, inventory=120), disabled=False, use_outdated=False, simulation=False)
Not using cache (Does not exist)
[ProgramFetcher] Execute data source
Calling: /omd/sites/monitoring/share/check_mk/agents/special/agent_vsphere '-u' 'root' '-s=<redacted>' '-i' 'hostsystem,virtualmachine,datastore,counters' '--direct' '--hostname' 'monolithone' '-P' '--spaces' 'underscore' '--no-cert-check' '192.168.1.238'
[cpu_tracking] Stop [7fdd98a405e0 - Snapshot(process=posix.times_result(user=0.0, system=0.0, children_user=0.24, children_system=0.03, elapsed=129.48999999836087))]
Source: SourceType.HOST/FetcherType.PIGGYBACK
[cpu_tracking] Start [7fdd98a406d0]
[PiggybackFetcher] Fetch with cache settings: NoCache(monolithone, base_path=/omd/sites/monitoring/tmp/check_mk/data_source_cache/piggyback, max_age=MaxAge(checking=0, discovery=120, inventory=120), disabled=True, use_outdated=False, simulation=False)
Not using cache (Cache usage disabled)
[PiggybackFetcher] Execute data source
No piggyback files for 'monolithone'. Skip processing.
No piggyback files for '192.168.1.238'. Skip processing.
Not using cache (Cache usage disabled)
[cpu_tracking] Stop [7fdd98a406d0 - Snapshot(process=posix.times_result(user=0.0, system=0.0, children_user=0.0, children_system=0.0, elapsed=0.0))]
+ PARSE FETCHER RESULTS
Source: SourceType.HOST/FetcherType.PROGRAM
-> Not adding sections: Agent exited with code 1: HTTPSConnectionPool(host='192.168.1.238', port=443): Max retries exceeded with url: /sdk (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f4d4f0611c0>: Failed to establish a new connection: [Errno 110] Connection timed out'))
Source: SourceType.HOST/FetcherType.PIGGYBACK
No persisted sections
-> Add sections: []
Received no piggyback data
Received no piggyback data
+ ANALYSE DISCOVERED HOST LABELS
Trying host label discovery with:
Trying host label discovery with:
SUCCESS - Found no new host labels
+ ANALYSE DISCOVERED SERVICES
+ EXECUTING DISCOVERY PLUGINS (0)
Trying discovery with:
SUCCESS - Found no new services