Hi,
On 23/10/2012 8:10 p.m., Ben wrote:
Hi,
On 23/10/2012 5:07 a.m., Ben wrote:
Hi,
My squid 3.2.3 latest version getting restart automatically with
error "FATAL: Bungled (null) line 192: icap_retry deny all". What
could be reason behind this problem? How to resolve it.?
Did you ./configure using --enable-icap-client ?
Yes, i configured with this options.
Squid Cache: Version 3.2.3
configure options: '--prefix=/opt/squid-3.2'
'--enable-storeio=aufs,ufs' '--enable-removal-policies=lru,heap'
'--enable-cachemgr-hostname=CACHE-Engine' '--enable-linux-netfilter'
'--enable-follow-x-forwarded-for' '--disable-auth' '--disable-ipv6'
'--enable-zph-qos' '--with-large-files' '--enable-snmp'
'--enable-wccp' '--enable-wccp2' '--enable-kill-parent-hack'
'--enable-http-violations' '--enable-async-io=128'
'--enable-err-languages=English'
'--enable-default-err-language=English' '--enable-icap-client'
'--enable-libcap' --enable-ltdl-convenience
Amos
since last day, there is no more entry for this fatal error. what
does this error says?
I'm not exactly sure what the bungled is about. I've just patched
latest 3.HEAD to explain "(null)" better. That means one of the
default values built-in to Squid is broken.
This message is saying the default value for when you have nothing in
your squid.conf about icap_retry is not able to be defined.
What do you mean by "since last day" ... you have a new build that
works? or you added icap_retry to the config and it works? or no
changes and it just started working?
Yes, no changes and it just started working.
One thing i noticed in 3.2.3, now there is no FATAL: dying issues which
I faced in 3.1. series for which i had sent mail to squid users.
Amos
BR
Ben
