Re: Windows 2016 server crashed after changes in Postgres 15.8 pgAdmin - Mailing list pgsql-hackers

From Sanjay Khatri
Subject Re: Windows 2016 server crashed after changes in Postgres 15.8 pgAdmin
Date
Msg-id CANLv43JgqRg03LbvSJTLgv4p8L+8H5kZu3btCEzisPT+qW2vWA@mail.gmail.com
Whole thread Raw
In response to Re: Windows 2016 server crashed after changes in Postgres 15.8 pgAdmin  (Sanjay Khatri <sanjaykhatri218@gmail.com>)
Responses Re: Windows 2016 server crashed after changes in Postgres 15.8 pgAdmin
List pgsql-hackers

We tried it on another server with similar configurations.
Just installed the Postgres 15 and its PgAdmin.
Kept the server ONN for the whole day, the server was okay.
But then we tried the pgAdmin workaround by deleting the pgAdmin.bak file in  'AppData/Roaming/pgAdmin' and restarted the PgAdmin.
Soon within an hour the server crashed. Its happening when PgAdmin workaround is performed.
Do Let me know if someone else faced the same issue?

On Wed, 20 Nov 2024, 19:14 Sanjay Khatri, <sanjaykhatri218@gmail.com> wrote:

Yes...I will....but in case someone could provide help it would be good. Rest I will contact the Hardware Support.

On Wed, 20 Nov 2024, 19:11 Daniel Gustafsson, <daniel@yesql.se> wrote:
> On 20 Nov 2024, at 14:34, Sanjay Khatri <sanjaykhatri218@gmail.com> wrote:
>
> These are the errors from the logs of iDrac M630.
> I uninstalled the Postgres 15.8 , once I got the connection. But sadly the server disconnected again and crashed, even after uninstalling.
> No I am not able to boot it.

I'm going to go out on a limb and say that this isn't a postgres bug, and
highly unlikely to be caused by one.  This smells like broken hardware and/or
corrupted BIOS/firmware, you should contact your hardware vendor for support.

--
Daniel Gustafsson

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: IMPORTANT: Out-of-cycle release scheduled for November 21, 2024
Next
From: Pavel Stehule
Date:
Subject: Re: proposal: schema variables