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 8EDFC5E40BA for ; Mon, 16 Aug 2004 04:42:18 -0300 (ADT) 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 64833-04 for ; Mon, 16 Aug 2004 07:42:11 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id 7C46F5E46DF for ; Mon, 16 Aug 2004 04:42:10 -0300 (ADT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.12.9/8.12.9) with ESMTP id i7G7g8iI067421 for ; Mon, 16 Aug 2004 07:42:09 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id i7G7Y8o3064927 for pgsql-admin@postgresql.org; Mon, 16 Aug 2004 07:34:08 GMT From: "Martin J. Brown, Jr." Subject: Re: can't authenticate pg admin User-Agent: Pan/0.14.2 (This is not a psychotic episode. It's a cleansing moment of clarity.) Message-ID: X-Newsgroups: comp.databases.postgresql.admin References: <25827.1092423276@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Lines: 49 X-Complaints-To: abuse@prodigy.net Organization: SBC http://yahoo.sbc.com X-UserInfo1: O@ZGB_ODGB^UCWDYIBHZOWP@YZOZ@GXOXZ\@LWQHBATBTSUBYFWEAE[YJLYPIWKHTFCMZKVMB^[Z^DOBRVVMOSPFHNSYXVDIE@X\BUC@GTSX@DL^GKFFHQCCE\G[JJBMYDYIJCZM@AY]GNGPJD]YNNW\GSX^GSCKHA[]@CCB\[@LATPD\L@J\\PF]VR[QPJN Date: Mon, 16 Aug 2004 07:30:59 GMT To: pgsql-admin@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=1.9 tagged_above=0.0 required=5.0 tests=WEIRD_PORT X-Spam-Level: * X-Archive-Number: 200408/183 X-Sequence-Number: 14578 On Fri, 13 Aug 2004 14:54:36 -0400, Tom Lane wrote: > "Martin J. Brown, Jr." writes: >> Other db users authenticate fine, only the admin fails. > > That seems very odd. The only theory that comes to mind is that you've > set a password expiration time for that account in pg_shadow. > After double checking... Yes, the pg admin, "postgres", fails authentication, and regular db users don't even get asked to authenticate!! 'pg_hba.conf' shows: local all all password # IPv4-style local connections: host all all 127.0.0.1 255.255.255.255 password # IPv6-style local connections: host all all ::1 ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff password As for 'pg_shadow', never touched it. In the process of trying to hunt down this problem, I've set "postgres"'s pw numerous times. And the time from that to testing would've been less than 30 seconds. A very short expiration, indeed. Is there a way to check that the pw has actually been set (to anything)? When I use 'alter user postgres with password 'abc'' within 'psql'and hit enter, I get a new psql prompt, but no indication of whether the command succeeded or failed. Is that normal?