Question

它可以正常工作，直到远程服务器一段时间不可用为止。在这种情况下，服务器将在日志中关闭，并且永远不会再次启动。 Config非常简单：

defaults
    retries 3
    timeout connect 5000
    timeout client 3600000
    timeout server 3600000
    log global
    option log-health-checks

listen amazon_ses
    bind 127.0.0.2:1234
    mode tcp
    no option http-server-close
    default_backend bk_amazon_ses

backend bk_amazon_ses
    mode tcp
    no option http-server-close
    server amazon email-smtp.us-west-2.amazonaws.com:587 check inter 30s fall 120 rise 1

以下是发生问题时的日志：

Jul  3 06:45:35 jupiter haproxy[40331]: Health check for server bk_amazon_ses/amazon failed, reason: Layer4 timeout, check duration: 30004ms, status: 119/120 UP. 
Jul  3 06:46:35 jupiter haproxy[40331]: Health check for server bk_amazon_ses/amazon failed, reason: Layer4 timeout, check duration: 30003ms, status: 118/120 UP. 
Jul  3 06:47:35 jupiter haproxy[40331]: Health check for server bk_amazon_ses/amazon failed, reason: Layer4 timeout, check duration: 30002ms, status: 117/120 UP.
...
Jul  3 08:44:36 jupiter haproxy[40331]: Health check for server bk_amazon_ses/amazon failed, reason: Layer4 timeout, check duration: 30000ms, st
atus: 0/1 DOWN. 
Jul  3 08:44:36 jupiter haproxy[40331]: Server bk_amazon_ses/amazon is DOWN. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 
0 remaining in queue. 
Jul  3 08:44:36 jupiter haproxy[40331]: backend bk_amazon_ses has no server available!

就是这样。操作员的干预使服务器恢复了生命。我还尝试删除了检查部分及其后续内容-仍然发生相同的事情。无法将haproxy配置为无限期尝试并且不将服务器标记为DOWN？谢谢。

Haproxy后端保持关闭状态，并且永远不会重新启动

0 个答案: