Squid 3 and squidguard problems

dvserg · Feb 7, 2011, 2:39 PM

Deinstall (1)squidGuard/(2)squid from GUI, and type pkg_info from console. Result pkg_info pls post here.

_igor_ · Feb 7, 2011, 7:46 PM

What happens on deinstallation of squidguard:

Backing up libraries... 
Removing package...
Starting package deletion for squidGuard-1.4_2...done.
Starting package deletion for cyrus-sasl-2.1...done.
Starting package deletion for openldap-client-2.4...done.
Starting package deletion for openssl-1.0...done.
Starting package deletion for squid-2.7...done.
Starting package deletion for db3-3.3...done.
Starting package deletion for db41-4.1.25_4...done.
Starting package deletion for db3-3.3.11_3,1...done.
Starting package deletion for cyrus-sasl-2.1.23...done.
Removing squidGuard components...
Tabs items... done.
Menu items... done.
Services... done.
Loading package instructions...

The squid 2.7 here… i had installed squid3!

output of pkg_info after deinstallation:

aspell-0.60.6_3 Spelling checker with better suggestion logic than ispell
bsdinstaller-2.0.2011.0131 BSD Installer mega-package
expat-2.0.1_1 XML 1.0 parser written in C
gettext-0.18.1.1 GNU gettext package
grub-0.97_4 GRand Unified Bootloader
joe-3.7,1 Joe's Own Editor
jpeg-8_3 IJG's jpeg compression utilities
libevent-1.4.14b_1 Provides an API to execute callback functions on certain ev
libiconv-1.13.1_1 A character set conversion library
lightsquid-1.8_2 A light and fast web based squid proxy traffic analyser
p7zip-9.13 File archiver with high compression ratio
perl-5.10.1_2 Practical Extraction and Report Language
perl-5.10.1_3 Practical Extraction and Report Language
unbound-1.4.8 A validating, recursive, and caching DNS resolver
zip-3.0 Create/update ZIP files compatible with pkzip

dvserg · Feb 7, 2011, 7:53 PM

The squid 2.7 here... i had installed squid3!

Yes - it's a SG depences. Need fix.
You can try install SG before and squid 3 then.

mnemonics.ca · May 23, 2011, 8:50 PM

@dvserg:

The squid 2.7 here... i had installed squid3!
Yes - it's a SG depences. Need fix.
You can try install SG before and squid 3 then.

There is a missing units in the line that creates the .conf file for Squid3. in the squid.inc file

The line

        $conf .= 'reply_body_max_size ' . ($down_limit * 1024) . " deny all\n";

Should read

        $conf .= 'reply_body_max_size ' . ($down_limit * 1024) . " all\n";

removing the "deny". In Squid version 3 the use of allow or deny are no longer valid for this directive.

the squid.inc file can be found in the /usr/local/pkg directory

Strangely though I was also having problems when the limit was set to 0, which according to the Squid documentation should be valid, however I would always receive a "request to large" error. I added a qualifier ( != 0) so that the line is only added if required.

if ($down_limit != 0) $conf .= 'reply_body_max_size ' . ($down_limit * 1024) . " all \n";

_igor_ · May 24, 2011, 10:53 AM

kewl!

That change should go into the package. Thats that nasty error which made me scratch my head in a way my balls never like…
I took out the whole line in my config to get rid of the error at last. What i can tell is that i didn't see any failures in the function of squid3 without that line.

Thanks a lot for your finding!!!!

jimp · May 25, 2011, 6:44 PM

Here ya go:
https://github.com/bsdperimeter/pfsense-packages/commit/54c49bf2b5358b35602cae3cf6a9fead0ba886e5

mnemonics.ca · Jun 13, 2011, 3:24 AM

@jimp:

Here ya go:
https://github.com/bsdperimeter/pfsense-packages/commit/54c49bf2b5358b35602cae3cf6a9fead0ba886e5

thank you very much, just installed a new router, install the Squid3 package and viola, the Change was made. :)

Woot, I don't have to make the change manually any more.

If I find any other bugs, I will post them here.

tester_02 · Jun 13, 2011, 11:35 PM

Newb question here..
I've been searching and can't seem to find an answer on version 3 vs 2. I can see posts from over a year ago on squid-cache about the comparison. v3 was in development, and 2 was stable.
Since then, I see v3 has stable versions (3.1).
So does this not mean instead of having both 2.x and 3.0.8 in pfsense, the path forward should actually be to remove the 2.x package and move into a stable 3.x release?
Not pushing and developers (although I'd contribute to a bounty), just trying to make sense of all the versions.
Am I understanding this right?

jimp · Jun 14, 2011, 12:00 AM

You are somewhat confusing the stability of squid with the stability of the pfSense package.

We still have a squid 2.7.x package for pfSense because it works, and it works well, and there isn't a large compelling reason to rush into 3.

The squid 3 pfSense package is largely untested and most likely still needs work. Until the squid 3 package for pfSense is proven to be stable, and work well with squidGuard/HAVP/whatever, then it will likely still remain in limbo.

There are FreeBSD ports still for Squid 2.x, 3.0.x, and 3.1.x, and 2.x is still the default as far as I can see there.

tester_02 · Jun 15, 2011, 5:25 AM

Thanks for the clarification. I'm running 2.X right now and it's running with no issues. I've always been confused as to the point of the 3.x packages.