Silent install 8.3 diiffers from 8.2

[Syra.Didelez@xxxxxxxx]

"You should probably send those logs to the list,
rather than straight to me.

However, this line sticks out at me:


2008-04-07 07:43:14 GMT FATAL:  lock file "postmaster.pid"
already exists
2008-04-07 07:43:14 GMT HINT:  Is another postmaster (PID 3724) running
in data directory "F:/B"?


Is it possible that the old server wasn't shut down cleanly on remove?
Is there really a postmaster.pid file present?

--
Craig Ringer"


Hi,

Crais, sorry to bother you directly !

The previous server was shut down (killed 6 postgres.exe
processes) and then removed completely,
both directories basedir & datadir are empty when
starting the install.

And yes, there is a postmaster.pid file created during
install.
It might not be important, but 'usually' there are
4 postgres.exe processes showing up.
Here there are 6 .. it might look like the server
is trying to be started up twice ...
-also regardig the error in the application log about
the lock file...

thus, here the log files:


the system event log shows the following:
Type        Date
       Time        Source
       Category        Event
       User        Computer
Information        4/7/2008
       9:44:18 AM        Service
Control Manager        None      
 7036        N/A    
   GS2479
--> The
PostgreSQL Database Server 8.3 service entered the stopped state.
Information        4/7/2008
       9:43:14 AM        Service
Control Manager        None      
 7035        SYSTEM    
   GS2479
--> The
PostgreSQL Database Server 8.3 service was successfully sent a start control.
Information        4/7/2008
       9:43:09 AM        Service
Control Manager        None      
 7036        N/A    
   GS2479
--> The
PostgreSQL Database Server 8.3 service entered the stopped state.
Information        4/7/2008
       9:42:05 AM        Service
Control Manager        None      
 7035        SYSTEM    
   GS2479
--> The
PostgreSQL Database Server 8.3 service was successfully sent a start contro
Information        4/7/2008
       9:41:59 AM        Service
Control Manager        None      
 7036        N/A    
   GS2479
--> The
PostgreSQL Database Server 8.3 service entered the stopped state.
Information        4/7/2008
       9:40:55 AM        Service
Control Manager        None      
 7035        SYSTEM    
   GS2479
--> The
PostgreSQL Database Server 8.3 service was successfully sent a start control.
Information        4/7/2008
       9:40:49 AM        Service
Control Manager        None      
 7036        N/A    
   GS2479
-->The
PostgreSQL Database Server 8.3 service entered the stopped state.
Information        4/7/2008
       9:39:43 AM        Service
Control Manager        None      
 7035        SYSTEM    
   GS2479
--> The
PostgreSQL Database Server 8.3 service was successfully sent a start control.
Information        4/7/2008
       9:38:13 AM        Service
Control Manager        None      
 7036        N/A    
   GS2479
--> The
Windows Installer service entered the running state.
Information        4/7/2008
       9:38:13 AM        Service
Control Manager        None      
 7035        SYSTEM    
   GS2479
--> The
Windows Installer service was successfully sent a start control.

the application event log:
Type        Date
       Time        Source
       Category        Event
       User        Computer
Error        4/7/2008
       9:43:14 AM        PostgreSQL
       None        0
       N/A        GS2479

--> 2008-04-07
07:43:14 GMT FATAL:  lock file "postmaster.pid" already
exists
      2008-04-07 07:43:14
GMT HINT:  Is another postmaster (PID 3724) running in data directory
"F:/B"?

Information        4/7/2008
       9:43:14 AM        PostgreSQL
       None        0
       N/A        GS2479
 --> Waiting
for server startup...

Information        4/7/2008
       9:43:09 AM        PostgreSQL
       None        0
       N/A        GS2479
 --> Timed
out waiting for server startup

Error        4/7/2008
       9:42:05 AM        PostgreSQL
       None        0
       N/A        GS2479

-->2008-04-07
07:42:05 GMT FATAL:  lock file "postmaster.pid" already
exists
2008-04-07 07:42:05 GMT HINT:  Is
another postmaster (PID 3724) running in data directory "F:/B"?

Information        4/7/2008
       9:42:05 AM        PostgreSQL
       None        0
       N/A        GS2479

--> Waiting
for server startup...

Information        4/7/2008
       9:41:59 AM        PostgreSQL
       None        0
       N/A        GS2479
 --> Timed
out waiting for server startup

Error        4/7/2008
       9:40:55 AM        PostgreSQL
       None        0
       N/A        GS2479
--> 2008-04-07
07:40:55 GMT FATAL:  lock file "postmaster.pid" already
exists

2008-04-07 07:40:55 GMT HINT:  Is
another postmaster (PID 3724) running in data directory "F:/B"?
Information        4/7/2008
       9:40:55 AM        PostgreSQL
       None        0
       N/A        GS2479

--> Waiting
for server startup...

Warning        4/7/2008
       9:40:49 AM        Userenv
       None        1517
       SYSTEM        GS2479

--> Windows
saved user GS2479\postgres registry while an application or service was
still using the registry during log off. The memory used by the user's
registry has not been freed. The registry will be unloaded when it is no
longer in use. 
 This is often caused by services
running as a user account, try configuring the services to run in either
the LocalService or NetworkService account.

Information        4/7/2008
       9:40:48 AM        PostgreSQL
       None        0
       N/A        GS2479
 --> Timed
out waiting for server startup

and after clicking the cancel button
on the error message, following is reported to the
system log:
Information        4/7/2008
       10:00:58 AM        Service
Control Manager        None      
 7036        N/A    
   GS2479
--> The
Windows Installer service entered the stopped state.
Information        4/7/2008
       9:44:18 AM        Service
Control Manager        None      
 7036        N/A    
   GS2479
--> The
PostgreSQL Database Server 8.3 service entered the stopped state.


and the application log:
in the application log, following appear
:

The description for Event ID ( 0 )
in Source ( PostgreSQL ) cannot be found. The local computer may not have
the necessary registry information or message DLL files to display messages
from a remote computer. You may be able to use the /AUXSOURCE= flag to
retrieve this description; see Help and Support for details. The following
information is part of the event: Waiting for server startup...

Windows saved user GS2479\postgres
registry while an application or service was still using the registry during
log off. The memory used by the user's registry has not been freed. The
registry will be unloaded when it is no longer in use. 

 This is often caused by services
running as a user account, try configuring the services to run in either
the LocalService or NetworkService account.

.Product: PostgreSQL 8.3 -- Error
1920. Service 'PostgreSQL Database Server 8.3' (pgsql-8.3) failed to start.
 Verify that you have sufficient privileges to start system services.






- Syra Didelez -
Apogee Portal Deployment Manager
Apogee Portal Hotfix Manager
Agfa-Gevaert N.V.

Tel.: +32 3 444 4237
http://www.agfa.com