Project

General

Profile

Actions

Bug #1486

closed

relayd does not set sticky-address option when set in advanced/misc

Added by John Welter over 10 years ago. Updated over 10 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Load Balancer
Target version:
Start date:
05/02/2011
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.0
Affected Architecture:

Description

When the sticky session flag is set in advanced/misc and then a relayd pool setup the sticky-session option is not set in the resulting /var/etc/relay.conf file.

Adding the sticky-session option manually allows session persistence to work as expected.

Here is a piece of the file, with the sticky-address manually added:

redirect "Prod_HTTPS" {
listen on 74.200.xxx.xxx port 443
sticky-address
forward to <Prod_HTTPS> port 443 check https '/wms/test.html' code 200 timeout 5000
}

Actions #1

Updated by Ermal Luçi over 10 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100
Actions #2

Updated by John Welter over 10 years ago

Unfortunately this still doesn't fix the issue. I tested and (isset($conf['system']['lb_use_sticky'])) returns false even though sticky is set in advanced/misc. Perhaps it has been renamed in v2.0 or something?

Actions #3

Updated by Chris Buechler over 10 years ago

  • Category set to Load Balancer
  • Target version set to 2.0
Actions #4

Updated by Warren Baker over 10 years ago

There was a typo s/conf/config/ - this has been fixed.

Applied in change set 327ef8eb3244f79e1b669dca792c83d45657f7d4

Actions #5

Updated by John Welter over 10 years ago

I tested the Tue May 3 11:16:02 EDT 2011 and the bug is fixed. Thanks for the quick turn around!

Actions #6

Updated by Chris Buechler over 10 years ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF