darold
commented
8 years ago Please use latest developement code from github, this issue may have been fixed. Then if all the squidlog file content have not been parsed, just remove the SquidAnalyzer.current file and run squid-analyzer again:
wget https://github.com/darold/squidanalyzer/archive/master.zip
unzip master.zip
cd squidanalyzer-master/
perl Makefile.PL
make
sudo make install
rm /var/www/html/proxy/squidanalyzer/SquidAnalyzer.current
squid-analyzer /var/log/squid/access.log
Hi,
Not quite sure how to trouble shoot this.
Whenever the cron job runs (daily) nothing changes in the stats & running it manually gives the below error
/usr/bin/squid-analyzer -d SquidAnalyzer version 6.4 SQUID LOG HISTORY TIME: Fri Feb 12 12:05:20 2016 - HISTORY OFFSET: 59841342 Starting to parse logfile /var/log/squid/access.log. DEBUG: this file will not been parsed: /var/log/squid/access.log, size lower than expected and 1454863822.914 is lower than history time 1455239120.684. Starting to parse logfile /var/log/squid/access_proxy1.log. DEBUG: this file will not been parsed: /var/log/squid/access_proxy1.log, line after offset is older than expected: 1455238807.355 < 1455239120.684. No new log registered... DEBUG: the log statistics gathering took: 0 wallclock secs ( 0.00 usr + 0.00 sys = 0.00 CPU) Skipping HTML build. DEBUG: generating HTML output took: 0 wallclock secs ( 0.00 usr + 0.00 sys = 0.00 CPU) DEBUG: total execution time: 0 wallclock secs ( 0.00 usr + 0.00 sys = 0.00 CPU)Even when I run
squid-analyzer --rebuildI still have the same issue.The only time it works is when I comment out in the
/var/www/html/proxy/squidanalyzer/SquidAnalyzer.current.The first line in the access.log is the same as the error 1454863822.914 & the contents of the SquidAnalyzer.current are
1455239120.684 59841342I'm running CentOS Linux release 7.1.1503 (Core)
Any help would be appreciated