Setting up Munin on Ubuntu 11.10

56 Setting up Munin on Ubuntu 11.10 setting-up-munin-on-ubuntu-11-10 munin.png This post is how to setup munin 1.4.5, one munin-server and one munin-node machine. I'm going to use two Ubuntu 11.10 (Oneiric Ocelot) EC2 instances to show you how to set this up. Just skip to the next step if you already have your machines available. If you want to setup some new machines on EC2, follow from here... <table border="1" cellpadding="1" cellspacing="1" style="width: 500px;"> <tbody> <tr> <td> Name</td> <td> Instance Type</td> <td> AMI ID</td> <td> Internal IP</td> </tr> <tr> <td> munin-server</td> <td> Micro</td> <td> ami-61b28015</td> <td> 10.224.78.60</td> </tr> <tr> <td> munin-node</td> <td> Micro</td> <td> ami-61b28015</td> <td> 10.234.185.182</td> </tr> </tbody> </table> Once those are built, you'll need to SSH into them and then change the hostnames to something more friendly. So connect to the machine you want to install munin-server on... <pre> <code>root@ip-10-56-65-94:~# hostname munin-server root@ip-10-56-65-94:~# nano /etc/hostname</code></pre> Delete what exists in here and replace it with 'munin-server' <pre> <code>root@ip-10-56-65-94:~# nano /etc/hosts</code></pre> Add 'munin-server' to the end of the first line so it looks like... <pre> <code>127.0.0.1 localhost munin-server</code></pre> Once your done, reconnect your SSH session and your terminal should change to be... <pre> <code>root@munin-server:~#</code></pre> Go ahead and then do the same thing for your node machine, and call it 'munin-node' We'll first update the apt database to make sure its got the latest information, then we'll install the munin server package. Not only does this give the server the ability to draw graphs for all nodes connected, but also so it can draw graphs for itself. <pre> <code>root@munin-server:~# apt-get update root@munin-server:~# apt-get install munin</code></pre> It'll install a lot of packages so it may take a while. Once it's done installing you'll be back on the console again and we'll now start munin-node running... <pre> <code>root@munin-server:~# start munin-node munin-node start/running, process 24963</code></pre> munin-server doesn't have a process that runs on the machine, instead every 5minutes through cron it will draw the graphs it needs to. Once it's drawn those graphs they can be found (by default), in /var/cache/munin/www. So we'll need a way to display that to users. For the examples sake i'm going to use nginx on the default IP and port. You'll probably want to use a hostname instead. <pre> <code>root@munin-server:~# apt-get install nginx root@munin-server:~# nano /etc/nginx/sites-available/default</code></pre> Edit the following line in the file... <pre> <code>root /usr/share/nginx/www;</code></pre> So it reads... <pre> <code>root /var/cache/munin/www;</code></pre> Then save the file and... <pre> <code>root@munin-server:~# /etc/init.d/nginx start Starting nginx: nginx.</code></pre> If you then visit your machines public IP you should see... <img alt="" src="http://files.limi.co.uk/blog/munin-http.png" /> You can click through and see that munin has already started to graph itself, however the names aren't very useful. So let's change those... <pre> <code>root@munin-server:~# nano /etc/munin/munin.conf</code></pre> Scroll down in this file and you'll eventually see... <pre> <code>[localhost.localdomain] address 127.0.0.1 use_node_name yes</code></pre> So let's change this so something more obvious, say we have a project called 'Lightning', we'd probably do something like this... <pre> <code>[lightning;munin-server] address 127.0.0.1 use_node_name yes</code></pre> Make those changes, then save the file. On the next round 5 minutes it'll regenerate all the HTML and the graphs. And you'll see... <img alt="" src="http://files.limi.co.uk/blog/munin-lightning.png" style="width: 506px; height: 161px;" /> We now have a munin-server which is producing graphs and monitoring itself. Next step is graphing another machine. SSH into the munin-node machine, or whichever machine you wish to start graphing... <pre> <code>root@munin-node:~# apt-get update root@munin-node:~# apt-get install munin-node</code></pre> Once its finished installing we need to allow our munin-server access to this machines data. By default munin-node won't allow any IP other than its own to connect and retrieve data. So we'll need to allow through our munin-server. <pre> <code>root@munin-node:~# nano /etc/munin/munin-node.conf</code></pre> Scroll down to where you see this... <pre> <code>allow ^127\.0\.0\.1$</code></pre> And add a line beneath it for your munin-servers public IP address, for me it was... <pre> <code>allow ^10\.224\.78\.60$</code></pre> Save and close that config file and restart munin-node as it started when we installed it... <pre> <code>root@munin-node:~# restart munin-node munin-node start/running, process 26046</code></pre> We now need to go back to our munin-server and tell it to graph this new machine. <pre> <code>root@munin-server:~# nano /etc/munin/munin.conf</code></pre> Scroll down to where we had our lightning block, put this afterwards substituting your machines IP with mine... <pre> <code>[lightning;munin-node] address 10.234.185.182 use_node_name yes</code></pre> Save the file, give it 5minutes to do another drawing cycle and you'll see this... <img alt="" src="http://files.limi.co.uk/blog/munin-both-nodes.png" style="width: 506px; height: 177px;" /> Hooray! All done! :D

