Hello,

after upgrading to the actual version pound seems to ignore one backend.
Yesterday it seemed to be the node with 192.168.12.22, but today - after 
a pound restart - it is 192.168.12.20!
I can see that some requests coming through, but only on of a hundred or 
something ... that's not what I wanted ;)

Any ideas?


Here is my (simple) config:

Service
        BackEnd
                Address         192.168.12.20
                Timeout         300
                Port            80
                Priority        6
        End

        BackEnd
                Address         192.168.12.21
                Timeout         300
                Port            80
                Priority        3
        End

        BackEnd
                Address         192.168.12.22
                Timeout         300
                Port            80
                Priority        6
        End

        BackEnd
                Address         192.168.12.23
                Timeout         300
                Port            80
                Priority        6
        End

        Session
        Type    PARM
                ID      "sid"
                TTL     300
        End

End


Thanks and regards,
Robert

Robert Klikics wrote:
[...]

This sounds very much as if dynamic rescaling was the culprit. Try
compiling pound with "--disable-dynscale" and there is a good chance the
problem will be gone.

Steve

Steve schrieb:[...]
Thanks for the info. But in which case makes the "dynamic rescaling" 
sense? For me it does not make sense ...[...]
Robert