Re: [squid-users] Warning squid -k parse

On 9/04/2013 6:36 a.m., Marcos A. Dzieva wrote:
> Dear
>
> Sorry for my english, I think you do not understand me.
> I delete everything inside the squid.conf and yet the warning appears.
>
> Thanks,
> Dzieva.

It turns out the newest parser additions for ACL flags was not quite
working and causing the built-in ACLs to be parsed twice. This is now
solved and will be working correctly in the next releases.

For now you can ignore the warnings when there are no squid.conf
entries. They are bogus.

Amos

>
> -----Mensagem Original----- From: Amos Jeffries
>
> On 5/04/2013 12:25 p.m., jeffrey j donovan wrote:
>> On Apr 4, 2013, at 2:24 PM, Marcos A. Dzieva wrote:
>>
>>> Dear...
>>>
>>> I am using squid 3.HEAD on a server ubuntu, and warning occurs
>>> before processing the configuration file.
>>> I have removed them acls from squid.conf, and warnings keep popping up.
>>>
>>> What could be wrong ?
>>>
>>> root_at_visa-proxy:~# squid -k parse
>>> 2013/04/04 15:04:09| WARNING: (B) '::/0' is a subnetwork of (A) '::/0'
>>> 2013/04/04 15:04:09| WARNING: because of this '::/0' is ignored to
>>> keep splay tree searching predictable
>>> 2013/04/04 15:04:09| WARNING: You should probably remove '::/0' from
>>> the ACL named 'all'
>>> 2013/04/04 15:04:09| WARNING: (B) '127.0.0.1' is a subnetwork of (A)
>>> '127.0.0.1'
>>> 2013/04/04 15:04:09| WARNING: because of this '127.0.0.1' is ignored
>>> to keep splay tree searching predictable
>>> 2013/04/04 15:04:09| WARNING: You should probably remove '127.0.0.1'
>>> from the ACL named 'localhost'
>>> 2013/04/04 15:04:09| WARNING: (B) '127.0.0.0/8' is a subnetwork of
>>> (A) '127.0.0.0/8'
>>> 2013/04/04 15:04:09| WARNING: because of this '127.0.0.0/8' is
>>> ignored to keep splay tree searching predictable
>>> 2013/04/04 15:04:09| WARNING: You should probably remove
>>> '127.0.0.0/8' from the ACL named 'to_localhost'
>>> 2013/04/04 15:04:09| Processing Configuration File:
>>> /etc/squid/squid.conf (depth 0)
>>>
>>> Thanks.
>>> Dzieva.
>>
>> I had the same thing
>>
>> uncomment any lines that look like this ;
>> #acl manager proto cache_object
>> #acl localhost src 127.0.0.1/32
>> #acl to_localhost dst 127.0.0.0/8 0.0.0.0/32 ::1
>>
>> it appears that squid knows who localhost is. error went away when i
>> commented those lines out.
>>
>> -j
>
> Yes. Please read http://www.squid-cache.org/Doc/config/acl/ and in
> particular notice the "Default Value" information
>
> Amos
Received on Sun May 05 2013 - 08:25:04 MDT