pg_upgrade help

Started by Akshay Ballarpurealmost 8 years ago14 messagesgeneral

akshay.ballarpure@tcs.com

almost 8 years ago

Hi all,
I need help on pg_upgrade from 8.4 to 9.4 version. Appreciate urgent
response.
Installed both version and stopped it. Do i need to run both version or
only one 8.4 or 9.4 . Both should run on 50432 ?

-bash-4.2$ id
uid=26(postgres) gid=26(postgres) groups=26(postgres)
context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023

-bash-4.2$ export OLDCLUSTER=/var/ericsson/esm-data/postgresql-data --
8.4 data
-bash-4.2$ export NEWCLUSTER=/var/ericsson/esm-data/postgresql-data-9.4
-- 9.4 data

-bash-4.2$ /opt/rh/rh-postgresql94/root/usr/bin/pg_upgrade
--old-bindir=/usr/bin --new-bindir=/opt/rh/rh-postgresql94/root/usr/bin
--old-datadir=$OLDCLUSTER --new-datadir=$NEWCLUSTER

connection to database failed: could not connect to server: No such file
or directory
Is the server running locally and accepting
connections on Unix domain socket
"/var/run/postgresql/.s.PGSQL.50432"?

could not connect to old postmaster started with the command:
"/usr/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D
"/var/ericsson/esm-data/postgresql-data" -o "-p 50432 -c autovacuum=off -c
autovacuum_freeze_max_age=2000000000 -c listen_addresses='' -c
unix_socket_permissions=0700" start
Failure, exiting

With Best Regards
Akshay
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you

Fabio Pardi

f.pardi@portavita.eu

almost 8 years ago

