From: Tom Lane <tgl@sss.pgh.pa.us>
To: Graeme <graeme@gemmill.name>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: Upgrade problem
Date: Mon, 11 Sep 2023 12:26:59 -0400
Message-ID: <2623618.1694449619@sss.pgh.pa.us> (raw)
In-Reply-To: <4e70f17d-1323-4a74-9b05-c7a76868f815@gemmill.name>
References: <ba7803a7-ff38-44dd-be56-12ad42e65c81@gemmill.name>
<2621665.1694448638@sss.pgh.pa.us>
<4e70f17d-1323-4a74-9b05-c7a76868f815@gemmill.name>
Graeme <graeme@gemmill.name> writes:
> Tom, thanks: it's finding other so. files in the correct place
> libpam.so.0 => /lib64/libpam.so.0 (0x00007f8d49e1e000)
> libssl.so.1.1 => not found
> libcrypto.so.1.1 => not found
> librt.so.1 => /lib64/librt.so.1 (0x00007f8d49e16000)
Note this only shows it looking in /lib64, maybe you need a symlink there?
Alternatively, try ldd on the libssl.so.1.1 file itself, to see if it
has unresolved dependencies. I'm not totally sure, but I think indirect
unresolved dependencies might display this way.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: tgl@sss.pgh.pa.us, graeme@gemmill.name
Subject: Re: Upgrade problem
In-Reply-To: <2623618.1694449619@sss.pgh.pa.us>
References: <ba7803a7-ff38-44dd-be56-12ad42e65c81@gemmill.name> <2621665.1694448638@sss.pgh.pa.us> <4e70f17d-1323-4a74-9b05-c7a76868f815@gemmill.name> <2623618.1694449619@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox