OpenShift 4 HAProxy log message: haproxy[2588504]: Starting|Stopping backend be_http in 0 ms

Solution Verified - Updated -

Issue

  • Why does HAProxy Access logs report a starting/stopping/started/stopped log for all routes?
  • HAProxy Access Logging reports a high frequency of the following type of log:
haproxy[3626877]: Proxy fe_no_sni started.
haproxy[3626877]: Proxy openshift_default started.
haproxy[3626877]: Proxy be_http:<project>:<route> started.
haproxy[3626877]: Proxy be_http:<project>:<route2> started.
...
haproxy[3626868]: Proxy fe_no_sni stopped (cumulated conns: FE: 9, BE: 0).
haproxy[3626868]: Proxy openshift_default stopped (cumulated conns: FE: 0, BE: 33).
haproxy[3626868]: Proxy be_http:<project>:<route> stopped (cumulated conns: FE: 0, BE: 0).
haproxy[3626868]: Proxy be_http:<project>:<route2> stopped (cumulated conns: FE: 0, BE: 0).

Environment

  • Red Hat OpenShift Container Platform (RHOCP) 4.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content