I have installed the latest Cygwin and it's PostgreSQL have gotten the database running just fine and have "ipc-daemon" and "postmaster" both running as services. I can start postmaster as a service from the SERVICES console and it runs just fine as well. However, even though I have the service set to startup automatically, fails to do so. Once the computer finishes starting I can go and start the service manually, but of course, this will not suffice for production use. I have reviewed the event logs to see if it might shed some light on why the service failed to start and found the following entry for the ipc-daemon (which did start):
Event Type: Information
Event Source: ipc-daemon
Event Category: None
Event ID: 0
Date: 10/25/2001
Time: 12:50:07 PM
User: NT AUTHORITY\SYSTEM
Computer: FRANKENSTEIN
Description:
The description for Event ID ( 0 ) in Source ( ipc-daemon ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: ipc-daemon : Win32 Process Id = 0x284 : Cygwin Process Id = 0x284 : (ipc-daemon) 'ipc-daemon' service started.
When I start the service manually I get the following in the EventLog for the postmaster:
Event Type: Information
Event Source: postmaster
Event Category: None
Event ID: 0
Date: 10/25/2001
Time: 12:54:23 PM
User: NT AUTHORITY\SYSTEM
Computer: FRANKENSTEIN
Description:
The description for Event ID ( 0 ) in Source ( postmaster ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: postmaster : Win32 Process Id = 0x5D0 : Cygwin Process Id = 0x5D0 : `postmaster' service started.
I am pressuming something in how the ipc-daemon started prevented the postmaster from starting automatically. I set the reccomonded environment variables (instead of the registry entries) for the ipc-daemon, so I am not sure what the problem is here.
Has anyone else run across this before? As I stated earlier, once I start the service manually I am able to run everything just fine.
Thanks for any help,
Nick McCalip
