Обсуждение: Upgrade 8.3.6 issues
Hi All, I'm testing for the first time a PG upgrade process, presently running 8.3.4 and try to upgrade to 8.3.6. I have installed 8.3.6 in separate dir - run pg_dumpall using the new PG 8.3.6 version - shutdown the server - create a new db cluster with 8.3.6 initdb -copy pg_gba.conf and postgres.conf to 8.3.6 PG location -Now I can't start the db server using the pg 8.3.6 version ., I'm using same port # default . Here is my message: > pg_ctl status > pg_ctl: no server running >0:bin$ pg_ctl start server starting postgres@cvodb0:bin$ 2009-02-18 08:00:59 PST::@:[16713]:LOG: could not bind IPv6 socket: Address already in use 2009-02-18 08:00:59 PST::@:[16713]:HINT: Is another postmaster already running on port 5432? If not, wait a few seconds and retry. 2009-02-18 08:00:59 PST::@:[16713]:LOG: could not bind IPv4 socket: Address already in use 2009-02-18 08:00:59 PST::@:[16713]:HINT: Is another postmaster already running on port 5432? If not, wait a few seconds and retry. 2009-02-18 08:00:59 PST::@:[16713]:FATAL: could not create any TCP/IP sockets pg_ctl status pg_ctl: no server running What do I miss ?
btw, no dump is required to flip from 8.3x to 8.3x, but testing is a good thing. check the postmaster.pid [postgresql@swallowtail alerts_oamp]$ cat postmaster.pid 2545 /var/database/pgsql/alerts_oamp 5478001 0 alerts_oamp]$ ps -ef | grep 2545 500 2545 1 0 Jan11 ? 00:00:29 /usr/local/pgsql833/bin/postgres -D /var/database/pgsql/alerts_oamp 500 2546 2545 0 Jan11 ? 00:00:00 postgres: logger process 500 2548 2545 0 Jan11 ? 00:00:00 postgres: writer process 500 2549 2545 0 Jan11 ? 00:00:00 postgres: wal writer process 500 2550 2545 0 Jan11 ? 00:00:00 postgres: autovacuum launcher process 500 2551 2545 0 Jan11 ? 00:00:02 postgres: stats collector process On Wed, Feb 18, 2009 at 08:09:57AM -0800, Isabella Ghiurea wrote: > > Hi All, > I'm testing for the first time a PG upgrade process, presently running > 8.3.4 and try to upgrade to 8.3.6. I have installed 8.3.6 in separate dir > - run pg_dumpall using the new PG 8.3.6 version > - shutdown the server > - create a new db cluster with 8.3.6 initdb > -copy pg_gba.conf and postgres.conf to 8.3.6 PG location > -Now I can't start the db server using the pg 8.3.6 version ., I'm using > same port # default . Here is my message: > > pg_ctl status > > pg_ctl: no server running > >0:bin$ pg_ctl start > server starting > postgres@cvodb0:bin$ 2009-02-18 08:00:59 PST::@:[16713]:LOG: could not > bind IPv6 socket: Address already in use > 2009-02-18 08:00:59 PST::@:[16713]:HINT: Is another postmaster already > running on port 5432? If not, wait a few seconds and retry. > 2009-02-18 08:00:59 PST::@:[16713]:LOG: could not bind IPv4 socket: > Address already in use > 2009-02-18 08:00:59 PST::@:[16713]:HINT: Is another postmaster already > running on port 5432? If not, wait a few seconds and retry. > 2009-02-18 08:00:59 PST::@:[16713]:FATAL: could not create any TCP/IP > sockets > pg_ctl status > pg_ctl: no server running > > What do I miss ? > > -- > Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-admin
Thank you , that worked! Isabella Ray Stell wrote: > > btw, no dump is required to flip from 8.3x to 8.3x, but > testing is a good thing. > > check the postmaster.pid > > [postgresql@swallowtail alerts_oamp]$ cat postmaster.pid > 2545 > /var/database/pgsql/alerts_oamp > 5478001 0 > alerts_oamp]$ ps -ef | grep 2545 > 500 2545 1 0 Jan11 ? 00:00:29 > /usr/local/pgsql833/bin/postgres -D /var/database/pgsql/alerts_oamp > 500 2546 2545 0 Jan11 ? 00:00:00 postgres: logger > process > 500 2548 2545 0 Jan11 ? 00:00:00 postgres: writer > process > 500 2549 2545 0 Jan11 ? 00:00:00 postgres: wal writer > process > 500 2550 2545 0 Jan11 ? 00:00:00 postgres: autovacuum > launcher process > 500 2551 2545 0 Jan11 ? 00:00:02 postgres: stats > collector process > > > > > > On Wed, Feb 18, 2009 at 08:09:57AM -0800, Isabella Ghiurea wrote: > > > > Hi All, > > I'm testing for the first time a PG upgrade process, presently running > > 8.3.4 and try to upgrade to 8.3.6. I have installed 8.3.6 in > separate dir > > - run pg_dumpall using the new PG 8.3.6 version > > - shutdown the server > > - create a new db cluster with 8.3.6 initdb > > -copy pg_gba.conf and postgres.conf to 8.3.6 PG location > > -Now I can't start the db server using the pg 8.3.6 version ., I'm using > > same port # default . Here is my message: > > > pg_ctl status > > > pg_ctl: no server running > > >0:bin$ pg_ctl start > > server starting > > postgres@cvodb0:bin$ 2009-02-18 08:00:59 PST::@:[16713]:LOG: could not > > bind IPv6 socket: Address already in use > > 2009-02-18 08:00:59 PST::@:[16713]:HINT: Is another postmaster already > > running on port 5432? If not, wait a few seconds and retry. > > 2009-02-18 08:00:59 PST::@:[16713]:LOG: could not bind IPv4 socket: > > Address already in use > > 2009-02-18 08:00:59 PST::@:[16713]:HINT: Is another postmaster already > > running on port 5432? If not, wait a few seconds and retry. > > 2009-02-18 08:00:59 PST::@:[16713]:FATAL: could not create any TCP/IP > > sockets > > pg_ctl status > > pg_ctl: no server running > > > > What do I miss ? > > > > -- > > Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) > > To make changes to your subscription: > > http://www.postgresql.org/mailpref/pgsql-admin >