HA Proxies restart events


#1

Since we upgraded Rancher version and starting from this week there are a lot of HA Proxies restart events.

On attached screenshots you can find statistic from Dynatrace for my server 1
Quite similar situation is for the other server 2, 3 and 4

17/10/2018 12:28:30

17/10/2018 12:28:53INFO[579715] – reloading haproxy config with the new config changes

17/10/2018 12:28:53 * Reloading haproxy haproxy

17/10/2018 12:28:53[WARNING] 289/102853 (32739) : config : ‘option forwardfor’ ignored for proxy ‘default’ as it requires HTTP mode.

17/10/2018 12:28:53[WARNING] 289/102853 (32741) : config : ‘option forwardfor’ ignored for proxy ‘default’ as it requires HTTP mode.

17/10/2018 12:28:53 …done.

17/10/2018 12:28:53

17/10/2018 12:28:55INFO[579717] – reloading haproxy config with the new config changes

17/10/2018 12:28:55 * Reloading haproxy haproxy

17/10/2018 12:28:55[WARNING] 289/102855 (32762) : config : ‘option forwardfor’ ignored for proxy ‘default’ as it requires HTTP mode.

17/10/2018 12:28:55[WARNING] 289/102855 (32764) : config : ‘option forwardfor’ ignored for proxy ‘default’ as it requires HTTP mode.

17/10/2018 12:28:55 …done.

17/10/2018 12:28:55

17/10/2018 12:29:09INFO[579731] – reloading haproxy config with the new config changes

17/10/2018 12:29:09 * Reloading haproxy haproxy

17/10/2018 12:29:09[WARNING] 289/102909 (352) : config : ‘option forwardfor’ ignored for proxy ‘default’ as it requires HTTP mode.

17/10/2018 12:29:09[WARNING] 289/102909 (354) : config : ‘option forwardfor’ ignored for proxy ‘default’ as it requires HTTP mode.

17/10/2018 12:29:09 …done.

17/10/2018 12:29:09

17/10/2018 12:29:11INFO[579733] – reloading haproxy config with the new config changes

17/10/2018 12:29:11 * Reloading haproxy haproxy

17/10/2018 12:29:11[WARNING] 289/102911 (380) : config : ‘option forwardfor’ ignored for proxy ‘default’ as it requires HTTP mode.

17/10/2018 12:29:11[WARNING] 289/102911 (382) : config : ‘option forwardfor’ ignored for proxy ‘default’ as it requires HTTP mode.

17/10/2018 12:29:11 …done.

17/10/2018 12:29:11

17/10/2018 12:29:28INFO[579750] – reloading haproxy config with the new config changes

17/10/2018 12:29:28 * Reloading haproxy haproxy

17/10/2018 12:29:28[WARNING] 289/102928 (469) : config : ‘option forwardfor’ ignored for proxy ‘default’ as it requires HTTP mode.

17/10/2018 12:29:28[WARNING] 289/102928 (471) : config : ‘option forwardfor’ ignored for proxy ‘default’ as it requires HTTP mode.

17/10/2018 12:29:28 …done.

17/10/2018 12:29:28

17/10/2018 12:29:30INFO[579752] – reloading haproxy config with the new config changes

17/10/2018 12:29:30 * Reloading haproxy haproxy

17/10/2018 12:29:30[WARNING] 289/102930 (492) : config : ‘option forwardfor’ ignored for proxy ‘default’ as it requires HTTP mode.

17/10/2018 12:29:30[WARNING] 289/102930 (494) : config : ‘option forwardfor’ ignored for proxy ‘default’ as it requires HTTP mode.

17/10/2018 12:29:30 …done.

17/10/2018 12:29:30

the config haproxy is here:

global
chroot /var/lib/haproxy
daemon
group haproxy
maxconn 4096
maxpipes 1024

ssl-default-bind-options no-sslv3 no-tlsv10

tune.ssl.default-dh-param 2048
user haproxy

defaults

maxconn 4096
mode tcp
option forwardfor
option http-server-close
option redispatch
retries 3
timeout client 50000
timeout connect 5000
timeout server 50000

resolvers rancher
nameserver dnsmasq 169.254.169.250:53

listen default
bind *:42

frontend 4000
bind *:4000
mode http
default_backend 4000_

backend 4000_
acl forwarded_proto hdr_cnt(X-Forwarded-Proto) eq 0
acl forwarded_port hdr_cnt(X-Forwarded-Port) eq 0
http-request add-header X-Forwarded-Port %[dst_port] if forwarded_port
http-request add-header X-Forwarded-Proto https if { ssl_fc } forwarded_proto
timeout check 10000
option httpchk GET “/health” “HTTP/1.0”
mode http
server da570b8c0091058ebb761c7ba4dac9ccb4eaf19a 10.42.87.166:3000 check port 3000 inter 20000 rise 2 fall 3
server b93352e68991e11660d03d7e3fd17a71bb4a8312 10.42.83.72:3000 check port 3000 inter 20000 rise 2 fall 3
server 92843be46e87a376712956cf2ac874d60f3fe414 10.42.82.233:3000 check port 3000 inter 20000 rise 2 fall 3
server 46929720de00f3afc7938e75157cce7adea73dde 10.42.53.57:3000 check port 3000 inter 20000 rise 2 fall 3
server 05c3c1e484b78006309da72eb02d77268a34a36c 10.42.28.241:3000 check port 3000 inter 20000 rise 2 fall 3
server aedb5dc425981ff16fd28d83bdff076d4395a06d 10.42.238.119:3000 check port 3000 inter 20000 rise 2 fall 3
server 055051c4fd1c8280d6c5d908246702e6b1670154 10.42.217.146:3000 check port 3000 inter 20000 rise 2 fall 3
server e4aa17f9c536375579233497d80a0d0c743713f3 10.42.212.224:3000 check port 3000 inter 20000 rise 2 fall 3
server e001dab4177cc5b00b10549873e6a67c39ec0953 10.42.206.18:3000 check port 3000 inter 20000 rise 2 fall 3
server 81cfca45e1ea13bbab8820623fa9782e27981b8e 10.42.202.157:3000 check port 3000 inter 20000 rise 2 fall 3
server 1a3c8807fec0dfc142e461af36cf776d3d0efc41 10.42.143.75:3000 check port 3000 inter 20000 rise 2 fall 3
server 17e947a1da6387e7e28c708407d1b68c2ef15d56 10.42.138.252:3000 check port 3000 inter 20000 rise 2 fall 3

So could you please helps us and find out way HA Proxy rancher is restarted so often?