Re: Windows 10 Pro issue

From: Cyclix <cyclix(at)tpg(dot)com(dot)au>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Windows 10 Pro issue
Date: 2018-02-13 21:37:28
Message-ID: 14113c03-cbd9-584a-9ec1-6412d5606404@tpg.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I've seen this before with Win10.

1.- Go to Windows ControlPanel-UserAccounts-ManageAnotherAccount, select
postgres and re-enter the Postgres User password, save and close.
2.- Start Windows Services (if running as a service) right click on
Postgres Service-Properties-LogOn then enter the same password click Ok
3.- Restart Postgres Service

With every new update of Win10, it tends to changes some of the folders
permissions, including postgres. Very annoying but common.

Good luck

On 02/14/2018 07:35 AM, Adrian Klaver wrote:
> On 02/13/2018 12:07 PM, Dale Seaburg wrote:
>> Server:  Windows 10 Pro system
>> Postgresql:  8.4.5 installed several months ago and working correctly,
>> until recently
>
> Should have mentioned earlier, version 8.4 went EOL about three and half
> years ago:
>
> https://www.postgresql.org/support/versioning/
>
> Probably should look at upgrading to a newer version sooner rather then
> later.
>
>
>>
>> On Feb 9, 2018 about 7 PM pg_log file recorded:
>>
>> 2018-02-09 15:04:23 CST LOG:  unexpected EOF on client connection
>> 2018-02-09 19:12:41 CST LOG:  received fast shutdown request
>> 2018-02-09 19:12:41 CST LOG:  aborting any active transactions
>> 2018-02-09 19:12:41 CST LOG:  autovacuum launcher shutting down
>> 2018-02-09 19:12:41 CST LOG:  shutting down
>> 2018-02-09 19:12:43 CST LOG:  database system is shut down
>>
>> On Feb 12, 2018 about 2 PM after computer was restarted, pg_log file
>> recorded:
>>
>> 2018-02-12 14:17:31 CST LOG:  could not open configuration file
>> "C:/WINDOWS/system32/ConfigDir/pg_hba.conf": No such file or directory
>> 2018-02-12 14:17:31 CST FATAL:  could not load pg_hba.conf
>>
>> The log event on Friday, appears to have recorded a forced shutdown -
>> Windows 10 update install, maybe?  No one at business to record what
>> may have happened.
>>
>> On Monday afternoon, postgres service refused to Start as indicated in
>> that day's log event.
>>
>> Any ideas as to what might have happened, or caused this anomaly? It's
>> almost as if some Environment Variables were missing, or scrambled.  I
>> don't think Postgresql uses the Windows Registry, in place of EV's,
>> does it?
>>
>> Dale Seaburg
>>
>>
>>
>
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message chiru r 2018-02-13 22:00:09 Re: oracle_fdw Question
Previous Message armand pirvu 2018-02-13 21:25:26 Re: cursors and function question