Project

General

Profile

Bug #3330

Load Balancer showing wrong Status when using aliases for the port

Added by System IT over 5 years ago. Updated over 1 year ago.

Status:
Confirmed
Priority:
Normal
Assignee:
-
Category:
Load Balancer
Target version:
-
Start date:
11/19/2013
Due date:
% Done:

0%

Estimated time:
Affected Version:
All
Affected Architecture:

Description

Hello,

I have come across the issue of using Load Balancer with Port Alias's and the status not showing properly in the GUI.

Checking using relayctl show summary shows the pool as being active with all 3 hosts.

I have tested changing the name of the Alias to not include _ underscores, but it does not work either (previous bug was using a (.) period would cause the Unknown - relayd not running? to show in the GUI

The only way the Status in the GUI would show is if i put in a single port number instead of an Alias.

I have restarted the relayd several times as well just to be sure.

Firewall Port Alias.JPG (21.2 KB) Firewall Port Alias.JPG System IT, 11/19/2013 01:37 PM
Load Balance Pool 01.JPG (24.9 KB) Load Balance Pool 01.JPG System IT, 11/19/2013 01:37 PM
Load Balance Pool Status 01.JPG (34 KB) Load Balance Pool Status 01.JPG System IT, 11/19/2013 01:37 PM
Load Balance Pool.JPG (78 KB) Load Balance Pool.JPG System IT, 11/19/2013 01:37 PM
Virtual Servers 01.JPG (33.6 KB) Virtual Servers 01.JPG System IT, 11/19/2013 01:37 PM
Virtual Servers Status 01.JPG (27 KB) Virtual Servers Status 01.JPG System IT, 11/19/2013 01:37 PM
ralayctl show summary.JPG (33.4 KB) ralayctl show summary.JPG System IT, 11/19/2013 01:37 PM

History

#1 Updated by Daniel Onisoru almost 5 years ago

I confirm that this is the case in the latest version (2.1.5).

Also there seems to be something wrong with monitors when using aliases for ports.
For example I've set up a alias named "web" with ports 80:443 and set up a HTTPS monitor expecting a 200 status.
The problem is that it's using a https request for port 80 and, of course, it replies with a 400 Bad request so port 80 is always down.
Maybe this should be a different issue ?

#2 Updated by Murray Crane almost 4 years ago

Just to bump, this is still the case in 2.2.3. If Daniel Onisoru's ports alias issue above hasn't been made into an issue (will check shortly), only workaround I have found thus far (i.e., have relayd keep both LB routes open/up) is to not use either an HTTP or HTTPS monitor, and instead use the relatively simple ICMP monitor (which is annoying as that's why we're using the LB in the first place. Yes, the machine may well be up, but that tells me nothing about the status of Apache...).

#3 Updated by Chris Buechler almost 4 years ago

  • Subject changed from Load Balancer showing wrong Status when using Alias's for the port to Load Balancer showing wrong Status when using aliases for the port
  • Status changed from New to Confirmed
  • Affected Version changed from 2.1 to All
  • Affected Architecture deleted (amd64)

#4 Updated by Rami Gherbal over 3 years ago

Bug still affecting 2.2.6, Pool Status is marked as down whenever Alias is used, even with ICMP as a monitor.

#5 Updated by Harry Coin about 3 years ago

Confirmed still in 2.3_1. Use of ip alias in address field of virtual server cause " causes status "Unknown - relayd not running?"

Also: Changing alias name does not update the alias name in the load balancer virtual pool list.

Use of _ or just alpha in the alias name makes no difference.

#6 Updated by Kilian Ries over 2 years ago

Can confirm the bug still exists in pfsense 2.3.2-RELEASE-p1

#7 Updated by Alex Stefan over 2 years ago

Indeed, is still there in 2.3.2-RELEASE-p1, is not assigned to anybody unfortunately and I need to do load balancing on 2 RTP servers that initiate connection on 554 and then use any of the 65535 ports.

#8 Updated by Kilian Ries over 1 year ago

Can confirm it is still present in 2.4.2-RELEASE-p1 (amd64). This is really sad, the bug exists for more than 4 years now!

Also available in: Atom PDF