On 11.07.2012 02:00, Alan wrote:
> Its written clearly in the manual:
> access_log <module>:<place> [<logformat name> [acl acl ...]]
>
> In your case:
> acl DENY_ACCESS http_status 403
> access_log squid DENY_ACCESS
>
> "squid" refers to a predefined logformat, see
> http://www.squid-cache.org/Doc/config/logformat/
You are missing the <module>:<place> parameters. He had access_log
right the first time.
>
> On Tue, Jul 10, 2012 at 10:23 PM, ml ml wrote:
>> Hello Amos,
>>
>> thanks. I am using Squid Version 3.1.19 and those rules:
>>
>> acl DENY_ACCESS http_status 403
>> access_log daemon:/var/log/squid/DENY.log squid DENY_ACCESS
>>
>> However i get:
>>
>> 2012/07/10 15:18:13| aclParseAclList: ACL name 'DENY_ACCESS' not
>> found.
>> FATAL: Bungled squid.conf line 695: access_log
>> daemon:/var/log/squid/DENY.log squid DENY_ACCESS
>> Squid Cache (Version 3.1.19): Terminated abnormally.
>>
>> What am i doing wrong here?
>>
Something about the "acl" line. It looks fine in the snippet you posted
here.
We have had similar issues with perfectly valid-looking config years
ago. In those cases it turned out to be Unicode-enabled text editor or
GUI editors adding binary characters or Unicode letters into squid.conf.
Check for that kind of thing on the acl definition line.
Also check that the "acl" line is above the access_log line in config,
like you posted here.
Run "squid -k parse" and see if there is anything earlier in the config
file clashing.
Amos
Received on Tue Jul 10 2012 - 23:01:23 MDT
This archive was generated by hypermail 2.2.0 : Wed Jul 11 2012 - 12:00:01 MDT