I can confirm I have see this a well. Started with the 2.2.x series.
Happens with almost every reboot or upgrade of package. re-downloading
the blacklist fixes it until the next cycle.
On 11/11/2015 12:08 AM, Volker Kuhlmann wrote:
After squid and squidguard updates it is neccessary to re-download the
blacklist before attempting to restart squid/guard. Done.
When applying the squidguard config
https://xxx/pkg_edit.php?xml=squidguard.xml&id=0
An error results and squid isn't running.
No change after several iterations of squid and squidguard config
saving, followed by a reboot.
cache.log contains
2015-11-11 17:59:23 [27438] logfile not allowed in acl other than default
2015-11-11 17:59:23 [27438] logfile not allowed in acl other than default
2015-11-11 17:59:23 [27438] logfile not allowed in acl other than default
2015-11-11 17:59:23 [27438] logfile not allowed in acl other than default
2015-11-11 17:59:23 [27438] logfile not allowed in acl other than default
This is a long-standing bug of an incorrect squidguard config being
generated.
Attempting to start squid succeeds.
Saving the squidguard config (which recreates SG config and restarts
squid) fails.
Attempting to start squid succeeds.
Saving the squidguard config fails.
Starting squidguard fails.
Starting squid succeeds.
Not really good :-((
Volker
_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
