Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 9AD25F6332B for ; Thu, 19 Jul 2012 13:20:02 -0300 (ADT) Received: from mail-wi0-f178.google.com ([209.85.212.178]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SrtSJ-0007Mz-Rn for pgsql-admin@postgresql.org; Thu, 19 Jul 2012 16:20:02 +0000 Received: by wibhr14 with SMTP id hr14so2758195wib.1 for ; Thu, 19 Jul 2012 09:19:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:message-id:mime-version:content-type:x-mailer :thread-index:content-language; bh=QnsNyHyem5xMXE2iBf3V5VZU4XidTmWr0hcGsAi3MKs=; b=BewtsHNlppF1hgT3W5EsOWccgYH6y6/kh9x0g72yzdSN32qzJGocenYSNybEQZbx6O bsKGt7YTiKRWPj24l0ikP82x+qt4h9T5J8+4tpNCxTerRJOIxmBQCkq03Nv+dPHwjgay N6ZO+1hKRv8wwg0/o72sAhgI5o/EGGNB70suUM/PGbH809COqWjQYelyPrzlCwb/yEiB Zed0xsrjCIz2cIPF6DxhRY+XlGxj76TF632X8hrmeGD2r3mK5yMSZmdM4VA0PEmjpUqw n2SyDYQ5m6JAjDRvdxgSA/bOVP0FhhG1N6xu35KydXevYFVfmXUIGj/eXCZbSRbEU6p9 /g2A== Received: by 10.180.100.131 with SMTP id ey3mr6165273wib.15.1342714786282; Thu, 19 Jul 2012 09:19:46 -0700 (PDT) Received: from LTNIT029071 ([39.47.230.252]) by mx.google.com with ESMTPS id bc2sm7144420wib.0.2012.07.19.09.19.43 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 19 Jul 2012 09:19:45 -0700 (PDT) From: "Umer Asghar" To: Subject: Postgres Database got down Date: Thu, 19 Jul 2012 21:19:39 +0500 Message-ID: <000901cd65ca$4eb7cd00$ec276700$@com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000A_01CD65F4.378DD500" X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ac1lykuza6PGHnpuT8CFsnkKH4UrPg== Content-Language: en-us X-Pg-Spam-Score: -2.6 (--) X-Archive-Number: 201207/48 X-Sequence-Number: 39765 This is a multi-part message in MIME format. ------=_NextPart_000_000A_01CD65F4.378DD500 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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. ------=_NextPart_000_000A_01CD65F4.378DD500 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

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?

 

---= ------------------------------------

 

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

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

201= 2-07-19 17:28:27 PKT LOG:  redo starts at = 102/ACFA57C8

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

201= 2-07-19 17:28:27 PKT LOG:  redo done at = 102/AD33E650

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

201= 2-07-19 17:28:27 PKT FATAL:  the database system is starting = up

201= 2-07-19 17:28:28 PKT LOG:  database system is ready to accept = connections

201= 2-07-19 17:28:28 PKT LOG:  autovacuum launcher = started

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

201= 2-07-19 18:05:08 PKT LOG:  terminating any other active server = processes

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

201= 2-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.

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

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

201= 2-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.

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

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

201= 2-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.

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

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

201= 2-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.

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

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

201= 2-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.

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

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

201= 2-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.

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

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

201= 2-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.

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

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

201= 2-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.

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

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

201= 2-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.

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

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

201= 2-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.

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

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

201= 2-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.

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

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

201= 2-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.

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

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

201= 2-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.

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

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

201= 2-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.

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

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

201= 2-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.

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

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

201= 2-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.

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

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

201= 2-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.

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

201= 2-07-19 18:05:08 PKT LOG:  all server processes terminated; = reinitializing

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

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

---= ------------------------------------

 

 

 

 

Regards,

Umer Asghar.

 

------=_NextPart_000_000A_01CD65F4.378DD500--