Thread: Dropping connections

This email and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error, please respond to the sender and delete the material from any computer and/or server. The City of Onalaska is subject to Wisconsin Statutes relating to public records. Emails sent or received by City employees are subject to these laws. Unless otherwise exempted from the public records law, senders and receivers of City email should presume that the emails are subject to release upon request, and to state record retention requirements.

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

Windows Defender is turned off and a 3rd party AV is being used.  We did ask about that and were told that would not be
theissue.  I would also think that I would be dropping the connection when I am on the Server itself which is not the
case.

I have attached the log files with the Errors highlighted in Yellow Go to last page in each one. In reading the whole
errorthe password authentication failed for the postgres user, which is not the user we are logged in as to this
database.

-----Original Message-----
From: Adrian Klaver <adrian.klaver@aklaver.com>
Sent: Wednesday, June 26, 2024 1:35 PM
To: Tarras, Tim <ttarras@onalaskawi.gov>; pgsql-general@lists.postgresql.org
Subject: Re: [External] Dropping connections



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
programhitting 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
This email and any files transmitted with it are confidential and are intended solely for the use of the individual or
entityto which they are addressed. If you have received this email in error, please respond to the sender and delete
thematerial from any computer and/or server. The City of Onalaska is subject to Wisconsin Statutes relating to public
records.Emails sent or received by City employees are subject to these laws. Unless otherwise exempted from the public
recordslaw, senders and receivers of City email should presume that the emails are subject to release upon request, and
tostate record retention requirements.
 

On 6/26/24 12:56, Tarras, Tim wrote:
> Windows Defender is turned off and a 3rd party AV is being used.  We did ask about that and were told that would not
bethe issue.  I would also think that I would be dropping the connection when I am on the Server itself which is not
thecase.
 
> 
> I have attached the log files with the Errors highlighted in Yellow Go to last page in each one. In reading the whole
errorthe password authentication failed for the postgres user, which is not the user we are logged in as to this
database.

Not sure if this is related but for completeness:

1) There seem to be quite a few of:

"ERROR:  relation <some_relation> does not exist at character"

Is that normal?

2) Also:

FATAL:  password authentication failed for user "postgres"

Somewhat concerning that someone/thing is trying to connect as the super 
user and failing. Maybe just erroneous password for some monitoring 
program or potentially someone trying to hack the database.

3) In your original post you said the issue pops up when you are 
remotely accessing the Postgres server via ArcgisPro 3.3.0.

a) Where is that remote machine located.

b) OS and version of the machine.

-- 
Adrian Klaver
adrian.klaver@aklaver.com