Bug #1063
closedLoad balancer status doesn't work if the virtual server name contains a '.'
100%
Description
Hi,
I've spent a while trying to work out why a test load balancer config I created seemed to be working fine, but have a status that suggested it wasn't working. The load balancer logs suggested relayd was running, backend nodes were being checks and add into the table once the checks succeeded. I confirmed that relayd was actually running using the shell.
However, whenever I visited the virtual servers tab on the load balancer status page, in the status column, it displays: 'Unknown - relayd not running?'.
It turns out that I had created a virtual server with a name containing a '.' (a period, a full stop, whatever you want to call it).
As soon as I changed the name to something not containing the '.', the status page resumed working again. It seems that a '.' in the name is valid within relayd's config else presumably the load balancing wouldn't have worked at all?
I assume the status page does some sort of regex matching against the log file, or something like that? And presumably this matching isn't working correctly with '.'s?
Files
Updated by Jim Pingle almost 14 years ago
Can you show the output of:
relayctl show summary
With and without a server that has a '.'?
Updated by Gary Richards almost 14 years ago
: relayctl show summary
Id Type Name Avlblty Status
1 redirect test active
1 table TEST_WEB_443:443 active (2 hosts)
1 host 10.105.255.21 100.00% up
2 host 10.105.255.22 100.00% up
2 redirect test.test active
2 table TEST_WEB_443:443 active (2 hosts)
3 host 10.105.255.21 100.00% up
4 host 10.105.255.22 100.00% up
Updated by Gary Richards almost 14 years ago
Bah, attached in a slightly more readable format
Updated by Jim Pingle almost 14 years ago
Actually nevermind, I think I got it. Commit is pending.
Updated by Jim Pingle almost 14 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset 0a0774b511c6833a2b87975c21fdb3b10897d6c9.
Updated by Chris Buechler over 13 years ago
- Status changed from Feedback to Resolved