Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id EE8D32E0133 for ; Mon, 17 Mar 2008 22:20:48 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 23469-06 for ; Mon, 17 Mar 2008 22:20:41 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.228]) by postgresql.org (Postfix) with ESMTP id 54EAB2E0042 for ; Mon, 17 Mar 2008 22:20:35 -0300 (ADT) Received: by wx-out-0506.google.com with SMTP id r21so5146610wxc.28 for ; Mon, 17 Mar 2008 18:20:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:from:to:subject:date:mime-version:content-type:x-priority:x-msmail-priority:x-mailer:x-mimeole; bh=q7gn4S+gZAqdfHjYsjDKym3M/u9zMSAplTZarve19H0=; b=sJyMqZpRHntQYFM/sJzqM7WsrqlFPx09ORqI5GWGJNPXYwu4i4sYKrjGba3lAq5+FmTTNA49EXW3cnjBtbxOeyQh3F9iRA6dwFnQvqRZQerukEaxe19jNCj9+B69NZYPTf5icAiRrtjJ99BEV2Ti5xWPL9RorRmbJiMye2eORO8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:subject:date:mime-version:content-type:x-priority:x-msmail-priority:x-mailer:x-mimeole; b=KfGs5Z4ghvNCHPNCaNo417T9MuRT/Exs2FLmN2Rlp/kRSS8fjccKDhvzxBSSRphV33QFt3JIlkWNhh63b13AHXMs/fqRgMETu4bLk+bPgAxVeZGY5GFbXsEUfvM7G7wcWj0ORHTO48ZHyUIKKmh8BUAaaHeD50iq5BG+0V01kNc= Received: by 10.100.110.16 with SMTP id i16mr100309anc.109.1205803219741; Mon, 17 Mar 2008 18:20:19 -0700 (PDT) Received: from ToshibaLaptop ( [64.84.15.165]) by mx.google.com with ESMTPS id i52sm709211rne.9.2008.03.17.18.20.17 (version=SSLv3 cipher=OTHER); Mon, 17 Mar 2008 18:20:18 -0700 (PDT) Message-ID: <71EB10BF787341C28A47F33667D0D8FC@ToshibaLaptop> From: "Chadwick Horn" To: Subject: postgres server crashes unexpectedly Date: Mon, 17 Mar 2008 18:20:15 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0039_01C8885B.8C596750" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Windows Mail 6.0.6000.16480 X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6000.16545 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=1.069 tagged_above=0 required=5 tests=AWL=1.068, HTML_MESSAGE=0.001 X-Spam-Level: * X-Archive-Number: 200803/93 X-Sequence-Number: 30421 This is a multi-part message in MIME format. ------=_NextPart_000_0039_01C8885B.8C596750 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable hi all, we've had a db to stop working for some reason and have searched through = google to it's ends to no avail. we have reindexed the database and = system database as tried to determine other things that would keep it = from working... again, to no avail. this just started occuring about 2 weeks ago and below is a recent = snippet of error log that we have. any idea what would/could be causing = these crashes? any response is much appreciated as this is not a = time-critial issue for us. thanks! chadwick error log: LOG: redo is not required LOG: database system is ready PANIC: corrupted item pointer: offset =3D 0, size =3D 0 LOG: autovacuum process (PID 3037) was terminated by signal 6 LOG: terminating any other active server processes LOG: all server processes terminated; reinitializing LOG: database system was interrupted at 2008-03-18 02:55:30 PDT LOG: checkpoint record is at 25/6068AE30 LOG: redo record is at 25/6068AE30; undo record is at 0/0; shutdown = TRUE LOG: next transaction ID: 0/414366728; next OID: 240102 LOG: next MultiXactId: 1132; next MultiXactOffset: 2431 LOG: database system was not properly shut down; automatic recovery in = progress LOG: record with zero length at 25/6068AE80 LOG: redo is not required LOG: database system is ready PANIC: corrupted item pointer: offset =3D 0, size =3D 0 LOG: autovacuum process (PID 3045) was terminated by signal 6 LOG: terminating any other active server processes LOG: all server processes terminated; reinitializing LOG: database system was interrupted at 2008-03-18 02:56:31 PDT LOG: checkpoint record is at 25/6068AE80 LOG: redo record is at 25/6068AE80; undo record is at 0/0; shutdown = TRUE LOG: next transaction ID: 0/414366728; next OID: 240102 LOG: next MultiXactId: 1132; next MultiXactOffset: 2431 LOG: database system was not properly shut down; automatic recovery in = progress LOG: record with zero length at 25/6068AED0 LOG: redo is not required LOG: database system is ready PANIC: corrupted item pointer: offset =3D 0, size =3D 0 LOG: autovacuum process (PID 3072) was terminated by signal 6 LOG: terminating any other active server processes WARNING: terminating connection because of crash of another server = process 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. HINT: In a moment you should be able to reconnect to the database and = repeat your command. LOG: all server processes terminated; reinitializing LOG: database system was interrupted at 2008-03-18 02:57:32 PDT LOG: checkpoint record is at 25/6068AED0 LOG: redo record is at 25/6068AED0; undo record is at 0/0; shutdown = TRUE LOG: next transaction ID: 0/414366728; next OID: 240102 LOG: next MultiXactId: 1132; next MultiXactOffset: 2431 LOG: database system was not properly shut down; automatic recovery in = progress LOG: record with zero length at 25/6068AF20 LOG: redo is not required LOG: database system is ready ------=_NextPart_000_0039_01C8885B.8C596750 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
hi all,
 
