On 30 May 2012 11:45, Alexander Sack asac@linaro.org wrote:

What's the problem we try to solve?

It can analyze squid access log, list the full statistics about times, hits, bytes, users, networks, top urls and top domains, gives us an overview of squid usage, which can help tune the squid configurations to adapt more to v.l.o tarball cache usage.

On Tue, May 29, 2012 at 11:55 AM, Spring Zhang spring.zhang@linaro.org wrote:

...

Hi,

I think we can deploy a Squid analyzer on the v.l.o, which will visualize the squid access log. Though it doesn't hit the big size tarball caching issue, but it's useful for the squid monitoring. I've deployed one on my

own

...

PC, seems cool.

http://squidanalyzer.darold.net/

-- Best wishes, Spring Zhang

---

linaro-validation mailing list linaro-validation@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-validation

-- Alexander Sack Technical Director, Linaro Platform Teams http://www.linaro.org | Open source software for ARM SoCs http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog

Spring Zhang spring.zhang@linaro.org writes:

When I deploy it, I modified the apache2 staging.validation.linaro.org.conf, only to add:

Alias /squidreport "/var/www/squidanalyzer"
<Directory /var/www/squidanalyzer>
    Options Indexes FollowSymLinks MultiViews
    AllowOverride None
    Order deny,allow
    allow from all
</Directory>

Just like the /linaro/images section, I feel strange that http://staging.validation.linaro.org/images can work, while http://staging.validation.linaro.org/squidreport only get some django warning message, Could someone point out what's wrong? You can see the error log by http://staging.validation.linaro.org/squidreport

The squidanalyzer html output is already in /var/www/squidanalyzer/.

You'll need to add SetHandler none somewhere to tell Apache that /squidreport is not handled by mod_uwsgi -- there is a similar section for /static, so copy that.

Cheers, mwh