X-Original-To: pgsql-bugs-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 6313DD1D202 for ; Tue, 27 Jan 2004 11:37:28 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 08561-08 for ; Tue, 27 Jan 2004 07:37:00 -0400 (AST) Received: from kriweb.com (mail140-97-kadikoy.kriter.com.tr [81.22.97.140]) by svr1.postgresql.org (Postfix) with SMTP id 81D21D1D1CD for ; Tue, 27 Jan 2004 07:36:54 -0400 (AST) Received: (qmail 19732 invoked by uid 0); 27 Jan 2004 13:33:36 +0200 Received: from unknown (HELO ckeskin) (212.174.53.174) by mail153-97-kadikoy.kriter.com.tr with SMTP; 27 Jan 2004 13:33:36 +0200 From: "Cavit Keskin" To: Cc: Subject: PgSQL Down Date: Tue, 27 Jan 2004 13:36:29 +0200 Message-ID: <000501c3e4c9$ce9d2370$2363a8c0@ckeskin> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2727.1300 Importance: Normal In-Reply-To: X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/176 X-Sequence-Number: 7755 Using Postgresql's source files I compiled postgresql 7.4.1 on a dedicated machine with a customized Redhat 7.2 system. Postgresql often stops after a time (unknown, changing). Below is the log file just after Postgresql database server is started manually. Log can't record the cause of this problem. _____________________ LOG: could not create IPv6 socket: Address family not supported by protocol LOG: database system was interrupted at 2004-01-27 03:18:09 CST LOG: checkpoint record is at 0/4470A6C LOG: redo record is at 0/4470A6C; undo record is at 0/0; shutdown FALSE LOG: next transaction ID: 1275; next OID: 234555 LOG: database system was not properly shut down; automatic recovery in progress LOG: record with zero length at 0/4470AAC LOG: redo is not required LOG: database system is ready ______________________________________ Please note that I don't experience such a problem on a Slackware 9.0 system. Cavit Keskin cavit@binbir.net