we've had a db to stop working for some = reason and=20 have searched through google to it's ends to no avail. we have reindexed = the=20 database and system database as tried to determine other things that = would keep=20 it from working... again, to no avail.
 
this just started occuring about 2 = weeks ago and=20 below is a recent snippet of error log that we have.  any idea what = would/could be causing these crashes? any response is much appreciated = as this=20 is not a time-critial issue for us.
 
 
thanks!
 
chadwick
 
error log:
 
 
LOG:  redo is not = required
LOG: =20 database system is ready
PANIC:  corrupted item pointer: offset = =3D 0,=20 size =3D 0
LOG:  autovacuum process (PID 3037) was terminated by = signal=20 6
LOG:  terminating any other active server = processes
LOG:  all=20 server processes terminated; reinitializing
LOG:  database = system was=20 interrupted at 2008-03-18 02:55:30 PDT
LOG:  checkpoint record = is at=20 25/6068AE30
LOG:  redo record is at 25/6068AE30; undo record is = at 0/0;=20 shutdown TRUE
LOG:  next transaction ID: 0/414366728; next OID:=20 240102
LOG:  next MultiXactId: 1132; next MultiXactOffset:=20 2431
LOG:  database system was not properly shut down; automatic = recovery in progress
LOG:  record with zero length at=20 25/6068AE80
LOG:  redo is not required
LOG:  database = system is=20 ready
PANIC:  corrupted item pointer: offset =3D 0, size =3D = 0
LOG: =20 autovacuum process (PID 3045) was terminated by signal 6
LOG: =20 terminating any other active server processes
LOG:  all server = processes=20 terminated; reinitializing
LOG:  database system was interrupted = at=20 2008-03-18 02:56:31 PDT
LOG:  checkpoint record is at=20 25/6068AE80
LOG:  redo record is at 25/6068AE80; undo record is = at 0/0;=20 shutdown TRUE
LOG:  next transaction ID: 0/414366728; next OID:=20 240102
LOG:  next MultiXactId: 1132; next MultiXactOffset:=20 2431
LOG:  database system was not properly shut down; automatic = recovery in progress
LOG:  record with zero length at=20 25/6068AED0
LOG:  redo is not required
LOG:  database = system is=20 ready
PANIC:  corrupted item pointer: offset =3D 0, size =3D = 0
LOG: =20 autovacuum process (PID 3072) was terminated by signal 6
LOG: =20 terminating any other active server processes
WARNING:  = terminating=20 connection because of crash of another server process
DETAIL:  = The=20 postmaster has commanded this server process to roll back the current=20 transaction and exit, because another server process exited abnormally = and=20 possibly corrupted shared memory.
HINT:  In a moment you should = be able=20 to reconnect to the database and repeat your command.
LOG:  all = server=20 processes terminated; reinitializing
LOG:  database system was=20 interrupted at 2008-03-18 02:57:32 PDT
LOG:  checkpoint record = is at=20 25/6068AED0
LOG:  redo record is at 25/6068AED0; undo record is = at 0/0;=20 shutdown TRUE
LOG:  next transaction ID: 0/414366728; next OID:=20 240102
LOG:  next MultiXactId: 1132; next MultiXactOffset:=20 2431
LOG:  database system was not properly shut down; automatic = recovery in progress
LOG:  record with zero length at=20 25/6068AF20
LOG:  redo is not required
LOG:  database = system is=20 ready
 
 
 
 
 
------=_NextPart_000_0039_01C8885B.8C596750--