Upgrade problem

Graeme <graeme@gemmill.name> writes:

Preparing to upgrade my small cluster from Mageia 8/Pg 9 to Mageia 9/Pg
15. I'm at the point of running pg_upgrade but have received anerror
message:

/mga8/usr/bin/postgres: error while loading shared libraries:
libssl.so.1.1: cannot open shared object file: No such file or directory
no data was returned by command ""/mga8/usr/bin/postgres" -V"

You might get useful info from "ldd /mga8/usr/bin/postgres"
about where that executable is looking for libssl.

regards, tom lane

On 9/11/23 09:04, Graeme wrote:

Preparing to upgrade my small cluster from Mageia 8/Pg 9 to Mageia 9/Pg
15. I'm at the point of running pg_upgrade but have received anerror
message:

You are going to have to be more specific on the Postgres version. Prior
to Postgres 10 major version changes where two digits. So for Postgres
9.X.x that meant 9.0.x --> 9.6.x

/mga8/usr/bin/postgres: error while loading shared libraries:
libssl.so.1.1: cannot open shared object file: No such file or directory
no data was returned by command ""/mga8/usr/bin/postgres" -V"

Where are you running the pg_upgrade and what version of it are you using?

However:

[root@bach lib64]# cd /mga8/usr/lib64
[root@bach lib64]# ls -l|grep libssl
-rwxr-xr-x  1 root root      426192 Jul  5 23:07 libssl3.so*
lrwxrwxrwx  1 root root          13 Jun  1 09:35 libssl.so ->
libssl.so.1.1*
-r-xr-xr-x  1 root root      442424 Feb 27  2021 libssl.so.1.0.0*
-rwxr-xr-x  1 root root      666496 Jun  1 09:36 libssl.so.1.1*

Can someone suggest my next move please?

Ta

Graeme Gemmill

--
Adrian Klaver
adrian.klaver@aklaver.com

On 11/09/2023 17:10, Tom Lane wrote:

Graeme<graeme@gemmill.name> writes:

Preparing to upgrade my small cluster from Mageia 8/Pg 9 to Mageia 9/Pg
15. I'm at the point of running pg_upgrade but have received anerror
message:
/mga8/usr/bin/postgres: error while loading shared libraries:
libssl.so.1.1: cannot open shared object file: No such file or directory
no data was returned by command ""/mga8/usr/bin/postgres" -V"

You might get useful info from "ldd /mga8/usr/bin/postgres"
about where that executable is looking for libssl.

regards, tom lane

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)

so there must be another problem.

Graeme

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

On 11/09/2023 17:13, Adrian Klaver wrote:

On 9/11/23 09:04, Graeme wrote:

Preparing to upgrade my small cluster from Mageia 8/Pg 9 to Mageia
9/Pg 15. I'm at the point of running pg_upgrade but have received
anerror message:

You are going to have to be more specific on the Postgres version.
Prior to Postgres 10 major version changes where two digits. So for
Postgres 9.X.x that meant 9.0.x --> 9.6.x

Don't have access to that version without re-booting; probably 9.5

/mga8/usr/bin/postgres: error while loading shared libraries:
libssl.so.1.1: cannot open shared object file: No such file or directory
no data was returned by command ""/mga8/usr/bin/postgres" -V"

Where are you running the pg_upgrade and what version of it are you
using?

pg_upgrade (PostgreSQL) 15.3

I specified -B /usr/bin

On 11/09/2023 17:33, Graeme wrote:

On 11/09/2023 17:13, Adrian Klaver wrote:

On 9/11/23 09:04, Graeme wrote:

Preparing to upgrade my small cluster from Mageia 8/Pg 9 to Mageia
9/Pg 15. I'm at the point of running pg_upgrade but have received
anerror message:

You are going to have to be more specific on the Postgres version.
Prior to Postgres 10 major version changes where two digits. So for
Postgres 9.X.x that meant 9.0.x --> 9.6.x

Don't have access to that version without re-booting; probably 9.5

select version();

?

