Re: FATAL: could not load library "/usr/pgsql-13/lib/libpqwalreceiver.so" during replication

On 12/19/20 5:05 PM, Rambabu V wrote:
> Hi Team,
>
> below is the link im getting packages.
>
> https://www.postgresql.org/download/linux/redhat/
> <https://www.postgresql.org/download/linux/redhat/>

This was fixed here:

https://redmine.postgresql.org/issues/4509

You will need community account to see issue.

Relevant parts:

2019-07-24
"After some analysis we found that the issue was the addition of
`X509_get_signature_nid` function calls in PG11, and the fact that the
customer was still on openssl-libs 1.0.1e, which doesn't have that
function implemented, and not the latest 1.0.2k available.

For that reason the postgresql11-libs should have a dependency so
openssl-libs 1.0.2 or better is installed."

...

2019-08-30

"I updated PostgreSQL 10+ spec files:

https://git.postgresql.org/gitweb/?p=pgrpms.git;a=commit;h=86f8778e077d250e9b3c0e695d5cc297057c511a

These changes will appear in next minor updates.
"

Have you looked at this announcement?:

https://yum.postgresql.org/news/new-repo-rpms-released/

>
> On Sun, Dec 20, 2020 at 6:33 AM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com
> <mailto:adrian(dot)klaver(at)aklaver(dot)com>> wrote:
>
> On 12/19/20 4:53 PM, Rambabu V wrote:
> > Hi Team,
> >
> > below are the os versions details. standalone machine running
> without
> > any issues, coming to replication not working, even i tried from
> > postgresql 10 onwards as well, no other versions running in the
> server now.
> >
> > [root(at)node2 ~]# openssl version
> > OpenSSL 1.0.1e-fips 11 Feb 2013
> > [root(at)node2 ~]# uname -a
> > Linux node2 3.10.0-327.el7.x86_64 #1 SMP Thu Oct 29 17:29:29 EDT
> 2015
> > x86_64 x86_64 x86_64 GNU/Linux
> > [root(at)node2 ~]# cat /etc/redhat-release
> > Red Hat Enterprise Linux Server release 7.2 (Maipo)
> > [root(at)node2 ~]#
> >
>
> Where are you getting the packages?
>
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com <mailto:adrian(dot)klaver(at)aklaver(dot)com>
>

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