Have anyone set pgbouncer for retool, if so could you please help us what are the pgbouncer setup required to add in out retool helm charts. thanks in advance.
1 Like
Hello @Godwin_Moses!
You should look to externalize your Postgres Database for storing data that you are going to be using and accessing with your Retool instance.
The helm chart by default sets up an internal Postgres but as outlined in our docs you likely want to follow these directions to externalize a separate Postgres DB. This will separate the database from the Helm charts scope.
Unfortunately I don't have experience doing it but know that many self hosted users have been able to set this up and it should be fairly straightforward but will depend on what unique custom factors are going into your self hosted set up.
I found these docs online about setting up a pgBouncer as well. I also moved your post to the 'Discussion' section of the forums so other users can see it and chime in any advice on the set up!
1 Like
Hi @Jack_T ,
I am able to successfully setup pgbouncer for my retool application,
We are successfully able to have the connection from pgbouncer to postgress database but from Retool to pgbouncer we are getting a error: SequelizeConnectionError: The server does not support SSL connections.
When we set the ssl_enabled: false we are getting the below error:
retool_backend/node_modules/.pnpm/sequelize@6.31.0_mysql2@2.3.3_oracledb@5.3.0_pg@8.7.3_snowflake-sdk@1.9.0_tedious@11.8.0/node_modules/sequelize/lib/dialects/postgres/connection-manager.js:143
reject(new sequelizeErrors.ConnectionError(err));
^
SequelizeConnectionError: SASL authentication failed
at Client._connectionCallback (/retool_backend/node_modules/.pnpm/sequelize@6.31.0_mysql2@2.3.3_oracledb@5.3.0_pg@8.7.3_snowflake-sdk@1.9.0_tedious@11.8.0/node_modules/sequelize/lib/dialects/postgres/connection-manager.js:143:24)
at Client._handleErrorWhileConnecting (/retool_backend/node_modules/.pnpm/pg@8.7.3/node_modules/pg/lib/client.js:305:19)
at Client._handleErrorMessage (/retool_backend/node_modules/.pnpm/pg@8.7.3/node_modules/pg/lib/client.js:325:19)
at Connection.emit (node:events:517:28)
at /retool_backend/node_modules/.pnpm/pg@8.7.3/node_modules/pg/lib/connection.js:114:12
at Parser.parse (/retool_backend/node_modules/.pnpm/pg-protocol@1.6.0/node_modules/pg-protocol/dist/parser.js:40:17)
at Socket. (/retool_backend/node_modules/.pnpm/pg-protocol@1.6.0/node_modules/pg-protocol/dist/index.js:11:42)
at Socket.emit (node:events:517:28)
at addChunk (node:internal/streams/readable:335:12)
at readableAddChunk (node:internal/streams/readable:308:9)
Standard Commons Logging discovery in action with spring-jcl: please remove commons-logging.jar from classpath in order to avoid potential conflicts
Have anyone faced this kind of error !