[special_kube] Agent exited with code 1: Failed to establish a connection at URL https://fqdns:30574/version(!

CMK version:2.3.0p2 CRE

Error message:[special_kube] Agent exited with code 1: Failed to establish a connection at URL https://fqdns:30574/version(!!

**Output of “cmk --debug -vvn hostname”:cmk --debug -vvn k8s-cluster
value store: synchronizing
Trying to acquire lock on /omd/sites/checkmkdev/tmp/check_mk/counters/k8s-cluster
Got lock on /omd/sites/checkmkdev/tmp/check_mk/counters/k8s-cluster
value store: loading from disk
Releasing lock on /omd/sites/checkmkdev/tmp/check_mk/counters/k8s-cluster
Released lock on /omd/sites/checkmkdev/tmp/check_mk/counters/k8s-cluster
Checkmk version 2.3.0p2

  • FETCHING DATA
    Source: SourceInfo(hostname=‘k8s-cluster’, ipaddress=None, ident=‘special_kube’, fetcher_type=<FetcherType.SPECIAL_AGENT: 6>, source_type=<SourceType.HOST: 1>)
    [cpu_tracking] Start [7ff831de0230]
    Read from cache: AgentFileCache(k8s-cluster, path_template=/omd/sites/checkmkdev/tmp/check_mk/data_source_cache/special_kube/{hostname}, max_age=MaxAge(checking=0, discovery=90.0, inventory=90.0), simulation=False, use_only_cache=False, file_cache_mode=6)
    Not using cache (does not exist)
    Calling: /omd/sites/checkmkdev/share/check_mk/agents/special/agent_kube --pwstore=6@0@/omd/sites/checkmkdev/var/check_mk/passwords_merged@kubernetes_Token --cluster k8s-cluster --kubernetes-cluster-hostname k8s-cluster --token ‘********************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************’ --monitored-objects deployments daemonsets statefulsets namespaces nodes pods pvcs cronjobs --cluster-aggregation-exclude-node-roles control-plane infra --api-server-endpoint https://nzjqrzr84c.bki1.metakube.syseleven.de:30574 --verify-cert-api --api-server-proxy FROM_ENVIRONMENT --cluster-collector-endpoint http://192.168.4.14:30035 --usage-proxy FROM_ENVIRONMENT
    Get data from program
    [cpu_tracking] Stop [7ff831de0230 - Snapshot(process=posix.times_result(user=0.0, system=0.0, children_user=0.83, children_system=0.12, elapsed=0.9699999988079071))]
    Source: SourceInfo(hostname=‘k8s-cluster’, ipaddress=None, ident=‘piggyback’, fetcher_type=<FetcherType.PIGGYBACK: 4>, source_type=<SourceType.HOST: 1>)
    [cpu_tracking] Start [7ff830c9c410]
    Read from cache: NoCache(k8s-cluster, 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 ‘k8s-cluster’. Skip processing.
    Get piggybacked data
    [cpu_tracking] Stop [7ff830c9c410 - 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 [7ff83176cb60]
  • PARSE FETCHER RESULTS
    HostKey(hostname=‘k8s-cluster’, source_type=<SourceType.HOST: 1>) → Add sections:
    Received no piggyback data
    No piggyback files for ‘k8s-cluster’. Skip processing.
    [cpu_tracking] Stop [7ff83176cb60 - Snapshot(process=posix.times_result(user=0.0, system=0.0, children_user=0.0, children_system=0.0, elapsed=0.0))]
    [special_kube] Agent exited with code 1: Failed to establish a connection at URL https://nzjqrzr84c.bki1.metakube.syseleven.de:30574/version(!!), [piggyback] Success (but no data found for this host), execution time 1.0 sec | execution_time=0.970 user_time=0.000 system_time=0.000 children_user_time=0.830 children_system_time=0.120 cmk_time_ds=0.020 cmk_time_agent=0.000** (If it is a problem with checks or plugins)

I am able to curl and get the response as expected.

Hi @SaiRam1,

I’m not 100% sure, but it looks like a certificate validation problem to me.

The certificate at

is self-signed and probably not known to the Checkmk server.

I’m not sure if the command line option

checks the cert or is doing the opposite, but from the information I see it looks like a certificate issue.

Looking forward to your response!

Regards
Norm

I have selected ignore certificates option in kubernetes setup and that is it, Its working now!!
Thanks!

1 Like

Hi @SaiRam1,

great to hear that this solved your issue. Can you please mark my answer as a solution to help future forum members and guests? Thanks in advance!

Regards
Norm