On Sun, Nov 22, 2009 at 12:09:37PM -0500, Joe Stein wrote:
> Hi, we are using HA-Proxy version 1.3.19 2009/07/27
When you have some time, please upgrade to 1.3.22 which fixes some bugs.
> For the second time in the last week we seem to be getting NOSRV in the
> haproxy logs for a few minutes without any reason (nothing in any log down
> stream).
The most important part is the "BADREQ" part, it indicates that the
client has sent you a bad request and that haproxy did not forward it
to any server :
208.54.90.71:47640 = client's IP:port
[22/Nov/2009:09:20:50.637] => accept date
ads_events = frontend
ads_events/ = backend (same)
<NOSRV> = server (none)
-1/-1/-1/-1/0 = no valid request received
400 = 400 Bad request sent in response
187 = length of the response
- - PR-- = terminated by proxy during request phase
10/10/0/0/0 = 10 connections total on frontend
0/0 = nothing in queue
{|} = nothing captured
"<BADREQ>" = no valid request to log
You can connect to the stats socket using socat and issue a "show errors".
It will tell you exactly what the last bad request contained. Most often
those are just bots trying to detect and exploit vulnerabilities on your
site, so there's not much to worry about.
Regards,
Willy
