Hello,

On my test station I upgraded pound from 2.1.4 to 2.2.5 and it works ok 
with the old configuration file.
I'm using freebsd 6.2-stable. and there are 2 problems that I found.
First and the very important is fail detection system it just does not work.

I have configured 3 backends, but one of them is not working at the 
moment (old pound deal OK with this),
but in 2.5.5 if I'm redirected to dead backend pound does nothing just 
continue to send request to it:

Mar  1 12:04:54 mb6 pound: backend 192.168.13.4:9090 connect: Connection 
refused
Mar  1 12:04:57 mb6 last message repeated 395 times
Mar  1 12:05:00 mb6 pound: backend 192.168.13.4:9090 connect: Connection 
refused
Mar  1 12:05:32 mb6 last message repeated 1691 times
Mar  1 12:06:43 mb6 last message repeated 4370 times
Mar  1 12:06:46 mb6 pound: backend 192.168.13.4:9090 connect: Connection 
refused
Mar  1 12:06:46 mb6 last message repeated 198 times

Finally after 3000 seconds it displayed the error page, but next request 
from my IP is again forwarded to the same dead backend.
In my opinion if the port of the backend is closed - e.g returns 
Connection refused, pound should immediately sent
request to next *alive* backend and stop sending request to the dead 
backend (before it is alive again).

If I hit refresh or restart browser, or even start new browser I'm 
unable to load the site.
The other weird thing is that there is no difference between LogLevel 2 
& 3.
I was looking how to log response time, I used custom patch in 2.1.4 
but  everything shows that this patch is already integrated
in latest pound.

Also (as I'm not 100% sure) transferring data over HTTPS seems lot 
slower in 2.5.5 compared to 2.1.4 - that's why I want to log response times.

Pound is configured with --enable-dynscale=no and I have this custom 
patch (to be able to compile on fbsd) :

--- pound.h.orig
+++ pound.h
(at)(at) -178,7 +178,8 (at)(at)
 #if HAVE_OPENSSL_SSL_H
 #define OPENSSL_THREAD_DEFINES
 #include    <openssl/ssl.h>
-#if OPENSSL_VERSION_NUMBER >= 0x00907000L
+#include    <openssl/opensslconf.h>
+#if OPENSSL_VERSION_NUMBER > 0x0090705FL
 #ifndef OPENSSL_THREADS
 #error  "Pound requires OpenSSL with thread support"
 #endif

And here is my configuration file.

ListenHTTPS
  Address 0.0.0.0
  Port    443
  Cert    "/usr/local/etc/pound/server.pem"
  Ciphers "ALL:!aNULL:!ADH:!eNULL:!LOW:!EXP:RC4+RSA:+HIGH:+MEDIUM:-SSLv2"
  NoHTTPS11 1
End

ListenHTTP
  Address 0.0.0.0
  Port    80
  RewriteLocation 0
  Err500 "/usr/local/etc/pound/error502.html"
  Err501 "/usr/local/etc/pound/error502.html"
  Err503 "/usr/local/etc/pound/error502.html"
  Err414 "/usr/local/etc/pound/error502.html"

End

#APP servers
Service
    URL ".*/app/*"
    BackEnd
        Address 192.168.13.13
        Port    8080
        TimeOut 3000
    End

    BackEnd
        Address 192.168.13.14
        Port    8080
        TimeOut 3000
    End
End

#Catch ALL
Service
    HeadDeny "X-SSL-Subject"
    HeadDeny "X-SSL-Issuer"
    HeadDeny "X-SSL-notBefore"
    HeadDeny "X-SSL-notAfter"
    HeadDeny "X-SSL-serial"
    HeadDeny "X-SSL-cipher"

    Session
        Type IP
        TTL  300
    End

    BackEnd
        Address 192.168.13.5
        Port    80
        TimeOut 3000
    End

    BackEnd
        Address 192.168.13.4
        Port    9090
        TimeOut 3000
    End

    BackEnd
        Address 192.168.13.8
        Port    80
        TimeOut 3000
    End
End

Alive 4
LogLevel 4

P.S. I plan to test with previous version of pound and to try to found 
where my problems starts, and let you know.
[...]

On Mar 1, 2007, at 5:34 AM, Stefan Lambrev wrote:
[...]


This is precisely the behavior I reported in my previous posting. It  
seems 2.5.5 is indeed broken somewhere.  FWIW, I backed down to  
2.1.3, and life went back to normal.

-mml

Hi,

McClain Looney wrote:[...][...][...]
Sorry, I missed your e-mail.
What about pound 2.2 ? it is the latest STABLE ? :)[...]