I can't get SARG Report working

aityahiaidir

thanks for replay

my sarg.conf appear to be good ,i have this in report-dir

output_dir /usr/local/sarg-reports

and the path exist really

aityahiaidir

i have find my report, they are generated in folder

/usr/pbi/sarg-i386/local/sarg-reports

where can i edit to put the correct path, that my reports are accessible from "View Report" Tab

marcelloc

Remove /usr/local/sarg-reports and
Symlink it to pbi dir


ln -s /usr/pbi/sarg-i386/local/sarg-reports /usr/local/sarg-reports

aityahiaidir

@marcelloc:

Remove /usr/local/sarg-reports and
Symlink it to pbi dir
 
ln -s /usr/pbi/sarg-i386/local/sarg-reports /usr/local/sarg-reports

i have tried this without success, what's do you mean by "Remove /usr/local/sarg-reports"
physically remove the folder ? or is something else

doktornotor

@aityahiaidir:

physically remove the folder ?

Yeah, bit of delicate fine tuning involving HDD platters and a chisel. (Make sure to stop the relevant services first, so that the bits stop moving on the platters, otherwise the job is kinda difficult to complete.)

For unexperienced/faint-hearted ones, perhaps

rm -rf /usr/local/sarg-reports

could be an acceptable workaround.

;D ;D ;D

aityahiaidir

thank dok ;D

but this is still not working, i have always this frightful message >:(

Error: Could not find report index file.
Check and save sarg settings and try to force sarg schedule.

marcelloc

Remove the folder and then create the Symlink ;)

The results should be /usr/local/sarg-reports with your report files.

aityahiaidir

@marcelloc:

Remove the folder and then create the Symlink ;)

The results should be /usr/local/sarg-reports with your report files.

yes i do both tasks, bu it still not working, it would seem that the problem is elsewhere, it's still weird, it's a bug, it should work without resorting to all this complexity :-\

aityahiaidir

:o it is a bug, when i select site_user and user_site from report type, its work
the bug is mentioned here

http://sourceforge.net/p/sarg/bugs/154/

KOM

it should work without resorting to all this complexity

I agree, and these problems have been hanging around since before 2.1.x. I've always had to fight with Lightsquid and Sarg. Always. They should just work or be removed from the repository. I know the base system is where all the real action is, but people's opinion of the project can be heavily influenced by the experience they have with the packages. Broken packages that remain broken after 1+ years just looks bad.

marcelloc

@KOM:

They should just work or be removed from the repository.

Or instead of just watching, using and complaining, start to contributing.

Github is not that complex to use.

https://www.pfsense.org/get-involved/

aityahiaidir

I have very good knowledge in PHP, I'll try to help, but first I have to understand the operation mechanism of Sarg generating report ;)

marcelloc

@aityahiaidir:

I have very good knowledge in PHP, I'll try to help, but first I have to understand the operation mechanism of Sarg generating report ;)

Great! :)

The pbi is the biggest problem today. It "jais" the package under /usr/pbi dir but a lot of libs and package conf files still looks for it on /usr/local

All package gui files are on https://github.com/pfsense/pfsense-packages

Pfsense 2.3 will move from pbi to pkg ng, but until it happens, we have to deal with this…

KOM

Or instead of just watching, using and complaining, start to contributing.

Pardon me, but I do believe that I contribute LOTS here, for free, in my spare time. I have almost the same karma as you with 1/10th the posts. I'm not a developer or I would have fixed these frustrations long ago. The arrogant answer "Fix it yourself or shut up" may play well on Slashdot, but it is not a practical solution for most people. All I can do here is to learn the hacky workarounds to these lingering problems and then pass them along to others when they inevitably run into the same problems.

marcelloc

@KOM:

Pardon me, but I do believe that I contribute LOTS here, for free, in my spare time.

Me too. And after creating and maintaining some packages I'm spending more then free time to keep it working on version changes.
Just an example, I'm working together with Renato and cino since december to get squid working with 2.2 and pbis and it's still not finished.

@KOM:

I have almost the same karma as you with 1/10th the posts. I'm not a developer or I would have fixed these frustrations long ago. The arrogant answer "Fix it yourself or shut up" may play well on Slashdot, but it is not a practical solution for most people.

Sometimes contributing to comunity and/or the project is frustrating. Most people understands the hard work to keep it working but posts like Fix it or remove it! does sounds really arrogant to me.

And I never posted things like "Fix it yourself or shut up" as you understood.

KOM

I don't want to fight with you because I know you're a good guy and the team is under pressure right now. I understand as I work for a software company and I am deeply involved in the development process here. I want the pfSense project to be seen in the best possible light because I actually care about it. It's strange to be emotionally invested in the success of a software project, but it is what it is. In that light, I feel personally embarrassed when new users try to get these very popular and common packages running, only to be frustrated because they don't seem to work. That was the source of my Fix it or remove it comment. If it doesn't work, it should be removed so as to not tarnish the project's image. What is the point of having a broken package in the list, after all? That is all I am trying to say.

marcelloc

Ok, never mind.

BTW, I'm not from pfsense team. Just a community user like many others…

KOM

Oh, I had no idea. I thought you were an employee of ESF. My mistake.

democles9308

hello guys,

By removing the /usr/local/sarg-reports folder and creating a symlink to /usr/pbi/amd-64/local/sarg-reports, it worked for me…

Report options:
graphics where possible
remove temp files
generate main index
generate index tree
overwrite report
show downloaded volume

Reports to generate
all selected

versions
Sarg : 2.3.9 v 0.6.4
Squid : 3.4.10_2 0.2.6
squidguard-suid3 : 1.4_7 v 1.9.6

KOM

This works for 2.2:

rm -r /usr/local/sarg-reports
ln -s /usr/pbi/sarg-amd64/local/sarg-reports /usr/local/sarg-reports