From: | "sivapostgres(at)yahoo(dot)com" <sivapostgres(at)yahoo(dot)com> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | Pgsql-general General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Issue in PG start |
Date: | 2021-05-08 11:33:27 |
Message-ID: | 1815674480.2182075.1620473607633@mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Or server’s log file is available elsewhere ?
On Saturday, 8 May, 2021, 01:24:50 pm IST, sivapostgres(at)yahoo(dot)com <sivapostgres(at)yahoo(dot)com> wrote:
The above is the contents of the log file from 'data' folder of PG.
Message in Windows Application Event2021-05-08 10:26:19.425 IST [5588] LOG: listening on IPv4 address "0.0.0.0", port 5433
On Saturday, 8 May, 2021, 11:02:06 am IST, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
On Friday, May 7, 2021, sivapostgres(at)yahoo(dot)com <sivapostgres(at)yahoo(dot)com> wrote:
Hello,
PG 11.8 in Windows 10 and currently PG 11.11
Yesterday [07th May] morning when we switched on the computer and subsequently PGAdmin, we got the message following messageFATAL: the database system is starting up
I uninstalled PG and installed [v 11.11] PG with the same data directory. Fortunately it worked even when we switched off /on the computer for lunch. NO issues yesterday.
But today morning [08th May], again we have the same issue and same message. The log file is with the following message only
2021-05-08 10:26:20.783 IST [7360] LOG: database system was interrupted; last known up at 2021-05-07 18:46:00 IST
How / where to debug the issue and correct it ?
To see why the server is not completing its startup cycle you need to look at the server’s log file. All you’ve shown is a client failing to establish a connection every ten seconds.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Avinash Kumar | 2021-05-08 12:28:36 | Re: idle_in_transaction_session_timeout |
Previous Message | Vijaykumar Jain | 2021-05-08 10:54:48 | Re: idle_in_transaction_session_timeout |