X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id BCB0E8B9F17; Wed, 16 Feb 2005 18:46:18 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 33055-08; Wed, 16 Feb 2005 18:45:56 +0000 (GMT) Received: from mail.deg.cc (mail.deg.cc [64.139.134.201]) by svr1.postgresql.org (Postfix) with ESMTP id 1E6F58B9F19; Wed, 16 Feb 2005 18:36:31 +0000 (GMT) Received: from mail.deg.cc (unknown [127.0.0.1]) by mail.deg.cc (Postfix) with ESMTP id 12FB55606A; Wed, 16 Feb 2005 13:36:27 -0500 (EST) Received: (from apache@localhost) by mail.deg.cc (8.12.8/8.12.8/Submit) id j1GIaQv0029541; Wed, 16 Feb 2005 13:36:26 -0500 X-Authentication-Warning: mail.deg.cc: apache set sender to pkalva@deg.cc using -f Received: from kyle.deg.cc (kyle.deg.cc [198.70.16.205]) by mail.deg.cc (IMP) with HTTP for ; Wed, 16 Feb 2005 13:36:26 -0500 Message-ID: <1108578986.421392aad28bd@mail.deg.cc> Date: Wed, 16 Feb 2005 13:36:26 -0500 From: pkalva@deg.cc To: pgsql-bugs@postgresql.org Cc: pgsql-admin@postgresql.org Subject: Postgres crashed on invalid IP entry in pg_hba.conf MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.2 X-Originating-IP: 198.70.16.205 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.114 tagged_above=0 required=5 tests=AWL, NO_REAL_NAME X-Spam-Level: X-Archive-Number: 200502/146 X-Sequence-Number: 16314 Hi Everybody, Yesterday, our production database was crashed as soon as we added an invlid entry in the pg_hba.conf file. Immediately, after the SIGHUP it tried to read the pg_hba.conf file and it couldnt validate the IP address and restarted the postgres server, as soon as we change the pg_hba.conf with the right entry everything was back to normal. Attached you will see the postgres log file at the time of the crash. Postgres version we are using is 7.4.2. Is this somekind of bug ? if so, is it fixed in Postgres 8 ? shouldnt it just give an error saying invalid IP address instead of restarting postgres ? Thanks! Pallav