This looks like a Bug: SquidGuard + Schedule time fail ? + blacklist update fail
-
I have Squidguard setup and in Proxy Filter, Times tab, I have added a schedule.
The problem is that the schedule FAILS to change from off time to on time (and on to off) without physically hitting the apply button EVERY TIME or by calling " /usr/local/sbin/squid -k reconfigure" from a crontab at every time crossing.
First, I don't think the crontab should be needed because the filters should handle this transition, no ?
If the crontab method needs to be done, shouldn't the schedule config take care of that ?
The problem is that this causes a temporary "hang" while everything is re-read and is rather disruptive to permitted operations. ie, imap email sessions hang and cannot read/write during the refresh time and this generates errors on the client stations.
Finally - the whole thing takes a big fat dump everytime the blacklist is updated (Shallalist updated via commandline script squidGuard_blacklist_update.sh posted on this forum)! I posted on that a couple weeks back, but got no responses. The squid -k reconfigure does NOT fix that problem. So far, only clicking the apply button will cause squidguard to re-read and resume running from emergency mode.
-
Hmm - I found the alarm messages I referred to. I see that I get these if I call reconfig during ON times, but NOT during OFF times. Thus, I believe that the filter will likely transition from ON to OFF without the crontab, but will NOT transition from OFF to ON. Maybe the bug is only with the OFF to ON setting and failure following the blacklist update.
2013-03-05 12:52:26 [42008] squidGuard ready for requests (1362509546.911)
2013-03-05 12:52:27 [42078] squidGuard 1.4 started (1362509546.484)
2013-03-05 12:52:27 [42078] Info: recalculating alarm in 4053 seconds
2013-03-05 12:52:27 [42078] squidGuard ready for requests (1362509547.003)
2013-03-05 12:52:27 [42326] squidGuard 1.4 started (1362509546.917)
2013-03-05 12:52:27 [42326] Info: recalculating alarm in 4053 seconds
2013-03-05 12:52:27 [42326] squidGuard ready for requests (1362509547.029)
2013-03-05 12:52:27 [42516] squidGuard 1.4 started (1362509546.918)
2013-03-05 12:52:27 [42516] Info: recalculating alarm in 4053 seconds
2013-03-05 12:52:27 [42516] squidGuard ready for requests (1362509547.069) -
I just confirmed - the alarm FAILS to trigger a filter update for ANY time crossing even though the SquidGuard log shows that the alarms are being calculated:
2013-03-05 14:02:43 [25967] squidGuard ready for requests (1362513763.536)
2013-03-05 14:02:43 [26036] squidGuard 1.4 started (1362513763.329)
2013-03-05 14:02:43 [26036] Info: recalculating alarm in 737 seconds
2013-03-05 14:02:43 [26036] squidGuard ready for requests (1362513763.558)
2013-03-05 14:02:43 [26132] squidGuard 1.4 started (1362513763.689)
2013-03-05 14:02:43 [26132] Info: recalculating alarm in 737 seconds
2013-03-05 14:02:43 [26132] squidGuard ready for requests (1362513763.764)VERIFIED: The change FAILS for both ON/OFF transition and OFF/ON transition.