Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

HAProxy replies client with RST when client side reuses port in http mode and soft reload is issued on HAProxy

Aperta
  • Qualcosa non va?
#3,472 6 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
c
Ambito
backend, networking

Direzione di ricerca

Start by reproducing the issue with HAProxy master-worker mode, the shown HTTP backend settings, connection pooling, and the specified keep-alive timeouts. Use the described tcpdump observations to trace the client connection across a soft reload; done means reused client requests continue without HAProxy sending FIN or RST.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

status: feedback required type: bug
Detailed Description of the Problem
Setup

Clients --> Gateway -> HAProxy -> Backend Server

Client side Gateway is using ConnectionPools which means the client tries to reuse exiting connection (5 sec timeout).
Client side keep alive timer: 5 seconds
HAProxy keep alive timeout: 60 seconds
HAProxy Version haproxy-3.0.17

Issue

Whenever client reuses existing connection towards HAProxy, and HAProxy is issued soft reload (due to changes to in the ingress or backend), then the HAProxy terminating the client connection with RST.

I believe above is not an expected behaviour on the HAProxy. Either the soft reload or client side connection reuse should not lead to termination of the existing connection by the HAProxy.

Current Analysis

Analysed the tcpdumps and client connection behaviour for the above scenario.
Tcpdump traces indicate that whenever clients have started the connections:

  • There is single tcp/SSL connection from client to the HAProxy for entire duration
  • There are multiple http connections from HAProxy to the backend server - one for each client request

When reload is issued on HAProxy the following observation is made:

  • No issue or tcp/http packets seen between HAProxy and the backend server
  • If client tries to send another request using the existing tcp connection, HAProxy is replying with FIN and RST
Expected Behavior

The client requests should continue to work as it was working prior to the reload of the HAProxy.

Steps to Reproduce the Behavior
  1. Connect some Gateway before the HAProxy with connection pooling enabled, set the port reuse timeout to 5 seconds
  2. Use standard master-worker mode on HAProxy, add a HTTP backend, set http-keep-alive time out to 1m
  3. Establish multiple http GET requests from the client side and while the requests are in progress, issue soft reload on the HAProxy
Do you have any idea what may have caused this?

No response

Do you have an idea how to solve the issue?

No response

What is your configuration?
**HAProxy Config**

 
global
     master-worker

 defaults
     log global
     option redispatch
     option http-server-close 
     option http-keep-alive
     timeout client          600s
     timeout client-fin      600s
     timeout connect         5s
     timeout http-keep-alive 1m
     timeout http-request    5s
     ...

 backend apps
     mode http
     balance hdr(xyz)
     option srvtcpka
    ...
Output of haproxy -vv
NA
Last Outputs and Backtraces
Additional Information

No response

Lingua principale
C
Stelle
6.9k
Fork
976
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di haproxy/haproxy

Tutte le issue di haproxy/haproxy

Issue simili

Altre issue su C

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.