Edit: Some additional configuration turned out to be necessary to achieve stable operation, see this post.
The built-in monitoring of the RN312 is ok for basic purposes, but still pretty limited.
I am really heading towards a Zabbix setup (I think at least, having tested it in a VM environment it seems pretty nice), but there is A LOT of configuration needed to get Zabbix up and running. That’s actually a downside of Zabbix: In order to get simple things like alarm/notification emails set up, you need to do a lot of configuration in the web UI. Yes, it is very flexible, but also quite demanding.
Setup was pretty painless, but some extra work was needed (as compared to the installation instructions). Good instructions for Debian can be found here though. Worth noting that I decided to install packages from a repository, rather than as a downloaded package, or from source.
- Add the needed sources. Good instructions here. I stored the repo key in /root, there is probably a better place for it… Btw you need to do the following as root, so run “su” to change user.
Use your editor of choice to edit /etc/apt/sources.list so it looks something like this (the last two lines are what we are after here):
deb http://apt.readynas.com/packages/readynasos 6.0.8 updates apps main deb http://mirrors.kernel.org/debian wheezy main # Monitorix packages deb http://apt.izzysoft.de/ubuntu generic universe
- Get the key for the repository. This is needed in order to install the package from the repo.
cd wget http://apt.izzysoft.de/izzysoft.asc apt-key add izzysoft.asc
apt-get update apt-get install monitorix
- In spite of what the Monitorix install instruction says about the system running out of the box, I had to do some additional changes:As Monitorix will run on the RN312, but you will access it from some other computer, you need to tell Apache2 that this is ok. Edit /etc/apache2/conf.d/monitorix.conf so that it looks like this (only the Directory section show to keep it short):
<Directory /usr/share/monitorix/cgi/> DirectoryIndex monitorix.cgi Options ExecCGI Order Deny,Allow Deny from all Allow from all </Directory>
Yes…. You should probably not allow anyone to access via insecure http… Better option might be to use specific IP numbers, instead of all. I.e. “Allow from w.x.y.z” instead of “Allow from all”.
Edit /etc/monitorix.conf. By default Monitorix’ own http server is enabled, but it will clash with the Apache2 server that is already running on the RN312. We need to disable Monitorix’ http server, and while we are at it, you might also want to change the hostname, as well as decide which graphs to show.
The first part of my /etc/monitorix.conf looks like this
Finally, for some reason the rights to Monitorix’ imgs directory were incorrect out-of-the-box. Fix it:
cd /usr/share/monitorix/ ls -la chown -R admin:admin imgs ls -la
- Almost there… We just need to restart Apache2 and Monitorix to make the new configuration take effect:
service apache2 reload service monitorix restart
Directing your browser to http://<IP of your NAS>/monitorix should now give you a screen like this:
Clicking ok should now take you to a page looking similar to this one (exactly what is shown will depend on the settings you did in /etc/monitorix.conf):
All in all – very nice! 🙂