Forum Discussion

mpete32_168869's avatar
Dec 12, 2014
Solved

Failure of SMTP health check

I've always received great help here and it's truly appreciated. Now I have another issue that requires some assistance. BTW, I have a support case with F5 regarding this and they have not been able to offer any solutions that have worked.

 

I have a virtual server that uses a single member pool doing SMTP health checks. The health check is failing (showing the member down) but all logs show proper connectivity, proper smtp responses from the mail server, and communications working correctly, but the health check still shows down and the logs related to this traffic are displaying a "Sending data failed, errno 'EPIPE'" type error message. I can telnet from the F5 to the member server from a SSH console and run the same SMTP commands and all checks out. Simply not sure why the health check would fail is all appears to be talking properly.

 

  • @mpete32

     

    You can also try to re-create SMTP monitor. Set Interval to 30, and Timeout to 91. And enable debug (Advanced configuration for the monitor), it may show some info in logs...

     

16 Replies

  • Mine is broken as well... HF4. Tried recreating. Was working fine on 11.4.1 prior.

     

    ERROR: failed to connect x.x.x.x%x:25 error: couldn't open socket: host is unreachable

     

    If I switch to TCP or TCP Half Open it works fine so it's not a TCP/25 listener issue.

     

  • See the following Solution Article SOL16631 which may do the trick for ya. Seems to be an issue with route domains in the default SMTP monitor. There are a few things that are lacking in the instructions. 1) installed the external monitor into the default route domain. 2)add the variable DOMAIN with the value of your domain. That is not mentioned in the workaround instructions.

     

  • Hi,

     

    The original problem of the thread (20 sec delay after server's 220 ) is a (now) Know Issue and we have an EngineeringHF for it. Please open a case with F5 Support. The smtp monitor on a non-default RD issue is a different one. The HF for RD issue does NOT fix the 20 sec delay issue.

     

    Regards Peter