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

# Troubleshooting

> Common issues with self hosting

There are a lot of moving parts in `eksctl`. Here’s a list of common issues we’ve seen customers run into:

<AccordionGroup>
  <Accordion title="Error while deleting &#x22;1 pods are unevictable from node ip&#x22;">
    This error happens when deleting the cluster and some pods in `kube-system` refuse to stop.
    To fix this, run the following command and the deletion process should be able to proceed.

    ```sh theme={null}
    kubectl get pods -n kube-system -o NAME | xargs kubectl -n kube-system delete
    ```
  </Accordion>

  <Accordion title="Error while deleting &#x22;cleaning up AWS load balancers created by Kubernetes objects of Kind Service or Ingress&#x22;">
    This happens when the cluster doesn't properly delete load balancers. To fix this:

    <Steps>
      <Step title="Get load balancers to be deleted">
        Run this to get the available load balancers

        ```sh theme={null}
        kubectl get ingress
        ```

        The output should look like this

        ```
        NAME                                           CLASS   HOSTS   ADDRESS                                                                  PORTS   AGE
        vector-inference-embedding-bgem3-ingress       alb     *       k8s-default-vectorin-25e84e25f0-1362792264.us-east-2.elb.amazonaws.com   80      3d19h
        vector-inference-embedding-nomic-ingress       alb     *       k8s-default-vectorin-eb664ce6e9-238019709.us-east-2.elb.amazonaws.com    80      2d20h
        vector-inference-embedding-spladedoc-ingress   alb     *       k8s-default-vectorin-8af81ad2bd-192706382.us-east-2.elb.amazonaws.com    80      3d19h
        ```
      </Step>

      <Step title="Delete Extra Load Balancers">
        Go to EC2 > LoadBalancers ([link](https://us-west-1.console.aws.amazon.com/ec2/home?region=us-west-1#LoadBalancers:v=3;\$case=tags:false%5C,client:false;\$regex=tags:false%5C,client:false)) and delete the ALBs that have the ingress point names
      </Step>

      <Step title="Restart the delete script, but it should auto resume">
        The delete script should be able to resume
      </Step>
    </Steps>
  </Accordion>
</AccordionGroup>