Re: Windows Service Stops Responding - Mailing list pgsql-novice

From mcassell@trimind.com
Subject Re: Windows Service Stops Responding
Date
Msg-id 628893445.586586.1552412633163@email.ionos.com
Whole thread Raw
In response to Windows Service Stops Responding  (mcassell@trimind.com)
List pgsql-novice

I tried again and got the same error "Connection attempt timed out.".  Log file is empty until I restart service, than I get the following.  This is the complete logfile.


2019-03-12 13:41:41.246 EDT [5948] LOG: received fast shutdown request
2019-03-12 13:41:41.287 EDT [5948] LOG: aborting any active transactions
2019-03-12 13:41:41.295 EDT [5948] LOG: background worker "logical replication launcher" (PID 19912) exited with exit code 1
2019-03-12 13:41:41.336 EDT [17468] LOG: shutting down
2019-03-12 13:41:41.533 EDT [5948] LOG: database system is shut down

Then a new log is opened when service restarts.

Thanks, 

Michael Cassell

On March 12, 2019 at 12:40 PM Moreno Andreo <moreno.andreo@evolu-s.it> wrote:

Il 08/03/2019 14:28, mcassell@trimind.com ha scritto:

I have installed PostgreSQL on two different Windows 10 systems and am having the same problem.  The server work great when I first connect to it but if I disconnect client and come back a few hours or a day later I am unable to connect to the service with a timeout error.   I have used both pgAdmin and DBeaver as clients.

If I do a restart on the window service everything works fine again until I disconnect the client for a extended period.  Can't find anywhere else this issue is discussed.   

Have used both the latest 11.2 release and an older 10.x release and both operate the same.  Is this a known issue?  Is there a solution?

 

Have you checked logs (Event viewer or the folder /data/pg_log)?

Cheers

Moreno.-


 

pgsql-novice by date:

Previous
From: mcassell@trimind.com
Date:
Subject: Windows Service Stops Responding
Next
From: Adam Lipinski
Date:
Subject: RE: Windows Service Stops Responding