Message-ID: <1512668252.2915.17.camel@cybertec.at>
Subject: Re: "FATAL: the database system is starting up" and hot_standby = on
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Ilnur Khanov <khanov.i@gmail.com>, pgsql-admin@lists.postgresql.org
Date: Thu, 07 Dec 2017 18:37:32 +0100
In-Reply-To: 
 <CAN+PxfQjAC_GiSZ7WHZxsYNQTx0f=k8C2k3HMhRifsWKYHPVQg@mail.gmail.com>
References: 
	<CAN+PxfQwWM5j4LvJNV1jERuvLV4x-Oi6w6JKQadPft_AztQBfQ@mail.gmail.com>
	 <1512634318.2188.3.camel@europecamions-interactive.com>
	 <CAN+PxfQjAC_GiSZ7WHZxsYNQTx0f=k8C2k3HMhRifsWKYHPVQg@mail.gmail.com>
Organization: Cybertec
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Precedence: bulk

Ilnur Khanov wrote:
> For me, when I saw "FATAL: the database system is starting up", nothing else hasn't been working: pgAdmin, psql, business apps.

"FATAL" just means that a client connection is terminated.
In this case, because the database is not up.

> Logs has been showing cycles: client connect - worker starts - "the-FATAL-error" -
> worker shutting down with exit code (1). No any informative errors.
> 
> I think, database engine is in some sort of recovery mode after crush, but I was
> waiting long enough - no CPU or HDD activity. If it's some sort of warning and waiting for me to check consistency and manually reset this mode flag, but then how to do this?!
> 
> More important: now problem is not solved, "hot_standby = on" is just workaround letting query databases.
> But PostgreSQL is still in some strange mode and I don't understand how serious is it and how resolve it correctly.

You cannot modify the database, right?
And "SELECT pg_is_in_recovery();" returns TRUE, right?

Could you show us what is written to the log after a new startup?

Yours,
Laurenz Albe