[squid-users] The url_rewriter helpers are crashing too rapidly
M.Funke at olpe.de
Tue Oct 27 06:38:04 UTC 2015
so squid is now working again. It was a problem with squidguard and option -s.
Why this all of sudden is a problem, I don’t know. I have some other servers and there everything works without a problem.
Thank you all for your great help :).
Von: squid-users [mailto:squid-users-bounces at lists.squid-cache.org] Im Auftrag von Amos Jeffries
Gesendet: Montag, 26. Oktober 2015 16:03
An: squid-users at lists.squid-cache.org
Betreff: Re: [squid-users] The url_rewriter helpers are crashing too rapidly
On 27/10/2015 3:42 a.m., Eliezer Croitoru wrote:
> Try to disable squidGuard and see if it solves the issue.
> Maybe a bad update for squidguard caused some issue with the startup
> of the helper.
> Also try to run the same command that is being used by squid to start
> squidGuard in order to start and debug the issue.
> * squid 2.7 is not supported anymore and I was pretty sure that SUSE
> SP3 supply a newer version of squid.
Correct. SUSE 11 came with Squid-3.1.
And, SUSE 12 was out with Squid-3.3 a whole year ago tomorrow.
Neither is great by our current standards (3.5), but still miles ahead of 2.7.
> On 26/10/2015 16:28, Funke, Martin wrote:
>> 2015/10/26 14:55:02| helperOpenServers: Starting 25 'squidGuard'
>> (squidGuard): invalid option -- 's'
>> I hope someone can give some hints.
Squid is already giving you huge hints:
"(squidGuard): invalid option -- 's'"
I'm also minded that the only changes anyone has published for squidGuard in the last few years were my release of patches to make it handle Squid-3.2+ helper protocol. Any Squid older than 3.2 will have horrible problems if passed responses from a SG patched with those. They were only ever intended for use to make SG compatible with a Squid upgrade to 3.4+.
squid-users mailing list
squid-users at lists.squid-cache.org
More information about the squid-users