PfSense 2.3.2-RELEASE-p1 squidGuard 1.4_15 running at 100% CPU
-
Found it to cause high CPU usage in squid once it starts filling up
-
Found it to cause high CPU usage in squid once it starts filling up
But this is squidGuard not squid :-)
-
No idea. You might try uninstalling squidguard, blowing away its folders and then installing fresh to see if i makes any difference.
-
@KOM:
No idea. You might try uninstalling squidguard, blowing away its folders and then installing fresh to see if i makes any difference.
These are all fresh installs.
-
Then it appears that you are cursed.
-
@KOM:
Then it appears that you are cursed.
Or just maybe there is a :( BUG!! :( in squidGuard OMG how could it be.
-
Anything is possible, but I have not seen anyone complain about this same issue before. I've been using it myself for years. squidguard hasn't been updated by its authors for years either, so even if it is a bug it's not likely to ever get fixed unless someone from the community picks it up.
-
Yes we've been using it for years too with boxes installed all over the UK but it's only on these latest pfSense version boxes that we have this problem.
-
It might be worthwhile to try and figure out exactly when it starts acting up, and then check squid's access.log & squidguard's Filter GUI log and Filter log to see if there is any correlation between what's going on when the problem starts happening. Is it a particular site that triggers the behaviour? Is it a particular Target Category that triggers it? etc etc.
-
@KOM:
It might be worthwhile to try and figure out exactly when it starts acting up, and then check squid's access.log & squidguard's Filter GUI log and Filter log to see if there is any correlation between what's going on when the problem starts happening. Is it a particular site that triggers the behaviour? Is it a particular Target Category that triggers it? etc etc.
Thanks but as I said at the start, we have not seen anything that we have identified yet over 15 servers, that are suffering this, that gives a symptom other than high CPU.
We will continue to monitor the issue and if we do find some common factor a small party will be held to celebrate. -
@KOM:
Anything is possible, but I have not seen anyone complain about this same issue before. I've been using it myself for years. squidguard hasn't been updated by its authors for years either, so even if it is a bug it's not likely to ever get fixed unless someone from the community picks it up.
It does not seem to be true to say that squidGuard has not been updated for years. The last update (1.4_15 on Freshports) was on the 8th of August this year.
-
I was talking about the squidguard project itself, not just a FreeBSD port from some random person. Their site hasn't been updated in years, and the links to their dev & bug pages are broken. Then there's this from Wiki:
Version 1.4, the current stable version, was released in 2009,[2] and version 1.5 was in development as of 2010.
Finally, the changelog shows the last update being to 1.5 beta in Feb 2015, almost 2 years ago, and it was the only update since 2010.
-
Yeah, indeed. Upstream appears completely dead (HAVP was pretty much the sames story), plus the package would need rewriting from scratch. Noone fixes any bugs there in the pfSense package because you get lost in the code in 5 minutes and develop a severe headache due to the coding style.
-
Ouch. I feel like I just got my wrist slapped for even using it.
-
Done a lot more digging through log files today. Not squidGuard log files but system log files.
It's looking like the squidGuard processes are not running as result of being fired up by squid
but as a results of a cron task that performs a daily blacklist update. -
Ah found it!
The plonk who setup the crontab entries (not mentioning who as I may incriminate myself) set the minutes parameter to "*". -
Good catch. Glad to hear t's now working as expected.
