Hello! We have several installations where pound balances a few HTTP (apache2 httpd) backends, and this usually works fine.
Sometimes we see "copy chunks" (and similar) errors, but this is to be expected since the clients are mostly mobile phones. But, in a recent installation we get errors that we can not find a cause for. Like this: Feb 6 13:34:55 <server> pound: (7fb2eb2c0700) e500 for PUBLIC-IP response error read from <backend-ip>:80/POST /some/url?bsid=5d830425 HTTP/1.1: Success (0.149 secs) The environment is: Pound 2.6 Apache HTTPD 2.2.22 Ubuntu 12.04 The POST messages are about 20k-40k. I have done tcpdumps both in front of Pound and in front of Apache. I can see that the HTTP 500 error is returned by Pound immediately, but it also looks like the request makes its way down to the Apache (which never sends an error, i guess that Pound closes the socket?). The request is part of a series of similar requests from the mobile phone, where we always get an error, but sometimes after 2-3 requests, sometimes after perhaps 10 requests. The POST is a chunked request. So, why does Pound immediately return a HTTP 500 to the client without waiting for the backend response? How can i see what error it finds? And... any way to increase logging in Pound? :) wbr / Alex -- Alexander Kolodziej System Administrator, Tactel AB Phone: +46761452104 Email: [email protected] -- To unsubscribe send an email with subject unsubscribe to [email protected]. Please contact [email protected] for questions.
