Re: Upgrade Process Says "The database server was not shut downcleanly" but it was - Mailing list pgsql-general

From TalGloz
Subject Re: Upgrade Process Says "The database server was not shut downcleanly" but it was
Date
Msg-id 1589320265473-0.post@n3.nabble.com
Whole thread Raw
In response to Re: Upgrade Process Says "The database server was not shut downcleanly" but it was  (Adrian Klaver <adrian.klaver@aklaver.com>)
Responses Re: Upgrade Process Says "The database server was not shut downcleanly" but it was  (Adrian Klaver <adrian.klaver@aklaver.com>)
List pgsql-general
Adrian Klaver-4 wrote
> On 5/11/20 2:45 PM, TalGloz wrote:
>> Well I tried your steps, both Postgres 10 and 12 are in perfect running
>> conditions and were shut down using the "systemctl" command. When I
>> execute:
>> 
>> /usr/pgsql-12/bin/pg_upgrade --old-bindir=/usr/pgsql-10/bin/
>> --new-bindir=/usr/pgsql-12/bin/ --old-datadir=/var/lib/pgsql/10/data
>> --new-datadir=/var/lib/pgsql/12/data --old-options '-c
>> config_file=/var/lib/pgsql/10/data/postgresql.conf' --new-options '-c
>> config_file=/var/lib/pgsql/12/data/postgresql.conf' --check
>> 
>> I get:
>> 
>> Performing Consistency Checks
>> -----------------------------
>> Checking cluster versions                                              
>> ok
>> Checking database user is the install user                          ok
>> Checking database connection settings                             ok
>> Checking for prepared transactions                                  ok
>> Checking for reg* data types in user tables                       ok
>> Checking for contrib/isn with bigint-passing mismatch          ok
>> Checking for tables WITH OIDS                                        ok
>> Checking for invalid "sql_identifier" user columns                 ok
>> Checking for presence of required libraries                         ok
>> Checking database user is the install user                         ok
>> Checking for prepared transactions                                  ok
>> 
>> *Clusters are compatible*
>> 
>> But if I execute the same command right after that without the "--check"
>> flag I get:
>> 
>> Performing Consistency Checks
>> -----------------------------
>> Checking cluster versions                                   ok
>> 
>> The target cluster was not shut down cleanly.
>> Failure, exiting
>> 
>> 
>> Both of the servers were still shut down. If I start form the beginning
>> with
>> a fresh Prostgres 12 installation and execute the upgrade command right
>> away
>> without the "--check" flag I get the problem described in my original
>> post.
> 
> How are you installing Postgres?
> 
> Are the 10 and 12 packages coming from the same location?
> 
>> 
>> Best regards,
>> TalGlo
>> 
>> 
>> 
>> --
>> Sent from:
>> https://www.postgresql-archive.org/PostgreSQL-general-f1843780.html
>> 
>> 
> 
> 
> -- 
> Adrian Klaver

> adrian.klaver@



This is my output for "ps ax| grep post" it is always the same after
shunting down the services.
  11232 pts/0    S+     0:00 grep --color=auto post

I've used the same installation steps for both of the instances:

1. Add the PostgreSQL Yum Repository (needed to be done once)
2. Install the desired Postgres instance using "sudo dnf install
postgresqlXX-*"

Best regards,
TalGloz



--
Sent from: https://www.postgresql-archive.org/PostgreSQL-general-f1843780.html



pgsql-general by date:

Previous
From: Karsten Hilbert
Date:
Subject: Re: Enforcing uniqueness on [real estate/postal] addresses
Next
From: Rich Shepard
Date:
Subject: Re: Enforcing uniqueness on [real estate/postal] addresses