Re: Explaining internal errors

From: Amos Jeffries <squid3_at_treenet.co.nz>
Date: Thu, 01 Jul 2010 00:17:57 +0000

On Wed, 30 Jun 2010 17:39:07 -0600, Alex Rousskov
<rousskov_at_measurement-factory.com> wrote:
> On 06/30/2010 05:17 PM, Amos Jeffries wrote:
<snip>
> The current patch is attached, FYI. It is not ready for merging yet.
>
> Here is an access.log sample from a lab test, with
> logformat xsquid %Ss/%03Hs %err_code/%err_detail %<Hs
>
> NONE/500 ERR_ICAP_FAILURE/100001 -
> NONE_ABORTED/500 ERR_ICAP_FAILURE/100001 -
> TCP_MISS/200 -/- 200
> TCP_MISS/200 ERR_ICAP_FAILURE/100004 200
> TCP_MISS/500 ERR_ICAP_FAILURE/100003 200
> TCP_MISS/500 ERR_ICAP_FAILURE/- 200
> TCP_MISS_ABORTED/000 -/- -
> TCP_MISS_ABORTED/000 -/- 200
> TCP_MISS_ABORTED/500 ERR_ICAP_FAILURE/100003 200
>

NP: you can log the details text for easier reading by placing the enum
definition in a file of its own and using the enum awk script to auto-build
a .cc with const string array ${enum}_str[]. The details code passed around
is the string array index.

see the 3.HEAD src/err_type.h and its Makefile.am entry for an example.

Amos
Received on Thu Jul 01 2010 - 00:18:00 MDT

This archive was generated by hypermail 2.2.0 : Thu Jul 01 2010 - 12:00:08 MDT