Postgres Pro
Downloads
Home   >   mailing lists

Thread: "No response from the backend" error while connecting to postgres db

"No response from the backend" error while connecting to postgres db

From
"tamanna madaan"
Date:

Hi All

 

I am getting error “No response from the backend” while connecting to my postgres database.

 

pg_log file logs the below messages :

 

GMT FATAL:  semop(id=1310723) failed: Invalid argument

GMT FATAL:  semop(id=1310723) failed: Invalid argument

GMT FATAL:  semctl(1310723, 7, SETVAL, 0) failed: Invalid argument

GMT FATAL:  semctl(1310723, 12, SETVAL, 0) failed: Invalid argument

GMT LOG:  server process (PID 10776) exited with exit code 1

GMT LOG:  terminating any other active server processes

GMT WARNING:  terminating connection because of crash of another server process

GMT DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server proc

ess exited abnormally and possibly corrupted shared memory.

GMT HINT:  In a moment you should be able to reconnect to the database and repeat your command.

 

The above message is printed a number of times and after that it prints

 

GMT LOG:  all server processes terminated; reinitializing

GMT LOG:  semctl(1245185, 0, IPC_RMID, ...) failed: Invalid argument

GMT LOG:  semctl(1277954, 0, IPC_RMID, ...) failed: Invalid argument

GMT LOG:  semctl(1310723, 0, IPC_RMID, ...) failed: Invalid argument

GMT LOG:  semctl(1343492, 0, IPC_RMID, ...) failed: Invalid argument

GMT LOG:  shmctl(2097152, 0, 0) failed: Invalid argument

GMT LOG:  database system was interrupted at 2009-09-15 07:28:40 GMT

GMT LOG:  checkpoint record is at A/2311BA94

GMT LOG:  redo record is at A/23106A14; undo record is at 0/0; shutdown FALSE

GMT LOG:  next transaction ID: 20175128; next OID: 58650

GMT LOG:  next MultiXactId: 1; next MultiXactOffset: 0

GMT LOG:  database system was not properly shut down; automatic recovery in progress

GMT LOG:  redo starts at A/23106A14

GMT LOG:  record with zero length at A/2317BF50

GMT LOG:  redo done at A/2317BF28

GMT FATAL:  the database system is starting up

GMT LOG:  database system is ready

 

 

The postgresql log file doesn’t print anything about restarting postgres. I couldn’t get any information from other logs regarding which process was killed, who killed it and why.

 

Please help.

 

Thanks…

Tamanna

Re: "No response from the backend" error while connecting to postgres db

From
Tom Lane
Date:
"tamanna madaan" <tamanna.madan@globallogic.com> writes:
> pg_log file logs the below messages :
> GMT FATAL:  semop(id=1310723) failed: Invalid argument
> GMT FATAL:  semctl(1310723, 7, SETVAL, 0) failed: Invalid argument
> GMT LOG:  semctl(1245185, 0, IPC_RMID, ...) failed: Invalid argument
> GMT LOG:  shmctl(2097152, 0, 0) failed: Invalid argument

It sure looks like something tried to kill off all your SysV resources
(semaphores and shared memory).  Look around and find out if anyone
was doing something with ipcrm, and take away their root privileges
if so.

            regards, tom lane