On 01/30/2016 11:01 AM, David Unsworth wrote:
Ccing list, so more eyes can see.
> Hello. Thanks for the reply. Here is some more info.
>
> Assuming this is a Windows machine, what version of the OS?
> Windows 7 Home Premium
>
> How did you install Postgres on this machine?
> With Hold'em Manager software many years ago.
>
> What user are you starting the service as?
> Administrator
>
> What if anything happened/changed between the time it was working and
> the time it stopped working?
> Editing pg_hba.conf, right clicking in Services, Properties editing log
> on details. Service would not start when logging on the next day but
> was okay at the time.
So the was the machine rebooted between the time it worked and the time
it did not or did you just log out and back in?
>
> What is in the Postgres log prior to it shutting down?
> Checked pg_log folder. Log file from 2012. Nothing since the problem.
I got to believe there is a newer log file then that.
Is there more then one instance of Postgres on this machine?
>
> What is in the system(Windows) logs when you try to start the service?
> 2016-01-25 18:45:19 GMTFATAL: the database system is starting up
> 2016-01-27 01:09:47 GMTFATAL: role "SYSTEM" does not exist
> pg_ctl: PID file "C:/Program Files
> (x86)/PostgreSQL/8.4/data/postmaster.pid" does not exist
So there is an almost two day gap between FATAL errors. There is nothing
else between those messages or immediately prior to the first one?
>
> Previously reported errors -
>
> In Services I cannot start the PostgreSQL Server 8.4 due to Error:1069
> The service did not start due to a logon failure.
>
> I have been getting the error "could not connect to Server: Connection
> refused" detailed below -
>
> http://www.pgadmin.org/docs/1.14/connect-error.html
>
> When trying to reload the configuration (before attempting to start the
> Service again ) and I got the error "Reload command returned an error (1)".
>
>
--
Adrian Klaver
adrian.klaver@aklaver.com
