pg.ddx.io pgsql-admin@postgresql.org mailing list archivehelp / color / mirror / Atom feed
From: Ziggy Skalski <zskalski@afilias.info>
To: pgsql-admin@postgresql.org
Subject: Re: Postgres update 9.1 to 9.3 - error port 50432
Date: Fri, 30 Jan 2015 14:05:19 -0500
Message-ID: <54CBD5EF.3010704@afilias.info> (raw)
In-Reply-To: <CAOQWw8ShKQEK=18wMjBL4Bt4V4d_N-GVjXzorBxw_XM_Yt15sw@mail.gmail.com>
References: <CAOQWw8ShKQEK=18wMjBL4Bt4V4d_N-GVjXzorBxw_XM_Yt15sw@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
On 15-01-30 12:31 PM, Mauricio Tavares wrote:
> Personal greetings ...
>
> Anyone ever have used pg_upgrade ????
>
> I tried to use it, but is giving the error
>
>
> The following are the commands and the returned error.
>
>
> -bash-4.1$ /usr/pgsql-9.3/bin/pg_upgrade -b /usr/pgsql-9.1/bin -B
> /usr/pgsql-9.3/bin -d /var/lib/pgsql/9.1/data/ -D
> /var/lib/pgsql/9.3/data/ -o "-c
> config_file=/var/lib/pgsql/9.1/data/postgresql.conf" -O "-c
> config_file=/var/lib/pgsql/9.3/data/postgresql.conf"
> Performing Consistency Checks
> -----------------------------
> Checking cluster versions ok
> Checking database user is a superuser ok
> Checking for prepared transactions ok
> Checking for reg* system OID user data types ok
> Checking for contrib/isn with bigint-passing mismatch ok
> Creating dump of global objects ok
> Creating dump of database schemas
> ok
>
> *failure*
> Consult the last few lines of "pg_upgrade_server.log" for
> the probable cause of the failure.
>
> 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/lib/pgsql/.s.PGSQL.50432"?
>
>
> could not connect to new postmaster started with the command:
> "/usr/pgsql-9.3/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D
> "/var/lib/pgsql/9.3/data/" -o "-p 50432 -b -c
> autovacuum_multixact_freeze_max_age=2000000000 -c
> synchronous_commit=off -c fsync=off -c full_page_writes=off-c
> config_file=/var/lib/pgsql/9.3/data/postgresql.conf -c
> listen_addresses='' -c unix_socket_permissions=0700 -c
> unix_socket_directories='/var/lib/pgsql'" start
> Failure, exiting
> -bash-4.1$
>
>
> I've changed the configs postgres the door, but still gives error ....
>
> I tried to force the use of the door with the parameters -p and -P,
> however the error was the same.
>
> Has anyone experienced this situation ???
>
>
> Thanks for listening ..
Hi,
Is there a backend running on port 50432 or is this a typo and it was
supposed to be 5432 in the above pg_upgrade command?
Ziggy
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
view thread (11+ messages) latest in thread
Message-ID: <54CBD5EF.3010704@afilias.info> Permalink: ../54CBD5EF.3010704@afilias.info/ Also on: postgresql.org/message-id/54CBD5EF.3010704@afilias.info ·
reply
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Reply to all the recipients using the --to and --cc options: reply via email To: pgsql-admin@postgresql.org Cc: zskalski@afilias.info Subject: Re: Postgres update 9.1 to 9.3 - error port 50432 In-Reply-To: <54CBD5EF.3010704@afilias.info> * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox