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 7CEDE8B9CB0 for ; Thu, 3 Feb 2005 06:10: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 88403-04 for ; Thu, 3 Feb 2005 06:10:15 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id EC8458B9B31 for ; Thu, 3 Feb 2005 06:10:15 +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 j136AEoF012551; Thu, 3 Feb 2005 01:10:14 -0500 (EST) To: vieglais@ku.edu Cc: pgsql-admin@postgresql.org Subject: Re: client authentication problem In-reply-to: <42002213.6070405@ku.edu> References: <42002213.6070405@ku.edu> Comments: In-reply-to Dave Vieglais message dated "Wed, 02 Feb 2005 13:42:59 +1300" Date: Thu, 03 Feb 2005 01:10:14 -0500 Message-ID: <12550.1107411014@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200502/18 X-Sequence-Number: 16186 Dave Vieglais writes: > Contents of pg_hba.conf: > local all postgres ident sameuser > local all all md5 > host all all 127.0.0.1 255.255.255.255 md5 > host all all 0.0.0.0 0.0.0.0 reject > # tail /var/log/postgresql/postgresql.log > LOG: redo record is at 0/6851324; undo record is at 0/0; shutdown TRUE > LOG: next transaction ID: 61873; next OID: 28747 > LOG: database system is ready > 2005-01-31 16:03:23 [31418] LOG: connection received: host=127.0.0.1 port=33377 > 2005-01-31 16:03:23 [31418] LOG: cannot use authentication method "crypt" > because password is MD5-encrypted > 2005-01-31 16:03:23 [31418] FATAL: Password authentication failed for user > "test" I'm fairly sure that this log entry is not possible unless the postmaster found a pg_hba.conf entry specifying "crypt". Accordingly I suspect pilot error. Perhaps you are looking at the wrong copy of pg_hba.conf? Or maybe you changed the file and forgot to SIGHUP the postmaster? regards, tom lane