By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
445,824 Members | 1,252 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 445,824 IT Pros & Developers. It's quick & easy.

could not bind IPv4 socket: Address already in use

P: n/a
I'm just getting started with postgresql and things are going pretty well. However, I
seem to be having trouble connecting to my database via TCP/IP. I'm assuming that
my problems are related to the message I get at startup (using "postmaster -D data -
i"). The postmaster starts but produces this message:

LOG: could not bind IPv4 socket: Address already in use
HINT: is another postmaster already running on port 5432. If not, wait a few seconds
and retry.

Looking into this a bit it seems that the most common issue here is 5432 being
claimed by an extra postmaster or another application. However, using "ps -ef" I can
confirm that NO other postmasters are running and using "netstat -a" I can confirm
that 5432 IS free so I'm at a loss.

Oddly, postgres does claim 5432 at startup and releases it at shutdown the way I
suspect it should but I still get that message. I came across a discussion at which seems to indicate
that the message can be ignored in which case I should look somewhere else for my
TCP/IP issues.

Has anyone else run into anything like? I'm running Postgresql 7.4.2 on SUSE 8.4.
Any thoughts are greatly appreciated.


Eric Hillmuth
GIS Systems Developer
Vermont Agency of Natural Resources
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

Nov 23 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.