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 C96E9D1B179 for ; Thu, 1 Jul 2004 12:24:58 -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 94702-08 for ; Thu, 1 Jul 2004 15:24:49 +0000 (GMT) Received: from mpls-qmqp-01.inet.qwest.net (mpls-qmqp-01.inet.qwest.net [63.231.195.112]) by svr1.postgresql.org (Postfix) with SMTP id 3EF4CD1B34A for ; Thu, 1 Jul 2004 12:24:48 -0300 (ADT) Received: (qmail 33608 invoked by uid 0); 1 Jul 2004 15:24:44 -0000 Received: from unknown (63.231.195.5) by mpls-qmqp-01.inet.qwest.net with QMQP; 1 Jul 2004 15:24:44 -0000 Received: from 63-227-127-37.dnvr.qwest.net (HELO ?10.0.0.2?) (63.227.127.37) by mpls-pop-05.inet.qwest.net with SMTP; 1 Jul 2004 15:24:42 -0000 Date: Thu, 01 Jul 2004 09:25:29 -0600 Message-Id: <1088695529.14882.3.camel@localhost.localdomain> From: "Scott Marlowe" To: "Jens Porup" Cc: pgsql-admin@postgresql.org Subject: Re: Postgres IDENT auth problems... In-Reply-To: <20040701054614.GB9047@vanilla.office.cyber.com.au> References: <20040701033844.GA7583@vanilla.office.cyber.com.au> <1088659984.4056.9.camel@localhost.localdomain> <20040701054614.GB9047@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/8 X-Sequence-Number: 14076 On Wed, 2004-06-30 at 23:46, Jens Porup wrote: > On Wed, Jun 30, 2004 at 11:33:04PM -0600, Scott Marlowe wrote: > > 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 > > > > > > > > > > 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. > > Trust me, I am a postgres newbie... I'm not trying to do anything but a *very* > ordinary install! Well, something is quite wrong then. Find your postgresql.conf file and see what port it is set to there. port 1042 is definitely not the default port. Also, try two things: nmap -p 1042 psql -h 127.0.0.1 -p 1042 If nmap can see the port open, and psql can open it, then you can just use it like that by specifying that port each time in your connect string. > > > > What does nmap show? > > root@request-tracker:~# nmap localhost > > Starting nmap 3.50 ( http://www.insecure.org/nmap/ ) at 2004-07-01 15:39 EST > Interesting ports on localhost (127.0.0.1): > (The 1654 ports scanned but not shown below are in state: closed) > PORT STATE SERVICE > 22/tcp open ssh > 25/tcp open smtp > 80/tcp open http > 113/tcp open auth > 515/tcp open printer > > Nmap run completed -- 1 IP address (1 host up) scanned in 1.735 seconds > root@request-tracker:~# > > > > 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. > > > My colleague here at work who built the user mode linux image I'm using > (the virtual "box") assures me there's no firewall installed.... how > would I check if there were? IF the database is configured for port 1042, then it might not be a firewall, just a misconfiguration of the database.