On 04/10/2015 11:04 AM, Volkan Unsal wrote:
Hi Melvin,
I followed your instructions above and modified the pg_hba.conf in
master to hardcode the IP address of the standby server. I kept the same
pg_hba.conf file for the standby server –– I hope that was right. The
log output hasn't changed much, but I'm enclosing it in this gist:
https://gist.github.com/volkanunsal/1778cf691223e77f2e30
I hope the answer is in there...
I would say it is this:
backend>
PostgreSQL stand-alone backend 9.3.6
My guess is these:
LOG: connection received: host=104.131.66.183 port=46406
LOG: replication connection authorized: user=replication
LOG: connection received: host=104.131.66.183 port=46407
are pg_basebackup connecting.
Pretty sure the stand alone(single user) does not support streaming
replciation.
On Fri, Apr 10, 2015 at 9:28 AM, Melvin Davidson <melvin6925@xxxxxxxxx
<mailto:melvin6925@xxxxxxxxx>> wrote:
Volkan,
What I see in the link is the original post.
I did not see any postgres log entry complaining about invalid entry
in pg_hba.conf.
The pg_hba.conf entry in your original post is wrong. What you need is
host replication replication 104.131.66.183/32
<http://104.131.66.183/32> md5
If you get an error after making that change, then please attach the
complete new
version of the pg_hba.conf AND the entry from postgres log where it
complains about
the invalid or non pg_hba.conf entry.
--
*Volkan Unsal*
/web and mobile development/
volkanunsal.com <http://bit.ly/1h1ebjy>
--
Adrian Klaver
adrian.klaver@xxxxxxxxxxx
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
