Windows Server 2008 can't start postgresql-x64-9.0 service: could not create any TCP/IP sockets

Posted by Rob on Server Fault See other posts from Server Fault or by Rob
Published on 2011-02-10T20:40:47Z Indexed on 2011/02/10 23:27 UTC
Read the original article Hit count: 259

After rebooting a Windows Server 2008 machine to apply system updates, we recently we began having some issues running PostgreSQL 9.0. When we noticed the problem, we reverted the Windows updates, but the issue persists:

From services.msc, attempting to start the postgresql-x64-9.0 service fails. Half-way through starting the progress bar becomes very slow, and eventually responds with error 1053; "the service did not respond in a timely fashion."

Interestingly enough, bringing up the task manager shows multiple instances of postgres.exe have been started, and looking at the log file shows:

2011-02-10 14:44:02 ESTLOG: database system is ready to accept connections

I then tried killing the processes, and starting via the command-line (as the user postgres), but I receive a different error:

> C:/Program Files/PostgreSQL/9.0/bin/pg_ctl.exe start -N "postgresql-x64-9.0" -D "F:/SHARE/postgres" -w

waiting for server to start...............................................................

pg_ctl: could not start server

ESTWARNING: could not create listen socket for "192.168.0.101"

ESTFATAL: could not create any TCP/IP sockets

The log file again indicates that the database is ready to accept connections.

Also, using netstat indicates that no other processes are using port 5432; I can't think of any other obvious reason that opening the listen socket might fail. Any help would be greatly appreciated.

© Server Fault or respective owner

Related posts about windows-server-2008

Related posts about postgresql