[squid-users] cache_peer name gone from logs after upgrade to 3.5
Amos Jeffries
squid3 at treenet.co.nz
Thu Sep 29 03:53:01 UTC 2016
On 29/09/2016 7:38 a.m., Daniel Sutcliffe wrote:
> On Wed, Sep 28, 2016 at 1:56 PM, Yuri Voinov <yvoinov at gmail.com> wrote:
>>> It's tragedy, man.
>>>
>>> But 3.1 is too antique against 3.5 to remain unchanged.
>
> On Wed, Sep 28, 2016 at 2:02 PM, Daniel Sutcliffe <dans at chairfour.com> wrote:
>> :) Thankfully, almost all of the changes are improvements
>>
>>> Also, do not expect good documentation from open source
>
> Also, perhaps do not expect 100% reliable answers on open source
> mailing lists ;)
>
> In the 3.1 logformat docs -
> http://www.squid-cache.org/Versions/v3/3.1/cfgman/logformat.html
> we have a default of:
> logformat squid %ts.%03tu %6tr %>a %Ss/%03>Hs %<st %rm %ru %un %Sh/%<A %mt
> Whereas in the 3.5 we have:
> logformat squid %ts.%03tu %6tr %>a %Ss/%03>Hs %<st %rm %ru %[un %Sh/%<a %mt
>
> This is new for 3.5
> <a Server IP address of the last server or peer connection
> And this changed from this:
> <A Server IP address or peer name
> to this:
> <A Server FQDN or peer name
>
> I just needed to read a bit more - problem solved :)
As for the why:
With many sites going IPv6-enabled we were getting a lot of complaints
and queries about why some requests would work and others not work, but
the log only have one name displayed for any access to the site(s). It
often turned out to be broken connections to just one IP of several.
With the new format one can see the broken IPs more clearly and identify
the issue without guessing.
Amos
More information about the squid-users
mailing list