From: | Jim Nasby <decibel(at)decibel(dot)org> |
---|---|
To: | George Weaver <gweaver(at)shaw(dot)ca> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: PostgreSQL doesn't accept connections when Windows Server is rebooted |
Date: | 2006-11-28 02:37:51 |
Message-ID: | 13F9DD59-7190-4069-90B8-B363F9945539@decibel.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
On Nov 21, 2006, at 9:15 AM, George Weaver wrote:
> 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.
Maybe the server is running with a different .conf when started
automatically? IIRC you can see what PGDATA is via show, but of
course you'd need to connect to the server first...
netstat (or the windows equivalent) might also shed some light.
--
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Nasby | 2006-11-28 02:49:53 | Re: nossl authentication |
Previous Message | Jim Nasby | 2006-11-28 02:07:16 | Re: Inserting values into a variable table |