Project

General

Profile

Actions
Copy link

Bug #16618

closed

Forcing a service restart of HAProxy does not affect backend servers

Added by Miroslav Vlach about 1 month ago. Updated 20 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
Marcos M
Category:
HAProxy
Target version:
-
Start date:
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Affected Version:
2.8.1
Affected Plus Version:
Affected Architecture:

Description

Reopening https://redmine.pfsense.org/issues/16596 since the author mentioned it shows as a warning
1) Because the closing comment says incorrect information as this is not the case (pfsense 2.8.1) - restarting service nor stopping it and starting made a difference, also the message does not say I should do anything beyond applying changes

2) Even if it was the case, if restarting service did not do anything, would I need to restart the entire pfsense? That makes no sense! I have tried stopping the service and starting it for the Service status menu and that did not make any difference. I spent 2 hours on new years eve with this so thank you very much.

This is a pretty nasty bug which is in pfsense for years (see https://forum.netgate.com/topic/184401/haproxy-seems-to-forward-to-wrong-backend-port?_=1767279314113 ) - the solution with `load-server-state-from-file none` and stopping and starting the service was the only solution that worked for me. The way I figured it out was thanks to haproxy stats - hovering over the backend name showed the IP and old port.

Files

Download all files
clipboard-202601011604-73sam.png (62.2 KB) clipboard-202601011604-73sam.png Miroslav Vlach, 01/01/2026 03:04 PM
clipboard-202601011604-2hoxx.png (69.1 KB) clipboard-202601011604-2hoxx.png Miroslav Vlach, 01/01/2026 03:04 PM
clipboard-202601101548-lqwzm.png (160 KB) clipboard-202601101548-lqwzm.png Danilo Zrenjanin, 01/10/2026 02:48 PM
Actions
Copy link
 #1

Updated by Danilo Zrenjanin 25 days ago

I was able to reproduce the behavior described here. In my case, after changing the backend port, the configuration (/var/etc/haproxy/haproxy.cfg) was updated, but the backend went down. The only way to bring it back up was to restart the entire firewall. A forced service restart did not help (Settings > Force Service Restart to apply changes immediately).

Actions
Copy link
 #2

Updated by Marcos M 23 days ago

  • Subject changed from HAProxy-Changing the port of an existing backend server, changes show in the GUI only but is not reloaded within haproxy itself to Forcing a serveice restart of HAProxy does not affect backend servers
  • Status changed from Confirmed to Feedback
  • Assignee set to Marcos M
  • Priority changed from Very High to Normal
  • % Done changed from 0 to 100

This should be fixed with e6c189dfd319f0a404b3462d519e8a6e0e64b685.

Actions
Copy link
 #3

Updated by Marcos M 23 days ago

  • Subject changed from Forcing a serveice restart of HAProxy does not affect backend servers to Forcing a service restart of HAProxy does not affect backend servers
Actions
Copy link
 #4

Updated by Danilo Zrenjanin 20 days ago

  • Status changed from Feedback to Resolved

Tested against:

haproxy-devel    net    0.66.6

It has been fixed. I am marking this case as resolved.

Actions
Copy link

Also available in: Atom PDF