Bug #4243: Last squidguard update prevents squid from starting - pfSense Packages - pfSense bugtracker

Actions

Copy link

Bug #4243

closed

Last squidguard update prevents squid from starting

Added by Volker Kuhlmann over 9 years ago. Updated about 8 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Category:

squidguard

Target version:

Start date:

01/19/2015

Due date:

% Done:

Estimated time:

Plus Target Version:

Affected Version:

2.1.5

Affected Plus Version:

Affected Architecture:

Description

I don't believe I am seeing a package update breaking things completely...

squidguard 1.4_4 pkg v.1.9.9 introduces illegal directives into the squid 2.7.9 pkg v.4.3.4 config file. For some reason, on boot or after installing the package, squid still starts up - although a fatal error is logged. When changing the configuration the change never becomes active because some safety mechanism prevents the running squid from being stopped, to avoid it not running afterwards. After stopping it squid can no longer be started.

Both these packages are marked as "stable", the rest of squid/squidguard for pfsense is all "beta".
Together with problems in https://redmine.pfsense.org/issues/4088 not being fixed that render squidguard useless by effectively bypassing it the "stable" status is best changed to "junk level". This is not pfsense quality :-(
Please test changes and pay attention to the log files before committing changes. ;-)

Patch attached.

Files

squidguard-fix-directives.diff (896 Bytes) squidguard-fix-directives.diff

Patch with fix

Volker Kuhlmann, 01/19/2015 02:54 PM

Actions

Copy link

Updated by Volker Kuhlmann over 9 years ago

The problem appears to be more complex than I first thought.
In a fresh install into virtualbox with squid 2.x and squidguard squid at least starts up and the squidguard processes are running, but it still gives an error:

squid -k reconfigure
2015/01/22 10:14:14| parseConfigFile: squid.conf:65 unrecognized: 'url_rewrite_bypass'

I find it somewhat hard to believe that and old version squid would execute a new version config command as well as complain about it.

In my in-serivice pfsense system I updated the squidguard package and had some trouble, so I reinstalled both squid and squidguard and ended up with a system where squid would die with an error about the url_rewrite_program directive but run when I changed that back to the old name.

Yes it would be good to have a single squidguard package, but would it be possible to adapt to the running squid version and configure accordingly?
How much is the squid 2.x still needed or can squis 3.x now take its place?

Actions

Copy link