Re: BUG #8328: Unable to start postgresql on the Debian machine.

From: Kevin Grittner <kgrittn(at)ymail(dot)com>
To: "vijayakumar(dot)subas(at)hp(dot)com" <vijayakumar(dot)subas(at)hp(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #8328: Unable to start postgresql on the Debian machine.
Date: 2013-08-02 13:22:17
Message-ID: 1375449737.24063.YahooMailNeo@web162901.mail.bf1.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"vijayakumar(dot)subas(at)hp(dot)com" <vijayakumar(dot)subas(at)hp(dot)com> wrote:

> We are facing issue when trying to start postgresql on the Debian
> machine.

This is almost certainly not a bug; so it doesn't belong on this
list.  pgsql-general would probably have been the best choice.
Please pick a more appropriate list for any future questions.

http://www.postgresql.org/community/lists/

> 2013-07-24 19:16:38 LOG: could not bind IPv4 socket: Permission denied
> 2013-07-24 19:16:38 HINT: Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
> 2013-07-24 19:16:38 WARNING: could not create listen socket for "127.0.0.1"
> 2013-07-24 19:16:38 FATAL: could not create any TCP/IP sockets

Is another postmaster running on port 5432?

You could run any or all of these statements to get insight into that:

lsof -i4TCP(at)127(dot)0(dot)0(dot)1:5432
netstat -plnt | grep ':5432 '
ps aux | grep postgres

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2013-08-02 17:04:36 Re: BUG #8293: There are no methods to convert json scalar text to text in v9.3 beta2
Previous Message grv87 2013-08-02 09:52:32 BUG #8355: PL/Python 3 can't convert infinity to PostgreSQL's value