Postgres Database Service Interruption

From: Bablu Kumar Nayak <bablukumarnayak1432(at)gmail(dot)com>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Postgres Database Service Interruption
Date: 2024-01-16 11:22:20
Message-ID: CAJmy-Un2Pyu+NuXU-qmNLC1+OfF-w8-bvHNwgVqdZ2nsXCp9XA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

Here are some details about the current situation:

*1) checking the status:-*

/apps/postgresdb/pgsql/bin/pg_ctl status -D /apps/postgresdb/pgsql/data
pg_ctl: no server running

*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.

Thanks
Bablu Nayak

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Anton A. Melnikov 2024-01-16 11:23:56 Re: ResourceOwner refactoring
Previous Message Daniel Gustafsson 2024-01-16 11:17:23 Re: initdb's -c option behaves wrong way?