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

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

am 16.09.2009 10:44:19 von tamanna madaan

This is a multi-part message in MIME format.

------_=_NextPart_001_01CA36A9.E216E6D1
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi All

=20

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

=20

pg_log file logs the below messages :

=20

GMT FATAL: semop(id=3D1310723) failed: Invalid argument

GMT FATAL: semop(id=3D1310723) 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.

=20

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

=20

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=20

=20

=20

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.

=20

Please help.

=20

Thanks...

Tamanna


------_=_NextPart_001_01CA36A9.E216E6D1
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">


charset=3Dus-ascii">









style=3D'font-size:10.0pt;
font-family:Arial'>Hi All



style=3D'font-size:10.0pt;
font-family:Arial'> 



style=3D'font-size:10.0pt;
font-family:Arial'>I am getting error “No response from the =
backend”
while connecting to my postgres database.



style=3D'font-size:10.0pt;
font-family:Arial'> 



style=3D'font-size:10.0pt;
font-family:Arial'>pg_log file logs the below messages =
:



style=3D'font-size:10.0pt;
font-family:Arial'> 



style=3D'font-size:10.0pt;
font-family:Arial'>GMT FATAL:  semop(id=3D1310723) failed: Invalid =
argument



style=3D'font-size:10.0pt;
font-family:Arial'>GMT FATAL:  semop(id=3D1310723) failed: Invalid =
argument



style=3D'font-size:10.0pt;
font-family:Arial'>GMT FATAL:  semctl(1310723, 7, SETVAL, 0) =
failed:
Invalid argument



style=3D'font-size:10.0pt;
font-family:Arial'>GMT FATAL:  semctl(1310723, 12, SETVAL, 0) =
failed:
Invalid argument



style=3D'font-size:10.0pt;
font-family:Arial'>GMT LOG:  server process (PID 10776) exited with =
exit
code 1



style=3D'font-size:10.0pt;
font-family:Arial'>GMT LOG:  terminating any other active server =
processes



style=3D'font-size:10.0pt;
font-family:Arial'>GMT WARNING:  terminating connection because of =
crash
of another server process



style=3D'font-size:10.0pt;
font-family:Arial'>GMT DETAIL:  The postmaster has commanded this =
server
process to roll back the current transaction and exit, because another =
server
proc



style=3D'font-size:10.0pt;
font-family:Arial'>ess exited abnormally and possibly corrupted shared =
memory.



style=3D'font-size:10.0pt;
font-family:Arial'>GMT HINT:  In a moment you should be able to =
reconnect
to the database and repeat your command.



style=3D'font-size:10.0pt;
font-family:Arial'> 



style=3D'font-size:10.0pt;
font-family:Arial'>The above message is printed a number of times and =
after
that it prints



style=3D'font-size:10.0pt;
font-family:Arial'> 



style=3D'font-size:10.0pt;
font-family:Arial'>GMT LOG:  all server processes terminated;
reinitializing



style=3D'font-size:10.0pt;
font-family:Arial'>GMT LOG:  semctl(1245185, 0, IPC_RMID, ...) =
failed:
Invalid argument



style=3D'font-size:10.0pt;
font-family:Arial'>GMT LOG:  semctl(1277954, 0, IPC_RMID, ...) =
failed:
Invalid argument



style=3D'font-size:10.0pt;
font-family:Arial'>GMT LOG:  semctl(1310723, 0, IPC_RMID, ...) =
failed:
Invalid argument



style=3D'font-size:10.0pt;
font-family:Arial'>GMT LOG:  semctl(1343492, 0, IPC_RMID, ...) =
failed:
Invalid argument



style=3D'font-size:10.0pt;
font-family:Arial'>GMT LOG:  shmctl(2097152, 0, 0) failed: Invalid
argument



style=3D'font-size:10.0pt;
font-family:Arial'>GMT LOG:  database system was interrupted at =
2009-09-15
07:28:40 GMT



style=3D'font-size:10.0pt;
font-family:Arial'>GMT LOG:  checkpoint record is at =
A/2311BA94



style=3D'font-size:10.0pt;
font-family:Arial'>GMT LOG:  redo record is at A/23106A14; undo =
record is
at 0/0; shutdown FALSE



style=3D'font-size:10.0pt;
font-family:Arial'>GMT LOG:  next transaction ID: 20175128; next =
OID:
58650



style=3D'font-size:10.0pt;
font-family:Arial'>GMT LOG:  next MultiXactId: 1; next =
MultiXactOffset: 0



style=3D'font-size:10.0pt;
font-family:Arial'>GMT LOG:  database system was not properly shut =
down;
automatic recovery in progress



style=3D'font-size:10.0pt;
font-family:Arial'>GMT LOG:  redo starts at =
A/23106A14



style=3D'font-size:10.0pt;
font-family:Arial'>GMT LOG:  record with zero length at =
A/2317BF50



style=3D'font-size:10.0pt;
font-family:Arial'>GMT LOG:  redo done at =
A/2317BF28



style=3D'font-size:10.0pt;
font-family:Arial'>GMT FATAL:  the database system is starting =
up



style=3D'font-size:10.0pt;
font-family:Arial'>GMT LOG:  database system is ready =



style=3D'font-size:10.0pt;
font-family:Arial'> 



style=3D'font-size:10.0pt;
font-family:Arial'> 



style=3D'font-size:10.0pt;
font-family:Arial'>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.



style=3D'font-size:10.0pt;
font-family:Arial'> 



style=3D'font-size:10.0pt;
font-family:Arial'>Please help.



style=3D'font-size:10.0pt;
font-family:Arial'> 



style=3D'font-size:10.0pt;
font-family:Arial'>Thanks…



style=3D'font-size:10.0pt;
font-family:Arial'>Tamanna









------_=_NextPart_001_01CA36A9.E216E6D1--

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

am 17.09.2009 16:14:29 von Tom Lane

"tamanna madaan" 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

--
Sent via pgsql-odbc mailing list (pgsql-odbc@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc