Project

General

Profile

Actions

Bug #15274

open

HAProxy Configuration Changes Require pfSense Reboot to Take Effect

Added by Zachary Cohen 3 months ago. Updated 2 months ago.

Status:
Incomplete
Priority:
Normal-package
Assignee:
-
Category:
haproxy
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Affected Version:
2.7.x
Affected Plus Version:
Affected Architecture:
amd64

Description

As originally reported here (https://forum.netgate.com/topic/172972/haproxy-config-changes-not-loaded-pfsense-restart-needed), changes made to the HAProxy configuration require a reboot to take effect.

I'm consistently able to reproduce this issue when adding new backends.

When browsing to the new backend, I receive a 503 - "no server is available to handle this request". After rebooting, it works as expected.

Other users have been able to validate that this issue was present starting with pfSense 2.6.0 and HAProxy version haproxy-devel 0.62.10.

While I was able to replicate that issue starting on that version, I'm currently replicating it in pfSense 2.7.2-RELEASE (amd64) and haproxy-devel 0.63_2.

Actions

Also available in: Atom PDF