pg.ddx.io pgsql-general@postgresql.org mailing list archive
help / color / mirror / Atom feedUpgrade problem
15+ messages / 8 participants
[nested] [flat]
* Upgrade problem
@ 2006-06-28 16:05 Nik <XLPizza@gmail.com>
0 siblings, 0 replies; 15+ messages in thread
From: Nik @ 2006-06-28 16:05 UTC (permalink / raw)
To: pgsql-general
I am trying to upgrade from 8.1.3 to 8.1.4 on Windows XP. I am a user
with admin rights and I am able to install programs, services and such.
I used the same account to install Postgres in the first place.
However, when I try to run the upgrade batch file, it goes through most
of the installation (file copying and such) and at the part where it is
supposed to install the Postgres service it gives me the following
error:
"Service 'PostgreSQL Database Server 8.1' (pgsql-8.1) could not be
installed. Verify that you have sufficient privileges to install system
services."
I logged in as Administrator and tried it again, and I got the same
error. What could be the issue?
Thanks.
^ permalink raw reply [nested|flat] 15+ messages in thread
* Upgrade problem
@ 2006-11-21 23:16 Bill Kurland <bill@panix.com>
0 siblings, 1 reply; 15+ messages in thread
From: Bill Kurland @ 2006-11-21 23:16 UTC (permalink / raw)
To: pgsql-general
I've just upgraded from 7.2 to 8.1.5 under AIX 4.3.
gcc 2.95.3
gmake 3.79.1
I ran into a build problem which I was able to resolve by adding adding
'LDFLAGS= -xlinker -bbigtoc' to the configure command line.
make check passes all 98 tests, but when I try to start postgresql I get:
LOG: could not translate service "5432" to address: Host not found
WARNING: could not create listen socket for "*"
FATAL: could not create any TCP/IP sockets
in the logfile.
I reread the INSTALL doc and sec 23.4 of the v8.1 manual and see no
mention of any config changes required for the newer release.
A google search didn't yield much except that it seems that the error
message is generated in src/backend/libpq/pqcomm.c. Can anyone tell what
I've done wrong?
Bill Kurland
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: Upgrade problem
@ 2006-11-22 03:44 Tom Lane <tgl@sss.pgh.pa.us>
parent: Bill Kurland <bill@panix.com>
0 siblings, 1 reply; 15+ messages in thread
From: Tom Lane @ 2006-11-22 03:44 UTC (permalink / raw)
To: Bill Kurland <bill@panix.com>; +Cc: pgsql-general
Bill Kurland <bill@panix.com> writes:
> I've just upgraded from 7.2 to 8.1.5 under AIX 4.3.
> make check passes all 98 tests, but when I try to start postgresql I get:
> LOG: could not translate service "5432" to address: Host not found
Hmm, this seems to be another one of those "AIX's getaddrinfo() is
broken" problems :-(. We patched around one problem last month:
http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/libpq/ip.c.diff?r1=1.32.2.1&r2=1.32...
I'm afraid that that patch does not fix your problem, but it would be
worth trying it before we dig any deeper.
regards, tom lane
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: Upgrade problem
@ 2006-11-27 05:27 Bill Kurland <bill@shakespeare-nyc.com>
parent: Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 15+ messages in thread
From: Bill Kurland @ 2006-11-27 05:27 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: pgsql-general
Tom:
Thanks for the reply. I've installed the patch and, as you predicted, it
had no effect.
I did a google search on AIX + getaddrinfo and found
> http://lists.samba.org/archive/rsync/2002-April/002063.html
In that context the author says that adding the port number in
etc/services solved his problem with getaddrinfo. So I tried that and,
lo, it has some effect, though I'm not sure it's 100% desirable. The log
entry is:
LOG: could not bind IPv6 socket: The type of socket is not supported in
this protocol family.
HINT: Is another postmaster already running on port 5432? If not, wait
a few seconds and retry.
LOG: database system was shut down at 2006-11-26 23:26:32 EST
LOG: checkpoint record is at 0/38D198
LOG: redo record is at 0/38D198; undo record is at 0/0; shutdown TRUE
LOG: next transaction ID: 565; next OID: 10793
LOG: next MultiXactId: 1; next MultiXactOffset: 0
LOG: database system is ready
LOG: transaction ID wrap limit is 2147484146, limited by database
"postgres"
but postmaster is running.
I've restored my database and a cursory look seems to show everything is
working as expected. Can you tell me what the log entries signify?
Thanks again.
Tom Lane wrote:
> Bill Kurland <bill@panix.com> writes:
>
>> I've just upgraded from 7.2 to 8.1.5 under AIX 4.3.
>> make check passes all 98 tests, but when I try to start postgresql I get:
>>
>
>
>> LOG: could not translate service "5432" to address: Host not found
>>
>
> Hmm, this seems to be another one of those "AIX's getaddrinfo() is
> broken" problems :-(. We patched around one problem last month:
> http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/libpq/ip.c.diff?r1=1.32.2.1&r2=1.32...
>
> I'm afraid that that patch does not fix your problem, but it would be
> worth trying it before we dig any deeper.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match
>
>
--
Bill Kurland
Shakespeare & Co.
138 Watts Street
New York, NY 10013
212-965-9683
212-965-9684 Fax
--
Can I now congratulate the same nation upon its freedom? Is it because liberty in the abstract may be classed amongst the blessings of mankind, that I am seriously to felicitate a madman, who has escaped from the protecting restraint and wholesome darkness of his cell, on his restoration to the enjoyment of light and liberty? Am I to congratulate a highwayman and murderer who has broke prison upon the recovery of his natural rights?
-Edmund Burke, "Reflections on the Revolution in France"
^ permalink raw reply [nested|flat] 15+ messages in thread
* Upgrade problem
@ 2023-09-11 16:04 Graeme <graeme@gemmill.name>
0 siblings, 4 replies; 15+ messages in thread
From: Graeme @ 2023-09-11 16:04 UTC (permalink / raw)
To: pgsql-general@lists.postgresql.org
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
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: Upgrade problem
@ 2023-09-11 16:10 Tom Lane <tgl@sss.pgh.pa.us>
parent: Graeme <graeme@gemmill.name>
3 siblings, 1 reply; 15+ messages in thread
From: Tom Lane @ 2023-09-11 16:10 UTC (permalink / raw)
To: Graeme <graeme@gemmill.name>; +Cc: pgsql-general@lists.postgresql.org
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
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: Upgrade problem
@ 2023-09-11 16:13 Adrian Klaver <adrian.klaver@aklaver.com>
parent: Graeme <graeme@gemmill.name>
3 siblings, 1 reply; 15+ messages in thread
From: Adrian Klaver @ 2023-09-11 16:13 UTC (permalink / raw)
To: Graeme <graeme@gemmill.name>; pgsql-general@lists.postgresql.org
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
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: Upgrade problem
@ 2023-09-11 16:22 Graeme <graeme@gemmill.name>
parent: Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 15+ messages in thread
From: Graeme @ 2023-09-11 16:22 UTC (permalink / raw)
To: pgsql-general@lists.postgresql.org
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
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: Upgrade problem
@ 2023-09-11 16:26 Tom Lane <tgl@sss.pgh.pa.us>
parent: Graeme <graeme@gemmill.name>
0 siblings, 0 replies; 15+ messages in thread
From: Tom Lane @ 2023-09-11 16:26 UTC (permalink / raw)
To: Graeme <graeme@gemmill.name>; +Cc: pgsql-general@lists.postgresql.org
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
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: Upgrade problem
@ 2023-09-11 16:33 Graeme <graeme@gemmill.name>
parent: Adrian Klaver <adrian.klaver@aklaver.com>
0 siblings, 2 replies; 15+ messages in thread
From: Graeme @ 2023-09-11 16:33 UTC (permalink / raw)
To: pgsql-general@lists.postgresql.org
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
>>
>> 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
>
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: Upgrade problem
@ 2023-09-11 16:36 Ray O'Donnell <ray@rodonnell.ie>
parent: Graeme <graeme@gemmill.name>
1 sibling, 0 replies; 15+ messages in thread
From: Ray O'Donnell @ 2023-09-11 16:36 UTC (permalink / raw)
To: Graeme <graeme@gemmill.name>; pgsql-general@lists.postgresql.org
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
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: Upgrade problem
@ 2023-09-11 16:50 Adrian Klaver <adrian.klaver@aklaver.com>
parent: Graeme <graeme@gemmill.name>
1 sibling, 0 replies; 15+ messages in thread
From: Adrian Klaver @ 2023-09-11 16:50 UTC (permalink / raw)
To: Graeme <graeme@gemmill.name>; pgsql-general@lists.postgresql.org
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
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: Upgrade problem
@ 2023-09-12 09:39 Peter J. Holzer <hjp-pgsql@hjp.at>
parent: Graeme <graeme@gemmill.name>
3 siblings, 0 replies; 15+ messages in thread
From: Peter J. Holzer @ 2023-09-12 09:39 UTC (permalink / raw)
To: pgsql-general@lists.postgresql.org
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!"
Attachments:
signature.asc (application/pgp-signature, 832B) download
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: Upgrade problem
@ 2023-09-12 10:51 Graeme <graeme@gemmill.name>
parent: Graeme <graeme@gemmill.name>
3 siblings, 1 reply; 15+ messages in thread
From: Graeme @ 2023-09-12 10:51 UTC (permalink / raw)
To: pgsql-general@lists.postgresql.org
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.
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: Upgrade problem
@ 2023-09-12 14:57 Adrian Klaver <adrian.klaver@aklaver.com>
parent: Graeme <graeme@gemmill.name>
0 siblings, 0 replies; 15+ messages in thread
From: Adrian Klaver @ 2023-09-12 14:57 UTC (permalink / raw)
To: Graeme <graeme@gemmill.name>; pgsql-general@lists.postgresql.org
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
^ permalink raw reply [nested|flat] 15+ messages in thread
end of thread, other threads:[~2023-09-12 14:57 UTC | newest]
Thread overview: 15+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2006-06-28 16:05 Upgrade problem Nik <XLPizza@gmail.com>
2006-11-21 23:16 Upgrade problem Bill Kurland <bill@panix.com>
2006-11-22 03:44 ` Tom Lane <tgl@sss.pgh.pa.us>
2006-11-27 05:27 ` Bill Kurland <bill@shakespeare-nyc.com>
2023-09-11 16:04 Upgrade problem Graeme <graeme@gemmill.name>
2023-09-11 16:10 ` Tom Lane <tgl@sss.pgh.pa.us>
2023-09-11 16:22 ` Graeme <graeme@gemmill.name>
2023-09-11 16:26 ` Tom Lane <tgl@sss.pgh.pa.us>
2023-09-11 16:13 ` Adrian Klaver <adrian.klaver@aklaver.com>
2023-09-11 16:33 ` Graeme <graeme@gemmill.name>
2023-09-11 16:36 ` Ray O'Donnell <ray@rodonnell.ie>
2023-09-11 16:50 ` Adrian Klaver <adrian.klaver@aklaver.com>
2023-09-12 09:39 ` Peter J. Holzer <hjp-pgsql@hjp.at>
2023-09-12 10:51 ` Graeme <graeme@gemmill.name>
2023-09-12 14:57 ` Adrian Klaver <adrian.klaver@aklaver.com>
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