Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 855BB9FB4CC for ; Mon, 22 Jan 2007 07:12:11 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-new, port 10024) with ESMTP id 93779-03 for ; Mon, 22 Jan 2007 07:12:04 -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 EF18D9FA4B4 for ; Mon, 22 Jan 2007 07:12:07 -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 1H8x5p-0004TY-4v for pgsql-admin@postgresql.org; Mon, 22 Jan 2007 13:12:05 +0200 From: Achilleas Mantzios Organization: Dynacom Tankers Mgmt To: pgsql-admin@postgresql.org Subject: server process (PID xxx) was terminated by signal 7 Date: Mon, 22 Jan 2007 13:12:04 +0200 User-Agent: KMail/1.9.3 References: <20070122105038.805CA19F306@smtp07l.fasthosts.co.uk> In-Reply-To: <20070122105038.805CA19F306@smtp07l.fasthosts.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200701221312.04840.achill@matrix.gatewaynet.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200701/190 X-Sequence-Number: 24346 In one of our remote pgsql 7.4.2 installations (no tcp/ip, no mgetty dialin works always), i got the above message. The pgsql server restarted right away, but in the meantime a significant cron job that just hapened to be executed between SIG7 and start, failed, and so that triggered the investigation. Could you think of a reason for this "signal 7" caught by the pgsql server? Memory or other HW problem maybe? Thank you. -- Achilleas Mantzios