Troubleshooting your Local Runner
Last updated
Was this helpful?
Last updated
Was this helpful?
You may find yourself:
Troubleshooting problems with your AI Teammates
Troubleshooting problems with your local runner
Wanting to check the health of your local runner
The often boil down to checking the health of your local runner and in some cases, restarting certain deployments. In this doc, you'll learn how to:
Check the health of your local runner
Restart deployments
We'll start by reviewing how to do this from the Kubiya web app. If you're interested in doing this manually from Kubernetes (kubectl), jump to this section for our guide on that.
Go to the
Next to each runner, you will see it's overall health, which is the aggregate health of all deployments. If any of its deployments are unhealthy, the health will appear is Unhealthy . If it says Healthy, that means all deployments are healthy.
To see the health of specific deployments, select a runner
In the right-side panel you will see additional information about your it, including the specific deployments and their health
Click on a specific runner
In the right-side panel, next to each deployment is a Restart button.
Click the Restart button and the deployment will restart
Run the following command :
Locate your runner in one of the deployments ( the runner name is kubiya-operator ).
A runner with a healthy status should have as follows:
Stream the logs from the runner deployment
Go to the
In case you are seeing an error in the streamed logs try to rollout restart the deployment and repeat steps and 1.