Note: A new version of RPi-Monitor is available: Version 1.3.
All the details about the latest version of Rpi-Monitor are in RPi-Monitor overview
All the details about the latest version of Rpi-Monitor are in RPi-Monitor overview
The version 1.2 of RPi-Monitor has been released.
If you don't know yet what RPI-Monitor do, have a look to my previous post.
What's new in this version?
- Bugs fix related to uptime.
- Adding preload spinner for statistics.
- Added package status into status page.
- Prepare embedded server to work with a secure reverse proxy.
- Remove SSL embedded capability (which is not working in RPi) to reduce dependencies.
Installation
Download it from the official repository in Github:
sudo wget http://goo.gl/gURYG -O rpimonitor_1.2-1_all.deb
Install the dependencies by executing the following command:
sudo apt-get install librrds-perl libhttp-daemon-perl
Installation or upgrade can be done with the command:
sudo dpkg -i rpimonitor_1.2-1_all.deb
Usage
Browse your http://RPiIpAddress:8888/.
How package status works
Status of packages is checked when RPi-Monitor is started and once a days thanks to a cron.daily script. Package status is also automatically updated after upgrade.
After RPi-Monitor installation, it is required to restart the process or to wait until daily cron trigger. Restart can be done with the following command:
sudo service rpimonitor restart
Stay tuned ;-)
In next post we will see how to configure a reverse proxy and how to activate shellinabox.
The "libhttp-daemon-ssl-perl" required, because this is dependent on.
ReplyDeleteOr an "apt-get -f install" required.
apt-get -f install is safe. I forgot to remove the dependency from libhttp-daemon-ssl-perl when I generate the package version 1.2. It will be fixed in version 1.3.
DeleteFeature requests:
ReplyDeleteNumber of logged errors: /var/log/error
CUPS server monitoring (cups install required), logs for CUPS: /var/log/cups/ >> page_log, error_log, access_log
Syslog server monitoring (syslog install required), logs: /var/log/syslog
To analyse the log, I think that something like logwatch may do a better job.
DeleteBut this request raised an interesting point: The customization. I'm thinking to extend the configuration file capability and allow advanced user to customize the status page. This require some work and I'm not expecting to publish such a feature soon. You will then have to wait until Version 2.0.
Ok, I'm waiting! :) Because I want to replace all Munin functions to it. This is a great app, thank you!
DeleteI would like to enable auth for the 8888 port, but the Lighttpd can't bind to port, because 8888 Address already in use by something (by rpi-monitor).
ReplyDeleteMy required setting in the lighttpd.conf:
$SERVER["socket"] == ":8888" {
auth.require = ( "" =>
(
"method" => "basic",
"realm" => "Authorization please",
"require" => "valid-user"
)
)
}
The port is configurable into the conf file /etc/rpimonitord.conf.
DeleteIf you want to secure rpimonitor, I would advise to wait a little bit I've a post almost ready to be published which is explaining how to secure RPi-Monitor with SSL and add authentication by using a reverse proxy based on nginx.
I would like to use the Lighttpd authorization, but the standard method is not working. The solution may, if it could be move the web access to /var/www/rpimonitor folder, because the folder authorization is working probably on eg. phpmyadmin or others on my Rpi.
DeleteIt is possible to start rpimonitord daemon without the embedded server by adding the parameter "-n". I designed that to allow user to use a server different that the embedded one but to be honest, I never test it...
DeleteTo achieve your goal, you will need the defined the webroot to /var/www/rpimonitor. This directory will have to contains the web pages. You may need to configure other parameters so, I would advise to read the manpage and the configuration file which contains explanation of configuration.
Your question just gave me an idea for a future post: "RPi-Monitor: Advanced usage and customization".
Wow...nice WORK!
ReplyDelete