Hi everyone, We have deployed 2.7.7 recently, to verify the CPU spike fixes we observed in https://github.com/haproxy/haproxy/issues/2046
The spikes seem to be fixed now. However, we are now observing log messages during shutdown that weren’t there before: May 12, 2023 @ 11:56:24.000 Proxy health_check_http_tcp-scheduler stopped (cumulated conns: FE: 0, BE: 0). May 12, 2023 @ 11:56:24.000 Proxy http-in stopped (cumulated conns: FE: 166, BE: 0). May 12, 2023 @ 11:56:24.000 Proxy st_http_req_rate stopped (cumulated conns: FE: 0, BE: 0). May 12, 2023 @ 11:56:24.000 Proxy https-in stopped (cumulated conns: FE: 29570, BE: 0). May 12, 2023 @ 11:56:24.000 Proxy st_tcp_conn_rate stopped (cumulated conns: FE: 0, BE: 0). May 12, 2023 @ 11:56:24.000 Proxy http-routers-http2 stopped (cumulated conns: FE: 0, BE: 14768). May 12, 2023 @ 11:56:24.000 Proxy stats stopped (cumulated conns: FE: 1, BE: 0). May 12, 2023 @ 11:56:24.000 Proxy health_check_http_url stopped (cumulated conns: FE: 1811, BE: 0). May 12, 2023 @ 11:56:24.000 Proxy tcp-frontend_scheduler stopped (cumulated conns: FE: 3, BE: 0). May 12, 2023 @ 11:56:24.000 Proxy <HTTPCLIENT> stopped (cumulated conns: FE: 0, BE: 0). May 12, 2023 @ 11:56:24.000 Proxy tcp-scheduler stopped (cumulated conns: FE: 0, BE: 3). May 12, 2023 @ 11:56:24.000 Proxy http-routers-http1 stopped (cumulated conns: FE: 0, BE: 134385). It seems one such message is logged per each “Proxy” (which I assume is an internal handler for listeners, backends, frontends etc.). We don’t suspect this to be a bug, but wanted to ask for clarification about the purpose of those log messages and if they present a problem or not. Best regards, Dominik Froehlich, SAP BTP
