Encountered issue after a power failure which cause all the nodes of the identity manager cluster to reboot. Based on the error, i’m getting the following: Error 500: org.hibernate.exception.GenericJDBCException: could not prepare statement Bookmark this KB as this explains how the internal Postgres cluster works – basically, if all the nodes failed – you need to manully bring up the VIP of the post
Making a post on this as I experienced this first hand. Issue is, after reboot, some pods will not run. Specifically, vco and pg. This can be verified by executing the following command in one of the node: kubectl get pods –all-namespaces You’ll notice some pods will be CrashLoop state. To resolve, the following KB will help: https://kb.vmware.com/s/article/78235 For new installs: https://kb.vmware.com/s/
With the recent ncov19 situation, this gave me time to start the long overdue updates to my site which include: Migrating to a new (beefier) VPS Server! End-to-End SSL certificates between CDN and the VPS Migrate from docker-compose to ansible for easier rebuild of the site. Overall, happy with the results.. and with that said, I’ll create a more detailed steps on the learning from this and what you can do with