We use cookies to try and give you a better experience in Freshdesk.
You can learn more about what kind of cookies we use, why, and how from our Privacy policy. If you hate cookies, or are just on a diet, you can disable them altogether too. Just note that the Freshdesk service is pretty big on some cookies (we love the choco-chip ones), and some portions of Freshdesk may not work properly if you disable cookies.
We’ll also assume you agree to the way we use cookies and are ok with it as described in our Privacy policy, unless you choose to disable them altogether through your browser.
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.
0 Votes
Ingmar Koecher posted almost 7 years ago Admin Best 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.
0 Votes
1 Comments
Ingmar Koecher posted almost 7 years ago Admin 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.
0 Votes
Login or Sign up to post a comment