pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jens Porup <jens@cyber.com.au>
To: Scott Marlowe <smarlowe@qwest.net>
Cc: pgsql-admin@postgresql.org
Subject: Re: Postgres IDENT auth problems...
Date: Fri, 2 Jul 2004 12:38:54 +1000
Message-ID: <20040702023854.GB22979@vanilla.office.cyber.com.au> (raw)
In-Reply-To: <1088695529.14882.3.camel@localhost.localdomain>
References: <20040701033844.GA7583@vanilla.office.cyber.com.au>
	<1088659984.4056.9.camel@localhost.localdomain>
	<20040701054614.GB9047@vanilla.office.cyber.com.au>
	<1088695529.14882.3.camel@localhost.localdomain>

On Thu, Jul 01, 2004 at 09:25:29AM -0600, Scott Marlowe wrote:
> > > > 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
> 
	root@request-tracker:~# nmap -p 1042

	Starting nmap 3.50 ( http://www.insecure.org/nmap/ ) at 2004-07-02 12:36 EST
	WARNING: No targets were specified, so 0 hosts scanned.
	Nmap run completed -- 0 IP addresses (0 hosts up) scanned in 0.003 seconds

	root@request-tracker:~# psql -h 127.0.0.1 -p 1042
	No database specified
	root@request-tracker:~#

*sigh*

I am beginning to think this is probably a build issue with the user mode linux
kernel I'm using. I'll look into that now.

Thanks,

Jens



> 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 <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?
> 
> IF the database is configured for port 1042, then it might not be a
> firewall, just a misconfiguration of the database.
> 



view thread (8+ messages)  latest in thread

Message-ID: <20040702023854.GB22979@vanilla.office.cyber.com.au>
Permalink:  ../20040702023854.GB22979@vanilla.office.cyber.com.au/
Also on:    postgresql.org/message-id/20040702023854.GB22979@vanilla.office.cyber.com.au

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: jens@cyber.com.au, smarlowe@qwest.net
  Subject: Re: Postgres IDENT auth problems...
  In-Reply-To: <20040702023854.GB22979@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> <1088695529.14882.3.camel@localhost.localdomain> <20040702023854.GB22979@vanilla.office.cyber.com.au>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox