Skip site navigation (1) Skip section navigation (2)

Postgres Database got down

From: "Umer Asghar" <umerasghar(at)gmail(dot)com>
To: <pgsql-admin(at)postgresql(dot)org>
Subject: Postgres Database got down
Date: 2012-07-19 16:19:39
Message-ID: 000901cd65ca$4eb7cd00$ec276700$@com (view raw or flat)
Thread:
Lists: pgsql-admin
Hi All,

 

I am sure, this question must have been asked many times, I tried to search
archives as well, but still unable to find solution.

Below are logs. I am using Windows 2003 server 2 and using Postgres as a
metadata database for my ODI.

 

I got similar error last week as well. And today it has crashed twice.

 

After that I gave it a reboot to my machine, and its 3 hrs now and its
running fine. but not sure why it got down and will it go down again soon.

Can somebody advice what should I looked into?

 

---------------------------------------

 

2012-07-19 17:28:27 PKT LOG:  database system was interrupted; last known up
at 2012-07-19 17:15:15 PKT

2012-07-19 17:28:27 PKT LOG:  database system was not properly shut down;
automatic recovery in progress

2012-07-19 17:28:27 PKT LOG:  redo starts at 102/ACFA57C8

2012-07-19 17:28:27 PKT LOG:  record with zero length at 102/AD33E680

2012-07-19 17:28:27 PKT LOG:  redo done at 102/AD33E650

2012-07-19 17:28:27 PKT LOG:  last completed transaction was at log time
2012-07-19 17:18:46.414+05

2012-07-19 17:28:27 PKT FATAL:  the database system is starting up

2012-07-19 17:28:28 PKT LOG:  database system is ready to accept connections

2012-07-19 17:28:28 PKT LOG:  autovacuum launcher started

2012-07-19 18:05:08 PKT LOG:  server process (PID 1836) exited with exit
code 128

2012-07-19 18:05:08 PKT LOG:  terminating any other active server processes

2012-07-19 18:05:08 PKT WARNING:  terminating connection because of crash of
another server process

2012-07-19 18:05:08 PKT DETAIL:  The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.

2012-07-19 18:05:08 PKT HINT:  In a moment you should be able to reconnect
to the database and repeat your command.

2012-07-19 18:05:08 PKT WARNING:  terminating connection because of crash of
another server process

2012-07-19 18:05:08 PKT DETAIL:  The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.

2012-07-19 18:05:08 PKT HINT:  In a moment you should be able to reconnect
to the database and repeat your command.

2012-07-19 18:05:08 PKT WARNING:  terminating connection because of crash of
another server process

2012-07-19 18:05:08 PKT DETAIL:  The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.

2012-07-19 18:05:08 PKT HINT:  In a moment you should be able to reconnect
to the database and repeat your command.

2012-07-19 18:05:08 PKT WARNING:  terminating connection because of crash of
another server process

2012-07-19 18:05:08 PKT DETAIL:  The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.

2012-07-19 18:05:08 PKT HINT:  In a moment you should be able to reconnect
to the database and repeat your command.

2012-07-19 18:05:08 PKT WARNING:  terminating connection because of crash of
another server process

2012-07-19 18:05:08 PKT DETAIL:  The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.

2012-07-19 18:05:08 PKT HINT:  In a moment you should be able to reconnect
to the database and repeat your command.

2012-07-19 18:05:08 PKT WARNING:  terminating connection because of crash of
another server process

2012-07-19 18:05:08 PKT DETAIL:  The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.

2012-07-19 18:05:08 PKT HINT:  In a moment you should be able to reconnect
to the database and repeat your command.

2012-07-19 18:05:08 PKT WARNING:  terminating connection because of crash of
another server process

2012-07-19 18:05:08 PKT DETAIL:  The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.

2012-07-19 18:05:08 PKT HINT:  In a moment you should be able to reconnect
to the database and repeat your command.

2012-07-19 18:05:08 PKT WARNING:  terminating connection because of crash of
another server process

2012-07-19 18:05:08 PKT DETAIL:  The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.

2012-07-19 18:05:08 PKT HINT:  In a moment you should be able to reconnect
to the database and repeat your command.

2012-07-19 18:05:08 PKT WARNING:  terminating connection because of crash of
another server process

2012-07-19 18:05:08 PKT DETAIL:  The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.

2012-07-19 18:05:08 PKT HINT:  In a moment you should be able to reconnect
to the database and repeat your command.

2012-07-19 18:05:08 PKT WARNING:  terminating connection because of crash of
another server process

2012-07-19 18:05:08 PKT DETAIL:  The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.

2012-07-19 18:05:08 PKT HINT:  In a moment you should be able to reconnect
to the database and repeat your command.

2012-07-19 18:05:08 PKT WARNING:  terminating connection because of crash of
another server process

2012-07-19 18:05:08 PKT DETAIL:  The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.

2012-07-19 18:05:08 PKT HINT:  In a moment you should be able to reconnect
to the database and repeat your command.

2012-07-19 18:05:08 PKT WARNING:  terminating connection because of crash of
another server process

2012-07-19 18:05:08 PKT DETAIL:  The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.

2012-07-19 18:05:08 PKT HINT:  In a moment you should be able to reconnect
to the database and repeat your command.

2012-07-19 18:05:08 PKT WARNING:  terminating connection because of crash of
another server process

2012-07-19 18:05:08 PKT DETAIL:  The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.

2012-07-19 18:05:08 PKT HINT:  In a moment you should be able to reconnect
to the database and repeat your command.

2012-07-19 18:05:08 PKT WARNING:  terminating connection because of crash of
another server process

2012-07-19 18:05:08 PKT DETAIL:  The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.

2012-07-19 18:05:08 PKT HINT:  In a moment you should be able to reconnect
to the database and repeat your command.

2012-07-19 18:05:08 PKT WARNING:  terminating connection because of crash of
another server process

2012-07-19 18:05:08 PKT DETAIL:  The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.

2012-07-19 18:05:08 PKT HINT:  In a moment you should be able to reconnect
to the database and repeat your command.

2012-07-19 18:05:08 PKT WARNING:  terminating connection because of crash of
another server process

2012-07-19 18:05:08 PKT DETAIL:  The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.

2012-07-19 18:05:08 PKT HINT:  In a moment you should be able to reconnect
to the database and repeat your command.

2012-07-19 18:05:08 PKT WARNING:  terminating connection because of crash of
another server process

2012-07-19 18:05:08 PKT DETAIL:  The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.

2012-07-19 18:05:08 PKT HINT:  In a moment you should be able to reconnect
to the database and repeat your command.

2012-07-19 18:05:08 PKT LOG:  all server processes terminated;
reinitializing

2012-07-19 18:05:18 PKT FATAL:  pre-existing shared memory block is still in
use

2012-07-19 18:05:18 PKT HINT:  Check if there are any old server processes
still running, and terminate them.

---------------------------------------

 

 

 

 

Regards,

Umer Asghar.

 

Responses

pgsql-admin by date

Next:From: David KerrDate: 2012-07-19 21:02:34
Subject: Re: Measurin the lag between a master and a replica
Previous:From: Sergey KonoplevDate: 2012-07-19 15:52:10
Subject: Re: Measurin the lag between a master and a replica

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group