Replies: 5 comments
-
Just chiming in here to say that I am experiencing the same issue. This is the output of the
Then the actual restore starts, but that eventually errors out:
|
Beta Was this translation helpful? Give feedback.
-
We have a similar issue. We had this error and also it is stuck in recovery mode. How do we bring the server out of recovery mode? |
Beta Was this translation helpful? Give feedback.
-
We have the same issue as well. Please help with the solution |
Beta Was this translation helpful? Give feedback.
-
Is there a way to interact with the CNPG controller directly? kubectl cnpg promote, restart, and reload do not bring the cluster back to a working state. We have had restore from backup on three different clusters because CNPG gets stuck. |
Beta Was this translation helpful? Give feedback.
-
We also have the same issue as well. Please help with the solution! Anyone? |
Beta Was this translation helpful? Give feedback.
-
I recently re-provisioned my k8s cluster and I am trying to get my cnpg postgres instances back up and running from a backup.
Configuration
I notice the recovery pods starts but then has this in the logs:
When that pod errors another one is created and that errors out with saying
Cannot restore, PGDATA exists
,several more pods are created but also error with that, after which it looks like cnpg just gives up. I couldn't find anything in the operator logs that looked relevant to this problem.Thanks for the help.
Beta Was this translation helpful? Give feedback.
All reactions