​
Troubleshooting

​
Collector-Manager not in Ready State

If you encounter a situation where the collector-manager is not in a Ready state, follow these steps to resolve the issue:
  • Ensure that your integration appears on the Integration page and validate the release.
  • Ensure that your integration status is Active and not Attention Required or Delete In Progress.
  • Ensure that the collector-manager pod has access to DNS resolution and Internet because it actively communicates with the Plerion Control Plane over HTTPS.
    copy
    kubectl logs -f  plerion-collector-manager-ccbc55c5d-dr27w
    Example output: 
    {"level":"info","ts":"2023-11-21T04:48:44Z","msg":"maxprocs: Updating GOMAXPROCS=2: determined from CPU quota\n"}
{"level":"info","ts":"2023-11-21T04:48:44Z","logger":"setup","msg":"initializing controller"}
{"level":"info","ts":"2023-11-21T04:48:44Z","logger":"setup","msg":"fetching tenant config"}
{"level":"error","ts":"2023-11-21T04:48:54Z","logger":"k8scbclient","msg":"request failed","error":"Post \"https://au.app.plerion.com/api****/extern****/kubern****/tenant****/7934cf****b34-4bda-adde-173a1fa30d9c/integr****ns/d09059****5cf-4e7f-b8da-18e2298a15a5/config****\": dial tcp: lookup au.app.plerion.com on 10.96.0.10:53: read udp 10.244.0.18:45231->10.96.0.10:53: read: connection refused","method":"POST","url":"https://au.app.plerion.com/api****/extern****/kubern****/tenant****/7934cf****b34-4bda-adde-173a1fa30d9c/integr****ns/d09059****5cf-4e7f-b8da-18e2298a15a5/config****","error...}
    You can check the status of the DNS pods with the following command:
    copy
    kubectl get pods -n kube-system
    Example output: 
    NAME                                         READY   STATUS             RESTARTS        AGE
coredns-5dd5756b68-hb4lq                     0/1     CrashLoopBackOff   6(7s ago)       4h28m
kube-proxy-lhxcq                             1/1     Running            0               4h28m
storage-provisioner                          1/1     Running            0               4h28m
    If you find that the DNS pods are in a Pending state, you need to address the DNS pod issue before proceeding. Once the DNS pods are functioning correctly, try restarting the collector-manager pod to see if it becomes Ready.

​
Retrieve Controller Logs

If the previous steps fail to resolve your issue, you can access the collector-manager logs by following these steps:
  1. First, list the currently running pods within the plerion-system namespace:
    copy
    kubectl get pods -n plerion-system
    Example output: 
    NAME                                                 READY   STATUS    RESTARTS   AGE
plerion-collector-manager-ccbc55c5d-dr27w   1/1     Running   0          10m
plerion-collector-manager-ccbc55c5d-x255n   1/1     Running   0          10m
    This command will provide a list of pods, including the collector-manager pod.
  2. To obtain the logs, use the following command, replace the name of the collector-manager pod you want to retrieve logs from:
    copy
    kubectl logs -f plerion-collector-manager-ccbc55c5d-dr27w
    The -f flag allows you to follow the logs in real-time.
By examining the collector-manager logs, you can gather more information to help diagnose and resolve the issue you are facing. If you need more detailed logs, please follow this guide.