Oops. I used a dummy IP address in the yml file for privacy reasons. The actual IP addresses would be placed there in my setup. The pg_basebackup connection to the MASTER_PORT_5432_TCP_ADDR is successful, so I know that slave can connect to the master at least. But it just cannot open a streaming backup connection...
On Thu, Apr 9, 2015 at 4:11 PM, Adrian Klaver <adrian.klaver@xxxxxxxxxxx> wrote:
Well if I am understanding. This:On 04/09/2015 01:00 PM, Volkan Unsal wrote:
Hi Adrian,
1) What version(s) of Postgres are you using on either end?
I'm using Postgres 9:3.
2) Are the primary and the standby in different containers?
Yes, and they are on different servers as well.
3) What is the container/machine/network layout?
I created a gist of all the files in my setup.
https://gist.github.com/volkanunsal/ad2173e2649393fcd3b6
The init-slave.sh and init-master.sh scripts are executed before the
server is started, so that's where I do all my preprocessing of conf
files. I checked the results and the substituted values are indeed correct.
primary_conninfo = 'host=${MASTER_PORT_5432_TCP_ADDR} port=5432
is getting translated to:
host=0.0.0.0 port=5432
Now the primary can receive connections from 0.0.0.0, which basically means it can receive from the Internet. The problem is that the standby can not connect to 0.0.0.0, that would mean it is connecting to the whole Internet. You will need to provide either the actual IP for the primary or its hostname.
--
*Volkan Unsal*
/web and mobile development/
volkanunsal.com <http://bit.ly/1h1ebjy>
--
Adrian Klaver
adrian.klaver@xxxxxxxxxxx
Volkan Unsal
web and mobile development