[squid-users] external_acl_type problem
Amos Jeffries
squid3 at treenet.co.nz
Mon Oct 24 06:51:09 UTC 2016
On 23/10/2016 11:39 p.m., reinerotto wrote:
> 1)
> According to
> http://www.squid-cache.org/Doc/config/external_acl_type/
>
> in squid.conf, this
>
> external_acl_type check_delay ttl=0 cache=0 %SRC /etc/squid/check_delay.sh
>
> should start 0 helpers immediately after squid (3.5.22) start-up.
> However, I always see 5.
Odd. The docs are slightly incorrect the max= value should be 5 not 20.
But the startup should be 0 in all Squid-3.2+ like you say. Are you
applying any patches to external_acl.cc or helper/ChildConfig.cc ?
>
> 2)
> I often see this:
> Sat Oct 22 23:51:18 2016 user.alert syslog: The check_delay helpers are
> crashing too rapidly, need help!
> Sat Oct 22 23:51:18 2016 local4.notice squid[21677]: Squid Parent: (squid-1)
> process 27685 exited with status 1
>
> Still trying to trace down the problem, I notice, that in this case some
> helpers still kept alive, although
> I expect them to be killed, too, in case squid-1 exits.
That is only logged when helpers exit by themselves. Properly
functioning helpers are required to always remain active and listening
for more lookups from Squid. Only when Squid terminates the stdin
channel should the helper exit.
>
> I need to add, that I am running squid on an embedded system, cross-compiled
> for MIPS.
> So there _might_ be some assumptions made for "standard LINUX" squid, which
> are not true in my case.
>
I hope there is no difference. Perl scripts are supposed to work the
same on any OSthat supports Perl.
Amos
More information about the squid-users
mailing list