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 C77C8D1B26E for ; Thu, 1 Jul 2004 10:09:26 -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 24198-02 for ; Thu, 1 Jul 2004 13:09:21 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id BE8BBD1B174 for ; Thu, 1 Jul 2004 10:09:16 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i61D9FeP026239; Thu, 1 Jul 2004 09:09:16 -0400 (EDT) To: Jens Porup Cc: pgsql-admin@postgresql.org Subject: Re: Postgres IDENT auth problems... In-reply-to: <20040701033844.GA7583@vanilla.office.cyber.com.au> References: <20040701033844.GA7583@vanilla.office.cyber.com.au> Comments: In-reply-to Jens Porup message dated "Thu, 01 Jul 2004 13:38:44 +1000" Date: Thu, 01 Jul 2004 09:09:15 -0400 Message-ID: <26238.1088687355@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200407/7 X-Sequence-Number: 14075 Jens Porup writes: > I can connect manually to the database, like so: > root@request-tracker:~# psql -d template1 -U rtuser -W > Password: > Welcome to psql 7.4.2, the PostgreSQL interactive terminal. > But it fails if I specify the host: > root@request-tracker:~# psql -d template1 -U rtuser -h localhost -W > Password: > psql: could not connect to server: Connection refused > Is the server running on host "localhost" and accepting > TCP/IP connections on port 5432? "Connection refused" means that you got a kernel-level rejection; the postmaster never saw your request at all. AFAICS you did everything right to ensure that the postmaster is listening on TCP port 5432 (though you may want to use netstat to reconfirm this). So that leaves firewall-type problems. There is of course no separate firewall box to blame, but there definitely can be kernel packet filters getting in the way. I know that recent Red Hat releases default to blocking port-5432 traffic (along with most other ports). I don't know Debian but I'd bet it's the same story. You need to look to your ipchains or iptables configuration. regards, tom lane