This repository has been archived by the owner on Aug 3, 2022. It is now read-only.
Changeserver has bug re-establishing connection to Postgres #54
Comments
|
Sorry I didn't jump on this yet.
What do you mean by "has bugs?"
It sounds like you did something like the following:
1) Start PG with an invalid pg_hba.conf
2) Start change server
3) Fix pg_hba.conf and signal Postgres to pick up the change
4) Verify that change server still isnt' working?
I also assume that if you restart the change server after this, that it
does work, right?
In other words, is this problem isolated to the case in which the change
server is unable to connect because pg_hba.conf does not allow it?
…On Mon, Mar 6, 2017 at 1:47 PM, Mitchell Fierro ***@***.***> wrote:
Changeserver was being denied connection to Postgres on the basis that
there was not a pg_hba.conf entry for replication.
Once that was fixed, it connected to Postgres as expected, but would
constantly (and unexpectedly) disconnect
time="2017-03-06T21:14:04Z" level=warning msg="Error connecting to Postgres. Retrying in 1m0s: FATAL FATAL 28000 no pg_hba.conf entry for replication connection from host \"130.211.127.19\", user \"ch
angeserver\", SSL off auth.c 471 ClientAuthentication "
time="2017-03-06T21:15:04Z" level=warning msg="Error connecting to Postgres. Retrying in 1m0s: FATAL FATAL 28000 no pg_hba.conf entry for replication connection from host \"130.211.127.19\", user \"ch
angeserver\", SSL off auth.c 471 ClientAuthentication "
time="2017-03-06T21:16:04Z" level=warning msg="Error connecting to Postgres. Retrying in 1m0s: FATAL FATAL 28000 no pg_hba.conf entry for replication connection from host \"130.211.127.19\", user \"ch
angeserver\", SSL off auth.c 471 ClientAuthentication "
time="2017-03-06T21:17:04Z" level=warning msg="Error connecting to Postgres. Retrying in 1m0s: FATAL FATAL 28000 no pg_hba.conf entry for replication connection from host \"130.211.127.19\", user \"ch
angeserver\", SSL off auth.c 471 ClientAuthentication "
time="2017-03-06T21:18:04Z" level=info msg="Connected to Postgres using replication slot \"ratc_2505620705112246567_a_gce\""
time="2017-03-06T21:19:04Z" level=warning msg="Disconnected from Postgres."
time="2017-03-06T21:19:04Z" level=info msg="Connected to Postgres using replication slot \"ratc_2505620705112246567_a_gce\""
time="2017-03-06T21:20:04Z" level=warning msg="Disconnected from Postgres."
time="2017-03-06T21:20:04Z" level=info msg="Connected to Postgres using replication slot \"ratc_2505620705112246567_a_gce\""
time="2017-03-06T21:21:04Z" level=warning msg="Disconnected from Postgres."
time="2017-03-06T21:21:04Z" level=info msg="Connected to Postgres using replication slot \"ratc_2505620705112246567_a_gce\""
time="2017-03-06T21:22:04Z" level=warning msg="Disconnected from Postgres."
time="2017-03-06T21:22:04Z" level=info msg="Connected to Postgres using replication slot \"ratc_2505620705112246567_a_gce\""
time="2017-03-06T21:23:04Z" level=warning msg="Disconnected from Postgres."
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#54>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAf0a6Z1suqv5gPmQpl1gCefgz1SqCGyks5rjH7VgaJpZM4MUvSS>
.
|
|
I think this issue was
then, you reload config, and postgres has this connection problem as in the error logs I think this just prevents live updates to pg_hba.conf |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Changeserver was being denied connection to Postgres on the basis that there was not a pg_hba.conf entry for replication.
Once that was fixed, it connected to Postgres as expected, but would constantly (and unexpectedly) disconnect
The text was updated successfully, but these errors were encountered: