1. Scanner was reinstalled from scratch.
2. Yes I can connect via SSH and there are no problems. No latency. All work fine.
3. We use scanner only for inbound filtering. So result of 'mta-control all status':
inbound MTA instance status:
Enabled: yes
Running: yes
outbound MTA instance status:
Enabled: no
Running: no
delivery MTA instance status:
Enabled: yes
Running: yes
4. Netstat -n shows about 1300 connections fron internet addresses. 1100 of them with status CLOSE_WAIT and 200 with status ESTABLISHED.
5. Hardware status from SBG:
CPU Usage CPU Iowait CPU Temp Memory Usage Memory Free Disk Usage Disk Read Disk Write Swap Used Swap Free
10.08% 0.08% — 2.54 GB 1.37 GB 3.93 GB 0 KB/s 1,512 KB/s 0 MB 4,143.33 MB
From ESXi:
latest maximum minimum average
Disk ReadRate 0 kbps 51 kbps 0 kbps 3,761 kbps
Disk Usage 2770 kpbs 5407 kpbs 181 kpbs 1102 kpbs
Disk WriteRate 2770 kpbs 5407 kpbs 181 kpbs 1098 kbps
6. There are a lot of warnings in scanner log. Warnings like this:
sieve: MAX connections from host 117.3.43.160: - message rejected.
There are many errors in DDS log:
- [1277903617829] 800412 com.symantec.sms.dds.api.exception.DataAccessUnavailableException: The data source is unavailable: LDAP_Domino at com.symantec.sms.dds.bl.EntrySourceMonitor.available(EntrySourceMonitor.java:108) at com.symantec.sms.dds.bl.EntrySou
- [1277903617829] failed to fetch recipient com.symantec.sms.dds.api.exception.DataAccessUnavailableException: The data source is unavailable: LDAP_Domino at com.symantec.sms.dds.bl.EntrySourceMonitor.available(EntrySourceMonitor.java:108) at com.symantec.
Do we have to increase the number of allowed connections? And what do DDS errors mean?
Best regards!