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 E5F568B9F37; Wed, 16 Feb 2005 20:19:27 +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 44043-10; Wed, 16 Feb 2005 20:18:51 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 860A68BA156; Wed, 16 Feb 2005 20:05:19 +0000 (GMT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j1GK5Hg2026830; Wed, 16 Feb 2005 15:05:17 -0500 (EST) To: pkalva@deg.cc Cc: pgsql-bugs@postgresql.org, pgsql-admin@postgresql.org Subject: Re: Postgres crashed on invalid IP entry in pg_hba.conf In-reply-to: <1108578986.421392aad28bd@mail.deg.cc> References: <1108578986.421392aad28bd@mail.deg.cc> Comments: In-reply-to pkalva@deg.cc message dated "Wed, 16 Feb 2005 13:36:26 -0500" Date: Wed, 16 Feb 2005 15:05:17 -0500 Message-ID: <26829.1108584317@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.007 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200502/148 X-Sequence-Number: 16316 pkalva@deg.cc writes: > 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. Works fine for me in 7.4.7 ... I get log entries like this: LOG: invalid IP address "1727.0.0.1" in pg_hba.conf file: Unknown server error LOG: invalid entry in pg_hba.conf file at line 56, token "1727.0.0.1" FATAL: missing or erroneous pg_hba.conf file HINT: See server log for details. and after I fix the pg_hba.conf file it lets me in again. I see no crash. regards, tom lane