Hi list,

I notice some problems with pound 2.2 balancing.
pound is compiled with:
--enable-dynscale=no
and PCRE support

ldd /usr/local/sbin/pound:
        libpcreposix.so.0 => /usr/local/lib/libpcreposix.so.0 (0x2808b000)
        libssl.so.4 => /usr/lib/libssl.so.4 (0x2808d000)
        libcrypto.so.4 => /lib/libcrypto.so.4 (0x280be000)
        libm.so.4 => /lib/libm.so.4 (0x281c3000)
        libpthread.so.2 => /lib/libpthread.so.2 (0x281d9000)
        libc.so.6 => /lib/libc.so.6 (0x28200000)
        libpcre.so.0 => /usr/local/lib/libpcre.so.0 (0x282f3000)


This is from my config file:

    BackEnd
        Address 192.168.13.13
        Port    8080
        Priority 5
    End

    BackEnd
        Address 192.168.13.14
        Port    8080
        Priority 5
    End

    BackEnd
        Address 192.168.13.18
        Port    8080
        Priority 7
    End

and this is what I see in my logfiles:

grep "Apr  7 14:56:"  /var/log/pound.log |grep 192.168.13.13 |wc -l
     170
 grep "Apr  7 14:56:"  /var/log/pound.log |grep 192.168.13.14 |wc -l
       2
grep "Apr  7 14:56:"  /var/log/pound.log |grep 192.168.13.18 |wc -l
     356

It seems that pound almost does not send requests to 192.168.13.14
Same situation with the *catch-all* service where priority is not set at 
all:

grep "Apr  7 14:56:"  /var/log/pound.log |grep 192.168.13.4 |wc -l
    2962
grep "Apr  7 14:56:"  /var/log/pound.log |grep 192.168.13.5 |wc -l
    1287
grep "Apr  7 14:56:"  /var/log/pound.log |grep 192.168.13.6 |wc -l
     158

And this is constant, not just a single case at this minute.

Also there is something weird in servicing SSL request from MSIE 6.x,
sometimes the page loads fore more then 20sec under MSIE, while there is 
not a single problem
with opera and firefox (and the page loads for ~2sec under opera and 
firefox).

I use
Ciphers "ALL:!aNULL:!ADH:!eNULL:!LOW:!EXP:RC4+RSA:+HIGH:+MEDIUM:-SSLv2
and can't support weaker encryptions because of the security issues, but 
this wasn't a problem with pound 2.1.4
I have set and "NoHTTPS11 2" (which is the default?), and tried with 
"NoHTTPS11 0", but not big difference.

Any ideas how to fix both issues?
[...]

Hi list,

Sorry that I reply to myself again .. :)
I found the problem for MSIE and it is not in pound. :)
It was caused by the firewall and MSIE itself ..

But the problem with balancing still bothers me.

Stefan Lambrev wrote:[...][...]

Stefan Lambrev wrote:[...]


There has been much discussion with dynamic scaling issues with the 2.2
release.  Try using 2.2.8 to see if that resolves your issue.

Kenneth Burgener wrote:[...][...][...]
The problem is that I compiled pound with --enable-dynscale=no and it 
still do dynamic scaling ?

Stefan Lambrev wrote:[...]


I could be wrong, but I believe the correct compiler parameter is
--disable-dynscale

Kenneth Burgener wrote:[...][...][...]
 From pound 2.2/configure --help :
Optional Features:
  --disable-FEATURE       do not include FEATURE (same as 
--enable-FEATURE=no)

  --enable-dynscale       enable or disable dynamic rescaling of priorities
                          (default: enabled)

Both should work if I understand correctly .

It will be good if pound can report what is enabled and what not, like  
"httpd -l".