I was able to get the reports running using the following procedure.
1. Start a console/terminal session as root. (I used the shell selection from the serial port.)
2. rm -Rf /usr/pbi/sarg-amd64/local/sarg-reports/
3. Edit: /usr/local/www/sarg_frame.php
3a. Find: $dir="/usr/local/sarg-reports"
3b. Change to: $dir="/usr/pbi/sarg-amd64/local/sarg-reports"
4. From the web interface, go to Status, sarg Reports, Schedule tab, a report, and click on Force Update Now. After this, I am able to see all of the report information. (It would be a nice option to state whether the access on the report were accepted of denied.)
* * *
It appears that the 64-bit version of sarg has some of it's directories mixed up with the 32-bit version. Here are two places where the 64-bit installation appears to be referencing 32-bit directories.
1. /usr/pbi/sarg-amd64/local/etc/sarg/sarg.conf has "output_dir" set to "/usr/local/sarg-reports/" while the reports are actually generated to /usr/pbi/sarg-amd64/local/sarg-reports/. Changing the output_dir does not appear to have an effect. If it is changed, it appears to be reset if you change configuration information from the web interface.
2. The /usr/local/www/sarg_frame.php has the html reports directory hard coded incorrectly as $dir="/usr/local/sarg-reports"
* * *
I don't think this has anything to do with the report problems, but I have squid set with the Custom Option "cache deny all" from the web interface Services, Proxy Server, General tab. The test system has only the squid and sarg optional packages installed.
* * *
Can anyone tell me whether these issues should be directed to pfSense or the Sarg sourceforge page?
Dale W.