In reply to: Akshay Ballarpure (#1)

Re: pg_upgrade help

Hi,

please avoid crossposting to multiple mailing lists.

You need to run both versions of the database, the old and the new.

They need to run on different ports (note that it is impossible to run 2
different processes on the same port, that's not a postgresql thing)

Show quoted text

On 04/18/2018 09:30 AM, Akshay Ballarpure wrote:

Hi all,
I need help on pg_upgrade from 8.4 to 9.4 version. Appreciate urgent
response.
Installed both version and stopped it. Do i need to run both version or
only one 8.4 or 9.4 . Both should run on 50432 ?

-bash-4.2$ id
uid=26(postgres) gid=26(postgres) groups=26(postgres)
context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023

-bash-4.2$ export OLDCLUSTER=/var/ericsson/esm-data/postgresql-data ï¿½ ï¿½
ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½-- 8.4 data
-bash-4.2$ export NEWCLUSTER=/var/ericsson/esm-data/postgresql-data-9.4
ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ -- 9.4 data

-bash-4.2$ /opt/rh/rh-postgresql94/root/usr/bin/pg_upgrade
--old-bindir=/usr/bin --new-bindir=/opt/rh/rh-postgresql94/root/usr/bin
--old-datadir=$OLDCLUSTER --new-datadir=$NEWCLUSTER

*connection to database failed: could not connect to server: No such
file or directory*
ï¿½ ï¿½ ï¿½ ï¿½ Is the server running locally and accepting
ï¿½ ï¿½ ï¿½ ï¿½ connections on Unix domain socket
"/var/run/postgresql/.s.PGSQL.50432"?

could not connect to old postmaster started with the command:
"/usr/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D
"/var/ericsson/esm-data/postgresql-data" -o "-p 50432 -c autovacuum=off
-c autovacuum_freeze_max_age=2000000000 ï¿½-c listen_addresses='' -c
unix_socket_permissions=0700" start
Failure, exiting

With Best Regards
Akshay

=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you

Akshay Ballarpure

akshay.ballarpure@tcs.com

almost 8 years ago

In reply to: Fabio Pardi (#2)

Re: pg_upgrade help

Thanks Fabio for instant reply.

I now started 8.4 with 50432 and 9.4 with default port but still its
failing ...Can you please suggest what is wrong ?

-bash-4.2$ /opt/rh/rh-postgresql94/root/usr/bin/pg_upgrade
--old-bindir=/usr/bin --new-bindir=/opt/rh/rh-postgresql94/root/usr/bin
--old-datadir=$OLDCLUSTER --new-datadir=$NEWCLUSTER

*failure*
Consult the last few lines of "pg_upgrade_server.log" for
the probable cause of the failure.

There seems to be a postmaster servicing the old cluster.
Please shutdown that postmaster and try again.
Failure, exiting
-bash-4.2$ ps -eaf | grep postgres
root 8646 9365 0 08:07 pts/1 00:00:00 su - postgres
postgres 8647 8646 0 08:07 pts/1 00:00:00 -bash
postgres 9778 1 0 09:17 ? 00:00:00 /usr/bin/postgres -p 50432
-D /var/ericsson/esm-data/postgresql-data/
postgres 9779 9778 0 09:17 ? 00:00:00 postgres: logger process
postgres 9781 9778 0 09:17 ? 00:00:00 postgres: writer process
postgres 9782 9778 0 09:17 ? 00:00:00 postgres: wal writer
process
postgres 9783 9778 0 09:17 ? 00:00:00 postgres: autovacuum
launcher process
postgres 9784 9778 0 09:17 ? 00:00:00 postgres: stats collector
process
postgres 9900 1 0 09:20 ? 00:00:00
/opt/rh/rh-postgresql94/root/usr/bin/postgres -D
/var/ericsson/esm-data/postgresql-data-9.4/
postgres 9901 9900 0 09:20 ? 00:00:00 postgres: logger process
postgres 9903 9900 0 09:20 ? 00:00:00 postgres: checkpointer
process
postgres 9904 9900 0 09:20 ? 00:00:00 postgres: writer process
postgres 9905 9900 0 09:20 ? 00:00:00 postgres: wal writer
process
postgres 9906 9900 0 09:20 ? 00:00:00 postgres: autovacuum
launcher process
postgres 9907 9900 0 09:20 ? 00:00:00 postgres: stats collector
process
postgres 9926 8647 0 09:21 pts/1 00:00:00 ps -eaf
postgres 9927 8647 0 09:21 pts/1 00:00:00 grep --color=auto postgres

-bash-4.2$ netstat -antp | grep 50432
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 127.0.0.1:50432 0.0.0.0:* LISTEN
9778/postgres
tcp6 0 0 ::1:50432 :::* LISTEN
9778/postgres
-bash-4.2$ netstat -antp | grep 5432
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 127.0.0.1:5432 0.0.0.0:* LISTEN
9900/postgres
tcp6 0 0 ::1:5432 :::* LISTEN
9900/postgres

-----------------------------------------------------------------
pg_upgrade run on Wed Apr 18 09:24:47 2018
-----------------------------------------------------------------

command: "/usr/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D
"/var/ericsson/esm-data/postgresql-data" -o "-p 50432 -c autovacuum=off -c
autovacuum_freeze_max_age=2000000000 -c listen_addresses='' -c
unix_socket_permissions=0700" start >> "pg_upgrade_server.log" 2>&1
pg_ctl: another server might be running; trying to start server anyway
FATAL: lock file "postmaster.pid" already exists
HINT: Is another postmaster (PID 9778) running in data directory
"/var/ericsson/esm-data/postgresql-data"?
pg_ctl: could not start server
Examine the log output.

[root@ms-esmon /]# cat
./var/ericsson/esm-data/postgresql-data-9.4/postmaster.pid
9900
/var/ericsson/esm-data/postgresql-data-9.4
1524039630
5432
/var/run/postgresql
localhost
5432001 2031616

[root@ms-esmon /]# cat
./var/ericsson/esm-data/postgresql-data/postmaster.pid
9778
/var/ericsson/esm-data/postgresql-data
50432001 1998850

With Best Regards
Akshay

From: Fabio Pardi <f.pardi@portavita.eu>
To: Akshay Ballarpure <akshay.ballarpure@tcs.com>,
pgsql-general@lists.postgresql.org
Date: 04/18/2018 01:06 PM
Subject: Re: pg_upgrade help

Hi,

please avoid crossposting to multiple mailing lists.

You need to run both versions of the database, the old and the new.

They need to run on different ports (note that it is impossible to run 2
different processes on the same port, that's not a postgresql thing)

Show quoted text

On 04/18/2018 09:30 AM, Akshay Ballarpure wrote:

Hi all,
I need help on pg_upgrade from 8.4 to 9.4 version. Appreciate urgent
response.
Installed both version and stopped it. Do i need to run both version or
only one 8.4 or 9.4 . Both should run on 50432 ?

-bash-4.2$ id
uid=26(postgres) gid=26(postgres) groups=26(postgres)
context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023

-bash-4.2$ export OLDCLUSTER=/var/ericsson/esm-data/postgresql-data
-- 8.4 data
-bash-4.2$ export NEWCLUSTER=/var/ericsson/esm-data/postgresql-data-9.4
-- 9.4 data

-bash-4.2$ /opt/rh/rh-postgresql94/root/usr/bin/pg_upgrade
--old-bindir=/usr/bin --new-bindir=/opt/rh/rh-postgresql94/root/usr/bin
--old-datadir=$OLDCLUSTER --new-datadir=$NEWCLUSTER

*connection to database failed: could not connect to server: No such
file or directory*
Is the server running locally and accepting
connections on Unix domain socket
"/var/run/postgresql/.s.PGSQL.50432"?

could not connect to old postmaster started with the command:
"/usr/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D
"/var/ericsson/esm-data/postgresql-data" -o "-p 50432 -c autovacuum=off
-c autovacuum_freeze_max_age=2000000000 -c listen_addresses='' -c
unix_socket_permissions=0700" start
Failure, exiting

With Best Regards
Akshay

=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you

Sergei Kornilov

sk@zsrv.org

almost 8 years ago

In reply to: Akshay Ballarpure (#1)

Re: pg_upgrade help

Hi
Both version should be correctly stopped. pg_upgrade started clusters itself.
Please check pg_upgrade_server.log file in directory where pg_upgrade was run.
Also where is postgresql.conf? In PGDATA? Otherwise you need tell pg_upgrade correct path, for example with options '-o " -c config_file=/etc/postgresql/8.4/main/postgresql.conf" -O " -c config_file=/etc/postgresql/9.4/main/postgresql.conf"'

regards, Sergei

Fabio Pardi

f.pardi@portavita.eu

almost 8 years ago

In reply to: Akshay Ballarpure (#3)

Re: pg_upgrade help

Hi,

i was too fast in reply (and perhaps i should drink my morning coffee
before replying), I will try to be more detailed:

both servers should be able to run at the moment you run pg_upgrade,
that means the 2 servers should have been correctly stopped in advance,
should have their configuration files, and new cluster initialized too.

Then, as Sergei highlights here below, pg_upgrade will take care of the
upgrade process, starting the servers.

Here there is a step by step guide, i considered my best ally when it
was time to upgrade:

https://www.postgresql.org/docs/9.4/static/pgupgrade.html

note point 7:

'stop both servers'

About the port the servers will run on, at point 9 there is some
clarification:

' pg_upgrade defaults to running servers on port 50432 to avoid
unintended client connections. You can use the same port number for both
clusters when doing an upgrade because the old and new clusters will not
be running at the same time. However, when checking an old running
server, the old and new port numbers must be different.'

Hope it helps,

Fabio Pardi

Show quoted text

On 04/18/2018 10:34 AM, Akshay Ballarpure wrote:

Thanks Fabio for instant reply.

I now started 8.4 with 50432 and 9.4 with default port but still its
failing ...Can you please suggest what is wrong ?

-bash-4.2$ /opt/rh/rh-postgresql94/root/usr/bin/pg_upgrade
--old-bindir=/usr/bin --new-bindir=/opt/rh/rh-postgresql94/root/usr/bin
--old-datadir=$OLDCLUSTER --new-datadir=$NEWCLUSTER

*failure*
Consult the last few lines of "pg_upgrade_server.log" for
the probable cause of the failure.

There seems to be a postmaster servicing the old cluster.
Please shutdown that postmaster and try again.
Failure, exiting
-bash-4.2$ ps -eaf | grep postgres
root ï¿½ ï¿½ ï¿½8646 ï¿½9365 ï¿½0 08:07 pts/1 ï¿½ ï¿½00:00:00 su - postgres
postgres ï¿½8647 ï¿½8646 ï¿½0 08:07 pts/1 ï¿½ ï¿½00:00:00 -bash
postgres ï¿½9778 ï¿½ ï¿½ 1 ï¿½0 09:17 ? ï¿½ ï¿½ ï¿½ ï¿½00:00:00 /usr/bin/postgres -p
50432 -D /var/ericsson/esm-data/postgresql-data/
postgres ï¿½9779 ï¿½9778 ï¿½0 09:17 ? ï¿½ ï¿½ ï¿½ ï¿½00:00:00 postgres: logger process
postgres ï¿½9781 ï¿½9778 ï¿½0 09:17 ? ï¿½ ï¿½ ï¿½ ï¿½00:00:00 postgres: writer process
postgres ï¿½9782 ï¿½9778 ï¿½0 09:17 ? ï¿½ ï¿½ ï¿½ ï¿½00:00:00 postgres: wal writer
process
postgres ï¿½9783 ï¿½9778 ï¿½0 09:17 ? ï¿½ ï¿½ ï¿½ ï¿½00:00:00 postgres: autovacuum
launcher process
postgres ï¿½9784 ï¿½9778 ï¿½0 09:17 ? ï¿½ ï¿½ ï¿½ ï¿½00:00:00 postgres: stats
collector process
postgres ï¿½9900 ï¿½ ï¿½ 1 ï¿½0 09:20 ? ï¿½ ï¿½ ï¿½ ï¿½00:00:00
/opt/rh/rh-postgresql94/root/usr/bin/postgres -D
/var/ericsson/esm-data/postgresql-data-9.4/
postgres ï¿½9901 ï¿½9900 ï¿½0 09:20 ? ï¿½ ï¿½ ï¿½ ï¿½00:00:00 postgres: logger process
postgres ï¿½9903 ï¿½9900 ï¿½0 09:20 ? ï¿½ ï¿½ ï¿½ ï¿½00:00:00 postgres: checkpointer
process
postgres ï¿½9904 ï¿½9900 ï¿½0 09:20 ? ï¿½ ï¿½ ï¿½ ï¿½00:00:00 postgres: writer process
postgres ï¿½9905 ï¿½9900 ï¿½0 09:20 ? ï¿½ ï¿½ ï¿½ ï¿½00:00:00 postgres: wal writer
process
postgres ï¿½9906 ï¿½9900 ï¿½0 09:20 ? ï¿½ ï¿½ ï¿½ ï¿½00:00:00 postgres: autovacuum
launcher process
postgres ï¿½9907 ï¿½9900 ï¿½0 09:20 ? ï¿½ ï¿½ ï¿½ ï¿½00:00:00 postgres: stats
collector process
postgres ï¿½9926 ï¿½8647 ï¿½0 09:21 pts/1 ï¿½ ï¿½00:00:00 ps -eaf
postgres ï¿½9927 ï¿½8647 ï¿½0 09:21 pts/1 ï¿½ ï¿½00:00:00 grep --color=auto postgres

-bash-4.2$ netstat -antp | grep 50432
(Not all processes could be identified, non-owned process info
ï¿½will not be shown, you would have to be root to see it all.)
tcp ï¿½ ï¿½ ï¿½ ï¿½0 ï¿½ ï¿½ ï¿½0 127.0.0.1:50432 ï¿½ ï¿½ ï¿½ ï¿½ 0.0.0.0:* ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½
LISTEN ï¿½ ï¿½ ï¿½9778/postgres
tcp6 ï¿½ ï¿½ ï¿½ 0 ï¿½ ï¿½ ï¿½0 ::1:50432 ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ :::* ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½
ï¿½LISTEN ï¿½ ï¿½ ï¿½9778/postgres
-bash-4.2$ netstat -antp | grep 5432
(Not all processes could be identified, non-owned process info
ï¿½will not be shown, you would have to be root to see it all.)
tcp ï¿½ ï¿½ ï¿½ ï¿½0 ï¿½ ï¿½ ï¿½0 127.0.0.1:5432 ï¿½ ï¿½ ï¿½ ï¿½ ï¿½0.0.0.0:* ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½
LISTEN ï¿½ ï¿½ ï¿½9900/postgres
tcp6 ï¿½ ï¿½ ï¿½ 0 ï¿½ ï¿½ ï¿½0 ::1:5432 ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½:::* ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½
ï¿½LISTEN ï¿½ ï¿½ ï¿½9900/postgres

-----------------------------------------------------------------
ï¿½ pg_upgrade run on Wed Apr 18 09:24:47 2018
-----------------------------------------------------------------

command: "/usr/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D
"/var/ericsson/esm-data/postgresql-data" -o "-p 50432 -c autovacuum=off
-c autovacuum_freeze_max_age=2000000000 ï¿½-c listen_addresses='' -c
unix_socket_permissions=0700" start >> "pg_upgrade_server.log" 2>&1
pg_ctl: another server might be running; trying to start server anyway
FATAL: ï¿½lock file "postmaster.pid" already exists
HINT: ï¿½Is another postmaster (PID 9778) running in data directory
"/var/ericsson/esm-data/postgresql-data"?
pg_ctl: could not start server
Examine the log output.

[root@ms-esmon /]# cat
./var/ericsson/esm-data/postgresql-data-9.4/postmaster.pid
9900
/var/ericsson/esm-data/postgresql-data-9.4
1524039630
5432
/var/run/postgresql
localhost
ï¿½ 5432001 ï¿½ 2031616
ï¿½
ï¿½
[root@ms-esmon /]# cat
./var/ericsson/esm-data/postgresql-data/postmaster.pid
9778
/var/ericsson/esm-data/postgresql-data
ï¿½50432001 ï¿½ 1998850

With Best Regards
Akshay

From: ï¿½ ï¿½ ï¿½ ï¿½Fabio Pardi <f.pardi@portavita.eu>
To: ï¿½ ï¿½ ï¿½ ï¿½Akshay Ballarpure <akshay.ballarpure@tcs.com>,
pgsql-general@lists.postgresql.org
Date: ï¿½ ï¿½ ï¿½ ï¿½04/18/2018 01:06 PM
Subject: ï¿½ ï¿½ ï¿½ ï¿½Re: pg_upgrade help
------------------------------------------------------------------------

Hi,

please avoid crossposting to multiple mailing lists.

You need to run both versions of the database, the old and the new.

They need to run on different ports (note that it is impossible to run 2
different processes on the same port, that's not a postgresql thing)

On 04/18/2018 09:30 AM, Akshay Ballarpure wrote:

Hi all,
I need help on pg_upgrade from 8.4 to 9.4 version. Appreciate urgent
response.
Installed both version and stopped it. Do i need to run both version or
only one 8.4 or 9.4 . Both should run on 50432 ?

-bash-4.2$ id
uid=26(postgres) gid=26(postgres) groups=26(postgres)
context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023

-bash-4.2$ export OLDCLUSTER=/var/ericsson/esm-data/postgresql-data ï¿½ ï¿½
ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½-- 8.4 data
-bash-4.2$ export NEWCLUSTER=/var/ericsson/esm-data/postgresql-data-9.4
ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ -- 9.4 data

-bash-4.2$ /opt/rh/rh-postgresql94/root/usr/bin/pg_upgrade
--old-bindir=/usr/bin --new-bindir=/opt/rh/rh-postgresql94/root/usr/bin
--old-datadir=$OLDCLUSTER --new-datadir=$NEWCLUSTER

*connection to database failed: could not connect to server: No such
file or directory*
ï¿½ ï¿½ ï¿½ ï¿½ Is the server running locally and accepting
ï¿½ ï¿½ ï¿½ ï¿½ connections on Unix domain socket
"/var/run/postgresql/.s.PGSQL.50432"?

could not connect to old postmaster started with the command:
"/usr/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D
"/var/ericsson/esm-data/postgresql-data" -o "-p 50432 -c autovacuum=off
-c autovacuum_freeze_max_age=2000000000 ï¿½-c listen_addresses='' -c
unix_socket_permissions=0700" start
Failure, exiting

With Best Regards
Akshay

=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you

Akshay Ballarpure

akshay.ballarpure@tcs.com

almost 8 years ago

In reply to: Fabio Pardi (#5)

Re: pg_upgrade help

Hi Fabio,
sorry to bother you again, its still failing with stopping both server
(8.4 and 9.4)

-bash-4.2$ /opt/rh/rh-postgresql94/root/usr/bin/pg_upgrade
--old-bindir=/usr/bin --new-bindir=/opt/rh/rh-postgresql94/root/usr/bin
--old-datadir=$OLDCLUSTER --new-datadir=$NEWCLUSTER

With Best Regards
Akshay
Ericsson OSS MON
Tata Consultancy Services
Mailto: akshay.ballarpure@tcs.com
Website: http://www.tcs.com
____________________________________________
Experience certainty. IT Services
Business Solutions
Consulting
____________________________________________

From: Fabio Pardi <f.pardi@portavita.eu>
To: Akshay Ballarpure <akshay.ballarpure@tcs.com>,
pgsql-general@lists.postgresql.org
Date: 04/18/2018 02:35 PM
Subject: Re: pg_upgrade help

Hi,

i was too fast in reply (and perhaps i should drink my morning coffee
before replying), I will try to be more detailed:

Then, as Sergei highlights here below, pg_upgrade will take care of the
upgrade process, starting the servers.

Here there is a step by step guide, i considered my best ally when it
was time to upgrade:

https://www.postgresql.org/docs/9.4/static/pgupgrade.html

note point 7:

'stop both servers'

About the port the servers will run on, at point 9 there is some
clarification:

Hope it helps,

Fabio Pardi

On 04/18/2018 10:34 AM, Akshay Ballarpure wrote:

Thanks Fabio for instant reply.

I now started 8.4 with 50432 and 9.4 with default port but still its
failing ...Can you please suggest what is wrong ?

-bash-4.2$ /opt/rh/rh-postgresql94/root/usr/bin/pg_upgrade
--old-bindir=/usr/bin --new-bindir=/opt/rh/rh-postgresql94/root/usr/bin
--old-datadir=$OLDCLUSTER --new-datadir=$NEWCLUSTER

*failure*
Consult the last few lines of "pg_upgrade_server.log" for
the probable cause of the failure.

There seems to be a postmaster servicing the old cluster.
Please shutdown that postmaster and try again.
Failure, exiting
-bash-4.2$ ps -eaf | grep postgres
root 8646 9365 0 08:07 pts/1 00:00:00 su - postgres
postgres 8647 8646 0 08:07 pts/1 00:00:00 -bash
postgres 9778 1 0 09:17 ? 00:00:00 /usr/bin/postgres -p
50432 -D /var/ericsson/esm-data/postgresql-data/
postgres 9779 9778 0 09:17 ? 00:00:00 postgres: logger process
postgres 9781 9778 0 09:17 ? 00:00:00 postgres: writer process
postgres 9782 9778 0 09:17 ? 00:00:00 postgres: wal writer
process
postgres 9783 9778 0 09:17 ? 00:00:00 postgres: autovacuum
launcher process
postgres 9784 9778 0 09:17 ? 00:00:00 postgres: stats
collector process
postgres 9900 1 0 09:20 ? 00:00:00
/opt/rh/rh-postgresql94/root/usr/bin/postgres -D
/var/ericsson/esm-data/postgresql-data-9.4/
postgres 9901 9900 0 09:20 ? 00:00:00 postgres: logger process
postgres 9903 9900 0 09:20 ? 00:00:00 postgres: checkpointer
process
postgres 9904 9900 0 09:20 ? 00:00:00 postgres: writer process
postgres 9905 9900 0 09:20 ? 00:00:00 postgres: wal writer
process
postgres 9906 9900 0 09:20 ? 00:00:00 postgres: autovacuum
launcher process
postgres 9907 9900 0 09:20 ? 00:00:00 postgres: stats
collector process
postgres 9926 8647 0 09:21 pts/1 00:00:00 ps -eaf
postgres 9927 8647 0 09:21 pts/1 00:00:00 grep --color=auto

postgres

Show quoted text

-bash-4.2$ netstat -antp | grep 50432
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 127.0.0.1:50432 0.0.0.0:*
LISTEN 9778/postgres
tcp6 0 0 ::1:50432 :::*
LISTEN 9778/postgres
-bash-4.2$ netstat -antp | grep 5432
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 127.0.0.1:5432 0.0.0.0:*
LISTEN 9900/postgres
tcp6 0 0 ::1:5432 :::*
LISTEN 9900/postgres

-----------------------------------------------------------------
pg_upgrade run on Wed Apr 18 09:24:47 2018
-----------------------------------------------------------------

command: "/usr/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D
"/var/ericsson/esm-data/postgresql-data" -o "-p 50432 -c autovacuum=off
-c autovacuum_freeze_max_age=2000000000 -c listen_addresses='' -c
unix_socket_permissions=0700" start >> "pg_upgrade_server.log" 2>&1
pg_ctl: another server might be running; trying to start server anyway
FATAL: lock file "postmaster.pid" already exists
HINT: Is another postmaster (PID 9778) running in data directory
"/var/ericsson/esm-data/postgresql-data"?
pg_ctl: could not start server
Examine the log output.

[root@ms-esmon /]# cat
./var/ericsson/esm-data/postgresql-data-9.4/postmaster.pid
9900
/var/ericsson/esm-data/postgresql-data-9.4
1524039630
5432
/var/run/postgresql
localhost
5432001 2031616

[root@ms-esmon /]# cat
./var/ericsson/esm-data/postgresql-data/postmaster.pid
9778
/var/ericsson/esm-data/postgresql-data
50432001 1998850

With Best Regards
Akshay

From: Fabio Pardi <f.pardi@portavita.eu>
To: Akshay Ballarpure <akshay.ballarpure@tcs.com>,
pgsql-general@lists.postgresql.org
Date: 04/18/2018 01:06 PM
Subject: Re: pg_upgrade help
------------------------------------------------------------------------

Hi,

please avoid crossposting to multiple mailing lists.

You need to run both versions of the database, the old and the new.

They need to run on different ports (note that it is impossible to run 2
different processes on the same port, that's not a postgresql thing)

On 04/18/2018 09:30 AM, Akshay Ballarpure wrote:

Hi all,
I need help on pg_upgrade from 8.4 to 9.4 version. Appreciate urgent
response.
Installed both version and stopped it. Do i need to run both version or
only one 8.4 or 9.4 . Both should run on 50432 ?

-bash-4.2$ id
uid=26(postgres) gid=26(postgres) groups=26(postgres)
context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023

-bash-4.2$ export OLDCLUSTER=/var/ericsson/esm-data/postgresql-data
-- 8.4 data
-bash-4.2$ export NEWCLUSTER=/var/ericsson/esm-data/postgresql-data-9.4
-- 9.4 data

-bash-4.2$ /opt/rh/rh-postgresql94/root/usr/bin/pg_upgrade
--old-bindir=/usr/bin --new-bindir=/opt/rh/rh-postgresql94/root/usr/bin
--old-datadir=$OLDCLUSTER --new-datadir=$NEWCLUSTER

*connection to database failed: could not connect to server: No such
file or directory*
Is the server running locally and accepting
connections on Unix domain socket
"/var/run/postgresql/.s.PGSQL.50432"?

could not connect to old postmaster started with the command:
"/usr/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D
"/var/ericsson/esm-data/postgresql-data" -o "-p 50432 -c autovacuum=off
-c autovacuum_freeze_max_age=2000000000 -c listen_addresses='' -c
unix_socket_permissions=0700" start
Failure, exiting

With Best Regards
Akshay

=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you

Fabio Pardi

f.pardi@portavita.eu

almost 8 years ago

In reply to: Akshay Ballarpure (#6)

Re: pg_upgrade help

did you run initdb on the new db?

what happens if you manually start the new db?

/opt/rh/rh-postgresql94/root/usr/bin/pg_ctl start -o "-p 50432 -c
listen_addresses='' -c unix_socket_permissions=0700" -D $NEWCLUSTER

after starting it, can you connect to it using psql?

psql -p 50432 -h /var/run/postgresql -U your_user _db_

regards,

fabio pardi

Show quoted text

On 04/18/2018 02:02 PM, Akshay Ballarpure wrote:

Hi Fabio,
sorry to bother you again, its still failing with stopping both server
(8.4 and 9.4)

-bash-4.2$ /opt/rh/rh-postgresql94/root/usr/bin/pg_upgrade
--old-bindir=/usr/bin --new-bindir=/opt/rh/rh-postgresql94/root/usr/bin
--old-datadir=$OLDCLUSTER --new-datadir=$NEWCLUSTER

connection to database failed: could not connect to server: No such file
or directory
ï¿½ ï¿½ ï¿½ ï¿½ Is the server running locally and accepting
ï¿½ ï¿½ ï¿½ ï¿½ connections on Unix domain socket
"/var/run/postgresql/.s.PGSQL.50432"?

could not connect to old postmaster started with the command:
"/usr/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D
"/var/ericsson/esm-data/postgresql-data" -o "-p 50432 -c autovacuum=off
-c autovacuum_freeze_max_age=2000000000 ï¿½-c listen_addresses='' -c
unix_socket_permissions=0700" start
Failure, exiting

With Best Regards
Akshay
Ericsson OSS MON
Tata Consultancy Services
Mailto: akshay.ballarpure@tcs.com
Website: http://www.tcs.com <http://www.tcs.com/>
____________________________________________
Experience certainty. ï¿½ ï¿½ ï¿½ ï¿½IT Services
ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½Business Solutions
ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½Consulting
____________________________________________

From: ï¿½ ï¿½ ï¿½ ï¿½Fabio Pardi <f.pardi@portavita.eu>
To: ï¿½ ï¿½ ï¿½ ï¿½Akshay Ballarpure <akshay.ballarpure@tcs.com>,
pgsql-general@lists.postgresql.org
Date: ï¿½ ï¿½ ï¿½ ï¿½04/18/2018 02:35 PM
Subject: ï¿½ ï¿½ ï¿½ ï¿½Re: pg_upgrade help
------------------------------------------------------------------------

Hi,

i was too fast in reply (and perhaps i should drink my morning coffee
before replying), I will try to be more detailed:

both servers should be able to run at the moment you run pg_upgrade,
that means the 2 servers should have been correctly stopped in advance,
should have their configuration files, and new cluster initialized too.

Then, as Sergei highlights here below, pg_upgrade will take care of the
upgrade process, starting the servers.

Here there is a step by step guide, i considered my best ally when it
was time to upgrade:

https://www.postgresql.org/docs/9.4/static/pgupgrade.html

note point 7:

'stop both servers'

About the port the servers will run on, at point 9 there is some
clarification:

' pg_upgrade defaults to running servers on port 50432 to avoid
unintended client connections. You can use the same port number for both
clusters when doing an upgrade because the old and new clusters will not
be running at the same time. However, when checking an old running
server, the old and new port numbers must be different.'

Hope it helps,

Fabio Pardi

On 04/18/2018 10:34 AM, Akshay Ballarpure wrote:

Thanks Fabio for instant reply.

I now started 8.4 with 50432 and 9.4 with default port but still its
failing ...Can you please suggest what is wrong ?

-bash-4.2$ /opt/rh/rh-postgresql94/root/usr/bin/pg_upgrade
--old-bindir=/usr/bin --new-bindir=/opt/rh/rh-postgresql94/root/usr/bin
--old-datadir=$OLDCLUSTER --new-datadir=$NEWCLUSTER

*failure*
Consult the last few lines of "pg_upgrade_server.log" for
the probable cause of the failure.

There seems to be a postmaster servicing the old cluster.
Please shutdown that postmaster and try again.
Failure, exiting
-bash-4.2$ ps -eaf | grep postgres
root ï¿½ ï¿½ ï¿½8646 ï¿½9365 ï¿½0 08:07 pts/1 ï¿½ ï¿½00:00:00 su - postgres
postgres ï¿½8647 ï¿½8646 ï¿½0 08:07 pts/1 ï¿½ ï¿½00:00:00 -bash
postgres ï¿½9778 ï¿½ ï¿½ 1 ï¿½0 09:17 ? ï¿½ ï¿½ ï¿½ ï¿½00:00:00 /usr/bin/postgres -p
50432 -D /var/ericsson/esm-data/postgresql-data/
postgres ï¿½9779 ï¿½9778 ï¿½0 09:17 ? ï¿½ ï¿½ ï¿½ ï¿½00:00:00 postgres: logger process
postgres ï¿½9781 ï¿½9778 ï¿½0 09:17 ? ï¿½ ï¿½ ï¿½ ï¿½00:00:00 postgres: writer process
postgres ï¿½9782 ï¿½9778 ï¿½0 09:17 ? ï¿½ ï¿½ ï¿½ ï¿½00:00:00 postgres: wal writer
process
postgres ï¿½9783 ï¿½9778 ï¿½0 09:17 ? ï¿½ ï¿½ ï¿½ ï¿½00:00:00 postgres: autovacuum
launcher process
postgres ï¿½9784 ï¿½9778 ï¿½0 09:17 ? ï¿½ ï¿½ ï¿½ ï¿½00:00:00 postgres: stats
collector process
postgres ï¿½9900 ï¿½ ï¿½ 1 ï¿½0 09:20 ? ï¿½ ï¿½ ï¿½ ï¿½00:00:00
/opt/rh/rh-postgresql94/root/usr/bin/postgres -D
/var/ericsson/esm-data/postgresql-data-9.4/
postgres ï¿½9901 ï¿½9900 ï¿½0 09:20 ? ï¿½ ï¿½ ï¿½ ï¿½00:00:00 postgres: logger process
postgres ï¿½9903 ï¿½9900 ï¿½0 09:20 ? ï¿½ ï¿½ ï¿½ ï¿½00:00:00 postgres: checkpointer
process
postgres ï¿½9904 ï¿½9900 ï¿½0 09:20 ? ï¿½ ï¿½ ï¿½ ï¿½00:00:00 postgres: writer process
postgres ï¿½9905 ï¿½9900 ï¿½0 09:20 ? ï¿½ ï¿½ ï¿½ ï¿½00:00:00 postgres: wal writer
process
postgres ï¿½9906 ï¿½9900 ï¿½0 09:20 ? ï¿½ ï¿½ ï¿½ ï¿½00:00:00 postgres: autovacuum
launcher process
postgres ï¿½9907 ï¿½9900 ï¿½0 09:20 ? ï¿½ ï¿½ ï¿½ ï¿½00:00:00 postgres: stats
collector process
postgres ï¿½9926 ï¿½8647 ï¿½0 09:21 pts/1 ï¿½ ï¿½00:00:00 ps -eaf
postgres ï¿½9927 ï¿½8647 ï¿½0 09:21 pts/1 ï¿½ ï¿½00:00:00 grep --color=auto postgres

-bash-4.2$ netstat -antp | grep 50432
(Not all processes could be identified, non-owned process info
ï¿½will not be shown, you would have to be root to see it all.)
tcp ï¿½ ï¿½ ï¿½ ï¿½0 ï¿½ ï¿½ ï¿½0 127.0.0.1:50432 ï¿½ ï¿½ ï¿½ ï¿½ 0.0.0.0:* ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½
LISTEN ï¿½ ï¿½ ï¿½9778/postgres
tcp6 ï¿½ ï¿½ ï¿½ 0 ï¿½ ï¿½ ï¿½0 ::1:50432 ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ :::* ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½
ï¿½LISTEN ï¿½ ï¿½ ï¿½9778/postgres
-bash-4.2$ netstat -antp | grep 5432
(Not all processes could be identified, non-owned process info
ï¿½will not be shown, you would have to be root to see it all.)
tcp ï¿½ ï¿½ ï¿½ ï¿½0 ï¿½ ï¿½ ï¿½0 127.0.0.1:5432 ï¿½ ï¿½ ï¿½ ï¿½ ï¿½0.0.0.0:* ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½
LISTEN ï¿½ ï¿½ ï¿½9900/postgres
tcp6 ï¿½ ï¿½ ï¿½ 0 ï¿½ ï¿½ ï¿½0 ::1:5432 ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½:::* ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½
ï¿½LISTEN ï¿½ ï¿½ ï¿½9900/postgres

-----------------------------------------------------------------
ï¿½ pg_upgrade run on Wed Apr 18 09:24:47 2018
-----------------------------------------------------------------

command: "/usr/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D
"/var/ericsson/esm-data/postgresql-data" -o "-p 50432 -c autovacuum=off
-c autovacuum_freeze_max_age=2000000000 ï¿½-c listen_addresses='' -c
unix_socket_permissions=0700" start >> "pg_upgrade_server.log" 2>&1
pg_ctl: another server might be running; trying to start server anyway
FATAL: ï¿½lock file "postmaster.pid" already exists
HINT: ï¿½Is another postmaster (PID 9778) running in data directory
"/var/ericsson/esm-data/postgresql-data"?
pg_ctl: could not start server
Examine the log output.

[root@ms-esmon /]# cat
./var/ericsson/esm-data/postgresql-data-9.4/postmaster.pid
9900
/var/ericsson/esm-data/postgresql-data-9.4
1524039630
5432
/var/run/postgresql
localhost
ï¿½ 5432001 ï¿½ 2031616
ï¿½
ï¿½
[root@ms-esmon /]# cat
./var/ericsson/esm-data/postgresql-data/postmaster.pid
9778
/var/ericsson/esm-data/postgresql-data
ï¿½50432001 ï¿½ 1998850

With Best Regards
Akshay

From: ï¿½ ï¿½ ï¿½ ï¿½Fabio Pardi <f.pardi@portavita.eu>
To: ï¿½ ï¿½ ï¿½ ï¿½Akshay Ballarpure <akshay.ballarpure@tcs.com>,
pgsql-general@lists.postgresql.org
Date: ï¿½ ï¿½ ï¿½ ï¿½04/18/2018 01:06 PM
Subject: ï¿½ ï¿½ ï¿½ ï¿½Re: pg_upgrade help
------------------------------------------------------------------------

Hi,

please avoid crossposting to multiple mailing lists.

You need to run both versions of the database, the old and the new.

They need to run on different ports (note that it is impossible to run 2
different processes on the same port, that's not a postgresql thing)

On 04/18/2018 09:30 AM, Akshay Ballarpure wrote:

Hi all,
I need help on pg_upgrade from 8.4 to 9.4 version. Appreciate urgent
response.
Installed both version and stopped it. Do i need to run both version or
only one 8.4 or 9.4 . Both should run on 50432 ?

-bash-4.2$ id
uid=26(postgres) gid=26(postgres) groups=26(postgres)
context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023

-bash-4.2$ export OLDCLUSTER=/var/ericsson/esm-data/postgresql-data ï¿½ ï¿½
ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½-- 8.4 data
-bash-4.2$ export NEWCLUSTER=/var/ericsson/esm-data/postgresql-data-9.4
ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ ï¿½ -- 9.4 data

-bash-4.2$ /opt/rh/rh-postgresql94/root/usr/bin/pg_upgrade
--old-bindir=/usr/bin --new-bindir=/opt/rh/rh-postgresql94/root/usr/bin
--old-datadir=$OLDCLUSTER --new-datadir=$NEWCLUSTER

*connection to database failed: could not connect to server: No such
file or directory*
ï¿½ ï¿½ ï¿½ ï¿½ Is the server running locally and accepting
ï¿½ ï¿½ ï¿½ ï¿½ connections on Unix domain socket
"/var/run/postgresql/.s.PGSQL.50432"?

could not connect to old postmaster started with the command:
"/usr/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D
"/var/ericsson/esm-data/postgresql-data" -o "-p 50432 -c autovacuum=off
-c autovacuum_freeze_max_age=2000000000 ï¿½-c listen_addresses='' -c
unix_socket_permissions=0700" start
Failure, exiting

With Best Regards
Akshay

=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you

Adrian Klaver

adrian.klaver@aklaver.com

almost 8 years ago

In reply to: Akshay Ballarpure (#6)

Re: pg_upgrade help

On 04/18/2018 05:02 AM, Akshay Ballarpure wrote:

Hi Fabio,
sorry to bother you again, its still failing with stopping both server
(8.4 and 9.4)

Actually according to the command show at bottom of post it is failing
trying to start the 8.4 server. In your previous post that was because
it was already running:

-bash-4.2$ ps -eaf | grep postgres
postgres 9778 1 0 09:17 ? 00:00:00 /usr/bin/postgres -p
50432 -D /var/ericsson/esm-data/postgresql-data/

FATAL: lock file "postmaster.pid" already exists
HINT: Is another postmaster (PID 9778) running in data directory
"/var/ericsson/esm-data/postgresql-data"?
pg_ctl: could not start server

Make sure both servers are stopped before running pg_upgrade. Per a
previous suggestion follow the check list here:

https://www.postgresql.org/docs/10/static/pgupgrade.html
"
Usage

These are the steps to perform an upgrade with pg_upgrade:

...

-bash-4.2$ /opt/rh/rh-postgresql94/root/usr/bin/pg_upgrade
--old-bindir=/usr/bin --new-bindir=/opt/rh/rh-postgresql94/root/usr/bin
--old-datadir=$OLDCLUSTER --new-datadir=$NEWCLUSTER

connection to database failed: could not connect to server: No such file
or directory
ï¿½ ï¿½ ï¿½ ï¿½ Is the server running locally and accepting
ï¿½ ï¿½ ï¿½ ï¿½ connections on Unix domain socket
"/var/run/postgresql/.s.PGSQL.50432"?

could not connect to old postmaster started with the command:
"/usr/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D
"/var/ericsson/esm-data/postgresql-data" -o "-p 50432 -c autovacuum=off
-c autovacuum_freeze_max_age=2000000000 ï¿½-c listen_addresses='' -c
unix_socket_permissions=0700" start
Failure, exiting

With Best Regards
Akshay

--
Adrian Klaver
adrian.klaver@aklaver.com

Rajni Baliyan

saan654@gmail.com

almost 8 years ago

In reply to: Adrian Klaver (#8)

Re: pg_upgrade help

Hello Akshay,

Try starting both servers individually. If you can then,it may be port
conflict

Below is the part of document-

Obviously, no one should be accessing the clusters during the upgrade.
pg_upgrade defaults to running servers on port 50432 to avoid unintended
client connections. You can use the same port number for both clusters when
doing an upgrade because the old and new clusters will not be running at
the same time. *However, when checking an old running server, the old and
new port numbers must be different. *

Thanks
Rajni

On Thu, Apr 19, 2018 at 12:02 AM, Adrian Klaver <adrian.klaver@aklaver.com>
wrote:

On 04/18/2018 05:02 AM, Akshay Ballarpure wrote:

Hi Fabio,
sorry to bother you again, its still failing with stopping both server
(8.4 and 9.4)

Actually according to the command show at bottom of post it is failing
trying to start the 8.4 server. In your previous post that was because it
was already running:

-bash-4.2$ ps -eaf | grep postgres
postgres 9778 1 0 09:17 ? 00:00:00 /usr/bin/postgres -p 50432
-D /var/ericsson/esm-data/postgresql-data/

FATAL: lock file "postmaster.pid" already exists
HINT: Is another postmaster (PID 9778) running in data directory
"/var/ericsson/esm-data/postgresql-data"?
pg_ctl: could not start server

Make sure both servers are stopped before running pg_upgrade. Per a
previous suggestion follow the check list here:

https://www.postgresql.org/docs/10/static/pgupgrade.html
"
Usage

These are the steps to perform an upgrade with pg_upgrade:

...

"

-bash-4.2$ /opt/rh/rh-postgresql94/root/usr/bin/pg_upgrade
--old-bindir=/usr/bin --new-bindir=/opt/rh/rh-postgresql94/root/usr/bin
--old-datadir=$OLDCLUSTER --new-datadir=$NEWCLUSTER

connection to database failed: could not connect to server: No such file
or directory
Is the server running locally and accepting
connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.
50432"?

could not connect to old postmaster started with the command:
"/usr/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D
"/var/ericsson/esm-data/postgresql-data" -o "-p 50432 -c autovacuum=off
-c autovacuum_freeze_max_age=2000000000 -c listen_addresses='' -c
unix_socket_permissions=0700" start
Failure, exiting

With Best Regards
Akshay

--
Adrian Klaver
adrian.klaver@aklaver.com

--
Thank you

Sincere Regards
Rajni

0410 472 086

#10

Akshay Ballarpure

akshay.ballarpure@tcs.com

almost 8 years ago

In reply to: Fabio Pardi (#7)

Re: pg_upgrade help

Hi Fabio,
Yes i ran initdb on new database and able to start as below.

[root@ms-esmon root]# su - postgres -c "/usr/bin/postgres -p 50432 -D
/var/ericsson/esm-data/postgresql-data/ 2>&1 &"
[root@ms-esmon root]# su - postgres -c
"/opt/rh/rh-postgresql94/root/usr/bin/postgres -D
/var/ericsson/esm-data/postgresql-data-9.4/ 2>&1 &"
[root@ms-esmon root]# 2018-04-19 08:17:53.553 IST LOG: redirecting log
output to logging collector process
2018-04-19 08:17:53.553 IST HINT: Future log output will appear in
directory "pg_log".

[root@ms-esmon root]#
[root@ms-esmon root]# ps -eaf | grep postgre
sroot 8646 9365 0 Apr18 pts/1 00:00:00 su - postgres
postgres 8647 8646 0 Apr18 pts/1 00:00:00 -bash
postgres 28009 1 2 08:17 ? 00:00:00 /usr/bin/postgres -p 50432
-D /var/ericsson/esm-data/postgresql-data/ --8.4
postgres 28010 28009 0 08:17 ? 00:00:00 postgres: logger process
postgres 28012 28009 0 08:17 ? 00:00:00 postgres: writer process
postgres 28013 28009 0 08:17 ? 00:00:00 postgres: wal writer
process
postgres 28014 28009 0 08:17 ? 00:00:00 postgres: autovacuum
launcher process
postgres 28015 28009 0 08:17 ? 00:00:00 postgres: stats collector
process
postgres 28048 1 0 08:17 ? 00:00:00
/opt/rh/rh-postgresql94/root/usr/bin/postgres -D
/var/ericsson/esm-data/postgresql-data-9.4/
postgres 28049 28048 0 08:17 ? 00:00:00 postgres: logger process
postgres 28051 28048 0 08:17 ? 00:00:00 postgres: checkpointer
process
postgres 28052 28048 0 08:17 ? 00:00:00 postgres: writer process
postgres 28053 28048 0 08:17 ? 00:00:00 postgres: wal writer
process
postgres 28054 28048 0 08:17 ? 00:00:00 postgres: autovacuum
launcher process
postgres 28055 28048 0 08:17 ? 00:00:00 postgres: stats collector
process
root 28057 2884 0 08:17 pts/0 00:00:00 grep --color=auto postgre

Also i am able to start db with the command provided by you and run psql.

/opt/rh/rh-postgresql94/root/usr/bin/pg_ctl start -o "-p 50432 -c
listen_addresses='' -c unix_socket_permissions=0700" -D
/var/ericsson/esm-data/postgresql-data-9.4/
pg_ctl: another server might be running; trying to start server anyway
server starting
-bash-4.2$ 2018-04-19 08:22:46.527 IST LOG: redirecting log output to
logging collector process
2018-04-19 08:22:46.527 IST HINT: Future log output will appear in
directory "pg_log".

-bash-4.2$ ps -eaf | grep postg
root 8646 9365 0 Apr18 pts/1 00:00:00 su - postgres
postgres 8647 8646 0 Apr18 pts/1 00:00:00 -bash
postgres 28174 1 0 08:22 pts/1 00:00:00
/opt/rh/rh-postgresql94/root/usr/bin/postgres -D
/var/ericsson/esm-data/postgresql-data-9.4 -p 50432 -c listen_addresses=
-c unix_socket_permissions=0700
postgres 28175 28174 0 08:22 ? 00:00:00 postgres: logger process
postgres 28177 28174 0 08:22 ? 00:00:00 postgres: checkpointer
process
postgres 28178 28174 0 08:22 ? 00:00:00 postgres: writer process
postgres 28179 28174 0 08:22 ? 00:00:00 postgres: wal writer
process
postgres 28180 28174 0 08:22 ? 00:00:00 postgres: autovacuum
launcher process
postgres 28181 28174 0 08:22 ? 00:00:00 postgres: stats collector
process
postgres 28182 8647 0 08:22 pts/1 00:00:00 ps -eaf
postgres 28183 8647 0 08:22 pts/1 00:00:00 grep --color=auto postg

-bash-4.2$ psql -p 50432 -h /var/run/postgresql -U rhqadmin -d rhq
psql (8.4.20, server 9.4.9)
WARNING: psql version 8.4, server version 9.4.
Some psql features might not work.
Type "help" for help.

rhq=>

Still its failing...

-bash-4.2$ ps -efa | grep postgre
root 8646 9365 0 Apr18 pts/1 00:00:00 su - postgres
postgres 8647 8646 0 Apr18 pts/1 00:00:00 -bash
postgres 28349 8647 0 08:34 pts/1 00:00:00 ps -efa
postgres 28350 8647 0 08:34 pts/1 00:00:00 grep --color=auto postgre

-bash-4.2$ echo $OLDCLUSTER
/usr/bin/postgres
-bash-4.2$ echo $NEWCLUSTER
/opt/rh/rh-postgresql94/

[root@ms-esmon rh-postgresql94]#
/opt/rh/rh-postgresql94/root/usr/bin/pg_upgrade --old-bindir=/usr/bin
--new-bindir=/opt/rh/rh-postgresql94/root/usr/bin
--old-datadir=/var/ericsson/esm-data/postgresql-data
--new-datadir=/var/ericsson/esm-data/postgresql-data-9.4

Performing Consistency Checks
-----------------------------
Checking cluster versions ok

From: Fabio Pardi <f.pardi@portavita.eu>
To: Akshay Ballarpure <akshay.ballarpure@tcs.com>
Cc: pgsql-general@lists.postgresql.org
Date: 04/18/2018 06:17 PM
Subject: Re: pg_upgrade help

did you run initdb on the new db?

what happens if you manually start the new db?

/opt/rh/rh-postgresql94/root/usr/bin/pg_ctl start -o "-p 50432 -c
listen_addresses='' -c unix_socket_permissions=0700" -D $NEWCLUSTER

after starting it, can you connect to it using psql?

psql -p 50432 -h /var/run/postgresql -U your_user _db_

regards,

fabio pardi

On 04/18/2018 02:02 PM, Akshay Ballarpure wrote:

Hi Fabio,
sorry to bother you again, its still failing with stopping both server
(8.4 and 9.4)

-bash-4.2$ /opt/rh/rh-postgresql94/root/usr/bin/pg_upgrade
--old-bindir=/usr/bin --new-bindir=/opt/rh/rh-postgresql94/root/usr/bin
--old-datadir=$OLDCLUSTER --new-datadir=$NEWCLUSTER

connection to database failed: could not connect to server: No such file
or directory
Is the server running locally and accepting
connections on Unix domain socket
"/var/run/postgresql/.s.PGSQL.50432"?

could not connect to old postmaster started with the command:
"/usr/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D
"/var/ericsson/esm-data/postgresql-data" -o "-p 50432 -c autovacuum=off
-c autovacuum_freeze_max_age=2000000000 -c listen_addresses='' -c
unix_socket_permissions=0700" start
Failure, exiting

With Best Regards
Akshay
Ericsson OSS MON
Tata Consultancy Services
Mailto: akshay.ballarpure@tcs.com
Website: http://www.tcs.com <http://www.tcs.com/>
____________________________________________
Experience certainty. IT Services
Business Solutions
Consulting
____________________________________________

From: Fabio Pardi <f.pardi@portavita.eu>
To: Akshay Ballarpure <akshay.ballarpure@tcs.com>,
pgsql-general@lists.postgresql.org
Date: 04/18/2018 02:35 PM
Subject: Re: pg_upgrade help
------------------------------------------------------------------------

Hi,

i was too fast in reply (and perhaps i should drink my morning coffee
before replying), I will try to be more detailed:

both servers should be able to run at the moment you run pg_upgrade,
that means the 2 servers should have been correctly stopped in advance,
should have their configuration files, and new cluster initialized too.

Then, as Sergei highlights here below, pg_upgrade will take care of the
upgrade process, starting the servers.

Here there is a step by step guide, i considered my best ally when it
was time to upgrade:

https://www.postgresql.org/docs/9.4/static/pgupgrade.html

note point 7:

'stop both servers'

About the port the servers will run on, at point 9 there is some
clarification:

' pg_upgrade defaults to running servers on port 50432 to avoid
unintended client connections. You can use the same port number for both
clusters when doing an upgrade because the old and new clusters will not
be running at the same time. However, when checking an old running
server, the old and new port numbers must be different.'

Hope it helps,

Fabio Pardi

On 04/18/2018 10:34 AM, Akshay Ballarpure wrote:

Thanks Fabio for instant reply.

I now started 8.4 with 50432 and 9.4 with default port but still its
failing ...Can you please suggest what is wrong ?

-bash-4.2$ /opt/rh/rh-postgresql94/root/usr/bin/pg_upgrade
--old-bindir=/usr/bin --new-bindir=/opt/rh/rh-postgresql94/root/usr/bin
--old-datadir=$OLDCLUSTER --new-datadir=$NEWCLUSTER

*failure*
Consult the last few lines of "pg_upgrade_server.log" for
the probable cause of the failure.

There seems to be a postmaster servicing the old cluster.
Please shutdown that postmaster and try again.
Failure, exiting
-bash-4.2$ ps -eaf | grep postgres
root 8646 9365 0 08:07 pts/1 00:00:00 su - postgres
postgres 8647 8646 0 08:07 pts/1 00:00:00 -bash
postgres 9778 1 0 09:17 ? 00:00:00 /usr/bin/postgres -p
50432 -D /var/ericsson/esm-data/postgresql-data/
postgres 9779 9778 0 09:17 ? 00:00:00 postgres: logger

process

postgres 9781 9778 0 09:17 ? 00:00:00 postgres: writer

process

postgres 9782 9778 0 09:17 ? 00:00:00 postgres: wal writer
process
postgres 9783 9778 0 09:17 ? 00:00:00 postgres: autovacuum
launcher process
postgres 9784 9778 0 09:17 ? 00:00:00 postgres: stats
collector process
postgres 9900 1 0 09:20 ? 00:00:00
/opt/rh/rh-postgresql94/root/usr/bin/postgres -D
/var/ericsson/esm-data/postgresql-data-9.4/
postgres 9901 9900 0 09:20 ? 00:00:00 postgres: logger

process

postgres 9903 9900 0 09:20 ? 00:00:00 postgres: checkpointer
process
postgres 9904 9900 0 09:20 ? 00:00:00 postgres: writer

process

postgres 9905 9900 0 09:20 ? 00:00:00 postgres: wal writer
process
postgres 9906 9900 0 09:20 ? 00:00:00 postgres: autovacuum
launcher process
postgres 9907 9900 0 09:20 ? 00:00:00 postgres: stats
collector process
postgres 9926 8647 0 09:21 pts/1 00:00:00 ps -eaf
postgres 9927 8647 0 09:21 pts/1 00:00:00 grep --color=auto

postgres

-bash-4.2$ netstat -antp | grep 50432
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 127.0.0.1:50432 0.0.0.0:*
LISTEN 9778/postgres
tcp6 0 0 ::1:50432 :::*
LISTEN 9778/postgres
-bash-4.2$ netstat -antp | grep 5432
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 127.0.0.1:5432 0.0.0.0:*
LISTEN 9900/postgres
tcp6 0 0 ::1:5432 :::*
LISTEN 9900/postgres

-----------------------------------------------------------------
pg_upgrade run on Wed Apr 18 09:24:47 2018
-----------------------------------------------------------------

command: "/usr/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D
"/var/ericsson/esm-data/postgresql-data" -o "-p 50432 -c autovacuum=off
-c autovacuum_freeze_max_age=2000000000 -c listen_addresses='' -c
unix_socket_permissions=0700" start >> "pg_upgrade_server.log" 2>&1
pg_ctl: another server might be running; trying to start server anyway
FATAL: lock file "postmaster.pid" already exists
HINT: Is another postmaster (PID 9778) running in data directory
"/var/ericsson/esm-data/postgresql-data"?
pg_ctl: could not start server
Examine the log output.

[root@ms-esmon /]# cat
./var/ericsson/esm-data/postgresql-data-9.4/postmaster.pid
9900
/var/ericsson/esm-data/postgresql-data-9.4
1524039630
5432
/var/run/postgresql
localhost
5432001 2031616

[root@ms-esmon /]# cat
./var/ericsson/esm-data/postgresql-data/postmaster.pid
9778
/var/ericsson/esm-data/postgresql-data
50432001 1998850

With Best Regards
Akshay

From: Fabio Pardi <f.pardi@portavita.eu>
To: Akshay Ballarpure <akshay.ballarpure@tcs.com>,
pgsql-general@lists.postgresql.org
Date: 04/18/2018 01:06 PM
Subject: Re: pg_upgrade help

------------------------------------------------------------------------

Hi,

please avoid crossposting to multiple mailing lists.

You need to run both versions of the database, the old and the new.

They need to run on different ports (note that it is impossible to run

different processes on the same port, that's not a postgresql thing)

On 04/18/2018 09:30 AM, Akshay Ballarpure wrote:

Hi all,
I need help on pg_upgrade from 8.4 to 9.4 version. Appreciate urgent
response.
Installed both version and stopped it. Do i need to run both version

only one 8.4 or 9.4 . Both should run on 50432 ?

-bash-4.2$ id
uid=26(postgres) gid=26(postgres) groups=26(postgres)
context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023

-bash-4.2$ export OLDCLUSTER=/var/ericsson/esm-data/postgresql-data

-- 8.4 data
-bash-4.2$ export

NEWCLUSTER=/var/ericsson/esm-data/postgresql-data-9.4

-- 9.4 data

-bash-4.2$ /opt/rh/rh-postgresql94/root/usr/bin/pg_upgrade
--old-bindir=/usr/bin

--new-bindir=/opt/rh/rh-postgresql94/root/usr/bin

--old-datadir=$OLDCLUSTER --new-datadir=$NEWCLUSTER

*connection to database failed: could not connect to server: No such
file or directory*
Is the server running locally and accepting
connections on Unix domain socket
"/var/run/postgresql/.s.PGSQL.50432"?

could not connect to old postmaster started with the command:
"/usr/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D
"/var/ericsson/esm-data/postgresql-data" -o "-p 50432 -c

autovacuum=off

Show quoted text

-c autovacuum_freeze_max_age=2000000000 -c listen_addresses='' -c
unix_socket_permissions=0700" start
Failure, exiting

With Best Regards
Akshay

=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you

#11

Fabio Pardi

f.pardi@portavita.eu

almost 8 years ago

In reply to: Akshay Ballarpure (#10)

Re: pg_upgrade help

Hi,

while trying to reproduce your problem, i noticed that on my Centos 6 installations Postgres 8.4 and Postgres 9.6 (I do not have 9.4 readily available) store the socket in different places:

Postgres 9.6.6 uses /var/run/postgresql/

Postgres 8.4 uses /tmp/

therefore using default settings, i can connect to 9.6 but not 8.4 without specifying where the socket is

Connect to 9.6

12:01 postgres@machine:~# psql
psql (8.4.20, server 9.6.6)
WARNING: psql version 8.4, server version 9.6.
Some psql features might not work.
Type "help" for help.

---------

Connect to 8.4

12:01 postgres@machine:~# psql
psql: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?

12:04 postgres@machine:~# psql -h /tmp
psql (8.4.20)
Type "help" for help.

I think you might be incurring in the same problem.

Can you confirm it?

regards,

fabio pardi

Show quoted text

On 04/19/2018 09:37 AM, Akshay Ballarpure wrote:

Hi Fabio,
Yes i ran initdb on new database and able to start as below.

[root@ms-esmon root]# su - postgres -c "/usr/bin/postgres -p 50432 -D /var/ericsson/esm-data/postgresql-data/ 2>&1 &"
[root@ms-esmon root]# su - postgres -c "/opt/rh/rh-postgresql94/root/usr/bin/postgres -D /var/ericsson/esm-data/postgresql-data-9.4/ 2>&1 &"
[root@ms-esmon root]# 2018-04-19 08:17:53.553 IST LOG: redirecting log output to logging collector process
2018-04-19 08:17:53.553 IST HINT: Future log output will appear in directory "pg_log".

[root@ms-esmon root]#
[root@ms-esmon root]# ps -eaf | grep postgre
sroot 8646 9365 0 Apr18 pts/1 00:00:00 su - postgres
postgres 8647 8646 0 Apr18 pts/1 00:00:00 -bash
postgres 28009 1 2 08:17 ? 00:00:00 /usr/bin/postgres -p 50432 -D /var/ericsson/esm-data/postgresql-data/ *--8.4*
postgres 28010 28009 0 08:17 ? 00:00:00 postgres: logger process
postgres 28012 28009 0 08:17 ? 00:00:00 postgres: writer process
postgres 28013 28009 0 08:17 ? 00:00:00 postgres: wal writer process
postgres 28014 28009 0 08:17 ? 00:00:00 postgres: autovacuum launcher process
postgres 28015 28009 0 08:17 ? 00:00:00 postgres: stats collector process
postgres 28048 1 0 08:17 ? 00:00:00 /opt/rh/rh-postgresql94/root/usr/bin/postgres -D /var/ericsson/esm-data/postgresql-data-9.4/
postgres 28049 28048 0 08:17 ? 00:00:00 postgres: logger process
postgres 28051 28048 0 08:17 ? 00:00:00 postgres: checkpointer process
postgres 28052 28048 0 08:17 ? 00:00:00 postgres: writer process
postgres 28053 28048 0 08:17 ? 00:00:00 postgres: wal writer process
postgres 28054 28048 0 08:17 ? 00:00:00 postgres: autovacuum launcher process
postgres 28055 28048 0 08:17 ? 00:00:00 postgres: stats collector process
root 28057 2884 0 08:17 pts/0 00:00:00 grep --color=auto postgre

Also i am able to start db with the command provided by you and run psql.

/opt/rh/rh-postgresql94/root/usr/bin/pg_ctl start -o "-p 50432 -c listen_addresses='' -c unix_socket_permissions=0700" -D /var/ericsson/esm-data/postgresql-data-9.4/
pg_ctl: another server might be running; trying to start server anyway
server starting
-bash-4.2$ 2018-04-19 08:22:46.527 IST LOG: redirecting log output to logging collector process
2018-04-19 08:22:46.527 IST HINT: Future log output will appear in directory "pg_log".

-bash-4.2$ ps -eaf | grep postg
root 8646 9365 0 Apr18 pts/1 00:00:00 su - postgres
postgres 8647 8646 0 Apr18 pts/1 00:00:00 -bash
postgres 28174 1 0 08:22 pts/1 00:00:00 /opt/rh/rh-postgresql94/root/usr/bin/postgres -D /var/ericsson/esm-data/postgresql-data-9.4 -p 50432 -c listen_addresses= -c unix_socket_permissions=0700
postgres 28175 28174 0 08:22 ? 00:00:00 postgres: logger process
postgres 28177 28174 0 08:22 ? 00:00:00 postgres: checkpointer process
postgres 28178 28174 0 08:22 ? 00:00:00 postgres: writer process
postgres 28179 28174 0 08:22 ? 00:00:00 postgres: wal writer process
postgres 28180 28174 0 08:22 ? 00:00:00 postgres: autovacuum launcher process
postgres 28181 28174 0 08:22 ? 00:00:00 postgres: stats collector process
postgres 28182 8647 0 08:22 pts/1 00:00:00 ps -eaf
postgres 28183 8647 0 08:22 pts/1 00:00:00 grep --color=auto postg

-bash-4.2$ psql -p 50432 -h /var/run/postgresql -U rhqadmin -d rhq
psql (8.4.20, server 9.4.9)
WARNING: psql version 8.4, server version 9.4.
Some psql features might not work.
Type "help" for help.

rhq=>

Still its failing...

-bash-4.2$ ps -efa | grep postgre
root 8646 9365 0 Apr18 pts/1 00:00:00 su - postgres
postgres 8647 8646 0 Apr18 pts/1 00:00:00 -bash
postgres 28349 8647 0 08:34 pts/1 00:00:00 ps -efa
postgres 28350 8647 0 08:34 pts/1 00:00:00 grep --color=auto postgre

-bash-4.2$ echo $OLDCLUSTER
/usr/bin/postgres
-bash-4.2$ echo $NEWCLUSTER
/opt/rh/rh-postgresql94/

[root@ms-esmon rh-postgresql94]# /opt/rh/rh-postgresql94/root/usr/bin/pg_upgrade --old-bindir=/usr/bin --new-bindir=/opt/rh/rh-postgresql94/root/usr/bin --old-datadir=/var/ericsson/esm-data/postgresql-data --new-datadir=/var/ericsson/esm-data/postgresql-data-9.4

Performing Consistency Checks
-----------------------------
Checking cluster versions ok

connection to database failed: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.50432"?

could not connect to old postmaster started with the command:
"/usr/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D "/var/ericsson/esm-data/postgresql-data" -o "-p 50432 -c autovacuum=off -c autovacuum_freeze_max_age=2000000000 -c listen_addresses='' -c unix_socket_permissions=0700" start
Failure, exiting

With Best Regards
Akshay
Ericsson OSS MON
Tata Consultancy Services
Mailto: akshay.ballarpure@tcs.com
Website: http://www.tcs.com <http://www.tcs.com/>
____________________________________________
Experience certainty. IT Services
Business Solutions
Consulting
____________________________________________

From: Fabio Pardi <f.pardi@portavita.eu>
To: Akshay Ballarpure <akshay.ballarpure@tcs.com>
Cc: pgsql-general@lists.postgresql.org
Date: 04/18/2018 06:17 PM
Subject: Re: pg_upgrade help
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

did you run initdb on the new db?

what happens if you manually start the new db?

/opt/rh/rh-postgresql94/root/usr/bin/pg_ctl start -o "-p 50432 -c
listen_addresses='' -c unix_socket_permissions=0700" -D $NEWCLUSTER

after starting it, can you connect to it using psql?

psql -p 50432 -h /var/run/postgresql -U your_user _db_

regards,

fabio pardi

On 04/18/2018 02:02 PM, Akshay Ballarpure wrote:

Hi Fabio,
sorry to bother you again, its still failing with stopping both server
(8.4 and 9.4)

-bash-4.2$ /opt/rh/rh-postgresql94/root/usr/bin/pg_upgrade
--old-bindir=/usr/bin --new-bindir=/opt/rh/rh-postgresql94/root/usr/bin
--old-datadir=$OLDCLUSTER --new-datadir=$NEWCLUSTER

connection to database failed: could not connect to server: No such file
or directory
Is the server running locally and accepting
connections on Unix domain socket
"/var/run/postgresql/.s.PGSQL.50432"?

could not connect to old postmaster started with the command:
"/usr/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D
"/var/ericsson/esm-data/postgresql-data" -o "-p 50432 -c autovacuum=off
-c autovacuum_freeze_max_age=2000000000 -c listen_addresses='' -c
unix_socket_permissions=0700" start
Failure, exiting

With Best Regards
Akshay
Ericsson OSS MON
Tata Consultancy Services
Mailto: akshay.ballarpure@tcs.com
Website: http://www.tcs.com <http://www.tcs.com/><http://www.tcs.com/>
____________________________________________
Experience certainty. IT Services
Business Solutions
Consulting
____________________________________________

From: Fabio Pardi <f.pardi@portavita.eu>
To: Akshay Ballarpure <akshay.ballarpure@tcs.com>,
pgsql-general@lists.postgresql.org
Date: 04/18/2018 02:35 PM
Subject: Re: pg_upgrade help
------------------------------------------------------------------------

Hi,

i was too fast in reply (and perhaps i should drink my morning coffee
before replying), I will try to be more detailed:

both servers should be able to run at the moment you run pg_upgrade,
that means the 2 servers should have been correctly stopped in advance,
should have their configuration files, and new cluster initialized too.

Then, as Sergei highlights here below, pg_upgrade will take care of the
upgrade process, starting the servers.

Here there is a step by step guide, i considered my best ally when it
was time to upgrade:

https://www.postgresql.org/docs/9.4/static/pgupgrade.html

note point 7:

'stop both servers'

About the port the servers will run on, at point 9 there is some
clarification:

' pg_upgrade defaults to running servers on port 50432 to avoid
unintended client connections. You can use the same port number for both
clusters when doing an upgrade because the old and new clusters will not
be running at the same time. However, when checking an old running
server, the old and new port numbers must be different.'

Hope it helps,

Fabio Pardi

On 04/18/2018 10:34 AM, Akshay Ballarpure wrote:

Thanks Fabio for instant reply.

I now started 8.4 with 50432 and 9.4 with default port but still its
failing ...Can you please suggest what is wrong ?

-bash-4.2$ /opt/rh/rh-postgresql94/root/usr/bin/pg_upgrade
--old-bindir=/usr/bin --new-bindir=/opt/rh/rh-postgresql94/root/usr/bin
--old-datadir=$OLDCLUSTER --new-datadir=$NEWCLUSTER

*failure*
Consult the last few lines of "pg_upgrade_server.log" for
the probable cause of the failure.

There seems to be a postmaster servicing the old cluster.
Please shutdown that postmaster and try again.
Failure, exiting
-bash-4.2$ ps -eaf | grep postgres
root 8646 9365 0 08:07 pts/1 00:00:00 su - postgres
postgres 8647 8646 0 08:07 pts/1 00:00:00 -bash
postgres 9778 1 0 09:17 ? 00:00:00 /usr/bin/postgres -p
50432 -D /var/ericsson/esm-data/postgresql-data/
postgres 9779 9778 0 09:17 ? 00:00:00 postgres: logger process
postgres 9781 9778 0 09:17 ? 00:00:00 postgres: writer process
postgres 9782 9778 0 09:17 ? 00:00:00 postgres: wal writer
process
postgres 9783 9778 0 09:17 ? 00:00:00 postgres: autovacuum
launcher process
postgres 9784 9778 0 09:17 ? 00:00:00 postgres: stats
collector process
postgres 9900 1 0 09:20 ? 00:00:00
/opt/rh/rh-postgresql94/root/usr/bin/postgres -D
/var/ericsson/esm-data/postgresql-data-9.4/
postgres 9901 9900 0 09:20 ? 00:00:00 postgres: logger process
postgres 9903 9900 0 09:20 ? 00:00:00 postgres: checkpointer
process
postgres 9904 9900 0 09:20 ? 00:00:00 postgres: writer process
postgres 9905 9900 0 09:20 ? 00:00:00 postgres: wal writer
process
postgres 9906 9900 0 09:20 ? 00:00:00 postgres: autovacuum
launcher process
postgres 9907 9900 0 09:20 ? 00:00:00 postgres: stats
collector process
postgres 9926 8647 0 09:21 pts/1 00:00:00 ps -eaf
postgres 9927 8647 0 09:21 pts/1 00:00:00 grep --color=auto postgres

-bash-4.2$ netstat -antp | grep 50432
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 127.0.0.1:50432 0.0.0.0:*
LISTEN 9778/postgres
tcp6 0 0 ::1:50432 :::*
LISTEN 9778/postgres
-bash-4.2$ netstat -antp | grep 5432
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 127.0.0.1:5432 0.0.0.0:*
LISTEN 9900/postgres
tcp6 0 0 ::1:5432 :::*
LISTEN 9900/postgres

-----------------------------------------------------------------
pg_upgrade run on Wed Apr 18 09:24:47 2018
-----------------------------------------------------------------

command: "/usr/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D
"/var/ericsson/esm-data/postgresql-data" -o "-p 50432 -c autovacuum=off
-c autovacuum_freeze_max_age=2000000000 -c listen_addresses='' -c
unix_socket_permissions=0700" start >> "pg_upgrade_server.log" 2>&1
pg_ctl: another server might be running; trying to start server anyway
FATAL: lock file "postmaster.pid" already exists
HINT: Is another postmaster (PID 9778) running in data directory
"/var/ericsson/esm-data/postgresql-data"?
pg_ctl: could not start server
Examine the log output.

[root@ms-esmon /]# cat
./var/ericsson/esm-data/postgresql-data-9.4/postmaster.pid
9900
/var/ericsson/esm-data/postgresql-data-9.4
1524039630
5432
/var/run/postgresql
localhost
5432001 2031616

[root@ms-esmon /]# cat
./var/ericsson/esm-data/postgresql-data/postmaster.pid
9778
/var/ericsson/esm-data/postgresql-data
50432001 1998850

With Best Regards
Akshay

From: Fabio Pardi <f.pardi@portavita.eu>
To: Akshay Ballarpure <akshay.ballarpure@tcs.com>,
pgsql-general@lists.postgresql.org
Date: 04/18/2018 01:06 PM
Subject: Re: pg_upgrade help
------------------------------------------------------------------------

Hi,

please avoid crossposting to multiple mailing lists.

You need to run both versions of the database, the old and the new.

They need to run on different ports (note that it is impossible to run 2
different processes on the same port, that's not a postgresql thing)

On 04/18/2018 09:30 AM, Akshay Ballarpure wrote:

Hi all,
I need help on pg_upgrade from 8.4 to 9.4 version. Appreciate urgent
response.
Installed both version and stopped it. Do i need to run both version or
only one 8.4 or 9.4 . Both should run on 50432 ?

-bash-4.2$ id
uid=26(postgres) gid=26(postgres) groups=26(postgres)
context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023

-bash-4.2$ export OLDCLUSTER=/var/ericsson/esm-data/postgresql-data
-- 8.4 data
-bash-4.2$ export NEWCLUSTER=/var/ericsson/esm-data/postgresql-data-9.4
-- 9.4 data

-bash-4.2$ /opt/rh/rh-postgresql94/root/usr/bin/pg_upgrade
--old-bindir=/usr/bin --new-bindir=/opt/rh/rh-postgresql94/root/usr/bin
--old-datadir=$OLDCLUSTER --new-datadir=$NEWCLUSTER

*connection to database failed: could not connect to server: No such
file or directory*
Is the server running locally and accepting
connections on Unix domain socket
"/var/run/postgresql/.s.PGSQL.50432"?

could not connect to old postmaster started with the command:
"/usr/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D
"/var/ericsson/esm-data/postgresql-data" -o "-p 50432 -c autovacuum=off
-c autovacuum_freeze_max_age=2000000000 -c listen_addresses='' -c
unix_socket_permissions=0700" start
Failure, exiting

With Best Regards
Akshay

=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you

#12

Akshay Ballarpure

akshay.ballarpure@tcs.com

almost 8 years ago

In reply to: Fabio Pardi (#11)

Re: pg_upgrade help

Hi Fabio,
I think you have found the problem. Please find o/p below.

-bash-4.2$ ps -aef | grep postgres
postgres 478 1 0 13:40 ? 00:00:00 /usr/bin/postgres -p 50432
-D /var/ericsson/esm-data/postgresql-data/
postgres 490 478 0 13:40 ? 00:00:00 postgres: logger process
postgres 492 478 0 13:40 ? 00:00:00 postgres: writer process
postgres 493 478 0 13:40 ? 00:00:00 postgres: wal writer
process
postgres 494 478 0 13:40 ? 00:00:00 postgres: autovacuum
launcher process
postgres 495 478 0 13:40 ? 00:00:00 postgres: stats collector
process
postgres 528 1 0 13:40 ? 00:00:00
/opt/rh/rh-postgresql94/root/usr/bin/postgres -D
/var/ericsson/esm-data/postgresql-data-9.4/
postgres 529 528 0 13:40 ? 00:00:00 postgres: logger process
postgres 531 528 0 13:40 ? 00:00:00 postgres: checkpointer
process
postgres 532 528 0 13:40 ? 00:00:00 postgres: writer process
postgres 533 528 0 13:40 ? 00:00:00 postgres: wal writer
process
postgres 534 528 0 13:40 ? 00:00:00 postgres: autovacuum
launcher process
postgres 535 528 0 13:40 ? 00:00:00 postgres: stats collector
process
postgres 734 8647 0 13:50 pts/1 00:00:00 ps -aef
postgres 735 8647 0 13:50 pts/1 00:00:00 grep --color=auto postgres
root 8646 9365 0 Apr18 pts/1 00:00:00 su - postgres
postgres 8647 8646 0 Apr18 pts/1 00:00:00 -bash

9.4
===

-bash-4.2$ psql
psql (8.4.20, server 9.4.9)
WARNING: psql version 8.4, server version 9.4.
Some psql features might not work.
Type "help" for help.

postgres=#

-bash-4.2$ /opt/rh/rh-postgresql94/root/usr/bin/psql
psql (9.4.9)
Type "help" for help.

postgres=#

8.4
====

-bash-4.2$ psql -p 50432
psql: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/tmp/.s.PGSQL.50432"?

==========================================================================================================

After setting PGHOST, i can connect to PSQL

-bash-4.2$ echo $PGHOST
/var/run/postgresql
-bash-4.2$ psql -p 50432
psql (8.4.20)
Type "help" for help.

postgres=#

From: Fabio Pardi <f.pardi@portavita.eu>
To: Akshay Ballarpure <akshay.ballarpure@tcs.com>,
pgsql-general@lists.postgresql.org
Date: 04/19/2018 03:45 PM
Subject: Re: pg_upgrade help

Hi,

while trying to reproduce your problem, i noticed that on my Centos 6
installations Postgres 8.4 and Postgres 9.6 (I do not have 9.4 readily
available) store the socket in different places:

Postgres 9.6.6 uses /var/run/postgresql/

Postgres 8.4 uses /tmp/

therefore using default settings, i can connect to 9.6 but not 8.4 without
specifying where the socket is

Connect to 9.6

12:01 postgres@machine:~# psql
psql (8.4.20, server 9.6.6)
WARNING: psql version 8.4, server version 9.6.
Some psql features might not work.
Type "help" for help.

---------

Connect to 8.4

12:04 postgres@machine:~# psql -h /tmp
psql (8.4.20)
Type "help" for help.

I think you might be incurring in the same problem.

Can you confirm it?

regards,

fabio pardi

On 04/19/2018 09:37 AM, Akshay Ballarpure wrote:

Hi Fabio,
Yes i ran initdb on new database and able to start as below.

[root@ms-esmon root]# su - postgres -c "/usr/bin/postgres -p 50432 -D

/var/ericsson/esm-data/postgresql-data/ 2>&1 &"

[root@ms-esmon root]# su - postgres -c

"/opt/rh/rh-postgresql94/root/usr/bin/postgres -D
/var/ericsson/esm-data/postgresql-data-9.4/ 2>&1 &"

[root@ms-esmon root]# 2018-04-19 08:17:53.553 IST LOG: redirecting log

output to logging collector process

2018-04-19 08:17:53.553 IST HINT: Future log output will appear in

directory "pg_log".

[root@ms-esmon root]#
[root@ms-esmon root]# ps -eaf | grep postgre
sroot 8646 9365 0 Apr18 pts/1 00:00:00 su - postgres
postgres 8647 8646 0 Apr18 pts/1 00:00:00 -bash
postgres 28009 1 2 08:17 ? 00:00:00 /usr/bin/postgres -p

50432 -D /var/ericsson/esm-data/postgresql-data/ *--8.4*

postgres 28010 28009 0 08:17 ? 00:00:00 postgres: logger process
postgres 28012 28009 0 08:17 ? 00:00:00 postgres: writer process
postgres 28013 28009 0 08:17 ? 00:00:00 postgres: wal writer

process

postgres 28014 28009 0 08:17 ? 00:00:00 postgres: autovacuum

launcher process

postgres 28015 28009 0 08:17 ? 00:00:00 postgres: stats

collector process

postgres 28048 1 0 08:17 ? 00:00:00

/opt/rh/rh-postgresql94/root/usr/bin/postgres -D
/var/ericsson/esm-data/postgresql-data-9.4/

postgres 28049 28048 0 08:17 ? 00:00:00 postgres: logger process
postgres 28051 28048 0 08:17 ? 00:00:00 postgres: checkpointer

process

postgres 28052 28048 0 08:17 ? 00:00:00 postgres: writer process
postgres 28053 28048 0 08:17 ? 00:00:00 postgres: wal writer

process

postgres 28054 28048 0 08:17 ? 00:00:00 postgres: autovacuum

launcher process

postgres 28055 28048 0 08:17 ? 00:00:00 postgres: stats

collector process

root 28057 2884 0 08:17 pts/0 00:00:00 grep --color=auto

postgre

Also i am able to start db with the command provided by you and run

psql.

/opt/rh/rh-postgresql94/root/usr/bin/pg_ctl start -o "-p 50432 -c

listen_addresses='' -c unix_socket_permissions=0700" -D
/var/ericsson/esm-data/postgresql-data-9.4/

pg_ctl: another server might be running; trying to start server anyway
server starting
-bash-4.2$ 2018-04-19 08:22:46.527 IST LOG: redirecting log output to

logging collector process

2018-04-19 08:22:46.527 IST HINT: Future log output will appear in

directory "pg_log".

-bash-4.2$ ps -eaf | grep postg
root 8646 9365 0 Apr18 pts/1 00:00:00 su - postgres
postgres 8647 8646 0 Apr18 pts/1 00:00:00 -bash
postgres 28174 1 0 08:22 pts/1 00:00:00

/opt/rh/rh-postgresql94/root/usr/bin/postgres -D
/var/ericsson/esm-data/postgresql-data-9.4 -p 50432 -c listen_addresses=
-c unix_socket_permissions=0700

postgres 28175 28174 0 08:22 ? 00:00:00 postgres: logger process
postgres 28177 28174 0 08:22 ? 00:00:00 postgres: checkpointer

process

postgres 28178 28174 0 08:22 ? 00:00:00 postgres: writer process
postgres 28179 28174 0 08:22 ? 00:00:00 postgres: wal writer

process

postgres 28180 28174 0 08:22 ? 00:00:00 postgres: autovacuum

launcher process

postgres 28181 28174 0 08:22 ? 00:00:00 postgres: stats

collector process

postgres 28182 8647 0 08:22 pts/1 00:00:00 ps -eaf
postgres 28183 8647 0 08:22 pts/1 00:00:00 grep --color=auto postg

-bash-4.2$ psql -p 50432 -h /var/run/postgresql -U rhqadmin -d rhq
psql (8.4.20, server 9.4.9)
WARNING: psql version 8.4, server version 9.4.
Some psql features might not work.
Type "help" for help.

rhq=>

Still its failing...

-bash-4.2$ ps -efa | grep postgre
root 8646 9365 0 Apr18 pts/1 00:00:00 su - postgres
postgres 8647 8646 0 Apr18 pts/1 00:00:00 -bash
postgres 28349 8647 0 08:34 pts/1 00:00:00 ps -efa
postgres 28350 8647 0 08:34 pts/1 00:00:00 grep --color=auto

postgre

-bash-4.2$ echo $OLDCLUSTER
/usr/bin/postgres
-bash-4.2$ echo $NEWCLUSTER
/opt/rh/rh-postgresql94/

[root@ms-esmon rh-postgresql94]#

/opt/rh/rh-postgresql94/root/usr/bin/pg_upgrade --old-bindir=/usr/bin
--new-bindir=/opt/rh/rh-postgresql94/root/usr/bin
--old-datadir=/var/ericsson/esm-data/postgresql-data
--new-datadir=/var/ericsson/esm-data/postgresql-data-9.4

Performing Consistency Checks
-----------------------------
Checking cluster versions ok

connection to database failed: could not connect to server: No such file

or directory

Is the server running locally and accepting
connections on Unix domain socket

"/var/run/postgresql/.s.PGSQL.50432"?

could not connect to old postmaster started with the command:
"/usr/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D

"/var/ericsson/esm-data/postgresql-data" -o "-p 50432 -c autovacuum=off -c
autovacuum_freeze_max_age=2000000000 -c listen_addresses='' -c
unix_socket_permissions=0700" start

Failure, exiting

With Best Regards
Akshay
Ericsson OSS MON
Tata Consultancy Services
Mailto: akshay.ballarpure@tcs.com
Website: http://www.tcs.com <http://www.tcs.com/>
____________________________________________
Experience certainty. IT Services
Business Solutions
Consulting
____________________________________________

From: Fabio Pardi <f.pardi@portavita.eu>
To: Akshay Ballarpure <akshay.ballarpure@tcs.com>
Cc: pgsql-general@lists.postgresql.org
Date: 04/18/2018 06:17 PM
Subject: Re: pg_upgrade help

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

did you run initdb on the new db?

what happens if you manually start the new db?

/opt/rh/rh-postgresql94/root/usr/bin/pg_ctl start -o "-p 50432 -c
listen_addresses='' -c unix_socket_permissions=0700" -D $NEWCLUSTER

after starting it, can you connect to it using psql?

psql -p 50432 -h /var/run/postgresql -U your_user _db_

regards,

fabio pardi

On 04/18/2018 02:02 PM, Akshay Ballarpure wrote:

Hi Fabio,
sorry to bother you again, its still failing with stopping both server
(8.4 and 9.4)

-bash-4.2$ /opt/rh/rh-postgresql94/root/usr/bin/pg_upgrade
--old-bindir=/usr/bin --new-bindir=/opt/rh/rh-postgresql94/root/usr/bin
--old-datadir=$OLDCLUSTER --new-datadir=$NEWCLUSTER

connection to database failed: could not connect to server: No such

file

or directory
Is the server running locally and accepting
connections on Unix domain socket
"/var/run/postgresql/.s.PGSQL.50432"?

could not connect to old postmaster started with the command:
"/usr/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D
"/var/ericsson/esm-data/postgresql-data" -o "-p 50432 -c autovacuum=off
-c autovacuum_freeze_max_age=2000000000 -c listen_addresses='' -c
unix_socket_permissions=0700" start
Failure, exiting

With Best Regards
Akshay
Ericsson OSS MON
Tata Consultancy Services
Mailto: akshay.ballarpure@tcs.com
Website: http://www.tcs.com <http://www.tcs.com/><http://www.tcs.com/>
____________________________________________
Experience certainty. IT Services
Business Solutions
Consulting
____________________________________________

From: Fabio Pardi <f.pardi@portavita.eu>
To: Akshay Ballarpure <akshay.ballarpure@tcs.com>,
pgsql-general@lists.postgresql.org
Date: 04/18/2018 02:35 PM
Subject: Re: pg_upgrade help

------------------------------------------------------------------------

Hi,

i was too fast in reply (and perhaps i should drink my morning coffee
before replying), I will try to be more detailed:

both servers should be able to run at the moment you run pg_upgrade,
that means the 2 servers should have been correctly stopped in advance,
should have their configuration files, and new cluster initialized too.

Then, as Sergei highlights here below, pg_upgrade will take care of the
upgrade process, starting the servers.

Here there is a step by step guide, i considered my best ally when it
was time to upgrade:

https://www.postgresql.org/docs/9.4/static/pgupgrade.html

note point 7:

'stop both servers'

About the port the servers will run on, at point 9 there is some
clarification:

' pg_upgrade defaults to running servers on port 50432 to avoid
unintended client connections. You can use the same port number for

both

clusters when doing an upgrade because the old and new clusters will

not

be running at the same time. However, when checking an old running
server, the old and new port numbers must be different.'

Hope it helps,

Fabio Pardi

On 04/18/2018 10:34 AM, Akshay Ballarpure wrote:

Thanks Fabio for instant reply.

I now started 8.4 with 50432 and 9.4 with default port but still its
failing ...Can you please suggest what is wrong ?

-bash-4.2$ /opt/rh/rh-postgresql94/root/usr/bin/pg_upgrade
--old-bindir=/usr/bin

--new-bindir=/opt/rh/rh-postgresql94/root/usr/bin

--old-datadir=$OLDCLUSTER --new-datadir=$NEWCLUSTER

*failure*
Consult the last few lines of "pg_upgrade_server.log" for
the probable cause of the failure.

There seems to be a postmaster servicing the old cluster.
Please shutdown that postmaster and try again.
Failure, exiting
-bash-4.2$ ps -eaf | grep postgres
root 8646 9365 0 08:07 pts/1 00:00:00 su - postgres
postgres 8647 8646 0 08:07 pts/1 00:00:00 -bash
postgres 9778 1 0 09:17 ? 00:00:00 /usr/bin/postgres -p
50432 -D /var/ericsson/esm-data/postgresql-data/
postgres 9779 9778 0 09:17 ? 00:00:00 postgres: logger

process

postgres 9781 9778 0 09:17 ? 00:00:00 postgres: writer

process

postgres 9782 9778 0 09:17 ? 00:00:00 postgres: wal writer
process
postgres 9783 9778 0 09:17 ? 00:00:00 postgres: autovacuum
launcher process
postgres 9784 9778 0 09:17 ? 00:00:00 postgres: stats
collector process
postgres 9900 1 0 09:20 ? 00:00:00
/opt/rh/rh-postgresql94/root/usr/bin/postgres -D
/var/ericsson/esm-data/postgresql-data-9.4/
postgres 9901 9900 0 09:20 ? 00:00:00 postgres: logger

process

postgres 9903 9900 0 09:20 ? 00:00:00 postgres: checkpointer
process
postgres 9904 9900 0 09:20 ? 00:00:00 postgres: writer

process

postgres 9905 9900 0 09:20 ? 00:00:00 postgres: wal writer
process
postgres 9906 9900 0 09:20 ? 00:00:00 postgres: autovacuum
launcher process
postgres 9907 9900 0 09:20 ? 00:00:00 postgres: stats
collector process
postgres 9926 8647 0 09:21 pts/1 00:00:00 ps -eaf
postgres 9927 8647 0 09:21 pts/1 00:00:00 grep --color=auto

postgres

-bash-4.2$ netstat -antp | grep 50432
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 127.0.0.1:50432 0.0.0.0:*
LISTEN 9778/postgres
tcp6 0 0 ::1:50432 :::*
LISTEN 9778/postgres
-bash-4.2$ netstat -antp | grep 5432
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 127.0.0.1:5432 0.0.0.0:*
LISTEN 9900/postgres
tcp6 0 0 ::1:5432 :::*
LISTEN 9900/postgres

-----------------------------------------------------------------
pg_upgrade run on Wed Apr 18 09:24:47 2018
-----------------------------------------------------------------

command: "/usr/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D
"/var/ericsson/esm-data/postgresql-data" -o "-p 50432 -c

autovacuum=off

-c autovacuum_freeze_max_age=2000000000 -c listen_addresses='' -c
unix_socket_permissions=0700" start >> "pg_upgrade_server.log" 2>&1
pg_ctl: another server might be running; trying to start server anyway
FATAL: lock file "postmaster.pid" already exists
HINT: Is another postmaster (PID 9778) running in data directory
"/var/ericsson/esm-data/postgresql-data"?
pg_ctl: could not start server
Examine the log output.

[root@ms-esmon /]# cat
./var/ericsson/esm-data/postgresql-data-9.4/postmaster.pid
9900
/var/ericsson/esm-data/postgresql-data-9.4
1524039630
5432
/var/run/postgresql
localhost
5432001 2031616

[root@ms-esmon /]# cat
./var/ericsson/esm-data/postgresql-data/postmaster.pid
9778
/var/ericsson/esm-data/postgresql-data
50432001 1998850

With Best Regards
Akshay

From: Fabio Pardi <f.pardi@portavita.eu>
To: Akshay Ballarpure <akshay.ballarpure@tcs.com>,
pgsql-general@lists.postgresql.org
Date: 04/18/2018 01:06 PM
Subject: Re: pg_upgrade help

------------------------------------------------------------------------

Hi,

please avoid crossposting to multiple mailing lists.

You need to run both versions of the database, the old and the new.

They need to run on different ports (note that it is impossible to run

different processes on the same port, that's not a postgresql thing)

On 04/18/2018 09:30 AM, Akshay Ballarpure wrote:

Hi all,
I need help on pg_upgrade from 8.4 to 9.4 version. Appreciate urgent
response.
Installed both version and stopped it. Do i need to run both version

only one 8.4 or 9.4 . Both should run on 50432 ?

-bash-4.2$ id
uid=26(postgres) gid=26(postgres) groups=26(postgres)
context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023

-bash-4.2$ export OLDCLUSTER=/var/ericsson/esm-data/postgresql-data

-- 8.4 data
-bash-4.2$ export

NEWCLUSTER=/var/ericsson/esm-data/postgresql-data-9.4

-- 9.4 data

-bash-4.2$ /opt/rh/rh-postgresql94/root/usr/bin/pg_upgrade
--old-bindir=/usr/bin

--new-bindir=/opt/rh/rh-postgresql94/root/usr/bin

--old-datadir=$OLDCLUSTER --new-datadir=$NEWCLUSTER

*connection to database failed: could not connect to server: No such
file or directory*
Is the server running locally and accepting
connections on Unix domain socket
"/var/run/postgresql/.s.PGSQL.50432"?

could not connect to old postmaster started with the command:
"/usr/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D
"/var/ericsson/esm-data/postgresql-data" -o "-p 50432 -c

autovacuum=off

Show quoted text

-c autovacuum_freeze_max_age=2000000000 -c listen_addresses='' -c
unix_socket_permissions=0700" start
Failure, exiting

With Best Regards
Akshay

=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you

#13

Akshay Ballarpure

akshay.ballarpure@tcs.com

almost 8 years ago

In reply to: Akshay Ballarpure (#1)

Re: pg_upgrade help

Hi Fabio,
Thanks so much for figuring out an issue..!!! much appreciated.
i have stopped both postgres version (8.4 and 9.4)

-bash-4.2$ export PGDATA=/var/ericsson/esm-data/postgresql-data -
postgresql 8.4
-bash-4.2$ pg_ctl stop -mfast
waiting for server to shut down.... done
server stopped

-bash-4.2$ export PGDATA=/var/ericsson/esm-data/postgresql-data-9.4/ -
postgresql 9.4
-bash-4.2$ ps -eaf | grep postgre^C
-bash-4.2$ /opt/rh/rh-postgresql94/root/usr/bin/pg_ctl stop -mfast
waiting for server to shut down.... done
server stopped

And set below environment variables on terminal where i ran pg_upgrade.
and its working fine. thanks so much for figuring out an issue..!!! much
appreciated.

-bash-4.2$ echo $PGDATA
/var/ericsson/esm-data/postgresql-data - postgresql 8.4
-bash-4.2$ echo $PGHOST
/var/run/postgresql

-bash-4.2$ env | grep PG
PGHOST=/var/run/postgresql
PGDATA=/var/ericsson/esm-data/postgresql-data

Performing Consistency Checks
-----------------------------
Checking cluster versions ok
Checking database user is a superuser ok
Checking database connection settings ok
Checking for prepared transactions ok
Checking for reg* system OID user data types ok
Checking for contrib/isn with bigint-passing mismatch ok
Checking for invalid "line" user columns ok
Checking for large objects ok
Creating dump of global objects ok
Creating dump of database schemas
ok
Checking for presence of required libraries ok
Checking database user is a superuser ok
Checking for prepared transactions ok

If pg_upgrade fails after this point, you must re-initdb the
new cluster before continuing.

Performing Upgrade
------------------
Analyzing all rows in the new cluster ok
Freezing all rows on the new cluster ok
Deleting files from new pg_clog ok
Copying old pg_clog to new server ok
Setting next transaction ID and epoch for new cluster ok
Deleting files from new pg_multixact/offsets ok
Setting oldest multixact ID on new cluster ok
Resetting WAL archives ok
Setting frozenxid and minmxid counters in new cluster ok
Restoring global objects in the new cluster ok
Adding support functions to new cluster ok
Restoring database schemas in the new cluster
ok
Setting minmxid counter in new cluster ok
Removing support functions from new cluster ok
Copying user relation files
ok
Setting next OID for new cluster ok
Sync data directory to disk ok
Creating script to analyze new cluster ok
Creating script to delete old cluster ok
Checking for large objects ok

Upgrade Complete
----------------
Optimizer statistics are not transferred by pg_upgrade so,
once you start the new server, consider running:
analyze_new_cluster.sh

Running this script will delete the old cluster's data files:
delete_old_cluster.sh

Now few more questions..

I migrated export PGDATA=/var/ericsson/esm-data/postgresql-data -
postgresql 8.4
I can start 9.4 with above PGDATA right ?
analyze_new_cluster.sh -- is this script will be from 9.4 ?

From: Akshay Ballarpure/HYD/TCS
To: Fabio Pardi <f.pardi@portavita.eu>
Cc: pgsql-general@lists.postgresql.org
Date: 04/19/2018 06:24 PM
Subject: Re: pg_upgrade help

Hi Fabio,
I think you have found the problem. Please find o/p below.

9.4
===

-bash-4.2$ psql
psql (8.4.20, server 9.4.9)
WARNING: psql version 8.4, server version 9.4.
Some psql features might not work.
Type "help" for help.

postgres=#

-bash-4.2$ /opt/rh/rh-postgresql94/root/usr/bin/psql
psql (9.4.9)
Type "help" for help.

postgres=#

8.4
====

-bash-4.2$ psql -p 50432
psql: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/tmp/.s.PGSQL.50432"?

==========================================================================================================

After setting PGHOST, i can connect to PSQL

-bash-4.2$ echo $PGHOST
/var/run/postgresql
-bash-4.2$ psql -p 50432
psql (8.4.20)
Type "help" for help.

postgres=#

From: Fabio Pardi <f.pardi@portavita.eu>
To: Akshay Ballarpure <akshay.ballarpure@tcs.com>,
pgsql-general@lists.postgresql.org
Date: 04/19/2018 03:45 PM
Subject: Re: pg_upgrade help

Hi,

while trying to reproduce your problem, i noticed that on my Centos 6
installations Postgres 8.4 and Postgres 9.6 (I do not have 9.4 readily
available) store the socket in different places:

Postgres 9.6.6 uses /var/run/postgresql/

Postgres 8.4 uses /tmp/

therefore using default settings, i can connect to 9.6 but not 8.4 without
specifying where the socket is

Connect to 9.6

12:01 postgres@machine:~# psql
psql (8.4.20, server 9.6.6)
WARNING: psql version 8.4, server version 9.6.
Some psql features might not work.
Type "help" for help.

---------

Connect to 8.4

12:04 postgres@machine:~# psql -h /tmp
psql (8.4.20)
Type "help" for help.

I think you might be incurring in the same problem.

Can you confirm it?

regards,

fabio pardi

On 04/19/2018 09:37 AM, Akshay Ballarpure wrote:

Hi Fabio,
Yes i ran initdb on new database and able to start as below.

[root@ms-esmon root]# su - postgres -c "/usr/bin/postgres -p 50432 -D

/var/ericsson/esm-data/postgresql-data/ 2>&1 &"

[root@ms-esmon root]# su - postgres -c

"/opt/rh/rh-postgresql94/root/usr/bin/postgres -D
/var/ericsson/esm-data/postgresql-data-9.4/ 2>&1 &"

[root@ms-esmon root]# 2018-04-19 08:17:53.553 IST LOG: redirecting log

output to logging collector process

2018-04-19 08:17:53.553 IST HINT: Future log output will appear in

directory "pg_log".

[root@ms-esmon root]#
[root@ms-esmon root]# ps -eaf | grep postgre
sroot 8646 9365 0 Apr18 pts/1 00:00:00 su - postgres
postgres 8647 8646 0 Apr18 pts/1 00:00:00 -bash
postgres 28009 1 2 08:17 ? 00:00:00 /usr/bin/postgres -p

50432 -D /var/ericsson/esm-data/postgresql-data/ *--8.4*

postgres 28010 28009 0 08:17 ? 00:00:00 postgres: logger process
postgres 28012 28009 0 08:17 ? 00:00:00 postgres: writer process
postgres 28013 28009 0 08:17 ? 00:00:00 postgres: wal writer

process

postgres 28014 28009 0 08:17 ? 00:00:00 postgres: autovacuum

launcher process

postgres 28015 28009 0 08:17 ? 00:00:00 postgres: stats

collector process

postgres 28048 1 0 08:17 ? 00:00:00

/opt/rh/rh-postgresql94/root/usr/bin/postgres -D
/var/ericsson/esm-data/postgresql-data-9.4/

postgres 28049 28048 0 08:17 ? 00:00:00 postgres: logger process
postgres 28051 28048 0 08:17 ? 00:00:00 postgres: checkpointer

process

postgres 28052 28048 0 08:17 ? 00:00:00 postgres: writer process
postgres 28053 28048 0 08:17 ? 00:00:00 postgres: wal writer

process

postgres 28054 28048 0 08:17 ? 00:00:00 postgres: autovacuum

launcher process

postgres 28055 28048 0 08:17 ? 00:00:00 postgres: stats

collector process

root 28057 2884 0 08:17 pts/0 00:00:00 grep --color=auto

postgre

Also i am able to start db with the command provided by you and run

psql.

/opt/rh/rh-postgresql94/root/usr/bin/pg_ctl start -o "-p 50432 -c

listen_addresses='' -c unix_socket_permissions=0700" -D
/var/ericsson/esm-data/postgresql-data-9.4/

pg_ctl: another server might be running; trying to start server anyway
server starting
-bash-4.2$ 2018-04-19 08:22:46.527 IST LOG: redirecting log output to

logging collector process

2018-04-19 08:22:46.527 IST HINT: Future log output will appear in

directory "pg_log".

-bash-4.2$ ps -eaf | grep postg
root 8646 9365 0 Apr18 pts/1 00:00:00 su - postgres
postgres 8647 8646 0 Apr18 pts/1 00:00:00 -bash
postgres 28174 1 0 08:22 pts/1 00:00:00

/opt/rh/rh-postgresql94/root/usr/bin/postgres -D
/var/ericsson/esm-data/postgresql-data-9.4 -p 50432 -c listen_addresses=
-c unix_socket_permissions=0700

postgres 28175 28174 0 08:22 ? 00:00:00 postgres: logger process
postgres 28177 28174 0 08:22 ? 00:00:00 postgres: checkpointer

process

postgres 28178 28174 0 08:22 ? 00:00:00 postgres: writer process
postgres 28179 28174 0 08:22 ? 00:00:00 postgres: wal writer

process

postgres 28180 28174 0 08:22 ? 00:00:00 postgres: autovacuum

launcher process

postgres 28181 28174 0 08:22 ? 00:00:00 postgres: stats

collector process

postgres 28182 8647 0 08:22 pts/1 00:00:00 ps -eaf
postgres 28183 8647 0 08:22 pts/1 00:00:00 grep --color=auto postg

-bash-4.2$ psql -p 50432 -h /var/run/postgresql -U rhqadmin -d rhq
psql (8.4.20, server 9.4.9)
WARNING: psql version 8.4, server version 9.4.
Some psql features might not work.
Type "help" for help.

rhq=>

Still its failing...

-bash-4.2$ ps -efa | grep postgre
root 8646 9365 0 Apr18 pts/1 00:00:00 su - postgres
postgres 8647 8646 0 Apr18 pts/1 00:00:00 -bash
postgres 28349 8647 0 08:34 pts/1 00:00:00 ps -efa
postgres 28350 8647 0 08:34 pts/1 00:00:00 grep --color=auto

postgre

-bash-4.2$ echo $OLDCLUSTER
/usr/bin/postgres
-bash-4.2$ echo $NEWCLUSTER
/opt/rh/rh-postgresql94/

[root@ms-esmon rh-postgresql94]#

Performing Consistency Checks
-----------------------------
Checking cluster versions ok

connection to database failed: could not connect to server: No such file

or directory

Is the server running locally and accepting
connections on Unix domain socket

"/var/run/postgresql/.s.PGSQL.50432"?

could not connect to old postmaster started with the command:
"/usr/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D

"/var/ericsson/esm-data/postgresql-data" -o "-p 50432 -c autovacuum=off -c
autovacuum_freeze_max_age=2000000000 -c listen_addresses='' -c
unix_socket_permissions=0700" start

Failure, exiting

With Best Regards
Akshay
Ericsson OSS MON
Tata Consultancy Services
Mailto: akshay.ballarpure@tcs.com
Website: http://www.tcs.com <http://www.tcs.com/>
____________________________________________
Experience certainty. IT Services
Business Solutions
Consulting
____________________________________________

From: Fabio Pardi <f.pardi@portavita.eu>
To: Akshay Ballarpure <akshay.ballarpure@tcs.com>
Cc: pgsql-general@lists.postgresql.org
Date: 04/18/2018 06:17 PM
Subject: Re: pg_upgrade help

did you run initdb on the new db?

what happens if you manually start the new db?

/opt/rh/rh-postgresql94/root/usr/bin/pg_ctl start -o "-p 50432 -c
listen_addresses='' -c unix_socket_permissions=0700" -D $NEWCLUSTER

after starting it, can you connect to it using psql?

psql -p 50432 -h /var/run/postgresql -U your_user _db_

regards,

fabio pardi

On 04/18/2018 02:02 PM, Akshay Ballarpure wrote:

Hi Fabio,
sorry to bother you again, its still failing with stopping both server
(8.4 and 9.4)

-bash-4.2$ /opt/rh/rh-postgresql94/root/usr/bin/pg_upgrade
--old-bindir=/usr/bin --new-bindir=/opt/rh/rh-postgresql94/root/usr/bin
--old-datadir=$OLDCLUSTER --new-datadir=$NEWCLUSTER

connection to database failed: could not connect to server: No such

file

or directory
Is the server running locally and accepting
connections on Unix domain socket
"/var/run/postgresql/.s.PGSQL.50432"?

could not connect to old postmaster started with the command:
"/usr/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D
"/var/ericsson/esm-data/postgresql-data" -o "-p 50432 -c autovacuum=off
-c autovacuum_freeze_max_age=2000000000 -c listen_addresses='' -c
unix_socket_permissions=0700" start
Failure, exiting

With Best Regards
Akshay
Ericsson OSS MON
Tata Consultancy Services
Mailto: akshay.ballarpure@tcs.com
Website: http://www.tcs.com <http://www.tcs.com/><http://www.tcs.com/>
____________________________________________
Experience certainty. IT Services
Business Solutions
Consulting
____________________________________________

From: Fabio Pardi <f.pardi@portavita.eu>
To: Akshay Ballarpure <akshay.ballarpure@tcs.com>,
pgsql-general@lists.postgresql.org
Date: 04/18/2018 02:35 PM
Subject: Re: pg_upgrade help

------------------------------------------------------------------------

Hi,

i was too fast in reply (and perhaps i should drink my morning coffee
before replying), I will try to be more detailed:

both servers should be able to run at the moment you run pg_upgrade,
that means the 2 servers should have been correctly stopped in advance,
should have their configuration files, and new cluster initialized too.

Then, as Sergei highlights here below, pg_upgrade will take care of the
upgrade process, starting the servers.

Here there is a step by step guide, i considered my best ally when it
was time to upgrade:

https://www.postgresql.org/docs/9.4/static/pgupgrade.html

note point 7:

'stop both servers'

About the port the servers will run on, at point 9 there is some
clarification:

' pg_upgrade defaults to running servers on port 50432 to avoid
unintended client connections. You can use the same port number for

both

clusters when doing an upgrade because the old and new clusters will

not

be running at the same time. However, when checking an old running
server, the old and new port numbers must be different.'

Hope it helps,

Fabio Pardi

On 04/18/2018 10:34 AM, Akshay Ballarpure wrote:

Thanks Fabio for instant reply.

I now started 8.4 with 50432 and 9.4 with default port but still its
failing ...Can you please suggest what is wrong ?

-bash-4.2$ /opt/rh/rh-postgresql94/root/usr/bin/pg_upgrade
--old-bindir=/usr/bin

--new-bindir=/opt/rh/rh-postgresql94/root/usr/bin

--old-datadir=$OLDCLUSTER --new-datadir=$NEWCLUSTER

*failure*
Consult the last few lines of "pg_upgrade_server.log" for
the probable cause of the failure.

There seems to be a postmaster servicing the old cluster.
Please shutdown that postmaster and try again.
Failure, exiting
-bash-4.2$ ps -eaf | grep postgres
root 8646 9365 0 08:07 pts/1 00:00:00 su - postgres
postgres 8647 8646 0 08:07 pts/1 00:00:00 -bash
postgres 9778 1 0 09:17 ? 00:00:00 /usr/bin/postgres -p
50432 -D /var/ericsson/esm-data/postgresql-data/
postgres 9779 9778 0 09:17 ? 00:00:00 postgres: logger

process

postgres 9781 9778 0 09:17 ? 00:00:00 postgres: writer

process

postgres 9782 9778 0 09:17 ? 00:00:00 postgres: wal writer
process
postgres 9783 9778 0 09:17 ? 00:00:00 postgres: autovacuum
launcher process
postgres 9784 9778 0 09:17 ? 00:00:00 postgres: stats
collector process
postgres 9900 1 0 09:20 ? 00:00:00
/opt/rh/rh-postgresql94/root/usr/bin/postgres -D
/var/ericsson/esm-data/postgresql-data-9.4/
postgres 9901 9900 0 09:20 ? 00:00:00 postgres: logger

process

postgres 9903 9900 0 09:20 ? 00:00:00 postgres: checkpointer
process
postgres 9904 9900 0 09:20 ? 00:00:00 postgres: writer

process

postgres 9905 9900 0 09:20 ? 00:00:00 postgres: wal writer
process
postgres 9906 9900 0 09:20 ? 00:00:00 postgres: autovacuum
launcher process
postgres 9907 9900 0 09:20 ? 00:00:00 postgres: stats
collector process
postgres 9926 8647 0 09:21 pts/1 00:00:00 ps -eaf
postgres 9927 8647 0 09:21 pts/1 00:00:00 grep --color=auto

postgres

-bash-4.2$ netstat -antp | grep 50432
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 127.0.0.1:50432 0.0.0.0:*
LISTEN 9778/postgres
tcp6 0 0 ::1:50432 :::*
LISTEN 9778/postgres
-bash-4.2$ netstat -antp | grep 5432
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 127.0.0.1:5432 0.0.0.0:*
LISTEN 9900/postgres
tcp6 0 0 ::1:5432 :::*
LISTEN 9900/postgres

-----------------------------------------------------------------
pg_upgrade run on Wed Apr 18 09:24:47 2018
-----------------------------------------------------------------

command: "/usr/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D
"/var/ericsson/esm-data/postgresql-data" -o "-p 50432 -c

autovacuum=off

-c autovacuum_freeze_max_age=2000000000 -c listen_addresses='' -c
unix_socket_permissions=0700" start >> "pg_upgrade_server.log" 2>&1
pg_ctl: another server might be running; trying to start server anyway
FATAL: lock file "postmaster.pid" already exists
HINT: Is another postmaster (PID 9778) running in data directory
"/var/ericsson/esm-data/postgresql-data"?
pg_ctl: could not start server
Examine the log output.

[root@ms-esmon /]# cat
./var/ericsson/esm-data/postgresql-data-9.4/postmaster.pid
9900
/var/ericsson/esm-data/postgresql-data-9.4
1524039630
5432
/var/run/postgresql
localhost
5432001 2031616

[root@ms-esmon /]# cat
./var/ericsson/esm-data/postgresql-data/postmaster.pid
9778
/var/ericsson/esm-data/postgresql-data
50432001 1998850

With Best Regards
Akshay

From: Fabio Pardi <f.pardi@portavita.eu>
To: Akshay Ballarpure <akshay.ballarpure@tcs.com>,
pgsql-general@lists.postgresql.org
Date: 04/18/2018 01:06 PM
Subject: Re: pg_upgrade help

------------------------------------------------------------------------

Hi,

please avoid crossposting to multiple mailing lists.

You need to run both versions of the database, the old and the new.

They need to run on different ports (note that it is impossible to run

different processes on the same port, that's not a postgresql thing)

On 04/18/2018 09:30 AM, Akshay Ballarpure wrote:

Hi all,
I need help on pg_upgrade from 8.4 to 9.4 version. Appreciate urgent
response.
Installed both version and stopped it. Do i need to run both version

only one 8.4 or 9.4 . Both should run on 50432 ?

-bash-4.2$ id
uid=26(postgres) gid=26(postgres) groups=26(postgres)
context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023

-bash-4.2$ export OLDCLUSTER=/var/ericsson/esm-data/postgresql-data

-- 8.4 data
-bash-4.2$ export

NEWCLUSTER=/var/ericsson/esm-data/postgresql-data-9.4

-- 9.4 data

-bash-4.2$ /opt/rh/rh-postgresql94/root/usr/bin/pg_upgrade
--old-bindir=/usr/bin

--new-bindir=/opt/rh/rh-postgresql94/root/usr/bin

--old-datadir=$OLDCLUSTER --new-datadir=$NEWCLUSTER

*connection to database failed: could not connect to server: No such
file or directory*
Is the server running locally and accepting
connections on Unix domain socket
"/var/run/postgresql/.s.PGSQL.50432"?

could not connect to old postmaster started with the command:
"/usr/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D
"/var/ericsson/esm-data/postgresql-data" -o "-p 50432 -c

autovacuum=off

Show quoted text

-c autovacuum_freeze_max_age=2000000000 -c listen_addresses='' -c
unix_socket_permissions=0700" start
Failure, exiting

With Best Regards
Akshay

=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you

Import Notes

Reply to msg id not found: OFFF84F36F.6794675A-ON65258274.0046D83F-65258274.0046EC0A@LocalDomain

#14

Fabio Pardi

f.pardi@portavita.eu

almost 8 years ago

In reply to: Akshay Ballarpure (#13)

Re: pg_upgrade help

Hi Akshay,

I m glad it worked.

* Your new data folder will be on /var/ericsson/esm-data/postgresql-data-9.4/ therefore you should set PGDATA accordingly

* analyze_new_cluster.sh runs on the new cluster, 9.4. Indeed you should start the db first, as mentioned in the upgrade message.

If you are happy with your upgrade, you can cleanup the leftovers running:

delete_old_cluster.sh

regards,

fabio pardi

Show quoted text

On 04/20/2018 11:24 AM, Akshay Ballarpure wrote:

Hi Fabio,
*Thanks so much for figuring out an issue..!!! much appreciated.*
i have stopped both postgres version (8.4 and 9.4)

-bash-4.2$ export PGDATA=/var/ericsson/esm-data/postgresql-data - postgresql 8.4
-bash-4.2$ pg_ctl stop -mfast
waiting for server to shut down.... done
server stopped

-bash-4.2$ export PGDATA=/var/ericsson/esm-data/postgresql-data-9.4/ - postgresql 9.4
-bash-4.2$ ps -eaf | grep postgre^C
-bash-4.2$ /opt/rh/rh-postgresql94/root/usr/bin/pg_ctl stop -mfast
waiting for server to shut down.... done
server stopped

And set below environment variables on terminal where i ran pg_upgrade. and*its working fine. thanks so much for figuring out an issue..!!! much appreciated.*

-bash-4.2$ echo $PGDATA
/var/ericsson/esm-data/postgresql-data - postgresql 8.4
-bash-4.2$ echo $PGHOST
/var/run/postgresql

-bash-4.2$ env | grep PG
PGHOST=/var/run/postgresql
PGDATA=/var/ericsson/esm-data/postgresql-data

/opt/rh/rh-postgresql94/root/usr/bin/pg_upgrade --old-bindir=/usr/bin --new-bindir=/opt/rh/rh-postgresql94/root/usr/bin --old-datadir=/var/ericsson/esm-data/postgresql-data --new-datadir=/var/ericsson/esm-data/postgresql-data-9.4

Performing Consistency Checks
-----------------------------
Checking cluster versions ok
Checking database user is a superuser ok
Checking database connection settings ok
Checking for prepared transactions ok
Checking for reg* system OID user data types ok
Checking for contrib/isn with bigint-passing mismatch ok
Checking for invalid "line" user columns ok
Checking for large objects ok
Creating dump of global objects ok
Creating dump of database schemas
ok
Checking for presence of required libraries ok
Checking database user is a superuser ok
Checking for prepared transactions ok

If pg_upgrade fails after this point, you must re-initdb the
new cluster before continuing.

Performing Upgrade
------------------
Analyzing all rows in the new cluster ok
Freezing all rows on the new cluster ok
Deleting files from new pg_clog ok
Copying old pg_clog to new server ok
Setting next transaction ID and epoch for new cluster ok
Deleting files from new pg_multixact/offsets ok
Setting oldest multixact ID on new cluster ok
Resetting WAL archives ok
Setting frozenxid and minmxid counters in new cluster ok
Restoring global objects in the new cluster ok
Adding support functions to new cluster ok
Restoring database schemas in the new cluster
ok
Setting minmxid counter in new cluster ok
Removing support functions from new cluster ok
Copying user relation files
ok
Setting next OID for new cluster ok
Sync data directory to disk ok
Creating script to analyze new cluster ok
Creating script to delete old cluster ok
Checking for large objects ok

Upgrade Complete
----------------
Optimizer statistics are not transferred by pg_upgrade so,
once you start the new server, consider running:
analyze_new_cluster.sh

Running this script will delete the old cluster's data files:
delete_old_cluster.sh

Now few more questions..

I migrated export PGDATA=/var/ericsson/esm-data/postgresql-data - postgresql 8.4
I can start 9.4 with above PGDATA right ?
analyze_new_cluster.sh -- is this script will be from 9.4 ?

With Best Regards
Akshay
Ericsson OSS MON
Tata Consultancy Services
Mailto: akshay.ballarpure@tcs.com
Website: http://www.tcs.com <http://www.tcs.com/>
____________________________________________
Experience certainty. IT Services
Business Solutions
Consulting
____________________________________________

From: Akshay Ballarpure/HYD/TCS
To: Fabio Pardi <f.pardi@portavita.eu>
Cc: pgsql-general@lists.postgresql.org
Date: 04/19/2018 06:24 PM
Subject: Re: pg_upgrade help
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Hi Fabio,
I think you have found the problem. Please find o/p below.

-bash-4.2$ ps -aef | grep postgres
postgres 478 1 0 13:40 ? 00:00:00 /usr/bin/postgres -p 50432 -D /var/ericsson/esm-data/postgresql-data/
postgres 490 478 0 13:40 ? 00:00:00 postgres: logger process
postgres 492 478 0 13:40 ? 00:00:00 postgres: writer process
postgres 493 478 0 13:40 ? 00:00:00 postgres: wal writer process
postgres 494 478 0 13:40 ? 00:00:00 postgres: autovacuum launcher process
postgres 495 478 0 13:40 ? 00:00:00 postgres: stats collector process
postgres 528 1 0 13:40 ? 00:00:00 /opt/rh/rh-postgresql94/root/usr/bin/postgres -D /var/ericsson/esm-data/postgresql-data-9.4/
postgres 529 528 0 13:40 ? 00:00:00 postgres: logger process
postgres 531 528 0 13:40 ? 00:00:00 postgres: checkpointer process
postgres 532 528 0 13:40 ? 00:00:00 postgres: writer process
postgres 533 528 0 13:40 ? 00:00:00 postgres: wal writer process
postgres 534 528 0 13:40 ? 00:00:00 postgres: autovacuum launcher process
postgres 535 528 0 13:40 ? 00:00:00 postgres: stats collector process
postgres 734 8647 0 13:50 pts/1 00:00:00 ps -aef
postgres 735 8647 0 13:50 pts/1 00:00:00 grep --color=auto postgres
root 8646 9365 0 Apr18 pts/1 00:00:00 su - postgres
postgres 8647 8646 0 Apr18 pts/1 00:00:00 -bash

9.4
===

-bash-4.2$ psql
psql (8.4.20, server 9.4.9)
WARNING: psql version 8.4, server version 9.4.
Some psql features might not work.
Type "help" for help.

postgres=#

-bash-4.2$ /opt/rh/rh-postgresql94/root/usr/bin/psql
psql (9.4.9)
Type "help" for help.

postgres=#

8.4
====

-bash-4.2$ psql -p 50432
*psql: could not connect to server: No such file or directory*
* Is the server running locally and accepting*
* connections on Unix domain socket "/tmp/.s.PGSQL.50432"?*

==========================================================================================================

After setting PGHOST, i can connect to PSQL

-bash-4.2$ echo $PGHOST
/var/run/postgresql
-bash-4.2$ psql -p 50432
psql (8.4.20)
Type "help" for help.

postgres=#

With Best Regards
Akshay
Ericsson OSS MON
Tata Consultancy Services
Mailto: akshay.ballarpure@tcs.com
Website: http://www.tcs.com <http://www.tcs.com/>
____________________________________________
Experience certainty. IT Services
Business Solutions
Consulting
____________________________________________

From: Fabio Pardi <f.pardi@portavita.eu>
To: Akshay Ballarpure <akshay.ballarpure@tcs.com>, pgsql-general@lists.postgresql.org
Date: 04/19/2018 03:45 PM
Subject: Re: pg_upgrade help
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Hi,

while trying to reproduce your problem, i noticed that on my Centos 6 installations Postgres 8.4 and Postgres 9.6 (I do not have 9.4 readily available) store the socket in different places:

Postgres 9.6.6 uses /var/run/postgresql/

Postgres 8.4 uses /tmp/

therefore using default settings, i can connect to 9.6 but not 8.4 without specifying where the socket is

Connect to 9.6

12:01 postgres@machine:~# psql
psql (8.4.20, server 9.6.6)
WARNING: psql version 8.4, server version 9.6.
Some psql features might not work.
Type "help" for help.

---------

Connect to 8.4

12:01 postgres@machine:~# psql
psql: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?

12:04 postgres@machine:~# psql -h /tmp
psql (8.4.20)
Type "help" for help.

I think you might be incurring in the same problem.

Can you confirm it?

regards,

fabio pardi

On 04/19/2018 09:37 AM, Akshay Ballarpure wrote:

Hi Fabio,
Yes i ran initdb on new database and able to start as below.

[root@ms-esmon root]# su - postgres -c "/usr/bin/postgres -p 50432 -D /var/ericsson/esm-data/postgresql-data/ 2>&1 &"
[root@ms-esmon root]# su - postgres -c "/opt/rh/rh-postgresql94/root/usr/bin/postgres -D /var/ericsson/esm-data/postgresql-data-9.4/ 2>&1 &"
[root@ms-esmon root]# 2018-04-19 08:17:53.553 IST LOG: redirecting log output to logging collector process
2018-04-19 08:17:53.553 IST HINT: Future log output will appear in directory "pg_log".

[root@ms-esmon root]#
[root@ms-esmon root]# ps -eaf | grep postgre
sroot 8646 9365 0 Apr18 pts/1 00:00:00 su - postgres
postgres 8647 8646 0 Apr18 pts/1 00:00:00 -bash
postgres 28009 1 2 08:17 ? 00:00:00 /usr/bin/postgres -p 50432 -D /var/ericsson/esm-data/postgresql-data/ *--8.4*
postgres 28010 28009 0 08:17 ? 00:00:00 postgres: logger process
postgres 28012 28009 0 08:17 ? 00:00:00 postgres: writer process
postgres 28013 28009 0 08:17 ? 00:00:00 postgres: wal writer process
postgres 28014 28009 0 08:17 ? 00:00:00 postgres: autovacuum launcher process
postgres 28015 28009 0 08:17 ? 00:00:00 postgres: stats collector process
postgres 28048 1 0 08:17 ? 00:00:00 /opt/rh/rh-postgresql94/root/usr/bin/postgres -D /var/ericsson/esm-data/postgresql-data-9.4/
postgres 28049 28048 0 08:17 ? 00:00:00 postgres: logger process
postgres 28051 28048 0 08:17 ? 00:00:00 postgres: checkpointer process
postgres 28052 28048 0 08:17 ? 00:00:00 postgres: writer process
postgres 28053 28048 0 08:17 ? 00:00:00 postgres: wal writer process
postgres 28054 28048 0 08:17 ? 00:00:00 postgres: autovacuum launcher process
postgres 28055 28048 0 08:17 ? 00:00:00 postgres: stats collector process
root 28057 2884 0 08:17 pts/0 00:00:00 grep --color=auto postgre

Also i am able to start db with the command provided by you and run psql.

/opt/rh/rh-postgresql94/root/usr/bin/pg_ctl start -o "-p 50432 -c listen_addresses='' -c unix_socket_permissions=0700" -D /var/ericsson/esm-data/postgresql-data-9.4/
pg_ctl: another server might be running; trying to start server anyway
server starting
-bash-4.2$ 2018-04-19 08:22:46.527 IST LOG: redirecting log output to logging collector process
2018-04-19 08:22:46.527 IST HINT: Future log output will appear in directory "pg_log".

-bash-4.2$ ps -eaf | grep postg
root 8646 9365 0 Apr18 pts/1 00:00:00 su - postgres
postgres 8647 8646 0 Apr18 pts/1 00:00:00 -bash
postgres 28174 1 0 08:22 pts/1 00:00:00 /opt/rh/rh-postgresql94/root/usr/bin/postgres -D /var/ericsson/esm-data/postgresql-data-9.4 -p 50432 -c listen_addresses= -c unix_socket_permissions=0700
postgres 28175 28174 0 08:22 ? 00:00:00 postgres: logger process
postgres 28177 28174 0 08:22 ? 00:00:00 postgres: checkpointer process
postgres 28178 28174 0 08:22 ? 00:00:00 postgres: writer process
postgres 28179 28174 0 08:22 ? 00:00:00 postgres: wal writer process
postgres 28180 28174 0 08:22 ? 00:00:00 postgres: autovacuum launcher process
postgres 28181 28174 0 08:22 ? 00:00:00 postgres: stats collector process
postgres 28182 8647 0 08:22 pts/1 00:00:00 ps -eaf
postgres 28183 8647 0 08:22 pts/1 00:00:00 grep --color=auto postg

-bash-4.2$ psql -p 50432 -h /var/run/postgresql -U rhqadmin -d rhq
psql (8.4.20, server 9.4.9)
WARNING: psql version 8.4, server version 9.4.
Some psql features might not work.
Type "help" for help.

rhq=>

Still its failing...

-bash-4.2$ ps -efa | grep postgre
root 8646 9365 0 Apr18 pts/1 00:00:00 su - postgres
postgres 8647 8646 0 Apr18 pts/1 00:00:00 -bash
postgres 28349 8647 0 08:34 pts/1 00:00:00 ps -efa
postgres 28350 8647 0 08:34 pts/1 00:00:00 grep --color=auto postgre

-bash-4.2$ echo $OLDCLUSTER
/usr/bin/postgres
-bash-4.2$ echo $NEWCLUSTER
/opt/rh/rh-postgresql94/

[root@ms-esmon rh-postgresql94]# /opt/rh/rh-postgresql94/root/usr/bin/pg_upgrade --old-bindir=/usr/bin --new-bindir=/opt/rh/rh-postgresql94/root/usr/bin --old-datadir=/var/ericsson/esm-data/postgresql-data --new-datadir=/var/ericsson/esm-data/postgresql-data-9.4

Performing Consistency Checks
-----------------------------
Checking cluster versions ok

connection to database failed: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.50432"?

could not connect to old postmaster started with the command:
"/usr/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D "/var/ericsson/esm-data/postgresql-data" -o "-p 50432 -c autovacuum=off -c autovacuum_freeze_max_age=2000000000 -c listen_addresses='' -c unix_socket_permissions=0700" start
Failure, exiting

With Best Regards
Akshay
Ericsson OSS MON
Tata Consultancy Services
Mailto: akshay.ballarpure@tcs.com
Website: http://www.tcs.com <http://www.tcs.com/><http://www.tcs.com/>
____________________________________________
Experience certainty. IT Services
Business Solutions
Consulting
____________________________________________

From: Fabio Pardi <f.pardi@portavita.eu>
To: Akshay Ballarpure <akshay.ballarpure@tcs.com>
Cc: pgsql-general@lists.postgresql.org
Date: 04/18/2018 06:17 PM
Subject: Re: pg_upgrade help
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- -----

did you run initdb on the new db?

what happens if you manually start the new db?

/opt/rh/rh-postgresql94/root/usr/bin/pg_ctl start -o "-p 50432 -c
listen_addresses='' -c unix_socket_permissions=0700" -D $NEWCLUSTER

after starting it, can you connect to it using psql?

psql -p 50432 -h /var/run/postgresql -U your_user _db_

regards,

fabio pardi

On 04/18/2018 02:02 PM, Akshay Ballarpure wrote:

Hi Fabio,
sorry to bother you again, its still failing with stopping both server
(8.4 and 9.4)

-bash-4.2$ /opt/rh/rh-postgresql94/root/usr/bin/pg_upgrade
--old-bindir=/usr/bin --new-bindir=/opt/rh/rh-postgresql94/root/usr/bin
--old-datadir=$OLDCLUSTER --new-datadir=$NEWCLUSTER

connection to database failed: could not connect to server: No such file
or directory
Is the server running locally and accepting
connections on Unix domain socket
"/var/run/postgresql/.s.PGSQL.50432"?

could not connect to old postmaster started with the command:
"/usr/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D
"/var/ericsson/esm-data/postgresql-data" -o "-p 50432 -c autovacuum=off
-c autovacuum_freeze_max_age=2000000000 -c listen_addresses='' -c
unix_socket_permissions=0700" start
Failure, exiting

With Best Regards
Akshay
Ericsson OSS MON
Tata Consultancy Services
Mailto: akshay.ballarpure@tcs.com
Website: http://www.tcs.com <http://www.tcs.com/><http://www.tcs.com/><http://www.tcs.com/>
____________________________________________
Experience certainty. IT Services
Business Solutions
Consulting
____________________________________________

From: Fabio Pardi <f.pardi@portavita.eu>
To: Akshay Ballarpure <akshay.ballarpure@tcs.com>,
pgsql-general@lists.postgresql.org
Date: 04/18/2018 02:35 PM
Subject: Re: pg_upgrade help
------------------------------------------------------------------------

Hi,

i was too fast in reply (and perhaps i should drink my morning coffee
before replying), I will try to be more detailed:

both servers should be able to run at the moment you run pg_upgrade,
that means the 2 servers should have been correctly stopped in advance,
should have their configuration files, and new cluster initialized too.

Then, as Sergei highlights here below, pg_upgrade will take care of the
upgrade process, starting the servers.

Here there is a step by step guide, i considered my best ally when it
was time to upgrade:

https://www.postgresql.org/docs/9.4/static/pgupgrade.html

note point 7:

'stop both servers'

About the port the servers will run on, at point 9 there is some
clarification:

' pg_upgrade defaults to running servers on port 50432 to avoid
unintended client connections. You can use the same port number for both
clusters when doing an upgrade because the old and new clusters will not
be running at the same time. However, when checking an old running
server, the old and new port numbers must be different.'

Hope it helps,

Fabio Pardi

On 04/18/2018 10:34 AM, Akshay Ballarpure wrote:

Thanks Fabio for instant reply.

I now started 8.4 with 50432 and 9.4 with default port but still its
failing ...Can you please suggest what is wrong ?

-bash-4.2$ /opt/rh/rh-postgresql94/root/usr/bin/pg_upgrade
--old-bindir=/usr/bin --new-bindir=/opt/rh/rh-postgresql94/root/usr/bin
--old-datadir=$OLDCLUSTER --new-datadir=$NEWCLUSTER

*failure*
Consult the last few lines of "pg_upgrade_server.log" for
the probable cause of the failure.

There seems to be a postmaster servicing the old cluster.
Please shutdown that postmaster and try again.
Failure, exiting
-bash-4.2$ ps -eaf | grep postgres
root 8646 9365 0 08:07 pts/1 00:00:00 su - postgres
postgres 8647 8646 0 08:07 pts/1 00:00:00 -bash
postgres 9778 1 0 09:17 ? 00:00:00 /usr/bin/postgres -p
50432 -D /var/ericsson/esm-data/postgresql-data/
postgres 9779 9778 0 09:17 ? 00:00:00 postgres: logger process
postgres 9781 9778 0 09:17 ? 00:00:00 postgres: writer process
postgres 9782 9778 0 09:17 ? 00:00:00 postgres: wal writer
process
postgres 9783 9778 0 09:17 ? 00:00:00 postgres: autovacuum
launcher process
postgres 9784 9778 0 09:17 ? 00:00:00 postgres: stats
collector process
postgres 9900 1 0 09:20 ? 00:00:00
/opt/rh/rh-postgresql94/root/usr/bin/postgres -D
/var/ericsson/esm-data/postgresql-data-9.4/
postgres 9901 9900 0 09:20 ? 00:00:00 postgres: logger process
postgres 9903 9900 0 09:20 ? 00:00:00 postgres: checkpointer
process
postgres 9904 9900 0 09:20 ? 00:00:00 postgres: writer process
postgres 9905 9900 0 09:20 ? 00:00:00 postgres: wal writer
process
postgres 9906 9900 0 09:20 ? 00:00:00 postgres: autovacuum
launcher process
postgres 9907 9900 0 09:20 ? 00:00:00 postgres: stats
collector process
postgres 9926 8647 0 09:21 pts/1 00:00:00 ps -eaf
postgres 9927 8647 0 09:21 pts/1 00:00:00 grep --color=auto postgres

-bash-4.2$ netstat -antp | grep 50432
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 127.0.0.1:50432 0.0.0.0:*
LISTEN 9778/postgres
tcp6 0 0 ::1:50432 :::*
LISTEN 9778/postgres
-bash-4.2$ netstat -antp | grep 5432
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 127.0.0.1:5432 0.0.0.0:*
LISTEN 9900/postgres
tcp6 0 0 ::1:5432 :::*
LISTEN 9900/postgres

-----------------------------------------------------------------
pg_upgrade run on Wed Apr 18 09:24:47 2018
-----------------------------------------------------------------

command: "/usr/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D
"/var/ericsson/esm-data/postgresql-data" -o "-p 50432 -c autovacuum=off
-c autovacuum_freeze_max_age=2000000000 -c listen_addresses='' -c
unix_socket_permissions=0700" start >> "pg_upgrade_server.log" 2>&1
pg_ctl: another server might be running; trying to start server anyway
FATAL: lock file "postmaster.pid" already exists
HINT: Is another postmaster (PID 9778) running in data directory
"/var/ericsson/esm-data/postgresql-data"?
pg_ctl: could not start server
Examine the log output.

[root@ms-esmon /]# cat
./var/ericsson/esm-data/postgresql-data-9.4/postmaster.pid
9900
/var/ericsson/esm-data/postgresql-data-9.4
1524039630
5432
/var/run/postgresql
localhost
5432001 2031616

[root@ms-esmon /]# cat
./var/ericsson/esm-data/postgresql-data/postmaster.pid
9778
/var/ericsson/esm-data/postgresql-data
50432001 1998850

With Best Regards
Akshay

From: Fabio Pardi <f.pardi@portavita.eu>
To: Akshay Ballarpure <akshay.ballarpure@tcs.com>,
pgsql-general@lists.postgresql.org
Date: 04/18/2018 01:06 PM
Subject: Re: pg_upgrade help
------------------------------------------------------------------------

Hi,

please avoid crossposting to multiple mailing lists.

You need to run both versions of the database, the old and the new.

They need to run on different ports (note that it is impossible to run 2
different processes on the same port, that's not a postgresql thing)

On 04/18/2018 09:30 AM, Akshay Ballarpure wrote:

Hi all,
I need help on pg_upgrade from 8.4 to 9.4 version. Appreciate urgent
response.
Installed both version and stopped it. Do i need to run both version or
only one 8.4 or 9.4 . Both should run on 50432 ?

-bash-4.2$ id
uid=26(postgres) gid=26(postgres) groups=26(postgres)
context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023

-bash-4.2$ export OLDCLUSTER=/var/ericsson/esm-data/postgresql-data
-- 8.4 data
-bash-4.2$ export NEWCLUSTER=/var/ericsson/esm-data/postgresql-data-9.4
-- 9.4 data

-bash-4.2$ /opt/rh/rh-postgresql94/root/usr/bin/pg_upgrade
--old-bindir=/usr/bin --new-bindir=/opt/rh/rh-postgresql94/root/usr/bin
--old-datadir=$OLDCLUSTER --new-datadir=$NEWCLUSTER

*connection to database failed: could not connect to server: No such
file or directory*
Is the server running locally and accepting
connections on Unix domain socket
"/var/run/postgresql/.s.PGSQL.50432"?

could not connect to old postmaster started with the command:
"/usr/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D
"/var/ericsson/esm-data/postgresql-data" -o "-p 50432 -c autovacuum=off
-c autovacuum_freeze_max_age=2000000000 -c listen_addresses='' -c
unix_socket_permissions=0700" start
Failure, exiting

With Best Regards
Akshay

=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you