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

2006-11-27 Thread Harald Armin Massa

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.


[GENERAL] PostgreSQL doesn't accept connections when Windows Server is rebooted

2006-11-27 Thread George Weaver
Hi everyone,

I recently installed PostgreSQL (Version 8.1.5.1) using the MSI installer on a 
Windows Server 2000 system.

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

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."

I surmized that the problem was that I was attempting to run the install as an 
Administrator, so I addressed the problem by running the install, but not 
having the installer run initdb step to intialize the database cluster.  When 
the install finished without error, I then logged onto the server under the 
postgres account and manually ran initdb.  I was able to initialize the cluster.

I then updated the postgresql.conf file with "listen_addresses = '*' and 
changed the port from 5432 (currently being used for a 7.3 server) to 5435.

Everything runs as expected.

Until the Windows Server is rebooted.  When this occurs, the PostgreSQL service 
starts as expected, but won't accept connections.

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?

Thanks in advance,
George