> For the complete documentation index, see [llms.txt](https://platform9.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://platform9.com/kb/pcd/self-hosted/perconadb-pod-being-in-crashloopbackoff-state.md).

# PerconaDB pod Being in "CrashLoopBackOff" State

## Problem

* Cluster details seem to be missing via GUI.
* The Neutron and Watcher-Api pods were in the error state due to `Liveness` and `Readiness` probe failures.
* PerconaDB in `CrashLoopBackOff` state.

## Environment

* Self-Hosted Private Cloud Director Virtualisation – v2025.4 \[ONLY]
* Component: Percona

## Cause

The PVC for PerconaDB has reached its current 6Gi limit; increasing the storage is necessary to ensure smooth operation. An enhancement request `PCD-2365` was created to fix this in the next release. 

## Resolution

This issue is resolved in the Self-Hosted Private Cloud Director Virtualisation version- **v2025.6 release.**

## Workaround

Update the PerconaDB persistent volume claim to use a minimum of 30Gi, rather than the default 6Gi.

To make these changes, proceed as follows:

> Make sure storage class must support volume expansion.

1. Update the PVCs for all the PerconaDB pods

```bash
$ kubectl edit pvc <DATADIR_PERCONA_DB_PXC-X>
...
spec:
  resources:
    requests:
      storage: 6Gi       # Replace this value to 30Gi
```

2. Ensure the modified PVC size is reflected in the PVCs.

```dart
Before
[REGION-1]    [DATADIR_PERCONA_DB_PXC_DB_PXC_0]       Bound    pvc-[..]   6Gi       RWO        pcd-sc         <unset>         32d
[REGION-1]    [DATADIR_PERCONA_DB_PXC_DB_PXC_1]       Bound    pvc-[..]   6Gi       RWO        pcd-sc         <unset>         32d
[REGION-1]    [DATADIR_PERCONA_DB_PXC_DB_PXC_2]       Bound    pvc-[..]   6Gi       RWO        pcd-sc         <unset>         32d
  
After
[REGION-1]     [DATADIR_PERCONA_DB_PXC_DB_PXC_0]      Bound    pvc-[..]   300Gi     RWO        pcd-sc         <unset>         32d
[REGION-1]     [DATADIR_PERCONA_DB_PXC_DB_PXC_1]      Bound    pvc-[..]   300Gi     RWO        pcd-sc         <unset>         32d
[REGION-1]     [DATADIR_PERCONA_DB_PXC_DB_PXC_2]      Bound    pvc-[..]   300Gi     RWO        pcd-sc         <unset>         32d
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://platform9.com/kb/pcd/self-hosted/perconadb-pod-being-in-crashloopbackoff-state.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.