X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 89B5A9FB90F for ; Fri, 25 Aug 2006 08:33:19 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 17598-09 for ; Fri, 25 Aug 2006 08:33:14 -0300 (ADT) X-Greylist: delayed 00:19:11.773484 by SQLgrey- Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id 09D539FB916 for ; Fri, 25 Aug 2006 08:33:11 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.3 Received: from smtp-out2.blueyonder.co.uk (smtp-out2.blueyonder.co.uk [195.188.213.5]) by svr4.postgresql.org (Postfix) with ESMTP id DEC4E5AF893 for ; Fri, 25 Aug 2006 11:13:58 +0000 (GMT) Received: from [172.23.170.143] (helo=anti-virus02-10) by smtp-out2.blueyonder.co.uk with smtp (Exim 4.52) id 1GGZdM-0001b9-Fj for pgsql-admin@postgresql.org; Fri, 25 Aug 2006 12:13:56 +0100 Received: from [82.44.23.191] (helo=demolish1) by asmtp-out2.blueyonder.co.uk with smtp (Exim 4.52) id 1GGZdL-0002Jc-9c for pgsql-admin@postgresql.org; Fri, 25 Aug 2006 12:13:55 +0100 Message-ID: <003401c6c837$8dc6cb90$7d64a8c0@demolish1> From: "Donald Fraser" To: "[ADMIN]" Subject: Strange message followed by server crash Date: Fri, 25 Aug 2006 12:13:54 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0031_01C6C83F.EED85E50" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.497 tagged_above=0 required=5 tests=HTML_40_50, HTML_MESSAGE X-Spam-Level: X-Archive-Number: 200608/280 X-Sequence-Number: 22823 This is a multi-part message in MIME format. ------=_NextPart_000_0031_01C6C83F.EED85E50 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I'm trying to figure out what exactly caused PostgreSQL to crash. PostgreSQL 8.0.7 OS: Red Hat Linux EL 4.0 Log messages: <1Tmenteshvili 10709 2006-08-24 17:48:19 BST 0> ERROR: invalid message = format < 3670 2006-08-24 17:48:19 BST > LOG: server process (PID 10709) was = terminated by signal 11 < 3670 2006-08-24 17:48:19 BST > LOG: terminating any other active = server processes Looking into PostgreSQL code I note that the message "invalid message = format" is generated by function: pq_getmsgend which is called when = processing incoming messages from clients.=20 So am I correct in assuming that there was an error in the front = end/back end data sent to PostgreSQL? I asked the client above what they were doing when this event occurred = and the answer was logging out of the database. At the same time, an engineer, who thought nobody was in the building, = was working on the network and changing a network switch. Therefore can I assume this crash was caused by some form of corrupt / = incomplete data sent to PostgreSQL? Thanks in advance regards Donald Fraser ------=_NextPart_000_0031_01C6C83F.EED85E50 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I'm trying to figure out what exactly caused = PostgreSQL to=20 crash.
 
PostgreSQL 8.0.7
OS: Red Hat Linux EL 4.0
 
Log messages:
<1Tmenteshvili 10709 2006-08-24 17:48:19 BST = 0>=20 ERROR:  invalid message format
< 3670 2006-08-24 17:48:19 BST = >=20 LOG:  server process (PID 10709) was terminated by signal = 11
< 3670=20 2006-08-24 17:48:19 BST > LOG:  terminating any other active = server=20 processes
 
Looking into PostgreSQL code I note that the message "invalid = message=20 format" is generated by function: pq_getmsgend which is called when = processing incoming messages from clients.
So am I correct in assuming that there was an error in the front = end/back=20 end data sent to PostgreSQL?
 
I asked the client above what they were doing when this event = occurred and=20 the answer was logging out of the database.
 
At the same time, an engineer, who thought nobody was in = the=20 building, was working on the network and changing a network = switch.
Therefore can I assume this crash was caused by some form of = corrupt /=20 incomplete data sent to PostgreSQL?
 
Thanks in advance
regards
Donald Fraser
 
 
------=_NextPart_000_0031_01C6C83F.EED85E50--