Message-ID: <51C1E5A9.2030502@afilias.info>
Date: Wed, 19 Jun 2013 13:08:57 -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>
 <51C0CADF.6040001@afilias.info> <1371651412536-5759873.post@n5.nabble.com>
In-Reply-To: <1371651412536-5759873.post@n5.nabble.com>
Content-Type: multipart/alternative;
 boundary="------------090208070004090700030704"
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

This is a multi-part message in MIME format.
--------------090208070004090700030704
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


On 13-06-19 10:16 AM, jmfox180 wrote:
> so i tried to do a
>
> /usr/local/pgsql.old/bin/postgres -D /usr/local/pgsql.old/data start
>
> LOG:  database system was shut down at 2013-06-19 08:10:51 CST
> LOG:  database system is ready to accept connections
> LOG:  autovacuum launcher started
>
> it got stuck there ^^
>
> the i tried to
> /usr/local/pgsql.old/bin/psql -p 5432
>
> and it turns that
> 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"?
>
> so basically i just moved the whole pgsql8.3.2 that i had to a new folder
> which is pgsql.old with sudo mv etc,etc
> but i can not turn on the 8.3 server, i did try to start the new one (9.2.4)
> and yes i can.
>
> any idea?
>
>
>
> --
> View this message in context: http://postgresql.1045698.n5.nabble.com/PG-UPGRADE-issues-this-utility-can-only-upgrade-to-postgresql-version-9-2-tp5759509p5759873.html
> Sent from the PostgreSQL - admin mailing list archive at Nabble.com.
>
>

Does the file /var/run/postgresql/.s.PGSQL.5432.lock exist on the system 
you're trying to upgrade ?   If so, what's inside (cat it), does it 
point to your /usr/local/pgsql.old/data directory?  I've found that in 
my (limited) experience with pg_upgrade, it's good to run the upgrade 
from /tmp directory, that way the lock file gets created there and 
usually there's no write permission problems in /tmp either :)

Ziggy


--------------090208070004090700030704
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix"><br>
      On 13-06-19 10:16 AM, jmfox180 wrote:<br>
    </div>
    <blockquote cite="mid:1371651412536-5759873.post@n5.nabble.com"
      type="cite">
      <pre wrap="">so i tried to do a 

/usr/local/pgsql.old/bin/postgres -D /usr/local/pgsql.old/data start

LOG:  database system was shut down at 2013-06-19 08:10:51 CST
LOG:  database system is ready to accept connections
LOG:  autovacuum launcher started

it got stuck there ^^

the i tried to 
/usr/local/pgsql.old/bin/psql -p 5432

and it turns that 
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"?

so basically i just moved the whole pgsql8.3.2 that i had to a new folder
which is pgsql.old with sudo mv etc,etc
but i can not turn on the 8.3 server, i did try to start the new one (9.2.4)
and yes i can.

any idea?


--
View this message in context: <a class="moz-txt-link-freetext" href="http://postgresql.1045698.n5.nabble.com/PG-UPGRADE-issues-this-utility-can-only-upgrade-to-postgresql-version-9-2-tp5759509p5759873.html">http://postgresql.1045698.n5.nabble.com/PG-UPGRADE-issues-this-utility-can-only-upgrade-to-postgresql-version-9-2-tp5759509p5759873.html</a>
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.


</pre>
    </blockquote>
    <br>
    Does the file <i class="moz-txt-slash"><span class="moz-txt-tag">/</span>var/run/postgresql<span
        class="moz-txt-tag">/</span></i>.s.PGSQL.5432.lock exist on the
    system you're trying to upgrade ? &nbsp; If so, what's inside (cat it),
    does it point to your /usr/local/pgsql.old/data directory?&nbsp; I've
    found that in my (limited) experience with pg_upgrade, it's good to
    run the upgrade from /tmp directory, that way the lock file gets
    created there and usually there's no write permission problems in
    /tmp either :)<br>
    <br>
    Ziggy<br>
    <br>
  </body>
</html>

--------------090208070004090700030704--