I recently was working with XenServer 6.5 and I wanted to install a Munin Node for graphing system vitals.
Getting Yum working properly to do the install required a bit of Googling, so I wanted to document these commands in case this is helpful to anyone else.
First, you’ll need to install the EPEL repository:
yum --enablerepo=extras install epel-release
Then, you’ll need to install munin-node using both base and epel repositories.
yum --enablerepo=epel --enablerepo=base install munin-node
If you are monitoring with a remote Munin server, don’t forget to add an allow rule in /etc/munin/munin-node.conf, using your favorite text editor.
You can put it somewhere by this line:
allow ^127\.0\.0\.1$
Do not fear the regex, that rule allows connections from “127.0.0.1”. Just replace the digits and leave the other characters alone, and you can use this regex to allow any IPv4 address easily.
Now, we want to go ahead and add the Munin Node to the system startup, and start the process.
chkconfig munin-node on
service munin-node start
Don’t forget to allow incoming port 4949 TCP in your firewall if you are using a remote server to monitor the connections. Munin shouldn’t talk to unauthorized IPs, but it wouldn’t hurt to only allow connections from the Munin server on that port. That will not be covered in the scope of this guide, as I don’t know what firewall solution you are using.
Of course, the last step is to add the node in your /etc/munin/munin.conf on your monitoring server. That config would look something like this, where 123.45.67.89 is your Xen server.
[xen1.myawesomexenstuff.com] address 123.45.67.89 use_node_name yes
From here, I assume you know the drill with Munin, the server should appear on your HTML pages in 5-10 minutes. If you’re impatient, you can nudge the cron job that does this by running this:
su munin --shell /bin/sh --command munin-cron
Have fun! As always, please feel free to post any questions you have in the comments section, and I will do my best to assist.
Recent Comments