Squid, SquidGuard, Lightsquid status on 2.3
-
New revision of the squid package is up now for testing. If you did the chgrp work around you need to change it back to 'proxy' or reboot before upgrading the package.
-
Rebooted, updated squid package. Seems to be ok. Content filtering and virus scanning are working.
-
Thx for fixing this issue
Transparentproxy works fine now.
-
I'm noticing that between the 12-24hr mark, DNS issues return. Timing has seemed relatively inconsistent and I haven't really narrowed down any possible causes just yet.
Here's what I've observed so far:
I restarted unbound, and the issue persisted.
I disabled squid and the issue went away.
I re-enabled squid and everything stayed good.Next time, I'll check the squid logs and restart the service and report back.
-
Update on Lightsquid: The package now runs in its own web server instance using lighttpd, on its own port and with password protection. It was the smoothest way to get perl cgi support without dragging extra dependencies into base.
Note there are some subtle changes to navigation in the package.
-
There is a port issue when you click Lightsquid. I see myip:9000:7445
-
There is a port issue when you click Lightsquid. I see myip:9000:7445
I'll look into that.
-
Also nothing happens if I hit refresh buttons.
It seems like it is working but I have no data in the logs.When I: /usr/local/www/lightsquid/lightparser.pl from console, data appears.
In logs I have: /pkg_edit.php: [lightsquid] Parsing today's entries in access.log using '/usr/bin/perl /usr/local/www/lightsquid/lightparser.pl today'There has to be something wrong here…
-
Oh and one more thing..
If I manually do: /usr/bin/perl /usr/local/www/lightsquid/lightparser.pl today
This is in the crontab.Output is /usr/bin/perl: Command not found.
-
I fixed the perl path (should be /usr/local/bin/perl) and fixed the parsing of the link with the port.
-
I split the unrelated hit % posts off into their own thread and cleaned up the references here.
-
One more thing:
a) After reboot Lightsquid Web Server won
t come up b) Starting it from status_services.php wont start it
c) Saving settings in pkg_edit.php?xml=lightsquid.xml will start it.:)
-
a) After reboot Lightsquid Web Server won
t come up b) Starting it from status_services.php wont start it
c) Saving settings in pkg_edit.php?xml=lightsquid.xml will start it.I can't reproduce this, it starts every time for me. Any errors in the system log, or in /var/log/lighttpd_lightsquid.log ?
-
lightsquid :
disable ssl , now click "open lightsquid" .. url go to "https" ….
-
lightsquid :
disable ssl , now click "open lightsquid" .. url go to "https" ….
I pushed a fix for that just now.
-
a) After reboot Lightsquid Web Server won
t come up b) Starting it from status_services.php wont start it
c) Saving settings in pkg_edit.php?xml=lightsquid.xml will start it.I can't reproduce this, it starts every time for me. Any errors in the system log, or in /var/log/lighttpd_lightsquid.log ?
That`s odd.
I cleared browsers cache and now it starts correctly. -
I'm noticing that between the 12-24hr mark, DNS issues return. Timing has seemed relatively inconsistent and I haven't really narrowed down any possible causes just yet.
Here's what I've observed so far:
I restarted unbound, and the issue persisted.
I disabled squid and the issue went away.
I re-enabled squid and everything stayed good.Next time, I'll check the squid logs and restart the service and report back.
Turns out that my issues are symptomatic of packet loss with my ISP and nothing to do with pfsense.
-
i upgraded one full install box from 2.2.6 to 2.3 and after solving all the other issues with the help of jimp im left with one issue with squid. I cleared all its cache, recreated the directories and also reinstalled squid as well as got rid of the older pbi mess but when i goto the general squid config page and hit save it never comes back and then i get 504 Gateway Time-out, on the other pages atleast after a while the page comes back on hitting save.
any idea what could be causing this?
-
Start a new thread for that one, it doesn't appear to be a common issue.
-
i found one issue with squid with almost all versions of squid, suppose if u set a custom log store directory, in my case was /var/squid/log instead of the default /var/squid/logs then u goto squid realtime tab then it doesnt show any data, only setting it to the default shows data so probably that page needs to use the custom path specified
