Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1f8nfW-00010c-Uq for pgsql-general@arkaria.postgresql.org; Wed, 18 Apr 2018 14:02:43 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1f8nfV-0007cr-Ss for pgsql-general@arkaria.postgresql.org; Wed, 18 Apr 2018 14:02:41 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1f8nfV-0007ci-Hy for pgsql-general@lists.postgresql.org; Wed, 18 Apr 2018 14:02:41 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1f8nfP-0001lg-5O for pgsql-general@lists.postgresql.org; Wed, 18 Apr 2018 14:02:40 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id D240E21F5F; Wed, 18 Apr 2018 10:02:33 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Wed, 18 Apr 2018 10:02:33 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=aJF4NHa7cFYGwHdjiYOpFeRL5c4V6 CPnDDI1TeYRrds=; b=WyRbXbi3XJgGJWXeXZOxSZJRVVEA2C9ppaxJksk+m+1qN eJQFSrjnhmjZlbMADqncqSGLkmkJwXCr8vk0sggKtCXgE3sJ2OcEejX4Y/C4ycdQ tYlm6OX6M/hs++dyH3v+z3+MHjbS0ew0OIIS51FmbwVNUVsuym1r9DD60EU50u3O MfgZ2aggMsgG/QuVBSWkDhSsk2U0IdBEAQbAnN70NpmC8NAVdRLTDQhZE36sBeTU oFXZPbKmwqjh9yi/IJDao/wdrS8WPZSOC4g8bIo9rszmvLjJheSEXuitotxzX/vD w1OID6QbQeSynFtcFpxLEgmKYPtdmW8rjFnyQw7PA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=aJF4NH a7cFYGwHdjiYOpFeRL5c4V6CPnDDI1TeYRrds=; b=YHrlM37VnjMpT1GaiVWO2/ 5cLu7nf8Vf68//04PcTClgklqnScb6lg6NE478yk5e22asVxWDv8L2Ej0b3/M1EF HqbOpJWeyvEAvh/wGNLkyuFKkpzoYIRABjPQI0mRe0A7AN0JCthZTLqlJBC2KQ4a 1BSkDwDPH69Zk/PURkpmxAK9zyBhHkhkNEkY4WvMA+GRkvQL6oo9gSC8lxsmXmoC neUZwKFxNBbOiiiUoJo7fvZEqs20lTpU0HIbJG6PFUfaWUV6S8uU61cSkFeQHQcx npexZ0hzZ9FSQUNTSomjh2OXkMxm34SEj5QtQ0UJKAlt++5vvWlVabILg7gs7Qtw == X-ME-Sender: Received: from [192.168.1.2] (unknown [71.212.135.74]) by mail.messagingengine.com (Postfix) with ESMTPA id 13E56E4122; Wed, 18 Apr 2018 10:02:32 -0400 (EDT) Subject: Re: pg_upgrade help To: Akshay Ballarpure , Fabio Pardi Cc: pgsql-general@lists.postgresql.org References: <5657f0ad-2510-d589-f860-92b306da475b@portavita.eu> <8ba65c19-be07-676b-98c5-f1368ecaae92@portavita.eu> From: Adrian Klaver Message-ID: Date: Wed, 18 Apr 2018 07:02:32 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 04/18/2018 05:02 AM, Akshay Ballarpure wrote: > Hi Fabio, > sorry to bother you again, its still failing with stopping both server > (8.4 and 9.4) Actually according to the command show at bottom of post it is failing trying to start the 8.4 server. In your previous post that was because it was already running: -bash-4.2$ ps -eaf | grep postgres postgres 9778 1 0 09:17 ? 00:00:00 /usr/bin/postgres -p 50432 -D /var/ericsson/esm-data/postgresql-data/ FATAL: lock file "postmaster.pid" already exists HINT: Is another postmaster (PID 9778) running in data directory "/var/ericsson/esm-data/postgresql-data"? pg_ctl: could not start server Make sure both servers are stopped before running pg_upgrade. Per a previous suggestion follow the check list here: https://www.postgresql.org/docs/10/static/pgupgrade.html " Usage These are the steps to perform an upgrade with pg_upgrade: ... " > > -bash-4.2$ /opt/rh/rh-postgresql94/root/usr/bin/pg_upgrade > --old-bindir=/usr/bin --new-bindir=/opt/rh/rh-postgresql94/root/usr/bin > --old-datadir=$OLDCLUSTER --new-datadir=$NEWCLUSTER > > 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/run/postgresql/.s.PGSQL.50432"? > > > could not connect to old postmaster started with the command: > "/usr/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D > "/var/ericsson/esm-data/postgresql-data" -o "-p 50432 -c autovacuum=off > -c autovacuum_freeze_max_age=2000000000  -c listen_addresses='' -c > unix_socket_permissions=0700" start > Failure, exiting > > > With Best Regards > Akshay -- Adrian Klaver adrian.klaver@aklaver.com