Squid upgrade to 2.2.3 full crash report
-
Ok, I put some traffic through it, seems to be logging fine. I had to stop-start Squid to get the Squidguard blacklists blocking correctly.
It's not fast but my test box is 'hardware limited'! Also it's mostly all cache misses at this point.Steve
-
is there anyway to clean complete squid directory etc to get it to install properly from scratch
-
https://doc.pfsense.org/index.php/Squid_Troubleshooting
-
i reapplied the 2.2.3 update file, it installed cron package on reboot but squid is stuck for ever
-
finally fixed it, applied the 2.2.3 update file once again and then gave it a while and finally squid started and all those errors and warnings disappeared
-
Ah, nice. :)
What hardware were you installing on?Steve
-
on the full install machine
-
Ah, yes I assumed it was a full install I just wondered about your box specs.
My test box is pretty low end, 1.3GHz Celeron, 512MB ram.Steve
-
well this is those asus eeepc with intel atom and 2GB ram
-
squid sorted out and on one another machine now squidguard wont install and this is in a remote location so lost complete access to webgui as well, i believe its something to do with package installation in general because smalelr packages install just fine but bigger ones r the issue
-
as soon as i reinstall squidguard the system goes dead and inaccessible, any fix for it?
-
Hmm, not able to replicate it yet. My box upgraded without issue including Squid3 and Squidguard with ClamAV. All running smoothely once I'd reloaded the Blacklists.
The only issue I saw was speed which is slow on my relatively ancient firebox.Steve
-
https://redmine.pfsense.org/issues/4793
after playing around for a while it seems squidguard needs to have something in target category then only it seems to avoid the crash when i tried in virtualbox but during upgrade thats already there
in general i still suffer package reinstalls on upgrade which go for ever or stuck at extracting which i guess some1 else also mentioned
https://forum.pfsense.org/index.php?topic=95674.0 -
That error looks exactly like the well discussed no-Blacklists problem. https://forum.pfsense.org/index.php?topic=90961.0
Just re-load the blacklists and Squidguard will then start. Add and enable at least one custom target to prevent it happening again.Steve
-
I don't use any blacklists and the majority of my issues is reinstall of packages after upgrade because custom targets I already have before the upgrade
-
Hmm, Squidguard not starting for some other reason then.
I would try completely removing Squidguard and reinstalling it clean with a minimal config. Make sure it runs like that before adding anything complex.
My config here on my test box is pretty basic, Squidguard with blacklists and 1 custom target.Steve
-
not starting is secondary, to get it to install is the main issue in boxes in remote locations and that gets stuck on extracting for both squid and squidguard, the smaller packages like cron install just fine. Imagine the tar program running for like more than 5mins on a intel atom and core2duo processors
-
Hmm, yes. Didn't take anything like that even on my ancient Celeron. Running from an SSD though.
Can you see what it's waiting for at the console? Try hitting Ctrl+T a few times to see what process is actually running.Steve
-
Firstly, you need to stop squid if it is running then go to squidGuard and download the blacklist again, check the enable squidGuard; save and apply. Once the your squidGuard is up the Squid will be up too if not go to status>service and click run for squid.
Good Luck
-
Hmm, yes. Didn't take anything like that even on my ancient Celeron. Running from an SSD though.
Can you see what it's waiting for at the console? Try hitting Ctrl+T a few times to see what process is actually running.Steve
the tar program
