Today I started getting this error in the Application log:
PostgreSQL
Application
7/12/2019 7:03:21 AM
Error (Info)
2975846
FATAL: no PostgreSQL user name specified in startup packet
===================================================
Is this something to do with EventSentry (we don't use PostgreSQL for anything other than EventSentry)?
Any help would be greatly appreciated.
Best Answer
I
Ingmar Koecher
said
about 5 years ago
This event is usually the result of a (vulnerability) scanner scanning the host where the EventSentry PostgreSQL database server is running. If you are using the EventSentry collector service and all EventSentry components (web reports, network services, heartbeat agent, ADMonitor) are installed on the same host as the EventSentry Database then I would recommend setting up a firewall rule to block external access to TCP port 5432.
1 Comment
Ingmar Koecher
said
about 5 years ago
Answer
This event is usually the result of a (vulnerability) scanner scanning the host where the EventSentry PostgreSQL database server is running. If you are using the EventSentry collector service and all EventSentry components (web reports, network services, heartbeat agent, ADMonitor) are installed on the same host as the EventSentry Database then I would recommend setting up a firewall rule to block external access to TCP port 5432.
Ingmar Koecher
Today I started getting this error in the Application log:
Is this something to do with EventSentry (we don't use PostgreSQL for anything other than EventSentry)?
Any help would be greatly appreciated.
This event is usually the result of a (vulnerability) scanner scanning the host where the EventSentry PostgreSQL database server is running. If you are using the EventSentry collector service and all EventSentry components (web reports, network services, heartbeat agent, ADMonitor) are installed on the same host as the EventSentry Database then I would recommend setting up a firewall rule to block external access to TCP port 5432.
Ingmar Koecher
This event is usually the result of a (vulnerability) scanner scanning the host where the EventSentry PostgreSQL database server is running. If you are using the EventSentry collector service and all EventSentry components (web reports, network services, heartbeat agent, ADMonitor) are installed on the same host as the EventSentry Database then I would recommend setting up a firewall rule to block external access to TCP port 5432.
-
EventSentry SQL Backup
-
Freeing up disk space
-
"The RPC server is unavailable" when trying to add any computer.
-
How to remove a list of Servers/Agents using a CSV
-
Pros and Cons of Database in a container for EventSentry
-
After installing trial with a collector, then removing the collector, Agents appear Disconnect or Frozen
-
Can EventSentry Light be used to monitor a phone server on my network?
-
Support for Windows Server 2019
-
Syslog Search Syntax
See all 37 topics