Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 030649FB5BD for ; Wed, 24 Jan 2007 04:47:53 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-new, port 10024) with ESMTP id 72532-09 for ; Wed, 24 Jan 2007 04:47:48 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from matrix.gatewaynet.com (host2.dynacom.ondsl.gr [62.103.35.210]) by postgresql.org (Postfix) with ESMTP id 594299FB588 for ; Wed, 24 Jan 2007 04:47:48 -0400 (AST) Received: from host3.dynacom.ondsl.gr ([62.103.35.211] helo=ip216.internal.net) by matrix.gatewaynet.com with esmtp (Exim 4.62) (envelope-from ) id 1H9dnF-0005Oj-RP for pgsql-admin@postgresql.org; Wed, 24 Jan 2007 10:47:45 +0200 From: Achilleas Mantzios Organization: Dynacom Tankers Mgmt To: pgsql-admin@postgresql.org Subject: Re: server process (PID xxx) was terminated by signal 7 User-Agent: KMail/1.9.3 References: <20070122105038.805CA19F306@smtp07l.fasthosts.co.uk> <200701230940.39784.achill@matrix.gatewaynet.com> <18126.1169562310@sss.pgh.pa.us> In-Reply-To: <18126.1169562310@sss.pgh.pa.us> MIME-Version: 1.0 Content-Disposition: inline Date: Wed, 24 Jan 2007 10:47:44 +0200 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <200701241047.45279.achill@matrix.gatewaynet.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200701/221 X-Sequence-Number: 24377 =CE=A3=CF=84=CE=B9=CF=82 =CE=A4=CF=81=CE=AF=CF=84=CE=B7 23 =CE=99=CE=B1=CE= =BD=CE=BF=CF=85=CE=AC=CF=81=CE=B9=CE=BF=CF=82 2007 16:25, =CE=B3=CF=81=CE= =AC=CF=88=CE=B1=CF=84=CE=B5: > Achilleas Mantzios writes: > >> Since you have not told us what the platform is, there is no way to > >> guess what signal 7 means. > > > > Its a Bus error (SIGBUS). Those remote servers run on linux. > > Hm, pretty indeterminate then --- could be flaky hardware, or an > invalid storage access caused either by a software bug or corrupted > data. > > My advice would be (1) update to something newer than 7.4.2, and > (2) run some hardware tests such as memtest86. We ship the new machines with 7.4.15 installed. Unfortunately the ones already at production are not easy to reach by any means (in the 7 seas, unreliable SAT coms, mgetty not always work), so not only we cannot boot memtest86, but many times we can't even get a shell to do basic admin work. oh and the lines are unreliable 64kbps ISDN, 9600bps or even 2400bps!!, Weird setup for most of you, but it proves postgresql robustness running 50 such servers with almost zero administration/problems. > > regards, tom lane =2D-=20 Achilleas Mantzios