Re: EXT: Re: PostgreSQL 9.5 service stopped intermittently on windows10 Pro version 1703.

On Tue, Apr 9, 2019 at 11:27 AM Kadam, Daulat (BHGE, consultant)
<Daulat.Kadam@bhge.com> wrote:
>
> Thanks for the response. Please find attached log files.

As I said, I'm not a windows user, but reading through the logs I can
see a lot of errors, occuring at the same time as postgres connection
drops.  For instance:

VPSX8101E <$DDNS$          > TCP/IP HOST NAME RESOLUTION FAILED,
HOST(vpsx.cloud.ge.com) ERROR(The requested name is valid, but no data
of the requested type was found.  )

Warning    4/9/2019 9:14:23 AM    SceCli    1202    None    "Security
policies were propagated with warning. 0x534 : No mapping between
account names and security IDs was done.

Advanced help for this problem is available on
http://support.microsoft.com. Query for ""troubleshooting 1202
events"".

Error 0x534 occurs when a user account in one or more Group Policy
objects (GPOs) could not be resolved to a SID.  This error is possibly
caused by a mistyped or deleted user account referenced in either the
User Rights or Restricted Groups branch of a GPO.  To resolve this
event, contact an administrator in the domain to perform the following
actions:


I can also see other postgres related errors:

Information    4/9/2019 10:48:50 AM    PostgreSQL    0    None
Waiting for server startup...

Error    4/9/2019 10:47:10 AM    PostgreSQL    0    None    Timed out
waiting for server startup

Error    4/9/2019 10:47:09 AM    PostgreSQL    0    None
"2019-04-09 10:47:09 IST FATAL:  lock file ""postmaster.pid"" already
exists
2019-04-09 10:47:09 IST HINT:  Is another postmaster (PID 5512)
running in data directory ""C:/Program Files/PostgreSQL/9.5/data""?


I can also see frequent mention of sqlserver being interrupted and restarting:

Information    4/8/2019 8:15:45 AM    MSSQL$SQLEXPRESS    6253
Server    Common language runtime (CLR) functionality initialized
using CLR version v4.0.30319 from
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
Information    4/8/2019 8:15:39 AM    MSSQL$SQLEXPRESS    3408
Server    Recovery is complete. This is an informational message only.
No user action is required.
Information    4/8/2019 8:15:39 AM    MSSQL$SQLEXPRESS    9688
Server    Service Broker manager has started.

same for "microsoft search service":

Information    4/8/2019 8:19:02 AM    ESENT    302    Logging/Recovery
   Windows (1800) Windows: The database engine has successfully
completed recovery steps.
Information    4/8/2019 8:18:53 AM    ESENT    301    Logging/Recovery
   Windows (1800) Windows: The database engine has begun replaying
logfile C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSS.log.
Information    4/8/2019 8:18:53 AM    ESENT    300    Logging/Recovery
   Windows (1800) Windows: The database engine is initiating recovery
steps.
Information    4/8/2019 8:18:53 AM    ESENT    102    General
Windows (1800) Windows: The database engine (6.01.7601.0000) started a
new instance (0).

Just look for "failure" in the event log to see a bunch of other problems.

In short, I have no idea of what's happening on your server, but it
looks like it needs some care.  It's also probably not postgres
related.