Thread: Postgres service refuses to start on windows

Postgres service refuses to start on windows

From
Roman Isitua
Date:
hello !

I having an issue with my postgres database installed on a windows xp. For some reason, I can no longer start the postgres service through pgadmin or the services window. I get the following error:
Error 1053: The service did not respond to the start or control request in a timely fashion.

Any ideas ?

Roman.

Re: Postgres service refuses to start on windows

From
Michael Swierczek
Date:
On Mon, Jun 20, 2011 at 2:39 AM, Roman Isitua <romanisitua@yahoo.com> wrote:
hello !

I having an issue with my postgres database installed on a windows xp. For some reason, I can no longer start the postgres service through pgadmin or the services window. I get the following error:
Error 1053: The service did not respond to the start or control request in a timely fashion.

Any ideas ?

Roman.

Sometimes the PostgreSQL logs for the current day have useful error messages.   If you did a regular install, they're probably in "C:\Program Files\PostgreSQL\(your version - probably 8.3, 8.4, or 9.0)\data\pg_log".  You may be able to figure out what is broken from that.  If you can't decipher the message and can't find anything on a web search, post it here and I'm sure someone will know what is going on.   Good luck.

-Mike

Re: Postgres service refuses to start on windows

From
Richard Broersma
Date:
On Sun, Jun 19, 2011 at 11:39 PM, Roman Isitua <romanisitua@yahoo.com> wrote:
I having an issue with my postgres database installed on a windows xp. For some reason, I can no longer start the postgres service through pgadmin or the services window. I get the following error:
Error 1053: The service did not respond to the start or control request in a timely fashion.

Any ideas ?

When you attempt to restart, notice any error logs in the pg-log directory.  Any information there will give a clue.

On a related note, I had this experience once with Pg 8.2 and Windows 2K.  For some reason, the Postgres working directory was set to be read-only.  I have no idea how this happened - perhaps it was the anti-virus software or a rogue admin.  But once I reset the directory it worked.

--
Regards,
Richard Broersma Jr.