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 194A3D1B34F for ; Thu, 1 Jul 2004 02:32:11 -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 97749-06 for ; Thu, 1 Jul 2004 05:32:10 +0000 (GMT) Received: from mpls-qmqp-04.inet.qwest.net (mpls-qmqp-04.inet.qwest.net [63.231.195.115]) by svr1.postgresql.org (Postfix) with SMTP id E51F1D1B2D9 for ; Thu, 1 Jul 2004 02:32:07 -0300 (ADT) Received: (qmail 8028 invoked by uid 0); 1 Jul 2004 05:32:08 -0000 Received: from mpls-pop-12.inet.qwest.net (63.231.195.12) by mpls-qmqp-04.inet.qwest.net with QMQP; 1 Jul 2004 05:32:08 -0000 Received: from 63-227-127-37.dnvr.qwest.net (HELO ?10.0.0.2?) (63.227.127.37) by mpls-pop-12.inet.qwest.net with SMTP; 1 Jul 2004 05:32:07 -0000 Date: Wed, 30 Jun 2004 23:33:04 -0600 Message-Id: <1088659984.4056.9.camel@localhost.localdomain> From: "Scott Marlowe" 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> Content-Type: text/plain Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.1 tagged_above=0.0 required=5.0 tests=RCVD_IN_SORBS X-Spam-Level: X-Archive-Number: 200407/4 X-Sequence-Number: 14072 On Wed, 2004-06-30 at 21:38, Jens Porup wrote: > The request tracker database setup script dies trying to connect to > the database: > > DBI connect('dbname=template1;host=localhost','rtuser',...) failed: could not > connect to server: Connection refused at /usr/sbin/rt-setup-database line 110 > > 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? > Now before you ask: > > Yes, the following lines appear uncommented in my > /etc/postgresql/postgresql.conf: > > tcpip_socket = true > port = 5432 > > But then: > > root@request-tracker:~# netstat -auntp > > shows postmaster running on a udp port??? > > udp 0 0 127.0.0.1:1042 127.0.0.1:1042 ESTABLISHED18375/postmaster > But can you nmap it? And that's not the right default port 5432... Maybe it's some new feature I'm familiar with, or you've changed it. What does nmap show? > A server restart shows: > > root@request-tracker:~# /etc/init.d/postgresql restart > Stopping PostgreSQL database server: autovacuumNo pg_autovacuum found running; > none killed. > postmaster. > Starting PostgreSQL database server: postmaster autovacuum. Sounds like a firewall to me. > What is pg_autovacuum anyway? I dunno.... Coolest thing since sliced bread? It's a process that comes along and cleans house in the back ground, without putting the onus of keeping the database well cleaned on the average user. > And finally, I *do* have lines in my pg_hba.conf file (and yes, in the correct > order) to allow my user 'rtuser' to connect to template1: > > host template1 rtuser 127.0.0.1 255.255.255.255 password > local template1 rtuser password > host rtdb rtuser 127.0.0.1 255.255.255.255 password > local rtdb rtuser password Yeah, you'd see it as a different error, one about not having permission to connect, like: psql: FATAL: no pg_hba.conf entry for host "10.0.0.2", user "postgres", database "postgres", SSL off Hope that helps.