Re: PostgreSQL doesn't accept connections when Windows Server is rebooted

George,

I guess your service is not running after rebooting? You can check this via
services.msc

Most propable cause: the postgres user does not have logon_as_service
privilege.

I ran the installer logged in under an Administrator account, and set the
> service account to postgres.
>

That is the recommended way. The installer will create an low-priv postgres
service account and run initdb as that user.

During the installation process, when it came time to run initdb,
> the installer would stop with the error message:
>
> "Failed to run initdb: 128. Please see the logfile in 'C:\Program
> Files\PostgreSQL\8.1\tmp\initdb.log.
> Note! You must read/copy this logfile before you click OK, or it
> will be automatically removed."
>

Did you read that log? Read and copy it befor clicking OK, just as the
message stated?

BECAUSE: running THE INSTALLER as Administrator is recommended AND necessary
to create the postgres user and to give correct rights to this user.

SO: in running initdb.exe something else went wrong, it is NOT because you
ran the installer as Administrator.

(guessing .... you installed with port 5432, and initdb tried to contact
5432, failing, because it is an 7.3 ?)

If the PostgreSQL service is then restarted manually (via Administrative
> Tools > Component Services > Restart), the service runs as expected and
> everything is normal.
> How can I correct this?
>

One try to repair this: login as Administrator, open services.msc, and
from the postgreSQL service refill the login information. That does reset
the LOGON_AS_SERVICE privilege.

Harald

--
GHUM Harald Massa
persuadere et programmare
Harald Armin Massa
Reinsburgstraße 202b
70197 Stuttgart
0173/9409607
-
Python: the only language with more web frameworks than keywords.