From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Volkan Unsal <spocksplanet(at)gmail(dot)com> |
Cc: | Melvin Davidson <melvin6925(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: no pg_hba.conf entry for replication connection from host |
Date: | 2015-04-09 21:53:33 |
Message-ID: | 5526F4DD.2000702@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 04/09/2015 02:38 PM, Volkan Unsal wrote:
> If you on the outside looking in would that not depend on firewall
> rules also?
>
>
> Hm, I guess. But I'm not behind a firewall and neither is the server.
>
>
> On the standby what does netstat -lt show?
>
>
> This is what I see on the standby
>
> Active Internet connections (only servers)
> Proto Recv-Q Send-Q Local Address Foreign Address State
> tcp 0 0 *:ssh *:* LISTEN
> tcp6 0 0 [::]:ssh [::]:* LISTEN
> tcp6 0 0 [::]:postgresql [::]:* LISTEN
>
So it is using IPv6. If you are looking for the port using IPv4 then you
will probably not see it.
Might try in your primary pg_hba.conf changing to:
host replication ${REP_USER} all md5
host replication ${REP_USER} 0.0.0.0/0 md5
host ${DB_NAME} ${DB_USER} 0.0.0.0/0 md5
>
> What do the FATAL errors say?
>
>
>
> I forgot their contents now, but I think they showed up for trying to
> connect via psql, and not as part of replication process.
>
>
>
>
>
> --
> *Volkan Unsal*
> /web and mobile development/
> volkanunsal.com <http://bit.ly/1h1ebjy>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Volkan Unsal | 2015-04-09 22:01:38 | Re: no pg_hba.conf entry for replication connection from host |
Previous Message | Volkan Unsal | 2015-04-09 21:41:40 | Re: no pg_hba.conf entry for replication connection from host |