Feedback-ID: i76984098:Fastmail
Message-ID: <14389955-b421-47dd-bcc1-641468845dde@aklaver.com>
Date: Wed, 26 Jun 2024 11:35:29 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Dropping connections
To: "Tarras, Tim" <ttarras@onalaskawi.gov>,
 "pgsql-general@lists.postgresql.org" <pgsql-general@lists.postgresql.org>
References: <842a688946204561ad0787606a644ecf@onalaskawi.gov>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <842a688946204561ad0787606a644ecf@onalaskawi.gov>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://www.postgresql.org/message-id/14389955-b421-47dd-bcc1-641468845dde%40aklaver.com>
Precedence: bulk


On 6/26/24 10:44 AM, Tarras, Tim wrote:
> Hello,
> 

> Underlying DBMS error [no connection to the server::SQLSTATE=å] 
> [xxxxxxx.xxx.GDB_Items][STATE_ID = 0]
> 
> X's replace actual names.
> 
> Working with ESRI we found the following information in the logs :
> 
> "*An existing connection was forcibly closed by the remote host*" where 
> host is the PostgreSQL Server and "*FATAL: terminating connection due to 
> administrator command*". The following PostgreSQL documentation provides 
> more information about the same 

I see *FATAL: terminating connection due to administrator command*" and 
Windows my first thought is Windows Anti-Virus program hitting the 
Postgres server.

Is there an AV program running on the Windows Server 2022 server?

It would also be helpful to get the Postgres log entries immediately 
prior to lines you show above.


-- 
Adrian Klaver
adrian.klaver@aklaver.com