This is probably going to be one of those of course! answers, but I've spent all night looking up tutorials and FAQs on Munin and can't seem to find the answer.
I have Munin installed, and I'm trying to serve the page that shows the graphs using Apache.
I've just installed Munin for the first time in around twelve months, and I've hit a familiar error.
I remember from last year that there is an oddity where Munin wants to keep its html files in /var/cache/munin/www, rather than the usual /var/www/munin.
Introduction
If you want to use Varnish with Virtual Hosts, you may face the problem of Varnish showing only the default site and not all other virtual sites.
Do not try to fix it tweaking Varnish, as this is something you need to solve in Apache or Nginx configuration, depending on which of them is behind varnish.
In this post I'll show you how to configure both of them Nginx and Apache.
How to c
Hi everyone
I'm currently trying to install munin to monitor my server loads etc but i'm having a few difficulties getting it running
this is what ive done so far
Installed Munin and Munin node
I've set the directory for munin to send HTML outputs to
home/username/public_html/munin and also given munin ownership of this directory
On Debian I have Varnish cache in front of apache and get 503 error when I try to get urls which are rarely fetched.
I'm running Apache2 and Munin on Ubuntu 12.04. All of my Munin graphs are showing up fine (cpu, memory, etc.), except for the Apache graphs.
The Apache graphs were working at one point, which you can see from this screenshot showing data from a few months ago: http://i.imgur.com/uk3aAnJ.png.
Putting Varnish In Front Of Apache On Ubuntu/Debian
Varnish is an open source "web accelerator" which you can use to
speed up your website. It can cache certain static elements, such as images or javascript
but you can also use it for other purposes such as Loadbalancing or some
additional security.
I'm trying to add a node to an existing munin master (which I didn't setup but which seems to be working fine as it shows graphs for 8 existing nodes) and I'm having some troubles.
I have Nginx listening on port 443 as an SSL terminator, and proxying unencrypted traffic to Varnish on the same server. Varnish 3 is handling this traffic, and traffic coming in directly on port 80. All traffic is passed, unencrypted, to Apache instances on other servers in the cluster.