CMK version: 2.4.0p11 cee
OS version: checmk-Appliance v1.7.11
Error message from special agent_jolokia: ERROR Cannot connect to server at https://10.50.33.76/jolokia/
cmk --debug -vvn portal.k8s-test.fqdn.domain
value store: loading from disk
Checkmk version 2.4.0p11
- FETCHING DATA
Source: SourceInfo(hostname=‘portal.k8s-test.fqdn.domain’, ipaddress=‘10.50.33.76’, ident=‘special_jolokia’, fetcher_type=<FetcherType.SPECIAL_AGENT: 6>, source_type=<SourceType.HOST: 1>)
[cpu_tracking] Start [7f334aee2a50]
Read from cache: AgentFileCache(path_template=/omd/sites/k8s/tmp/check_mk/data_source_cache/special_jolokia/portal.k8s-test.fqdn.domain, max_age=MaxAge(checking=0, discovery=90.0, inventory=90.0), simulation=False, use_only_cache=False, file_cache_mode=6)
Not using cache (Too old. Age is 263 sec, allowed is 0 sec)
Calling: /omd/sites/k8s/share/check_mk/agents/special/agent_jolokia –server 10.50.33.76 --port 443 --suburi jolokia --protocol https
Get data from program
Write data to cache file /omd/sites/k8s/tmp/check_mk/data_source_cache/special_jolokia/portal.k8s-test.fqdn.domain
Trying to acquire lock on /omd/sites/k8s/tmp/check_mk/data_source_cache/special_jolokia/portal.k8s-test.fqdn.domain
Got lock on /omd/sites/k8s/tmp/check_mk/data_source_cache/special_jolokia/portal.k8s-test.fqdn.domain
Releasing lock on /omd/sites/k8s/tmp/check_mk/data_source_cache/special_jolokia/portal.k8s-test.fqdn.domain
Released lock on /omd/sites/k8s/tmp/check_mk/data_source_cache/special_jolokia/portal.k8s-test.fqdn.domain
[cpu_tracking] Stop [7f334aee2a50 - Snapshot(process=posix.times_result(user=0.0, system=0.0, children_user=0.35, children_system=0.04, elapsed=0.41999999806284904))]
Source: SourceInfo(hostname=‘portal.k8s-test.fqdn.domain’, ipaddress=‘10.50.33.76’, ident=‘piggyback’, fetcher_type=<FetcherType.PIGGYBACK: 4>, source_type=<SourceType.HOST: 1>)
[cpu_tracking] Start [7f334a3dbf20]
Read from cache: NoCache(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)
0 piggyback files for ‘portal.k8s-test.fqdn.domain’.
0 piggyback files for ‘10.50.33.76’.
Get piggybacked data
[cpu_tracking] Stop [7f334a3dbf20 - 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 [7f334ac6ef60] - PARSE FETCHER RESULTS
<<<jolokia_info:sep(0)>>> / Transition NOOPParser → HostSectionParser
HostKey(hostname=‘portal.k8s-test.fqdn.domain’, source_type=<SourceType.HOST: 1>) → Add sections: [‘jolokia_info’]
HostKey(hostname=‘portal.k8s-test.fqdn.domain’, source_type=<SourceType.HOST: 1>) → Add sections:
Received no piggyback data
0 piggyback files for ‘portal.k8s-test.fqdn.domain’.
[cpu_tracking] Stop [7f334ac6ef60 - Snapshot(process=posix.times_result(user=0.009999999999999787, system=0.0, children_user=0.0, children_system=0.0, elapsed=0.0))]
[special_jolokia] Success, [piggyback] Success (but no data found for this host), execution time 0.4 sec | execution_time=0.420 user_time=0.010 system_time=0.000 children_user_time=0.350 children_system_time=0.040 cmk_time_ds=0.030 cmk_time_agent=0.000
The fqdn-host in a Kubernetes deployment behind a reverse proxy.