Dynatrace / dynatrace-oneagent-operator

Kubernetes/Openshift Operator for managing Dynatrace OneAgent deployments
Apache License 2.0
88 stars 48 forks source link

oneagent readiness probe fails and writes huge amount of logs #412

Closed shashank2300 closed 1 year ago

shashank2300 commented 1 year ago

Oneagent readiness probe is failing and it shows below error:

  Warning  Unhealthy  31s                 kubelet  Readiness probe failed: grep: /proc/241348/stat: No such file or directory
grep: /proc/241379/stat: No such file or directory
grep: /proc/241383/stat: No such file or directory
grep: /proc/241389/stat: No such file or directory
  Warning  Unhealthy  13s  kubelet  Readiness probe failed: grep: /proc/242591/stat: No such file or directory
grep: /proc/242597/stat: No such file or directory

and as long as readiness probe is failing oneagent pods are writing a lot of logs to the VMs as a result filling the storage space on VMs. Snippet of logs in oneagent pods: '/var/log/dynatrace/oneagent/go/ruxitagent_grpc_health_probe_redhat-operators_90620(2).0.log' -> '/mnt/host_root/var/log/dynatrace/oneagent/go/ruxitagent_grpc_health_probe_redhat-operators_90620(2).0.log' '/var/log/dynatrace/oneagent/go/ruxitagent_grpc_health_probe_community-operators_bootstrap_26687.0.log' -> '/mnt/host_root/var/log/dynatrace/oneagent/go/ruxitagent_grpc_health_probe_community-operators_bootstrap_26687.0.log' '/var/log/dynatrace/oneagent/go/ruxitagent_grpc_health_probe_community-operators_bootstrap_26686(1).0.log' -> '/mnt/host_root/var/log/dynatrace/oneagent/go/ruxitagent_grpc_health_probe_community-operators_bootstrap_26686(1).0.log' '/var/log/dynatrace/oneagent/go/ruxitagent_grpc_health_probe_community-operators_26687.0.log' -> '/mnt/host_root/var/log/dynatrace/oneagent/go/ruxitagent_grpc_health_probe_community-operators_26687.0.log'

I'm using oneagent version 1.261.249 image. Operator version v0.12.1.

DaRoli commented 1 year ago

The "Dynatrace OneAgent Operator" is deprecated in favor of its successor, the "Dynatrace Operator". Given your mentioning of the version number 0.12.1, I believe your issue accidentally was opened in this deprecated repository. Please open your issue again in the new repository.

shashank2300 commented 1 year ago

Thanks @DaRoli I've opened issue in the Dynatrace operator repo.