X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 391089FBAD6 for ; Fri, 25 Aug 2006 11:46:28 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 50883-05 for ; Fri, 25 Aug 2006 14:46:15 +0000 (UTC) X-Greylist: delayed 03:32:14.296204 by SQLgrey- Received: from smtp-out2.blueyonder.co.uk (smtp-out2.blueyonder.co.uk [195.188.213.5]) by postgresql.org (Postfix) with ESMTP id 65C739FBAD5 for ; Fri, 25 Aug 2006 11:46:15 -0300 (ADT) Received: from [172.23.170.143] (helo=anti-virus02-10) by smtp-out2.blueyonder.co.uk with smtp (Exim 4.52) id 1GGcwn-0001a2-OR for pgsql-admin@postgresql.org; Fri, 25 Aug 2006 15:46:13 +0100 Received: from [82.44.23.191] (helo=demolish1) by asmtp-out5.blueyonder.co.uk with smtp (Exim 4.52) id 1GGcwn-0001hY-0z for pgsql-admin@postgresql.org; Fri, 25 Aug 2006 15:46:13 +0100 Message-ID: <008c01c6c855$35f6cd20$7d64a8c0@demolish1> From: "Donald Fraser" To: "[ADMIN]" References: <003401c6c837$8dc6cb90$7d64a8c0@demolish1> <23160.1156513462@sss.pgh.pa.us> Subject: Re: Strange message followed by server crash Date: Fri, 25 Aug 2006 15:46:11 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0089_01C6C85D.97250FA0" 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/287 X-Sequence-Number: 22830 This is a multi-part message in MIME format. ------=_NextPart_000_0089_01C6C85D.97250FA0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable >"Donald Fraser" writes: >> 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 >> At the same time, an engineer, who thought nobody was in the = building, was working on the network and changing a network switch. "Tom Lane" writes: >And what do you make of the apparent junk on the log line? (What's >your log_line_prefix exactly?) The log messages are good, log prefix is: <%u %p %t %x>=20 "1Tmenteshvili" is actually a user login name... don't ask. >Given that this sounds like it won't be easy to reproduce, I'm hoping >you have a core file left from that and can get a stack trace from it. >That would give us some clue where to look. Where would I look for a core file? There's nothing unusual in the data directory, nothing in the /tmp = directory? I had my email turned off yesterday and PostgreSQL restarted itself so I = didn't find out about the crash till this morning when I logged in. Everything seems to have be running smoothly since then... If there isn't a core file, how would I go about ensuring one is created = next time? (touch wood there wont be one). Regards Donald Fraser ------=_NextPart_000_0089_01C6C85D.97250FA0 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
>"Donald Fraser" <postgres@kiwi-fraser.net>= =20 writes:
>> Log messages:
>> <1Tmenteshvili 10709 = 2006-08-24=20 17:48:19 BST 0> ERROR:  invalid message format
>> < = 3670=20 2006-08-24 17:48:19 BST > LOG:  server process (PID 10709) was=20 terminated by signal 11

>> At the same time, an engineer, = who=20 thought nobody was in the building, was working on the network and = changing a=20 network switch.
 
"Tom Lane" writes:
>And what do you = make of the=20 apparent junk on the log line?  (What's
>your log_line_prefix = exactly?)
The log messages are good, log prefix is: <%u %p = %t %x>=20
"1Tmenteshvili" is actually a user login name... don't = ask.

>Given=20 that this sounds like it won't be easy to reproduce, I'm = hoping
>you have=20 a core file left from that and can get a stack trace from = it.
>That would=20 give us some clue where to look.

Where would I = look for a=20 core file?
There's nothing unusual in the data directory, = nothing in the=20 /tmp directory?
 
I had my email turned off yesterday and PostgreSQL = restarted=20 itself so I didn't find out about the crash till this morning when I = logged=20 in.
Everything seems to have be running smoothly since=20 then...
If there isn't a core file, how would I go about = ensuring one=20 is created next time? (touch wood there wont be one).
 
Regards
Donald Fraser
 
------=_NextPart_000_0089_01C6C85D.97250FA0--