Re: [squid-users] log problem

On 29/01/2013 5:37 a.m., Clemente Aguiar wrote:
> I have calamaris running on a daily basis, parsing the log files.
>
> I have recently seen a problem with logging, I think since I updated
> to ver. 3.2.x.
>
> I see some weird characters on the "method" field, for example
> yesterday the calamaris log had 2 lines with "non readable" chars on
> the method column:
>
> Incoming requests by method:
>
> method request % Byte % sec kB/sec
> ----------------------------------------------------------------------
> GET 57420 95.16 5744092K 99.86 20 4.92
> POST 2029 3.36 7202213 0.12 0 5.50
> HEAD 646 1.07 228642 0.00 0 2.58
> PUT 230 0.38 543536 0.01 14 0.16
> NONE 12 0.02 50775 0.00 0 41320.80
> â‚S…›S.D>Õf…yÁv¢ž% 1 0.00 3776 0.00 0 36875.00
> ñµbc 1 0.00 3614 0.00 0 35292.97
>
>
> I verified that these lines with weird chars where present in the
> squid log file case by running the following command:
>
> $ sudo cat access.log.0 | awk '{print $6}' | sort | uniq
> ��bc
> GET
> HEAD
> NONE
> POST
> PUT
> ��S��S.D>�f�y�v��%
>
> As can be seen there are 2 instances of "non-printing" characters on
> field 6 of the log file. This means that squid in printing garbage on
> field 6 (method).
>
> Has anybody else seen this problem? Is this a (known and reported) bug?

Is not a bug as such. These are the methods clients sent.
As you can see Squid responded with an extremely fast rejection/error
message. Most likely ERR_INVALID_REQUEST response.

Earlier Squid hid such transactions 3.2 and later make them visible.

Amos
Received on Tue Jan 29 2013 - 11:32:26 MST