New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PostgreSQL database keep recovering #1685
Comments
If nothing lib files or system settings has been modified manually, possibly due to OOM and kill the process. Could you share the
|
Could you please also describe database pod, and share the output with us? |
This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days. |
If nothing lib files or system settings has been modified manually, possibly due to OOM and kill the process. Could you share the
Hello, sorry for late reply, conf is in the attachment, only what i changed was the shared_buffers to 1024MB ( the rest is defautl) `database: if external database is used, set "type" to "external"and fill the connection informations in "external" sectiontype: internal |
Hello, sorry for late response, here is the described pod. (attach) |
Hello @Noisia0800 , did you fix the issue ? I have same issue , harbor is install by helm , using psql internal this is apart of my values.yaml
|
Hello,
I've install Harbor via helm chart in kubernetes. Our version of harbor is v2.7.1, harbor seems to running good for few months, but now we are facing some issues with PostgreSQL database. (goharbor/harbor-db:v2.7.1)
PostgreSQL database keep recovering state, but sometimes its is running somehow.
2024-01-16 14:53:15.270 UTC [1] LOG: terminating any other active server processes
2024-01-16 14:53:15.297 UTC [1] LOG: all server processes terminated; reinitializing
2024-01-16 14:53:15.624 UTC [27] LOG: database system was shut down at 2024-01-16 14:53:12 UTC
2024-01-16 14:53:15.624 UTC [28] FATAL: the database system is in recovery mode
2024-01-16 14:53:16.526 UTC [1] LOG: database system is ready to accept connections
2024-01-16 14:53:22.282 UTC [1] LOG: server process (PID 41) exited with exit code 141
2024-01-16 14:53:22.282 UTC [1] LOG: terminating any other active server processes
2024-01-16 14:53:22.282 UTC [44] WARNING: terminating connection because of crash of another server process
2024-01-16 14:53:22.282 UTC [44] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2024-01-16 14:53:22.282 UTC [44] HINT: In a moment you should be able to reconnect to the database and repeat your command.
2024-01-16 14:53:22.283 UTC [32] WARNING: terminating connection because of crash of another server process
2024-01-16 14:53:22.283 UTC [32] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2024-01-16 14:53:22.283 UTC [32] HINT: In a moment you should be able to reconnect to the database and repeat your command.
2024-01-16 14:53:22.936 UTC [1] LOG: all server processes terminated; reinitializing
2024-01-16 14:53:23.239 UTC [45] LOG: database system was interrupted; last known up at 2024-01-16 14:53:16 UTC
2024-01-16 14:53:30.791 UTC [55] FATAL: the database system is in recovery mode
2024-01-16 14:53:40.794 UTC [65] FATAL: the database system is in recovery mode
2024-01-16 14:53:50.805 UTC [75] FATAL: the database system is in recovery mode
2024-01-16 14:54:00.811 UTC [85] FATAL: the database system is in recovery
how to resolve this issue ?
Thanks for help
The text was updated successfully, but these errors were encountered: