Message-ID: <51C0CADF.6040001@afilias.info>
Date: Tue, 18 Jun 2013 17:02:23 -0400
From: Ziggy Skalski <zskalski@afilias.info>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:17.0) Gecko/20130330 Thunderbird/17.0.5
MIME-Version: 1.0
To: pgsql-admin@postgresql.org
Subject: Re: Re: PG_UPGRADE issues "this utility can only upgrade
 to postgresql version 9.2."
References: <1371491646614-5759509.post@n5.nabble.com>
 <20130617230803.GC1997@momjian.us> <1371578763431-5759711.post@n5.nabble.com>
In-Reply-To: <1371578763431-5759711.post@n5.nabble.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org


On 13-06-18 02:06 PM, jmfox180 wrote:
> so after trying i advance just a little bit but when running pg_upgrade for a
> check or upgrade
>
> i get:
>
> pg_control values:
>
> First log file ID after reset:        0
> First log file segment after reset:   2
> pg_control version number:            922
> Catalog version number:               201204301
> Database system identifier:           5890882831378718649
> Latest checkpoint's TimeLineID:       1
> Latest checkpoint's full_page_writes: on
> Latest checkpoint's NextXID:          0/726
> Latest checkpoint's NextOID:          12047
> Latest checkpoint's NextMultiXactId:  1
> Latest checkpoint's NextMultiOffset:  0
> Latest checkpoint's oldestXID:        716
> Latest checkpoint's oldestXID's DB:   1
> Latest checkpoint's oldestActiveXID:  0
> Maximum data alignment:               4
> Database block size:                  8192
> Blocks per segment of large relation: 131072
> WAL block size:                       8192
> Bytes per WAL segment:                16777216
> Maximum length of identifiers:        64
> Maximum columns in an index:          32
> Maximum size of a TOAST chunk:        2000
> Date/time type storage:               floating-point numbers
> Float4 argument passing:              by value
> Float8 argument passing:              by reference
> "/usr/local/pgsql.old/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D
> "/usr/local/pgsql.old/data/" -o "-p 5432 -c autovacuum=off -c
> autovacuum_freeze_max_age=2000000000  -c listen_addresses='' -c
> unix_socket_permissions=0700" start >> "pg_upgrade_server.log" 2>&1
> *failure*
> There were problems executing ""/usr/local/pgsql.old/bin/pg_ctl" -w -l
> "pg_upgrade_server.log" -D "/usr/local/pgsql.old/data/" -o "-p 5432 -c
> autovacuum=off -c autovacuum_freeze_max_age=2000000000  -c
> listen_addresses='' -c unix_socket_permissions=0700" start >>
> "pg_upgrade_server.log" 2>&1"
> Consult the last few lines of "pg_upgrade_server.log" for
> the probable cause of the failure.
>
> pg_ctl failed to start the old server, or connection failed
> Failure, exiting
>
>
> when going to the log file:
>
>    pg_upgrade run on Tue Jun 18 11:58:08 2013
> -----------------------------------------------------------------
>
> command: "/usr/local/pgsql.old/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D
> "/usr/local/pgsql.old/data/" -o "-p 5432 -c autovacuum=off -c $
> waiting for server to start....LOG:  database system was shut down at
> 2013-06-18 11:30:47 CST
> LOG:  database system is ready to accept connections
> ...........................................................could not start
> server
>
>   
>
>
>
>
> --
> View this message in context: http://postgresql.1045698.n5.nabble.com/PG-UPGRADE-issues-this-utility-can-only-upgrade-to-postgresql-version-9-2-tp5759509p5759711.html
> Sent from the PostgreSQL - admin mailing list archive at Nabble.com.
>
>

Just a shot, but are you sure the user you're running the pg_upgrade 
with has permissions to start the backend in /usr/local/pgsql.old/data/ 
?   Can you do a test using pg_ctl? anything in postgres log?

Ziggy


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin