Sarg package for pfsense
-
hi,
what pfsense version are you using?
PfSense 2.1.5 (i386)
-
Hi I am new to pfsense and i was able to figure out IP sec vpn but i can not get the reports to work nor can I get the realtime to show any dans names.
Can any one help me?
I am running the latest version of pfsense. -
Hi I am new to pfsense and i was able to figure out IP sec vpn but i can not get the reports to work nor can I get the realtime to show any dans names.
Can any one help me?
I am running the latest version of pfsense.Maybe you forgot to enable logging on squid settings.
-
Hi,
My goal with Sarg is to create Squid's daily reports. I have logging and logging rotation both enabled on Squid. My question is why Sarg doesn't show any reports for the previous day (with -d
date -v-1d +%d/%m/%Y
extra args) even though I definitely have yesterday's reports in /var/squid/logs. Is it because of Squid's own logging rotation feature? Do I need to turn it off? Or is it because of 60 minutes restriction on "Find Limit" option? I'm asking this because Sarg easily creates daily reports with -ddate +%d/%m/%Y
extra args.I'm using pfSense 2.2-RELEASE (amd64) with Sarg package 2.3.9 pkg v.0.6.4. Enabled Sarg report options are: 1, 5-10, 13-16.
Thank you!
-
I had a look in the sarg.conf file when I was looking for somthing other and I found that the configuration there only points to the actual access.log file.
access_log /var/log/squid/access.log
So I assume when squid rotates your logs then sarg cannot analyze the logs form access.log.1.
I did some research and found out that since some newer version of sarg (2.3?) - which is installed on pfsense - there is the possibility to set a "*" so sarg analyzes more logfiles.access_log /var/log/squid/access.log*
Source:
http://sourceforge.net/p/sarg/discussion/363374/thread/e2e10ffb/ -
Thanks for your reply!
I modified access_log string in sarg.conf and after that I got "file not found" error (Cannot get the modification time of input log file /var/squid/logs/access.log* (No such file or directory)). So the current version doesn't support this feature.
-
@worldfirst You can not directly edit the sarg.conf since it will be changed backed to its original configuration using the template which is the sarg.template file
-
Yes, I noticed that.
-
pfSense 2.2 (i386)
Squid 3 + SargCan't get report, error message:
Error: Could not find report index file. Check and save sarg settings and try to force sarg schedule.
Interesting thing with 2 almost same commands in console:
1. Don't work. No report in destination directory after run, i.e. dir is empty.sarg -x -f /usr/pbi/sarg-i386/etc/sarg/sarg.conf -o /usr/local/sarg-reports/
2. Works fine. Generates report in destination directory and after linking this dir to /usr/local/sarg-reports i can see reports via pfsense's GUI.
sarg -x -f /usr/pbi/sarg-i386/etc/sarg/sarg.conf -o /sarg-reports/
So, sarg works for 1st level directory but don't work for 3rd level subdir.
Any ideas how to solve problem?
-
I confirm the problem ! :(
-
Try this from the shell:
rm -r /usr/local/sarg-reports
ln -s /usr/pbi/sarg-i386/local/sarg-reports /usr/local/sarg-reportsUse ln -s /usr/pbi/sarg-amd64/local/sarg-reports /usr/local/sarg-reports if you have 64-bit build.
-
@KOM:
Try this from the shell:
rm -r /usr/local/sarg-reports
ln -s /usr/pbi/sarg-i386/local/sarg-reports /usr/local/sarg-reportsThanks! Fixes problem :)
-
My Hardware: APU1C4
only this solved the Problem:
in console
rm -rf /usr/local/sarg-reports
ln -s /usr/pbi/sarg-amd64/local/sarg-reports /usr/local/sarg-reports -
Was having a similar issue glad i found this post fixed the issue for me thanks
-
I ran the above commands to delete the directory and create the symlink to /usr/pbi/sarg-amd64/local/sarg-reports. I can see sarg generated logs under here. However on the 'View Report' tab I still get
Error: Could not find report index file. Check and save sarg settings and try to force sarg schedule.
This is on a fresh pfSense install running 2.2-RELEASE with Sarg 2.3.9 pkg v.0.6.4, Squid3 4.3.10_2 pkg 0.2.6
-
Check your other options. Sarg seems to be finicky and will not work right with the wrong combination of report options. Do you have Generate main index.html and Generate the index tree by file set to Yes, for instance?
-
Thanks KOM - checked the two options you suggested about index.html and they were selected. I then selected all and thought to try that and reduce it to my original set.
After selecting every option, I ran```
sarg -xThanks for the help.
-
for who have this error even after creating symlink /usr/local/sarg-reports to /usr/pbi/sarg-i386/local/sarg-reports /usr/local/sarg-reports or /usr/pbi/sarg-amd64/local/sarg-reports /usr/local/sarg-reports depending on the version you have installed
Error: Could not find report index file. Check and save sarg settings and try to force sarg schedule.
you certainly chosen SquidGuard as proxy server in Sarg general report setting (with Squid it's work fine).
after some debug,i noticed that Sarg is looking for SquidGuard config file in the below location
/usr/pbi/squidguard-i386/etc/squidguard/squidGuard.conf
but the conf file is located in an other folder
/usr/pbi/squidguard-i386/local/etc/squid/squidGuard.conf
for this Srag break generating index report, even if you try to change the folder in the Sarg configuration file, it will always set to the wrong one after each saving Sarg configuration.
i wil tryed to fixe that with symlink but it's dont work,
-
I too am having problems with sarg reports, but having looked at this thread I can't see an identical issue - realtime report is OK but normal reports aren't generated, in syslog I get
php-fpm[68742]: /pkg_edit.php: The command 'export LC_ALL=C && /usr/pbi/sarg-amd64/bin/sarg -d `date +%d/%m/%Y' returned exit code '2', the output was ''
In SSH I get
export: Command not found.
Sarg is 2.3.9 v0.6.4 and pfsense is 2.2.1 (amd64) ie. both the latest.
Any ideas?
thanks
-
Forget that. It was the wrong close quote mark ie should have been:
date +%d/%m/%Y
more dumb questions coming soon.
Oh and add me to the "me too" people who had to do the link command ln -s to get this to work