Postgres Pro
Downloads
Home   >   mailing lists

Re: SSL cert "not initialized" error with logical replication with 13.11 - Mailing list pgsql-admin

From Cary Huang
Subject Re: SSL cert "not initialized" error with logical replication with 13.11
Date
Msg-id 188def6e7c3.e5c815f6150300.1204203706527206764@highgo.ca
Whole thread Raw
In response to Re: SSL cert "not initialized" error with logical replication with 13.11  (Jeff Janes <jeff.janes@gmail.com>)
List pgsql-admin
Tree view
Hello

expired CA certificate could also cause "SSL error: sslv3 alert certificate expired" error. You should check the validity of your CA certificate. 

You can use this openssl command to verify your CA and your server certificate, see if it gives the same "certificate verify failed" error

openssl verify -verbose -CAfile $PATH_TO_CACERT $PATH_TO_SERVER_CERT

or it could be that your server clock is wrong, which is unlikely though.

best regards

Cary Huang
-----------------------------
Highgo Software (Canada)
www.highgo.ca




---- On Wed, 21 Jun 2023 08:05:15 -0700 Jeff Janes <jeff.janes@gmail.com> wrote ---


On Wed, Jun 21, 2023 at 6:11 AM Axel Rau <Axel.Rau@chaos1.de> wrote:
Hi all,

After upgrading to 13.11, Publisher no longer accepts cert of subscriber.

What did you upgrade from?  How did you do the upgrade?
 

Publisher:

"connection received: host=<some IP6> port=32501",,,,,,,,,"","not initialized"
"could not accept SSL connection: certificate verify failed",,,,,,,,,"","not initialized"


Your log files appear to have been mutilated.  What column is 'not initialized' appearing in?

 
Servercert:
...
 
        Validity
            Not Before: Aug 18 09:12:35 2022 GMT
            Not After : Aug 29 09:12:35 2023 GMT

What about the validity of the CA?

Cheers,

Jeff


pgsql-admin by date:

Previous
From: Wells Oliver
Date:
Subject: Re: AWS RDS "sessions" and pg_stat_activity
Next
From: Sean O'Grady
Date:
Subject: Re: Question about wal_compression and what to expect