Lightsquid package Test
-
It works again.
Great job!!
-
Great !! it's working now
-
Reinstallation-update fix bug already found, but not updated. Near time will be fixed ::)
Include files in lightsquid.xml !must have full path!
-
Now works perfect.
many thanks
Alfredo -
pfSense RC1
Lightsquid 1.7.1404 error when trying to view report
-
-
squid transparent?
Yes. Same here. Squid tranparent and also 404 - Not Found
on /lightsquid/index.cgi -
squid transparent?
Yes. Same here. Squid tranparent and also 404 - Not Found
on /lightsquid/index.cgiDo you test with non-transparent squid mode? And pls test access from browser as
'http://youpfsense/lightsquid/index.cgi'
This different with url from GUI -
I have tested it with transparent and non-transparent, with both configurations it´s a 404 - index.cgi not found…. and the report is not going on
Reinstall lightsquid package is not helpful.
Greetings
heiko -
Transparent non-transpart modes fail. 'http://youpfsense/lightsquid/index.cgi' also fails with a 404 error.
-
Transparent non-transpart modes fail. 'http://youpfsense/lightsquid/index.cgi' also fails with a 404 error.
- delete package lightsquid
- go to command prompt and execute 'pkg_delete lightsquid-1.7.1_1' command
- install lightsquid
bug exists on deletion package. Will looking for this bug..
-
for me it works, thanks a lot dvserg
-
That did the trick
Thanks for your help ;)
-
I am having a problem with this version of lightsquid on the 1.2 release versions (final not the RC's).
I updated from 1.2RC2 to RC3 and then to 1.2 final and lightsquid quit working. I tried reinstalling the package to no avail.
I get a 500 internal server error when attempting to access the index.cgi. I tried the command prompt pkg_delete but I get this:
pkg_delete lightsquid-1.7.1_1
pkg_delete: the package info for package 'pcre-6.6_1' is corrupt
pkg_delete: the package info for package 'pcre-6.6_1' is corrupt
pkg_delete: the package info for package 'pcre-6.6_1' is corrupt
pkg_delete: the package info for package 'pcre-6.6_1' is corrupt
pkg_delete: the package info for package 'pcre-6.6_1' is corrupt
pkg_delete: the package info for package 'pcre-6.6_1' is corrupt
pkg_delete: the package info for package 'pcre-6.6_1' is corruptif I install it again, I have my old configuration still and all the processed logs are still there, but it still doesn't work right.
I noticed there is some issue with one of the cgi files being compiled for the older version of perl or something? Is there a fix for 1.2 final for this?
-
I hate to dig this thread up, but I figured it would be better than starting a new one.
I'm seeing the same behavior as the original poster. When clicking “LightSquid" under "Proxy Report” The following is displayed:
LigthSquid diagnostic.
Error : report folder '/var/lightsquid/report' not contain any valid data! Please run lightparser.pl (and check 'report' folder content)
Please check config file !
–------------------------------------------------------------------------------
Variable value
$tplpatph /usr/local/www/lightsquid/tpl
$templatename base
$langpatph /usr/local/share/lightsquid/lang
$langname eng
$reportpath /var/lightsquid/report
Access to '/var/lightsquid/report' folder yes
folder content:
I've enabled logging in the proxy server, as well as "Allow users on interface" check box checked. I've also tried it with the "Transparent proxy" check box checked as well as unchecked.
Any help would be appreciated.
Thanks
-Marty
-
squid:
– Enable log option
-- Set log path as /var/squid/log
-- use squid 5-10 min (web browsing trough squid)
lightsquid
-- click Refresh_now
-- goto Lightsquid tab -
Everything's done as you suggested, yet it still gives the exact same message as I posted. What am I missing?
-
This message man only, what LS not have information in his DB. For update information to LS db need have enabling squid log and squid must create log file in '/var/squid/log'.
Can you checking /var/squid/log/access.log file for exists? -
Access.log exists in /var/squid/log/, however it's empty…shocker right!
-
I don;t know how or why, but it seems to be working perfectly now. Thanks for the help!
-Marty