DAProxy service crashes due to Traefik HTTP/2 panic

Products

• Network Observability
• CA Performance Management

Issue/Introduction

The DAProxy service stops unexpectedly and fails to restart automatically due to a Traefik HTTP/2 panic. This article outlines the steps to diagnose this specific failure and remediate the DAProxy service state in DX NetOps Performance Management.

Environment

DX NetOps Performance Management (24.3.x versions utilizing DAProxy).

Cause

The Traefik component within DAProxy experiences an HTTP/2 panic, leading to a service crash. The default systemd unit configuration fails to initiate an automatic recovery when this condition occurs.

Resolution

1. Verify DAProxy Service Status Execute the following command to check the current status of the DAProxy service:

text

systemctl show daproxy.service -p Restart,RestartUSec

2. Inspect Service Logs Review the logs to confirm the presence of the Traefik HTTP/2 panic. Run:

text

journalctl -u daproxy --since "2026-07-01" | grep -B2 "Main process exited"

Search the output for errors similar to the following:

text

traefik[1531366]: panic: id (6) <= evictCount (7)

3. Manually Restart the Service If the panic is confirmed, manually restart the service to restore functionality:

text

systemctl restart daproxy

 

This is a known issue fixed in 25.4.1 and higher versions. Please upgrade DX NetOps to 25.4.x.

Resolved Issues

• Symptom:

  The version of Traefik that the data aggregator proxy server includes is experiencing some panic failures.
  

  Resolution:

  With this fix, the data aggregator proxy server now installs Traefik 3.5.1 to address the panic failures.
  (25.4.1, DE175379, 36535837)