Squidguard-squid3-1.4_4-amd64 failed on pfsense 2.2

doktornotor

That's awesome. Very useful to know you get the same unknown error…

Fesoj

I ran into the same problem.

The log files showed that there was an error evaluating /tmp/rules.test.packages.

It seems as if this file does not get written correctly.

Cino

maybe post the output of your logs??? system, squidguard and squid logs?

this may help for now until squidguard can be corrected as I feel this is the issue..


ln -s /usr/pbi/squidguard-devel-amd64/local/lib/libldap-2.4.so.8 /usr/local/lib/libldap-2.4.so.8
ln -s /usr/pbi/squidguard-devel-amd64/local/lib/libldap-2.4.so.8 /lib/libldap-2.4.so.8
ln -s /usr/pbi/squidguard-devel-amd64/local/lib/libdb-4.6.so.0 /usr/local/lib/libdb-4.6.so.0
ln -s /usr/pbi/squidguard-devel-amd64/local/lib/libdb-4.6.so.0 /usr/lib/libdb-4.6.so.0

marcelloc

Better send it as a pull request, just like we did with icap on squid3…

Cino

true! I submitted a bug report around the same time but no has looked at it. I'lltake a look at squidguard.inc but I think this needs to fix in the pbi build and the pbi's are missing the dig digital signature

marcelloc

Just for feedback.

I've tested squidguard-devel without symlinks and ldap as well. It's working fine togheter with squid3 and clamav integration.

https://forum.pfsense.org/index.php?topic=87424.msg480232#msg480232

Cino

Have you rebooted your box? On initial install, everything seems to be fine.. Its when I reboot when the lib issues pop up, and I have to create the lnks to resolve it.

marcelloc

Didn't tried a reboot yet.

Pistolero

Hi Marcello,

Is the clamav integration in squid working in 2.2 x64? Or does c-icap still crash?

thanx!

Pistolero.

@marcelloc:

Just for feedback.

I've tested squidguard-devel without symlinks and ldap as well. It's working fine togheter with squid3 and clamav integration.

https://forum.pfsense.org/index.php?topic=87424.msg480232#msg480232

marcelloc

@Pistolero:

Is the clamav integration in squid working in 2.2 x64? Or does c-icap still crash?

working.

https://forum.pfsense.org/index.php?topic=87424.msg480232#msg480232

jimp

squidGuard-squid3 should be OK now. It installed fine for me in a VM today after I rebuilt the PBI.

Cino

@jimp:

squidGuard-squid3 should be OK now. It installed fine for me in a VM today after I rebuilt the PBI.

Were you also able to rebuild SquidGuard-Dev PBIs? I noticed some changes in github but didn't see any new binaries.

jimp

No the build failed and I didn't have time to investigate.

Cino

:-\ If there is anything I could assist with, I'll be glad to help..

Antonio_Grande

Subj does not start after reboot until you do not update the blacklist :-\

bioperiodik

Hello,

I have the same Problem with pfSense and Squidguard.

I installed pfSense2.2 with FreeBDS (amd64), squid (2.7.9 pkg v. 4.3.6), squidGuard-devel (1.5_1beta pkg v. 1.5.6) and Captive Protal Plus in VMware Player.
Yesterday everything worked fine , but today the squid and squidGuard service keep crashing all the time.

I updates the Blacklist, and then everything was fine again.

Is this a normal behavior of this package? How can i fix this?

Im not so skilled with linux, would be grade if anyone can help me :-)

cplmayo

@bioperiodik:

Hello,

I have the same Problem with pfSense and Squidguard.

I installed pfSense2.2 with FreeBDS (amd64), squid (2.7.9 pkg v. 4.3.6), squidGuard-devel (1.5_1beta pkg v. 1.5.6) and Captive Protal Plus in VMware Player.
Yesterday everything worked fine , but today the squid and squidGuard service keep crashing all the time.

I updates the Blacklist, and then everything was fine again.

Is this a normal behavior of this package? How can i fix this?

Im not so skilled with linux, would be grade if anyone can help me :-)

I am having the same issue on my box.

Has this been resolved?

marcelloc

Try squid3 + squidguard 3

mir

It seems the cause for the problem is that the blacklist db is either removed or corrupted when restarting the box. Proof: The blacklist tab shows no sign of a downloaded blacklist and a blacklist database. Since squidguard is configured to use a blacklist it will fail which subsequently also causes squid to fail since the url_rewriter fails.

foresthus

Hi folks,

I tried to get squid3 and squidguard for squid3 to function on a 64Bit-system. I updated from 2.1.5 to 2.2.1. Some packages did not update at all like squi3, squidguard for squid3 and pfblocker (because the package has now a new name = pfblockerng). That was still ok for me. So I treid to install pfblockerng at first. The installtaion and the configuration where successful and to me is this package realy good.

Then I tried to install squid3 without squidguard. All OK so far. I was able to start both addons clamav and icap. Then came the test, if squid3 and squidguard for squid3 are operational. This failed. Squid3 stopped and squidguard never started. Then I read in the forum to tr squidguard-devel instead. I did so, but this did not function at all.

Disapointed about thes packages I deinstalled both packages. After a reboot, I installed squid2 and squidguard for squid2. Everthing was OK and squid with squidguard are OK now. The blacklist were still there after a reboot and the system ist working now.

Now a question to those how are responsible for the package squi3 and its squidguard: When will there be a solution for this problem and is it possible not to implement clamav and icap? I suggest that this should be a separate package.

Hope to see a new package as soon as possible.

thnx a lot.

I TRIED THIS ON THE LATEST pfsense 2.2.1

Sorry for this overhasty message that squid2 with squidguard works fine on pfsense 2.2.1.

That is not realy true. Some things work and some do not. I tried it with several clients and some had connection and some did not. What is the reason. I don not know, but what I know is that not all "Proxy filter SquidGuard: Groups Access Control List (ACL)" work. If you try to configure more than 2 acls you are able to save them, but those clients have no internet at all.

example:
First 192.168.1.60-192.168.1.69 ist set to client1 = These IPs are able to surf.
Second 192.168.1.70-192.168.1.79 ist set to client1 = These IPs are able to surf.
… everyting follows has no connection.
fith 192.168.1.90-192.168.1.99 ist set to client1 = These IPs are able to surf.

Therefor I guess, there ist still work to do. I am going back to the older release pfsense 2.1.5.
:'( :-\ >:(