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 <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1f8idL-0000xq-LU
	for pgsql-admin@arkaria.postgresql.org; Wed, 18 Apr 2018 08:40:08 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1f8idK-0007Ur-Fc
	for pgsql-admin@arkaria.postgresql.org; Wed, 18 Apr 2018 08:40:06 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <sk@zsrv.org>)
	id 1f8idK-0007UR-4o; Wed, 18 Apr 2018 08:40:06 +0000
Received: from forward3j.cmail.yandex.net ([2a02:6b8:0:1630::16])
	by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <sk@zsrv.org>)
	id 1f8idG-0000v5-UM; Wed, 18 Apr 2018 08:40:05 +0000
Received: from mxback2o.mail.yandex.net (mxback2o.mail.yandex.net
 [IPv6:2a02:6b8:0:1a2d::1c])
	by forward3j.cmail.yandex.net (Yandex) with ESMTP id D08EE20FA7;
	Wed, 18 Apr 2018 11:39:57 +0300 (MSK)
Received: from localhost (localhost [::1])
	by mxback2o.mail.yandex.net (nwsmtp/Yandex) with ESMTP id
 roNamFWlcH-dunS4rIJ;
	Wed, 18 Apr 2018 11:39:56 +0300
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zsrv.org; s=mail;
 t=1524040796;
	bh=6Fzhfvh6urAHJbs4xLjcV0Ex+rTdCyC/6V+FgW8Mjkc=;
	h=From:To:In-Reply-To:References:Subject:Message-Id:Date;
	b=l8WLjLU8SMGrko1bJhNMzJ5btZlivxMmI4Sjrqwld//aW9lV97H+YM13UETehNIB2
	 PK9T9xhldCVR2nBp4g0dctf3sJJ9zNs5d90G/Q2s/xajCX4Y6xyw9IeOerUiuVTcpi
	 IkBMbc9OJ//Z2gV1QhPAwZ5eWWXZ+myJzhmQaRTQ=
Authentication-Results: mxback2o.mail.yandex.net; dkim=pass header.i=@zsrv.org
Received: by web46j.yandex.ru with HTTP;
	Wed, 18 Apr 2018 11:39:56 +0300
From: Sergei Kornilov <sk@zsrv.org>
To: Akshay Ballarpure <akshay.ballarpure@tcs.com>,
	"pgsql-general@lists.postgresql.org" <pgsql-general@lists.postgresql.org>,
	"pgsql-admin@lists.postgresql.org" <pgsql-admin@lists.postgresql.org>,
	"pgsql-performance@lists.postgresql.org"
 <pgsql-performance@lists.postgresql.org>
In-Reply-To: 
 <OFCDF011F0.3CF96533-ON65258273.002856FC-65258273.002913C0@tcs.com>
References: 
 <OFCDF011F0.3CF96533-ON65258273.002856FC-65258273.002913C0@tcs.com>
Subject: Re: pg_upgrade help
MIME-Version: 1.0
Message-Id: <115471524040796@web46j.yandex.ru>
X-Mailer: Yamail [ http://yandex.ru ] 5.0
Date: Wed, 18 Apr 2018 11:39:56 +0300
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
List-Id: <pgsql-admin.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-admin@lists.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-admin>
Precedence: bulk

Hi
Both version should be correctly stopped. pg_upgrade started clusters itself.
Please check pg_upgrade_server.log file in directory where pg_upgrade was run.
Also where is postgresql.conf? In PGDATA? Otherwise you need tell pg_upgrade correct path, for example with options '-o " -c config_file=/etc/postgresql/8.4/main/postgresql.conf" -O " -c config_file=/etc/postgresql/9.4/main/postgresql.conf"'

regards, Sergei