Re: pg_basebackup + SSL error: bad length

On 08/27/2018 02:00 AM, Csaba Ragasits wrote:
> Hello,
>
> I would like to create a streaming replication, when I'm trying the
> basebackup from the node1, I've the following errors:
>
> pg_basebackup -P -v -D ./main -h node1 -p 5432  -U repmgr
>
> pg_basebackup: initiating base backup, waiting for checkpoint to complete
> pg_basebackup: checkpoint completed
> pg_basebackup: write-ahead log start point: 2/13000028 on timeline 1
> pg_basebackup: directory "/srv/pgdata/tbs_int302" exists but is not empty
> pg_basebackup: removing data directory "./main"
>
> In the node1 postgresql.log:
>
> LOG:  could not send data to client: Connection reset by peer
> ERROR:  base backup could not send data, aborting backup
> LOG:  SSL error: bad length
> LOG:  SSL error: bad length
> FATAL:  connection to client lost
>
> When I set off the SSL in the postgresql.conf, i've the folloving error
> message when I try use the pg_basebackup command:
> LOG:  could not send data to client: Broken pipe
> FATAL:  connection to client lost
>
> Have you got any information, suggestion how can I solve this errors?

Can you connect to node1 using psql with and without SSL?

Where is node1 relative to the machine you are running pg_basebackup from?

Just to be clear both Postgres instances are running 10.5, correct?

>
> My area:
> - Updated Debian GNU/Linux 9
> - PostgreSQL 10.5 (Debian 10.5-1.pgdg90+1) on x86_64-pc-linux-gnu,
> compiled by gcc (Debian 6.3.0-18+deb9u1) 6.3.0 20170516, 64-bit
>
> Thx,
> Csaba

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com