> ## Documentation Index
> Fetch the complete documentation index at: https://docs.envzero.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting

> Troubleshoot common env zero self-hosted Kubernetes agent issues, including SIGABRT crash errors from pod memory limits and resource configuration.

# Deploy failed with signal SIGABRT

If your deployment failed with this error message it means the pod got `SIGABRT` signal from the k8s cluster it runs on - It usually indicates a crash due to memory limitation.

In this case, we suggest defining `requests` and `limits` for the pod size as described in [Custom/Optional Configuration](/guides/admin-guide/self-hosted-kubernetes-agent/custom-optional-configuration).

## Next steps

* [Custom/Optional Configuration](/guides/admin-guide/self-hosted-kubernetes-agent/custom-optional-configuration) - Set resource requests and limits for deployment pods.
* [Monitoring Self-Hosted Agents](/guides/admin-guide/self-hosted-kubernetes-agent/self-hosted-agents-monitoring) - Check agent state and connectivity status.
* [Self-Hosted Kubernetes Agent](/guides/admin-guide/self-hosted-kubernetes-agent/self-hosted-kubernetes-agent) - Reinstall or upgrade the agent Helm chart.