Re: [BUGS] BUG #8328: Unable to start postgresql on the Debian machine.
"vijayakumar.su...@hp.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@127.0.0.1:5432 netstat -plnt | grep ':5432 ' ps aux | grep postgres -- Kevin Grittner EDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
[BUGS] BUG #8328: Unable to start postgresql on the Debian machine.
The following bug has been logged on the website: Bug reference: 8328 Logged by: Vijay Email address: vijayakumar.su...@hp.com PostgreSQL version: Unsupported/Unknown Operating system: Debian Description: Hello, We are facing issue when trying to start postgresql on the Debian machine. Error: - tuxux:~# /etc/init.d/postgresql-8.3 start Starting PostgreSQL 8.3 database server: mainThe PostgreSQL server failed to start. Please check the log output: 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 failed! failed! Could you please help us to resolve this issue? FYI, I was able to ping localhost and do nslookup. -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs