Re: Postgres IDENT auth problems... - Mailing list pgsql-admin
From | Jens Porup |
---|---|
Subject | Re: Postgres IDENT auth problems... |
Date | |
Msg-id | 20040701054614.GB9047@vanilla.office.cyber.com.au Whole thread Raw |
In response to | Postgres IDENT auth problems... (Jens Porup <jens@cyber.com.au>) |
Responses |
Re: Postgres IDENT auth problems...
|
List | pgsql-admin |
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 > > <snip> > > > > 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! > > What does nmap <ip> 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? > > 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: > > > > 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 Well, that helps eliminate one possibility anyway. Any more ideas? Thanks, Jens > > Hope that helps.
pgsql-admin by date: