Search Postgresql Archives

Re: no pg_hba.conf entry for replication connection from host

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



The database and the users are created using the --single flag, though. Here is the relevant shell script:

https://github.com/docker-library/postgres/blob/e616341507a7beec3a161b0a366ba0d3400328fd/9.3/docker-entrypoint.sh



On Fri, Apr 10, 2015 at 3:06 PM, Volkan Unsal <spocksplanet@xxxxxxxxx> wrote:
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.klaver@xxxxxxxxxxx> 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@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



--
Volkan Unsal
web and mobile development



--
Volkan Unsal
web and mobile development

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux