Squid3 - New GUI with sync, normal and reverse proxy
-
Bumping up thread…
Anyone also experiencing the same problem here?
I have the following packages installed on pfsense 2.1.2-RELEASE:
Cron
pfBlocker
Sarg
squid3-dev
squid-Guard-squid3
System PatchesDetailed info of pfsense:
Version
2.1.2-RELEASE (amd64)
built on Thu Apr 10 05:42:13 EDT 2014
FreeBSD 8.3-RELEASE-p15CPU Type
Intel(R) Xeon(R) CPU E3-1220 V2 @ 3.10GHz
4 CPUs: 1 package(s) x 4 core(s)Temperature 29.8°C
Load average 0.10, 0.22, 0.27
CPU usage 2%Memory usage 12% of 32716 MB
SWAP usage 0% of 65536 MB
Disk usage 55% of 840G
Thanks in advance!
-
Hi all,
I had the same problem as you can read in a preavoius tread, it seams I've solved it removing the addon libraries from usr/local/lib, maybe they are in 2.1.2 or in squid don't know. -
Hi all,
I had the same problem as you can read in a preavoius tread, it seams I've solved it removing the addon libraries from usr/local/lib, maybe they are in 2.1.2 or in squid don't know.Hi!
Can you kindly give a list of libraries you safely removed?
Thanks in advance.
-
The files Marcelloc says must be added in this post:
https://forum.pfsense.org/index.php/topic,62256.0.html
I had to add these files with 2.1to have squid3dev working, don't know about 2.1.1 had it only few hours, now with 2.1.2 (speaking about i386) first added files but then removed and can confirm after 24 more hours it is working.
-
If you are running owa or active sync thru reverse proxy please reply to this thread or new topic I posted about
-why does squid3 reverse proxy require owa for activesync to function?
-how to securing owa & activesynchttps://forum.pfsense.org/index.php?topic=75991.0
-
I tried and monitored every day. Squid still turns off after a day.
I will try a pfsense reinstall soon and see if it will happen again.
-
Hi all,
Thanks to all the posts here I am successfully running squid3-dev 3.3.10 as a squid-in-the-middle SSL proxy.Before I put this in production, I'd like to put additional CAs we trust (the US Department of Defense root CAs) where squid can use them. I got the impression that importing them into the pfSense web GUI System: Certificate Authority Manager would help, but it has not made a difference so far. Do I need to put those certs somewhere else?
Thanks
-
Failed to install package.
Installation halted.
Be patient. I had also this problem some weeks ago:
https://forum.pfsense.org/index.php?topic=73919.0
I will try to install it many times in row. But seems every try it needs system reboot because once installation fails it cannot see packages.
many thnx for reply :)
Still same error. Did anyone solve it so far?
Seems i have similar issues when im trying to install any other package:/
Thnx in advance :)
-
Same Problem after upgrading to 2.1.3 amd64. Squid stops accepting connections and crashes shortly after with nothing in the log files indicating what might be the culprit. Darkstats, Arpwatch, and my ntop packages have also started to stop unexpectedly. Squid3+SquidGuard run smooth for about 24 hours and this problem occurs. I only cache large updates, and YouTube viral videos; otherwise, Squid for my environment is there to monitor usage and restrict sites. This setup is on edge appliance with three 1GB WANs that host about 2000+ public connections. It saves me around 1TB of traffic a month. When it goes down, my day does not go well. Uninstalled for now, would appreciate anyone advice what might the cause of this; furthermore, if anyone has had luck 2.1.3 + Squid-devel package on amd64.
-
I am still experiencing the same problem.
I've got the time last week to reinstall pfsense amd-64 and the same problem exists.
So my solution right now is to reboot pfsense everyday using CRON @ 1 am. That way pfsense will be alive the next working day.
I'm suspecting one of the packages installed is messing it up at 12 midnight so I do a cron to reboot the machine @ 1am daily.
To heimdal, you can install the CRON package then add a cron task:
0 1 * * * root /sbin/reboot
I hope the fix will be released soon.
-
Same issue here - squid stops working every now and then randomly, with the same log entries as shared by member below: Squid 3.1.20 pkg 2.0.7 on pfSense 2.1.3
Since upgrading, I noticed that Squid and Squidguard stops after a day.
It will work the whole day after I restarted the services but the next day, it's not working again. I then need to restart the services again then it will work for the day then stops again the next day and so on….
-
Guys, i thinki solved mine issue…
I had problems installing packages on new builds... only if SNORT is on.
So, i simply disable Snort while installing and all is fine.
Hope someone will find it useful.
-
Thanks to marcelloc!
The latest update seems to have fixed the problem of squid stopping at midnight and never restarted properly.
My pfsense machine has now been up for 5 days and counting.
-
I'm getting the error as described in this thread: http://www.squid-cache.org/mail-archive/squid-users/201406/0117.html with this version: 3.3.10 pkg 2.2.6 on pfSense 2.1.4-RELEASE (amd64).
According to the thread, it could be fixed with the 3.3.11 version. Any chance of getting an update to that version? Thanks.
Sample error log:
2014/06/27 00:42:40 kid1| parse error while reading template file: /usr/pbi/squid-amd64/etc/squid/errors/en/error-details.txt 2014/06/27 00:42:40 kid1| Unable to load default error language files. Reset to backups. 2014/06/27 00:42:40 kid1| parse error while reading template file: /usr/pbi/squid-amd64/etc/squid/errors/templates/error-details.txt 2014/06/27 00:42:40 kid1| WARNING: failed to find or read error text file error-details.txt
-
i get the same error on but squid is running for me with no other issues. I am running i386 tho
-
I actually found this while fixing another issue. The issue is fixed now and squid is running even with the error.
-
was the fix copying over some files? I've been meaning to switch over to amd64 but haven't since other installs have had issues with squid and dansguardian
-
Uh no. It's not actually fixed per the above error message. I just had an issue with my settings in the reverse proxy and that issue is fixed now. Otherwise, squid is running good with squidGuard. I think I tried dansguardian before but SSL filtering doesn't seem to work so I just opted for squidGuard.
-
I was getting the previously discussed msgget failed error and the squid service would not stay running. The issue only appeared about a week after installing lightsquid, probably when the files were set to update. I uninstalled lightsquid but that didn't seem to help. I cleared the squid cache but that didn't seem to help. The only fix I found was to reboot the box after removing lightsquid and now everything is up and running smoothly.
-
Recently we install the following:
- pfSense 2.1.5 VM
- Squid3dev 3.3.10 pkg 2.2.6
- Diladele 3.3.0.E807
We are running in transparent mode with HTTPS bumping.
Lately we have been getting icap errors:
The message is coming from Squid:
ICAP protocol error.
The system returned: [No Error]Is there anywhere I can look for more detail?
Also, while looking in the /var/squid/logs/cache.log I have been seeing many:
parse error while reading template file: /usr/pbi/squid-amd64/etc/squid/errors/templates/error-details.txt
WARNING: failed to find or read error text file error-details.txtThis file does exist:
-r–r--r-- 1 proxy proxy 7151 Nov 26 2013 error-details.txt