Project

General

Profile

Actions
Copy link

Bug #4243

closed

Last squidguard update prevents squid from starting

Added by Volker Kuhlmann almost 10 years ago. Updated almost 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
squidguard
Target version:
-
Start date:
01/19/2015
Due date:
% Done:

0%

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

Also available in: Atom PDF