Re: can't run on TCP/IP ports

I figured out the problem, postmaster when run as postgres didn't have
write permissions to /var/run/postgresql directory (where the Debian
version puts its socket files) and therefore didn't have permission to
open the socket. .

Vince Vielhaber wrote:
>
> On Sun, 4 Feb 2001, Patrick Raphael wrote:
>
> >
> > When I attempt to run postmaster on a TCP/IP socket, I get the following
> > error:
> >
> >
> > FATAL: StreamServerPort: bind() failed: Permission denied
> > Is another postmaster already running on that port?
> > If not, remove socket node (/var/run/postgresql/.s.PGSQL.5432)
> > and retry.
> > /usr/lib/postgresql/bin/postmaster: cannot create UNIX stream port
> >
> >
> > There is no other postmaster running, there is nothing in
> > /var/run/postgresql, nothing else is on port 5432(switching to another
> > port doesn't make a difference), I am logged on as user postgres, the
> > user postgres owns all files in the postgres home directory, and
> > postmaster works fine with UNIX domain sockets. Does anyone have any
> > other ideas what could be wrong? I am running Debian 2.2
> >
>
> Telnet to port 5432 and see if something answers. Are you running
> something like portsentry or something that may be listening on it?
>
> Vince.
> --
> ==========================================================================
> Vince Vielhaber -- KA8CSH email: vev(at)michvhf(dot)com http://www.pop4.net
> 128K ISDN from $22.00/mo - 56K Dialup from $16.00/mo at Pop4 Networking
> Online Campground Directory http://www.camping-usa.com
> Online Giftshop Superstore http://www.cloudninegifts.com
> ==========================================================================