Open vishantsolanki opened 3 years ago
Your Postgres seems to got stuck and is not running. The operator logs are not very helpful here. Exec into the pod and check the Postgres logs (under $PGLOG
). Check also patroni logs kubectl logs
on the database pod(s). There you should find the reason to the problem.
Hi, FxKu
Again i have faced same issue in our postgres cluster sysnc failed due to my production impacted can you please help me out where it got stuck i have checked logs but didn't able to found any concrete reason.
Operator Logs:
Postgres Pod Logs:
@vishantsolanki please, check the Postgres logs in the pod for errors on why it's not starting. And if this is for your production system, go with at least two pods so that there's always a replica to switch over to.
I also encountered the same problem, and there will be a core dump in the pod data directory.Check the contents of postgresql-5.csv and postgresql-5.log in the pg_log directory, and the following errors appear respectively:
2021-07-02 03:01:24 UTC [24347]: [1-1] 60de8182.5f1b 0 LOG: could not rename file "current_logfiles.tmp" to "current_logfiles": No such file or directory
ERROR:replication slot "acid_upgrade_test_1" does not exist
FATAL:could not start WAL streaming: ERROR: replication slot "acid_upgrade_test_1" does not exist
Hi Folks,
I have deployed zalando postgres operator in my production environment k8s, and my cluster and pod are running fine after 3 days,Im facing some problems with Postgres clusters and my db clusters are presenting the status SyncFailed error getting (could not sync cluster: could not sync roles: could not init db connection: could not init db connection: pq: the database system is starting up)
Postgres operator pod logs:
Can you please help me out to resolve this issue i have tried to find out solution but not yet up to mark