Relayd - and fall back pool on different port



  • Hello :)
    I did not find any items about my problem.

    I am configuring a load balancer policy with 2 pools: an "active" and a fallback.
    The active pool is configured on port 80
    The fallback pool is on port 8080.

    The fallback pool is down, an not packet are issued by relayd checks (verified by tcpdump).
    The active pool is working as expected (checks on port 80).

    The configuration for relayd is:

    log updates
    timeout 1000
    table <web-frontend>{
    10.6.0.5
    10.6.0.6
    10.6.0.7
    10.6.0.8
    10.6.0.9
    10.6.0.10
    10.6.0.11
    10.6.0.12
    10.6.0.13
    10.6.0.14
    10.6.0.15
    10.6.0.16
    10.6.0.17
    10.6.0.18
    10.6.0.19
    10.6.0.20
    10.6.0.21
    10.6.0.22
    10.6.0.23
    10.6.0.24
    10.6.0.25
    10.6.0.26
    10.6.0.27
    10.6.0.28
    10.6.0.29
    10.6.0.30
    }
    table <web-master>{
    10.6.0.3
    }
    dns protocol "dnsproto" {
    tcp { nodelay, sack, socket buffer 1024, backlog 1000 }
    }
    redirect "Elections" {
      listen on 1.2.3.4 port 80
      forward to <web-frontend>port 80 check http '/municipales/'  code 200
      forward to <web-master>port 80 check http '/municipales/'  code 200
    }</web-master></web-frontend></web-master></web-frontend>

    I attach a screen capture of the pool configuration.
    As you can see, web-master is configured as port 80, not 8080 …

    Is it a known bug, a dumb configuration or something new ?

    Thanks for you help
    Regards,
    Nicolas

    EDIT: I am using version 2.1 release


Log in to reply