English
Chinese (Simplified)
French
German
Italian
Japanese
Russian
Spanish
Vietnamese
Problem with Outbreak Protection
-
Hello,
We see the following error in our MDaemon 24.5.2 Logs (Windows Server 2019) .
MD Restart does not help.
What is the reason ? What can we do ?
Mon 2025-01-27 14:09:45.396: I [784B8F40] Installing plug-in (Outbreak Protection)
Mon 2025-01-27 14:09:45.396: I [784B8F40] D:\MDAEMON\SecurityPlus\mdop.dll
Mon 2025-01-27 14:09:45.397: I [784B8F40] MDOP, 1.3.8
Mon 2025-01-27 14:09:45.398: I [784B8F40] Outbreak Protection::ConfigFuncName @00007FF8C5064E80
Mon 2025-01-27 14:09:45.398: I [784B8F40] Initializing Outbreak Protection plug-in
Mon 2025-01-27 14:09:45.398: I [784B8F40] Outbreak Protection plug-in loaded in slot 7
Mon 2025-01-27 14:14:32.722: * Outbreak Protection Error: CURL error: Callback aborted. Request timeout occured
Mon 2025-01-27 14:14:32.722: ----------
Mon 2025-01-27 14:15:13.029: * Outbreak Protection Error: still unable to connect: 2
Mon 2025-01-27 14:15:13.029: ----------
Mon 2025-01-27 14:17:22.704: * Outbreak Protection Error: still unable to connect: 2
Mon 2025-01-27 14:17:22.705: ----------
Mon 2025-01-27 14:24:23.795: * Outbreak Protection Error: still unable to connect: 2Many thanks in advance
Best Regards,
Udo Baldewig
Systemadministrator
CAD Schroer GmbH
Germany
-
If you open a command prompt and run:
ping resolver1-mdaemon.ctmail.com
What IP address is returned?
-
@Arron
C:\>ping resolver1-mdaemon.ctmail.com
Ping wird ausgeführt für resolver.1.geo.ctmail.com [84.39.152.31] mit 32 Bytes Daten:
Antwort von 84.39.152.31: Bytes=32 Zeit=14ms TTL=56
Antwort von 84.39.152.31: Bytes=32 Zeit=13ms TTL=55
Antwort von 84.39.152.31: Bytes=32 Zeit=14ms TTL=55
Antwort von 84.39.152.31: Bytes=32 Zeit=14ms TTL=56
-
Please restart MDaemon again.
The error indicates that it was not able to connect to the data center. I configured my MDaemon to point to the same data center you are using and was not able to reproduce the issue, which leads me to believe there was a temporary issue with the data center that has arleady been resolved. The outbreak protection components cash responses, including errors. To clear the cache, you have to restart MDaemon.
-
@Arron
Arron,
The problem has been solved. The reason was an update from our GDATA protection(normaly MDAEMON is completely excluded) and the server was in state of "reboot required". After a complete Windows server restart the problem was gone.
Cheers
Udo Baldewig
-
I'm glad you were able to solve the issue, thank you for letting us know.
