Project

General

Profile

Actions

Bug #15182

open

Changing backend port - status remains down

Added by Mike Moore 10 months ago. Updated 9 months ago.

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

0%

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

Description

I noticed that if you enable basic health checks on a backend server, in my example port 443 the health check succeeds.
Later on if the port changes and you update the configuration to reflect that, the healthcheck fails. In my case reviewing the haproxy_stats page shows that its still checking port 443 even though the configuration is set for port 80.
I also receive a new 'warning' from the package when i attempt to apply my changes

I did notice that if the backend server health check is DOWN already before you make the health check modification this is what causes the problem.
1. first have a successful health check.
2. Change backend application to a different service port. In my case from port 443 to port 80
3. Update the health check. If you check the status it should be down
4. Attempt to apply config. You will see the warning but that prevents the changes from going forward.

I tried with 23.05 and my problem doesn't exist on that version.


Files

changed to port 80 from 443.png (38.3 KB) changed to port 80 from 443.png Mike Moore, 01/22/2024 03:38 AM
still checking for 443.png (24.1 KB) still checking for 443.png Mike Moore, 01/22/2024 03:39 AM
warning.png (45.2 KB) warning.png Mike Moore, 01/22/2024 03:40 AM
Actions

Also available in: Atom PDF