2011-11-10T19:10:00Z

2011-11-10T22:14:50Z

2011-11-10T23:07:56Z

55 League of Legends (LoLBase) Automatic Log Uploader league-of-legends-lolbase-automatic-log-uploader jax2.png I have an unhealthy obsession with statistics, graphs and the like. One of the games I like to play, League of Legends, has a community run statistics site called LoLBase, but they are highly dependant on people sending in their game logs to generate the data. They currently have a Windows based client to upload the files whenever the user asks it to, however I felt that this step was not really necessary. I hunted around to see if someone else had automated the process but unfortunately not, so I set about doing it myself. A couple of days later and Jax Uploader was finished! Built in C#, it will watch for you to close LoL before attempting to upload the log files (since they are written to the disk in exclusive mode until then). It's very simple and does exactly what it says on the tin. It's overall quite a nice small project as its needs a few key features such as process scanning and holding, registry reading/writing and storing user settings correctly. Very good for getting me back into C# at least. It's missing auto updating (or even knowing that it could be updated) right now, but that's something i'm going to be working on soon. Until then you can download it here... <a _mce_href="http://riotstats.com/client" href="http://riotstats.com/client">Jax Uploader</a> (v1.0.0.6) It requires the .NET framework version 4, so make sure you've got that before trying to run it (otherwise it'll probably explode in your face and you'll feel very stupid indeed!)

2011-01-07T19:10:00Z

2011-11-06T02:11:41Z

2011-11-08T22:34:44Z

1 Using RRDTool data files from a different architecture using-rrdtool-data-files-from-a-different-architecture rrdtool.png RRD data files aren't compatible across different architectures, this post will explain how you can convert them so you can utilise them on a different system. Recently I got the RRDTool addiction again and decided to start graphing pretty much anything I could think of. I have been generating some data sets on my server for this and needed to try out some new generation options but had no data on the local machine... "i'll just download the rrd files from the server then!", if only it was as easy as that! If your server is one architecture and your local machine another you'll need to convert the files before RRDTool will go near them, and the following is how you do it. I had quite a few rrd files I wanted to use, so this is a batch method to get them all done in one go. First on the server run this command in the folder containing your rrd files... <pre> <code>for i in `find -name "*.rrd"`; do rrdtool dump $i > $i.xml; done </code></pre> Then download all the XML files locally, then run this command to rebuild them... <pre> <code>for i in `find -name "*.xml"`; do rrdtool restore $i `echo $i |sed s/.xml//g`; done</code></pre> With that, all done!

2010-11-23T09:00:00Z

2011-10-25T22:54:47Z

2011-11-08T22:38:38Z

2 Installing MongoDB on Ubuntu 8.04 LTS (Hardy Heron) installing-mongodb-on-ubuntu-8-04-lts-hardy-heron mongo-db-huge-logo.png The MongoDB package maintainers don't provide dedicated aptitute packages for older Ubuntu releases, i'll show you how you can install MongoDB through packages on these unsupported versions. Today I needed to install MongoDB on one of my servers, however it still runs on 8.04 LTS, and MongoDB don't provide a dedicated apt package for that release. However you can safely use the 9.04 Jaunty source lines. It will at least save you compiling from source and maintaining it yourself. Edit your sources.list... <pre> <code>sudo nano /etc/apt/sources.list</code></pre> Add this to the bottom... <pre> <code>deb http://downloads.mongodb.org/distros/ubuntu 9.4 10gen</code></pre> Then run these commands... <pre> <code>sudo apt-key adv --keyserver keyserver.ubuntu.com --recv 7F0CEB10 sudo apt-get update</code></pre> Finally install MongoDB... <pre> <code>sudo apt-get install mongodb-stable</code></pre> Job done!

2010-10-19T09:00:00Z

2011-10-25T22:57:51Z

2011-11-08T22:40:03Z

3 mySQL gem on clean Ubuntu installation mysql-gem-on-clean-ubuntu-installation 20091016_textmate_twilight.jpg Another very quick post showing you how to fix the most common error you get when installing the mySQL gem on a clean Ubuntu installation. As I always seem to forget the package name required to install the mySQL gem and get this error... <pre> <code>ERROR: While executing gem ... (RuntimeError) ERROR: Failed to build gem native extension. Gem files will remain installed in /usr/lib/ruby/gems/1.8/gems/mysql-2.8.1 for inspection.</code></pre> The fix is as simple as... <pre> <code>sudo apt-get install libmysqlclient-dev</code></pre> Problem solved.

2010-09-06T09:00:00Z

2011-10-26T22:58:27Z

2011-11-08T22:40:39Z