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

# Validate and troubleshoot Rancher installs

> Check operator status, pods, jobs, stuck init jobs, and log safety after installing Arize AX on Rancher-managed Kubernetes.

## Check the install

After `arize.sh install` finishes, do not rely only on the shell exit code. Confirm the operator and pods are healthy:

```bash theme={null}
kubectl get pods -n arize-operator
kubectl get pod arize-op-arize-operator-operator-0 -n arize-operator \
  -o jsonpath='{.metadata.annotations.operator\.arize\.com/status}{"\n"}'
kubectl get pods -n arize
kubectl get jobs -n arize
```

`./arize.sh -y install-status` can also be useful when Arize AI Support asks for a deeper status check, but it prints the startup configuration, including secret values such as `hubJwt`, and it can produce a lot of output. Redact the output before sharing it.

Useful operator statuses:

| Status       | Meaning                                                                                                                                                                                                                   |
| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Executing`  | The operator is rendering and applying manifests.                                                                                                                                                                         |
| `Installing` | Core install jobs and dependencies are still starting.                                                                                                                                                                    |
| `Delayed`    | The operator is waiting for active install jobs to finish before it can reconcile. If a job is stuck Running for an unreasonable time, see [Troubleshooting failed or stuck jobs](#troubleshooting-failed-or-stuck-jobs). |
| `Running`    | The operator reports the deployment is complete.                                                                                                                                                                          |
| `Error`      | Check operator logs and failed jobs.                                                                                                                                                                                      |

A successful install should leave the Arize AX Operator running in `arize-operator`, all install jobs completed in `arize`, and application pods running.

## Troubleshooting failed or stuck jobs

If the operator reports `Error`, `Delayed`, or says bad jobs exist, check jobs and logs:

```bash theme={null}
kubectl get jobs -n arize

for job in install-postgres-init install-gazette-init install-druid-init; do
  echo "===== $job ====="
  pod=$(kubectl get pod -n arize -l job-name=$job -o jsonpath='{.items[0].metadata.name}' 2>/dev/null || true)
  [ -n "$pod" ] && kubectl logs -n arize "$pod" --tail=120
done
```

A `Failed` job blocks retry. So does a `Running` job that has been waiting for hours on a dependency that has since recovered. The init pod will not reconnect, and the operator stays `Delayed` reconciling around it. In either case, delete the Arize AX-owned job and re-apply:

```bash theme={null}
kubectl delete job <failed-or-stuck-job-name> -n arize || true
./arize.sh -y apply
```

The operator recreates fresh init jobs on the next reconcile.

## Log safety

<Warning>
  `arize.sh` prints secret values such as `hubJwt` in the startup configuration block at the top of every install run. Redact install logs before sharing them with anyone outside your team.
</Warning>

## Next steps

* [Validate deployment](/docs/ax/selfhosting/installation/validate-deployment)
* [Fresh reinstall cleanup](/docs/ax/selfhosting/advanced/fresh-reinstall-cleanup), only when intentionally discarding the previous install