The following bug has been logged online:

Bug reference: 1560
Logged by: Joerg Ertl
Email address: joerg.ertl (AT) dog-gmbh (DOT) de
PostgreSQL version: 8.0
Operating system: Windows XP Professional
Description: Service does not start
Details:

Error message are:
could not connect to server: Connection refused (0x0000274D/10061)
Is the server running on host "???" and accepting TCP/IP connections on port
5432?

After the installation a few days ago of PostgreSQL 8.0 everything works
fine, but now the service does not start.

---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend

You'll need to look in the server logs to see why it doesn't start.

//Magnus

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

Joerg,

I had this problem MANY times. Most often it was:

- the service account lost it privilege to log on as a service

we suspect it were some interfering group policies.

It was possible to "reactivate" by opening service control panel,
reappling password. Windows then reported, that the "log on as service
privilege" was granted.

It worked again for some days.

Final solution was to build a domain account which belongs to the
"logon as service" group.

that is NOT a postgreSQL problem, as long talks with magnus revealed
.... the rights are lost within windows, and postgreSQL-Service-Account
does NOT have privileges to change these rights.

So, maybe this problem which eat much of my time is the same with you..

Harald




--=20
GHUM Harald Massa
persuasion python postgresql
Harald Armin Massa
Reinsburgstra=DFe 202b
70197 Stuttgart
0173/9409607

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

....

FYI, I've seen this in a couple of other cases as well. It seems if you
configure a group policy to lock down who is granted the "log on as a
service" right, a local administrator can still grant this right.
*however*, upon next group policy refresh (interval is configured in...
group policy!) the right will be removed. A way to force this is to run
"gpupdate /force" and see if things work after that...


//Magnus

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo (AT) postgresql (DOT) org so that your
message can get through to the mailing list cleanly