Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YHGK1-0005Bl-Iy for pgsql-admin@arkaria.postgresql.org; Fri, 30 Jan 2015 18:29:37 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YHGK1-0001qb-35 for pgsql-admin@arkaria.postgresql.org; Fri, 30 Jan 2015 18:29:37 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YHGK0-0001qV-BU for pgsql-admin@postgresql.org; Fri, 30 Jan 2015 18:29:36 +0000 Received: from mail-yh0-x230.google.com ([2607:f8b0:4002:c01::230]) by magus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1YHGJw-0002cu-HZ for pgsql-admin@postgresql.org; Fri, 30 Jan 2015 18:29:35 +0000 Received: by mail-yh0-f48.google.com with SMTP id a41so11628615yho.7 for ; Fri, 30 Jan 2015 10:29:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=vn+ofKFvS/RhE5UgS9FSdhfjPRzAtFCR77FsI5h9Xls=; b=qNZNyrhec/sZn3q+atTpq012f3Ucmjm7B2p14V0nU6ebdexU9GpAfEYtNjOsO34Uzl hxw37SNa5CO1qSOFMvoMJRWWiBEkHEzCqkMO2Rrtbjf6PMrlwuqUM0k14mEotHOzHqJF 4ydFedTa4uVfeu4gVCY5gU1vyBq24ALEq5ji4yHh6bB2jnVDro4W4UqVGk+IjK+4zHcp QMnNSU2TJO+PjDmpIf3TXcOym3pGMpzyGksCAU583Hh+/wludcihjTFbi+FHaHdni4hz x8AgqUbJOjLNxsmsQvE7TROuGOsbiukEqC80F+ePN84h93Z1b1iC9aXJ+TD/vwhuhLt6 fbwA== X-Received: by 10.170.145.212 with SMTP id m203mr4344534ykc.80.1422642570189; Fri, 30 Jan 2015 10:29:30 -0800 (PST) Received: from [192.168.254.3] (h77.89.102.166.static.ip.windstream.net. [166.102.89.77]) by mx.google.com with ESMTPSA id q39sm6964589yhg.43.2015.01.30.10.29.28 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 30 Jan 2015 10:29:29 -0800 (PST) Message-ID: <54CBCD82.4040802@gmail.com> Date: Fri, 30 Jan 2015 13:29:22 -0500 From: John Scalia User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Mauricio Tavares , pgsql-admin@postgresql.org Subject: Re: Postgres update 9.1 to 9.3 - error port 50432 References: In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org On 1/30/2015 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 .. Mauricio, First off, and I'm not trying to say that you're inexperienced, but have you run an initdb on the new 9.3 instance? And if so, can you start that instance manually? If so and if the database refuses start manually, what's that error? Also, have you checked the pgstartup.log for 9.3 when using pg_upgrade? Or even the daily log file in the 9.3 data/pg_log directory? -- Jay -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin