Closed RyanCDS closed 1 year ago
How is your database configured? Is it fronted by PgBouncer?
Yes, is it fronted by PgBouncer. Which configuration information may be relevant for helping ?
This error isn’t coming from the pact broker, it’s from pgbouncer. You can correct it by telling pgbouncer to ignore the options parameter:
https://github.com/Athou/commafeed/issues/559#issuecomment-169551299
Ok, so the options "-c statement_timeout=15s" will be manage directly by postgre and we will not override this with pact-broker docker ? I thought that i had an issue on the format from "driver_options" who needs the options directly for pgbouncer and not with the format "{:options=>"-c statement_timeout=15s"}".
I ask to my database admin to try your solution and let you know if it works.
The error isn’t coming from the pact broker (or the way it behaves), it’s because pgbouncer doesn’t support the startup parameter options, so yes, your db admin will need to check that everything is in order
Thanks Tim, great spot.
The logs below come from version 2.107.0.1 (it's similar issue with version 2.87.0.1).
This seems to imply that it previous did work. Is that right and if so, which version previously worked?
Thanks Tim, great spot.
The logs below come from version 2.107.0.1 (it's similar issue with version 2.87.0.1).
This seems to imply that it previous did work. Is that right and if so, which version previously worked?
This is right, the version 2.87.0.0 work without errors.
Have you tried it recently, or was that when you introduced pgbouncer?
Nothing change on my configuration between each test, only the version change.
Hello, for the record i successfully deploy the pact broker docker after update pgbouncer options startup. It's still weird that i have to change that since version 2.87.0.1.
I mark the issue as completed.
Pre issue-raising checklist
I have already (please mark the applicable with an
x
):Software versions
Expected behaviour
The pact broker should start correctly
Actual behaviour
I got an error during kubernetes deployment.
For information, i did some test with different version and the changeset who broke the deployment appears with version 2.87.0.1
The logs below come from version 2.107.0.1 (it's similar issue with version 2.87.0.1).
Steps to reproduce
Deploy image docker v 2.107.0.1 with config below (for information, i use postgre in version 11) :
Relevent log files
Here the log file from Kubernetes during deployment