Hi Mark, Can you try the following:
lsof | grep 5432 See what is listening on port 5432. My guess is that there is a doppleganger process around that is holding onto the port. Karl On Mon, Nov 4, 2013 at 1:17 PM, Mark Libucha <[email protected]> wrote: > I've been happily running MCF with postgres for several days now, and all > of a sudden postgres just stopped working. It stopped answering on port > 5432. Trying to start it gives me: > > LOG: could not bind IPv4 socket: Cannot assign requested address > HINT: Is another postmaster already running on port 5432? If not, wait a > few seconds and retry. > WARNING: could not create listen socket for "localhost" > FATAL: could not create any TCP/IP sockets > > I've done all the expected stuff -- googled it, gone through the > recommended fixes on the postgres site (like trying to start on port 666 > instead, but I still get the same error), tried some other random fixes. > Nothing helps. > > No postmaster/postgress process is running. Nothing is listening on port > 5432 according to netstat. (I'm on CentOS 6.). I've uninstalled and > reinstalled postgres. > > I'm guessing there is some sort of resource problem, but the error message > is so incredibly unhelpful, I'm ready to dump postgres and try mysql. > > Any suggestions before I do that? > > Thanks, > > Mark >
