Re: BUG #8328: Unable to start postgresql on the Debian machine. - Mailing list pgsql-bugs

From Kevin Grittner
Subject Re: BUG #8328: Unable to start postgresql on the Debian machine.
Date
Msg-id 1375449737.24063.YahooMailNeo@web162901.mail.bf1.yahoo.com
Whole thread Raw
In response to BUG #8328: Unable to start postgresql on the Debian machine.  (vijayakumar.subas@hp.com)
List pgsql-bugs
"vijayakumar.subas@hp.com" <vijayakumar.subas@hp.com> wrote:=0A=0A> We are =
facing issue when trying to start postgresql on the Debian=0A> machine.=0A=
=0AThis is almost certainly not a bug; so it doesn't belong on this=0Alist.=
=A0 pgsql-general would probably have been the best choice. =0APlease pick =
a more appropriate list for any future questions.=0A=0Ahttp://www.postgresq=
l.org/community/lists/=0A=0A> 2013-07-24 19:16:38 LOG: could not bind IPv4 =
socket: Permission denied=0A> 2013-07-24 19:16:38 HINT: Is another postmast=
er already running on port 5432? If not, wait a few seconds and retry.=0A> =
2013-07-24 19:16:38 WARNING: could not create listen socket for "127.0.0.1"=
=0A> 2013-07-24 19:16:38 FATAL: could not create any TCP/IP sockets=0A=0AIs=
 another postmaster running on port 5432?=0A=0AYou could run any or all of =
these statements to get insight into that:=0A=0Alsof -i4TCP@127.0.0.1:5432=
=0Anetstat -plnt | grep ':5432 '=0Aps aux | grep postgres=0A=0A--=0AKevin G=
rittner=0AEDB: http://www.enterprisedb.com=0AThe Enterprise PostgreSQL Comp=
any

pgsql-bugs by date:

Previous
From: Klaus Ita
Date:
Subject: Re: [GENERAL] Recovery_target_time misinterpreted?
Next
From: Bruce Momjian
Date:
Subject: Re: BUG #8293: There are no methods to convert json scalar text to text in v9.3 beta2