Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YHGst-0006xe-2M for pgsql-admin@arkaria.postgresql.org; Fri, 30 Jan 2015 19:05:39 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YHGss-0006gj-EP for pgsql-admin@arkaria.postgresql.org; Fri, 30 Jan 2015 19:05:38 +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 1YHGsr-0006gd-M5 for pgsql-admin@postgresql.org; Fri, 30 Jan 2015 19:05:37 +0000 Received: from outbound.afilias.info ([66.199.183.4]) by magus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YHGsn-0003LN-9X for pgsql-admin@postgresql.org; Fri, 30 Jan 2015 19:05:36 +0000 Received: from maia.afilias-int.info ([10.109.8.9] helo=smtp.afilias.info) by outbound.afilias.info with esmtp (Exim 4.72) (envelope-from ) id 1YHGsi-0004AK-5j for pgsql-admin@postgresql.org; Fri, 30 Jan 2015 19:05:28 +0000 Received: from mail-ie0-f177.google.com ([209.85.223.177]) by smtp.afilias.info with esmtps (TLSv1:RC4-SHA:128) (Exim 4.72) (envelope-from ) id 1YHGsi-0003EG-5V for pgsql-admin@postgresql.org; Fri, 30 Jan 2015 19:05:28 +0000 Received: by mail-ie0-f177.google.com with SMTP id vy18so5475502iec.8 for ; Fri, 30 Jan 2015 11:05:23 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=PWwWn6s/DpasoHQmFxW5UaidvZ3dGsIiG3Wqty10DgU=; b=HsWomv2wMGOi+vCMitQfHu4ILgJB9VSPSrZ0H+flaBatB9uqgRhj9OV3baDrMoh7Mq kHuypqLO39ReAcJt90OeyXvB8GOMeE3wcCAU8oW2yd9SE72S3809KowROxeM33t07aF+ f+2qPBYUQhvUytQdJeaS3t2xf7lxKnWKc9msa+6r8F50LpmubefDjXXf+3mgw8U3/Ebn FmUCfyDfSTls84tQ5DyGWJqmQOBNRcPM5r4ERRjStzQRjJZBmaHeoh/QSF/Jhp2mj95I d6yATkinSttqQlRs8qNZ2sCSrLeThC+TQqzdCigpt3XjD+IrU/pMi9jLgv/bSfM3vpcx ykJA== X-Gm-Message-State: ALoCoQmJYW7Acgykl8SInNPcpD5s5TLEEueRf+RRGGKYrkZC+RTIlKvaw7YP408xJ9oPRVi0GX2RJgmiATdy9OfnMLYUZy80h1S0fyH4eE09GOyF3qYR/6MfXTTSCJm2BvBhTyKbAbJe1pkI0NstQhMqy9kKcJgc2w== X-Received: by 10.50.18.108 with SMTP id v12mr283669igd.34.1422644723476; Fri, 30 Jan 2015 11:05:23 -0800 (PST) X-Received: by 10.50.18.108 with SMTP id v12mr283643igd.34.1422644723200; Fri, 30 Jan 2015 11:05:23 -0800 (PST) Received: from [10.10.46.35] (tor-gateway.afilias.info. [199.15.87.4]) by mx.google.com with ESMTPSA id aw9sm1579234igc.18.2015.01.30.11.05.21 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 30 Jan 2015 11:05:22 -0800 (PST) Message-ID: <54CBD5EF.3010704@afilias.info> Date: Fri, 30 Jan 2015 14:05:19 -0500 From: Ziggy Skalski User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: 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: -4.2 (----) 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 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