pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedPostgres Database got down
3+ messages / 2 participants
[nested] [flat]
* Postgres Database got down
@ 2012-07-19 16:19 Umer Asghar <umerasghar@gmail.com>
0 siblings, 1 reply; 3+ messages in thread
From: Umer Asghar @ 2012-07-19 16:19 UTC (permalink / raw)
To: 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.
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Postgres Database got down
@ 2012-07-20 04:38 Craig Ringer <ringerc@ringerc.id.au>
parent: Umer Asghar <umerasghar@gmail.com>
0 siblings, 1 reply; 3+ messages in thread
From: Craig Ringer @ 2012-07-20 04:38 UTC (permalink / raw)
To: Umer Asghar <umerasghar@gmail.com>; +Cc: pgsql-admin
On 07/20/2012 12:19 AM, Umer Asghar wrote:
> 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?
>
> [snip]
>
> 2012-07-19 18:05:08 PKT LOG: server process (PID 1836) exited with
> exit code 128
>
Maybe this?
http://support.microsoft.com/kb/974509
Thankyou for including your logs without having to be asked. It's
usually helpful if you also provide your PostgreSQL version and
architecture (x86 or x64) - but in this case I don't think it matters as
it seems to be a Windows issue.
--
Craig Ringer
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Postgres Database got down
@ 2012-07-20 05:24 Umer Asghar <umerasghar@gmail.com>
parent: Craig Ringer <ringerc@ringerc.id.au>
0 siblings, 0 replies; 3+ messages in thread
From: Umer Asghar @ 2012-07-20 05:24 UTC (permalink / raw)
To: Craig Ringer <ringerc@ringerc.id.au>; +Cc: pgsql-admin
Thanks- the sysmtoms seems same on my machine here.
i will take up this with my Operating system team.
good news is that after yesterday's reboot, its around 20 hrs and still
this problem has not appear again.
On Fri, Jul 20, 2012 at 9:38 AM, Craig Ringer <ringerc@ringerc.id.au> wrote:
> On 07/20/2012 12:19 AM, Umer Asghar wrote:
>
> 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?
> [snip]
>
> 2012-07-19 18:05:08 PKT LOG: server process (PID 1836) exited with exit
> code 128
>
>
> Maybe this?
>
> http://support.microsoft.com/kb/974509
>
> Thankyou for including your logs without having to be asked. It's usually
> helpful if you also provide your PostgreSQL version and architecture (x86
> or x64) - but in this case I don't think it matters as it seems to be a
> Windows issue.
>
> --
> Craig Ringer
>
--
Regards,
Umer Asghar
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2012-07-20 05:24 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2012-07-19 16:19 Postgres Database got down Umer Asghar <umerasghar@gmail.com>
2012-07-20 04:38 ` Craig Ringer <ringerc@ringerc.id.au>
2012-07-20 05:24 ` Umer Asghar <umerasghar@gmail.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox