We strongly recommend a packaged install, as the source distribution isn’t as tested as the packaged one. The current state of the packages is so satisfactory, that even the developers use them instead.
You will have to install the
munin-node package on each node you want to monitor, and
munin on the master. Example instructions for Ubuntu / Debian:
Please note that this might not be the latest version of Munin. On Debian you have the option of enabling “backports”, which may give access to later versions of Munin.
The munin node listens on all interfaces by default, but has a restrictive access list. You need to add your master’s IP address.
Start munin-node service, or restart it if it was already started:
Add the previously configured nodes to the master configuration file:
The master service does not need to be reloaded: its configuration file will be read on the next poll.
Now that munin is up and running, you can view report pages in your browser (munin 2.0:
http://localhost/munin/ / munin 3.0:
You may have to wait up to 5 minutes until nodes gets polled and data goes live on the report pages.
If anything goes wrong, please head to the support page and check the FAQ: chances are that you will find a solution for your issues here.Read more on Munin Guide
Usually you don’t want to do that. The following lines are for completeness, and reference for packagers. The other reason would be because you want to contribute to the development of Munin, and then you should use a development install.
Get documentation from basic configuration up to becoming a munin power-user
Installation from packages, tarballs or sources
Receive help from documentation references, FAQ or real people