Valkan,
I do not see any errors in the postgres log regarding no entry in
pg_hba.conf. So either you have sent the log from the slave, or you
are not specifying the correct address in the slave's recovery.conf
connection info
On 4/10/15, Volkan Unsal <spocksplanet@gmail.com> 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...
>
>
>
> On Fri, Apr 10, 2015 at 9:28 AM, Melvin Davidson <melvin6925@gmail.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 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>
>
--
*Melvin Davidson*
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.