Well, I reported the issue because the sarg monthly report was never made in a pristine installation. In the research I found that the access.log file was truncated in a period of time (daily) which is not appropriate for a monthly report, nor even weekly reports. Even though sarg scripts are correctly installed and execute, the problem isn't in them a.f.a I can see, but in the amount of information available in the access.log file. If it is truncated daily, it is not possible for sarg to have enough information to make a monthly report.
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1414754 Title: /etc/logrotate.d/squid3 fails to execute sarg-reports To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1414754/+subscriptions -- Ubuntu-server-bugs mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
