-
-
Notifications
You must be signed in to change notification settings - Fork 774
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
Gitea Down Because pg become read-only #173
Comments
The problem is resolved.
|
Thank you for posting the solution! I'll close this issue as resolved. |
configure-gitea
Run Failed
@khuedoan The same problem occurred again today.
Given this, I think a possible reason is that the bitnami pg used by gitea is not robust enough. Could you consider replacing it with a better k8s pg implementation, such as CloudNativePG? Thanks! |
Thanks for following up on the issue. I'll look into it. For Gitea specifically, I'm considering switching to single-node mode with SQLite because I don't need HA for Gitea that much. With fewer components involved, there's less things that could go wrong (the tradeoff is accepting downtime during weekly upgrades, but I've scheduled those for when I'm asleep) |
I agree. |
Describe the bug
After installing in high availability mode, gitea was rebooted, and after the reboot, gitea went down because the init container
configure-gitea
failed to run.To reproduce
Steps to reproduce the behavior:
Expected behavior
Please guide me step by step on how to troubleshoot this problem.
Logs and screenshots
init container
configure-gitea
logs:Command error: pq: cannot execute UPDATE in a read-only transaction
The text was updated successfully, but these errors were encountered: