From: | Volkan Unsal <spocksplanet(at)gmail(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | Melvin Davidson <melvin6925(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: no pg_hba.conf entry for replication connection from host |
Date: | 2015-04-10 19:06:15 |
Message-ID: | CAMcqKmmmVOoyj0pMiL_1-hnZ8uRFORQSWcdyE5Z2WxA9kVfrfg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi Adrian,
I didn't realize stand-alone was the same thing as single-user mode –– are
you sure? I guess I don't know what the alternative is to "a stand-alone
backend."
The server is started using a straightforward call to "postgres". It's not
using the --single flag, which is what I assume is needed for the
single-user mode.
On Fri, Apr 10, 2015 at 2:46 PM, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
wrote:
> 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(at)gmail(dot)com
>> <mailto:melvin6925(at)gmail(dot)com>> 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(dot)klaver(at)aklaver(dot)com
>
--
*Volkan Unsal*
*web and mobile development*
volkanunsal.com <http://bit.ly/1h1ebjy>
From | Date | Subject | |
---|---|---|---|
Next Message | Volkan Unsal | 2015-04-10 19:14:32 | Re: no pg_hba.conf entry for replication connection from host |
Previous Message | Pawel Veselov | 2015-04-10 19:02:26 | Slow table update |