Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qLlvz-000dix-PX for pgsql-general@arkaria.postgresql.org; Tue, 18 Jul 2023 14:44:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qLlvw-009y97-By for pgsql-general@arkaria.postgresql.org; Tue, 18 Jul 2023 14:44:12 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qLlvw-009y8z-2G for pgsql-general@lists.postgresql.org; Tue, 18 Jul 2023 14:44:12 +0000 Received: from mail-yb1-xb29.google.com ([2607:f8b0:4864:20::b29]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qLlvs-0009AN-80 for pgsql-general@lists.postgresql.org; Tue, 18 Jul 2023 14:44:10 +0000 Received: by mail-yb1-xb29.google.com with SMTP id 3f1490d57ef6-cc4f4351ac7so4082943276.2 for ; Tue, 18 Jul 2023 07:44:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1689691447; x=1692283447; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:from:to:cc:subject:date:message-id :reply-to; bh=D7a/oeCQKJsI2xNbvK3bB5rUHMIPXrJulFji5rRKNe4=; b=rppT6cA2zApru9EWXMsdQ1Gyqn8lIgzOAv3jjNv2DPacAsppHrmPg7tbm0b8pXQBJQ czYiJcyHl8YGiCZdLGDW32snjfVNSi4Lu4AlH1i2qup/NuLM/NYDVWwy6Vg3380IZ93l 4Uq3OBoi38TUCF/E5vBUJsxiij8WaeHqxOuukeoRe9lAvQ5ML6fpMez0ydcugkpLOJL/ BSFZkLqjK33JDAR2yer7iIVJ7aWKZN+tksQ445R1SSe5PXzFkYrVzH1eVSHooeOxwQsv 1FBuFcrPgGucg2rUDPla9bv61lNnnsWbcJ2TxPHzVsYfnQceM3bnTF4dCBSvBoamlN/k 4w7g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1689691447; x=1692283447; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=D7a/oeCQKJsI2xNbvK3bB5rUHMIPXrJulFji5rRKNe4=; b=YNHKBploEymyXS8c+OiELVqInw+2h9N+J/FkmbJZDlLGyxpBxd6B00eJZU7V0olQoX sOBTNLNzKf0SHQFGKRFzJ/tR4M9gsUA2x760qChrX4Z6fh/be+sQZtK35WVFXeOVruTZ Z04l2wz90he6+xFFPU+oWk48IJqlNOqFYSN3dnuCGtIy9TOMyEZGSxlGYeZ/7gNE7kHL F2jkakcQe15RC3OtBGeHoFxJ22la4IYJc8kDjE9c4jrgjIDg4oDG/c14z6TI4l78pBM6 OoVTwsuDkFuqbCbKLDzHybGPa8IFbPaX12iVBmiNHEjNw/0niwuyTy1kTK+VJbuavJiK mf1Q== X-Gm-Message-State: ABy/qLadC3Ydq1dRf6So23o0wcU3aMh2HAXj3R6ZEclWuZnsBKsmpXIf J+wdtgfzFsEHV/cO06KsBKyHY7xjscU= X-Google-Smtp-Source: APBJJlEvMAtDVWANvzU/uiNwMCv7T9MWkSJPVN8qkhleHJmXKlDwY+giqC1SFVt6Stfw/4kVFs2VJA== X-Received: by 2002:a25:9384:0:b0:cd6:48ea:fd2d with SMTP id a4-20020a259384000000b00cd648eafd2dmr63359ybm.32.1689691446666; Tue, 18 Jul 2023 07:44:06 -0700 (PDT) Received: from ?IPV6:2600:1700:bd2c:b810:8af:58b8:efa3:99c2? ([2600:1700:bd2c:b810:8af:58b8:efa3:99c2]) by smtp.googlemail.com with ESMTPSA id j203-20020a2523d4000000b00bcf788d09e3sm459338ybj.34.2023.07.18.07.44.06 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 18 Jul 2023 07:44:06 -0700 (PDT) Content-Type: multipart/alternative; boundary="------------c76PcHxNjutyEjwral7tiybK" Message-ID: <7bd4204a-ba57-2c12-1dcd-073a1470eb6c@gmail.com> Date: Tue, 18 Jul 2023 09:44:03 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 Subject: Re: Upgrade Failure Content-Language: en-US To: pgsql-general@lists.postgresql.org References: <0E725F4C-4319-4697-8F7A-6F2ED4BA3B97@yesql.se> From: Ron In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------c76PcHxNjutyEjwral7tiybK Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit pg_ctl is not pg_controldata. (I bet you ran "pg_ctl stop --mode=immediate".  That's not a clean shutdown.) On 7/18/23 05:26, Johnathan Tiamoh wrote: > I used pg_ctl to stop the cluster. > > When I used the same pg_ctl to check status, it says no server is running > > On Tue, Jul 18, 2023 at 6:14 AM Daniel Gustafsson wrote: > > > On 18 Jul 2023, at 12:02, Johnathan Tiamoh > wrote: > > > The source cluster was not shut down cleanly. > > Failure, exiting > > > > Please how do you resolve this > > pg_upgrade runs bin/pg_controldata on the source cluster data > directory and > ensures that the "Database cluster state" says "shut down". If you run the > same command, which state is the cluster reported to be in? > > -- > Daniel Gustafsson > -- Born in Arizona, moved to Babylonia. --------------c76PcHxNjutyEjwral7tiybK Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit pg_ctl is not pg_controldata.

(I bet you ran "pg_ctl stop --mode=immediate".  That's not a clean shutdown.)

On 7/18/23 05:26, Johnathan Tiamoh wrote:
I used pg_ctl to stop the cluster. 

When I used the same pg_ctl to check status, it says no server is running 

On Tue, Jul 18, 2023 at 6:14 AM Daniel Gustafsson <daniel@yesql.se> wrote:
> On 18 Jul 2023, at 12:02, Johnathan Tiamoh <johnathantiamoh@gmail.com> wrote:

> The source cluster was not shut down cleanly.
> Failure, exiting
>
> Please how do you resolve this

pg_upgrade runs bin/pg_controldata on the source cluster data directory and
ensures that the "Database cluster state" says "shut down".  If you run the
same command, which state is the cluster reported to be in?

--
Daniel Gustafsson


--
Born in Arizona, moved to Babylonia.
--------------c76PcHxNjutyEjwral7tiybK--