Hi, we are still running in the issue I mentioned ...
# pact-broker
c
Hi, we are still running in the issue I mentioned a few months ago. We have set up the (open-source) pact-broker and a postgresDB in kubernetes. We are receiving status 500 for some calls and then the next will return normally. In the logs I see something like. Is there some obvious issue I am missing?
Copy code
2022-06-02 06:10:26.905288 E [6:puma server threadpool 001 log_quietener.rb:18] pact-broker -- PG::UnableToSend: server closed the connection unexpectedly
        This probably means the server terminated abnormally
        before or while processing the request.: SELECT NULL
2022-06-02 06:34:23 +0000 Rack app ("POST /pacts/provider/xyz/for-verification" - (10.249.112.192)): #<Sequel::DatabaseDisconnectError: PG::ConnectionBad: PQconsumeInput() server closed the connection unexpectedly
        This probably means the server terminated abnormally
        before or while processing the request.
 >
2022-06-02 06:34:23.894050 E [6:puma server threadpool 001 log_quietener.rb:18] pact-broker -- PG::ConnectionBad: PQconsumeInput() server closed the connection unexpectedly
        This probably means the server terminated abnormally
        before or while processing the request.: BEGIN
2022-06-02 06:34:23.896197 E [6:puma server threadpool 001 log_quietener.rb:18] pact-broker -- PG::UnableToSend: no connection to the server: ROLLBACK
Can also happen when trying to access the HAL-Browser (using latest pact-broker version), stacktrace:
b
What is your database set up?
It's not Aurora is it?
Try setting the connection validation time out to -1
c
Hi, it's postgres-9.8.12 running in kubernetes as a single node.
Ok gonna try that setting,
Thank you, let's see if it works :)
b
Postgres 9 is pretty old.
It should work, but we're using 13 at pactflow
c
The setting seems to have helped, so far the error has not occurred anymore. Thank you!
👍🏼 1