Links

Troubleshooting

This section describes the steps to debug your Kubiya's Action Runner deployed on your Kubernetes cluster.

Debug steps

Check the runner connectivity status:

  1. 1.
    In the web UI --> go to the Action Runner Menu and check that the runner status is "Healthy"
  2. 2.
    Open your terminal or command prompt and make sure you are in the Kubernetes context you installed the kubiya runner.
  3. 3.
    Find your runner name from the web UI Action Runner dashboard:
Try to run a forced health check:

From Kubernetes:

  1. 1.
    Run the following command :
$ kubectl get deployments -n kubiya
  1. 1.
    Locate your runner in one of the deployments ( the runner name is the suffix of the deployment kubiya-connector-runner-name ).
  2. 2.
    A runner with a healthy status should have as follows:
    NAME READY UP-TO-DATE AVAILABLE AGE
    kubiya-connector-test-runner. 1/1 1 1 15d

Check the runner deployment logs

  1. 1.
    Stream the logs from the runner deployment
    $ kubectl logs -f deployment/kubiya-connector-runner-name -n kubiya
    ___ __
    __ ______ / (_)___ / /__
    / / / / __ \/ / / __ \/ //_/
    / /_/ / /_/ / / / / / / ,<
    \__,_/ .___/_/_/_/ /_/_/|_|
    /_/
    inlets (tm) uplink client. All rights reserved OpenFaaS Ltd (2022)
    time="2023/08/04 06:19:19" level=info msg="Connecting to proxy" url="wss://tunnel.kubiya.ai/kubiya-solutions-engineering/kubiya-solutions-engineering-tunnel-se-runner"
    time="2023/08/04 06:19:19" level=info msg="Connection established" client_id=123456789
  2. 2.
    In case you are seeing an error in the streamed logs try to rollout restart the deployment and repeat steps 4-5 and 1.
    # example error
    ---------------
    $ kubectl logs -f deployment/kubiya-connector-se-runner-20230801-2 -n kubiya
    time="2023/08/01 14:35:53" level=info msg="Connecting to proxy" url="wss://tunnel.kubiya.ai/kubiya-solutions-engineering/kubiya-solutions-engineering-tunnel-se-runner-20230801-2"
    time="2023/08/01 14:35:53" level=error msg="Failed to connect to proxy. Response status: 502 - 502 Bad Gateway. Response body: " error="websocket: bad handshake"
    # rollout restart
    -----------------
    $ kubectl rollout restart deployment kubiya-connector-se-runner-20230801-2 -n kubiya
    deployment.apps/kubiya-connector-se-runner-20230801-2 restarted
Last modified 1mo ago