We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Getting this error when trying to apply the Helm chart (using default config values) on a GKE cluster:
27 Jul 2024 10:06:29:849 +0000 | ERROR | pid: 1e9271b7-c717-48a2-8bb1-54ec2e498ca8 | [main] thread | io.supertokens.storage.postgresql.HikariLoggingAppender.doAppend(HikariLoggingAppender.java:132) | |postgres.postgres|5432|supertokens|public~|10|postgres|********|allowPublicKeyRetrieval=true|postgresql|60000 - Exception during pool initialization. 27 Jul 2024 10:06:29:852 +0000 | INFO | pid: 1e9271b7-c717-48a2-8bb1-54ec2e498ca8 | [main] thread | io.supertokens.Main.stopApp(Main.java:417) | Tenant(, public, public) | Stopping SuperTokens... [31mTenant(, public, public) | What caused the crash: io.supertokens.pluginInterface.exceptions.DbInitException: io.supertokens.pluginInterface.exceptions.DbInitException: java.sql.SQLException: com.zaxxer.hikari.pool.HikariPool$PoolInitializationException: Failed to initialize pool: The connection attempt failed.�[0m
The text was updated successfully, but these errors were encountered:
Hi. The Helm chart is community contributed, so we can wait for someone to fix it. Or if you find the fix, you could let us know or issue a PR. Thanks
Sorry, something went wrong.
No branches or pull requests
Getting this error when trying to apply the Helm chart (using default config values) on a GKE cluster:
The text was updated successfully, but these errors were encountered: