Postgres Database Service Interruption

On 1/16/24 09:29, Bablu Kumar Nayak wrote:

Dear PostgreSQL Team,

I am writing to inform you that our PostgreSQL database service is
currently down. We are experiencing an unexpected interruption, and we
are seeking your expertise to help us resolve this issue promptly.

We would greatly appreciate your immediate attention to this matter.
If there are specific steps we should follow or additional information
you require, please let us know as soon as possible.

Your assistance in resolving this issue is crucial, and we are
confident in your expertise to help us bring the PostgreSQL database
back online.

Explain your current env. postgres version, how it was install.
OS/Version etc
What do you see when you "Examine the log output".

On 1/16/24 08:29, Bablu Kumar Nayak wrote:

Dear PostgreSQL Team,

I am writing to inform you that our PostgreSQL database service is
currently down. We are experiencing an unexpected interruption, and we
are seeking your expertise to help us resolve this issue promptly.

We would greatly appreciate your immediate attention to this matter. If
there are specific steps we should follow or additional information you
require, please let us know as soon as possible.

Your assistance in resolving this issue is crucial, and we are confident
in your expertise to help us bring the PostgreSQL database back online.

I believe you are looking for this:

https://www.postgresql.org/support/professional_support/

HINT:  This probably means that some data is corrupted and you will have
to use the last backup for recovery.

The above being the critical issue.
I'm guessing there was a hardware failure.

Thanks
Bablu Nayak

--
Adrian Klaver
adrian.klaver@aklaver.com

On Tue, 2024-01-16 at 21:59 +0530, Bablu Kumar Nayak wrote:

I am writing to inform you that our PostgreSQL database service is currently down.
We are experiencing an unexpected interruption, and we are seeking your expertise
to help us resolve this issue promptly.
We would greatly appreciate your immediate attention to this matter. If there are
specific steps we should follow or additional information you require, please let
us know as soon as possible.
Your assistance in resolving this issue is crucial, and we are confident in your
expertise to help us bring the PostgreSQL database back online.
 
Here are some details about the current situation:

2) Starting the server
/apps/postgresdb/pgsql/bin/pg_ctl start -D /apps/postgresdb/pgsql/data
waiting for server to start....2024-01-15 11:15:08.010 GMT [] LOG:  listening on IPv4 address "0.0.0.0", port 
LOG:  listening on IPv6 address "::", port 
LOG:  listening on Unix socket "/tmp/.s.PGSQL."
LOG:  database system was interrupted while in recovery at 2024-01-15 10:51:44 GMT
HINT:  This probably means that some data is corrupted and you will have to use the last backup for recovery.
FATAL:  the database system is starting up
LOG:  database system was not properly shut down; automatic recovery in progress
LOG:  redo starts at 0/
FATAL:  could not access status of transaction
DETAIL:  Could not read from file "pg_xact/0001" at offset 204800: Success.
CONTEXT:  WAL redo at 0/7A845458 for Transaction/COMMIT: 2023-12-30 23:26:16.017062+00
LOG:  startup process (PID 2731458) exited with exit code 1
LOG:  aborting startup due to startup process failure
LOG:  database system is shut down
 stopped waiting
pg_ctl: could not start server
Examine the log output.

You are suffering from data corruption. What did you do to get into this state?

The canonical solution is to restore your backup.

If you have no backup, and the data are important for you (which is a contradiction
in terms), you should hire a consultant with extensive PostgreSQL knowledge in
the hope that he or she can salvage some of your data.

Yours,
Laurenz Albe