Re: clientReadRequest: FD 312 Invalid Request

You're right, it seems to be a client. It's a remote one and behind
a NAT box so it'll take some time to locate it.

Here is the relevant access.log record that generates those messages in
/var/log/messages:

960190604.607 4 111.111.111.111 NONE/400 2577 GET
error:missing-http-ident -
 NONE/- -
 
960190751.454 14 111.111.111.111 NONE/400 2577 GET
error:missing-http-ident -
 NONE/- -

I've changed the sourse IP obviously.
Does this make any sence to you?

This is a transparent proxy I am running using wccp to redirect the
traffic.

Thank you,
slava

On Sun, 4 Jun 2000, Duane Wessels wrote:

>
>
> On Sun, 4 Jun 2000, Veaceslav Revutchi wrote:
>
> >
> > Hello,
> >
> > I'm seeing lots of this in /var/log/messages. Is this an indication of
> > something wrong? (i'm running 2.3stable3 on FreeBSD 4.0stable).
> > The overall performance of the caching server seems to be good though...
> >
> > thanks,
> > slava
> >
> > Jun 4 19:49:56 xeon squid[163]: clientReadRequest: FD 312 Invalid Request
> > Jun 4 19:49:57 xeon squid[163]: clientReadRequest: FD 128 Invalid Request
> > Jun 4 19:49:59 xeon squid[163]: clientReadRequest: FD 266 Invalid Request
> > Jun 4 19:50:00 xeon squid[163]: clientReadRequest: FD 88 Invalid Request
> > Jun 4 19:50:02 xeon squid[163]: clientReadRequest: FD 49 Invalid Request
> > Jun 4 19:50:03 xeon squid[163]: clientReadRequest: FD 63 Invalid Request
> > Jun 4 19:50:05 xeon squid[163]: clientReadRequest: FD 38 Invalid Request
> > Jun 4 19:50:06 xeon squid[163]: clientReadRequest: FD 191 Invalid Request
> > Jun 4 19:50:08 xeon squid[163]: clientReadRequest: FD 128 Invalid Request
> > Jun 4 19:50:09 xeon squid[163]: clientReadRequest: FD 62 Invalid Request
> > Jun 4 19:50:14 xeon squid[163]: clientReadRequest: FD 92 Invalid Request
> > Jun 4 19:50:15 xeon squid[163]: clientReadRequest: FD 23 Invalid Request
> > Jun 4 19:50:17 xeon squid[163]: clientReadRequest: FD 268 Invalid Request
> > Jun 4 19:50:18 xeon squid[163]: clientReadRequest: FD 48 Invalid Request
> > Jun 4 19:50:24 xeon squid[163]: clientReadRequest: FD 23 Invalid Request
> > Jun 4 19:50:24 xeon squid[163]: clientReadRequest: FD 159 Invalid Request
> > Jun 4 19:50:27 xeon squid[163]: clientReadRequest: FD 84 Invalid Request
> > Jun 4 19:50:28 xeon squid[163]: clientReadRequest: FD 105 Invalid Request
> > Jun 4 19:50:30 xeon squid[163]: clientReadRequest: FD 37 Invalid Request
> > Jun 4 19:50:31 xeon squid[163]: clientReadRequest: FD 183 Invalid Request
> > Jun 4 19:50:33 xeon squid[163]: clientReadRequest: FD 104 Invalid Request
> > Jun 4 19:50:34 xeon squid[163]: clientReadRequest: FD 84 Invalid Request
> > Jun 4 19:50:36 xeon squid[163]: clientReadRequest: FD 210 Invalid Request
>
> It probably means one of two things: either you have a client that
> is misbehaving, or there is an incompatibility with persistent connections.
>
> It should be possible to correlate these with access.log entries, so you
> can see if they all come from one client, same URL, etc...
>
> Duane W.
>
>
Received on Mon Jun 05 2000 - 02:04:31 MDT