Ray.

--
Raymond O'Donnell // Galway // Ireland
ray@rodonnell.ie

On 9/11/23 09:33, Graeme wrote:

On 11/09/2023 17:13, Adrian Klaver wrote:

On 9/11/23 09:04, Graeme wrote:

Preparing to upgrade my small cluster from Mageia 8/Pg 9 to Mageia
9/Pg 15. I'm at the point of running pg_upgrade but have received
anerror message:

You are going to have to be more specific on the Postgres version.
Prior to Postgres 10 major version changes where two digits. So for
Postgres 9.X.x that meant 9.0.x --> 9.6.x

Don't have access to that version without re-booting; probably 9.5

In psql do:

select version();

Where are you running the pg_upgrade and what version of it are you
using?

pg_upgrade (PostgreSQL) 15.3

I specified -B /usr/bin

Your Postgres 15 is on one machine(OS version) and your Postgres 9.X is
on another machine(OS version), how are reaching the Postgres installs
on both?

Graeme Gemmill

--
Adrian Klaver
adrian.klaver@aklaver.com

On 2023-09-11 17:04:54 +0100, Graeme wrote:

Preparing to upgrade my small cluster from Mageia 8/Pg 9 to Mageia 9/Pg 15. I'm
at the point of running pg_upgrade but have received anerror message:

/mga8/usr/bin/postgres: error while loading shared libraries: libssl.so.1.1:
cannot open shared object file: No such file or directory
no data was returned by command ""/mga8/usr/bin/postgres" -V"

However:

[root@bach lib64]# cd /mga8/usr/lib64

I'm not familiar with the Mageia update process, but the paths look
strange, Is it normal that old binaries and libraries are moved into a
directory named after the old version (I assume "mga8" is short for
Mageia version 8") or is this something you have done?

In any case, /mga8/usr/lib64 would not normally be on the library
search path, Have you somehow told /mga8/usr/bin/postgres to look there?

hp

--
_ | Peter J. Holzer | Story must make more sense than reality.
|_|_) | |
| | | hjp@hjp.at | -- Charles Stross, "Creative writing
__/ | http://www.hjp.at/ | challenge!"

On 11/09/2023 17:04, Graeme wrote:

Preparing to upgrade my small cluster from Mageia 8/Pg 9 to Mageia
9/Pg 15. I'm at the point of running pg_upgrade but have received
anerror message:

/mga8/usr/bin/postgres: error while loading shared libraries:
libssl.so.1.1: cannot open shared object file: No such file or directory
no data was returned by command ""/mga8/usr/bin/postgres" -V"

However:

[root@bach lib64]# cd /mga8/usr/lib64
[root@bach lib64]# ls -l|grep libssl
-rwxr-xr-x  1 root root      426192 Jul  5 23:07 libssl3.so*
lrwxrwxrwx  1 root root          13 Jun  1 09:35 libssl.so ->
libssl.so.1.1*
-r-xr-xr-x  1 root root      442424 Feb 27  2021 libssl.so.1.0.0*
-rwxr-xr-x  1 root root      666496 Jun  1 09:36 libssl.so.1.1*

Can someone suggest my next move please?

Ta

Graeme Gemmill

Tom, Adrian, Ray: thanks for your comments. I see the problem now,
trying to gat a Mga8 module to link against Mga9 libraries. I suspecy a
carefully placed sym-link or two will sort the problem.

On 9/12/23 03:51, Graeme wrote:

On 11/09/2023 17:04, Graeme wrote:

Ta

Graeme Gemmill

Tom, Adrian, Ray: thanks for your comments. I see the problem now,
trying to gat a Mga8 module to link against Mga9 libraries. I suspecy a
carefully placed sym-link or two will sort the problem.

I'm thinking you would be better off doing a pg_dumpall of the old
cluster and psql <connection parameters> -f dump_file.sql on the new
cluster per:

https://www.postgresql.org/docs/current/app-pg-dumpall.html

--
Adrian Klaver
adrian.klaver@aklaver.com