Sunday, August 18, 2013

RPi-Monitor: Version 2.3 is available

Note: A new version of RPi-Monitor is available: Version 2.4.
All the details about the latest version of Rpi-Monitor are in RPi-Monitor overview

The version 2.3 of RPi-Monitor has been released.

If you don't know yet what RPI-Monitor do, have a look to RPi-Monitor Overview.

Photo from Flickr AttributionNoncommercialShare Alike cc-by-nc-sa by reidab

What's new in this version?

This version mainly comes with bug fixes and few optimisation.

Here is the changelog of version 2.3:
  • Add small improvement given by a feedback in RPi-Experiences blog
  • Use javascript to resize correctly shellinabox iframe even in Firefox
  • Fix issue #9: Wrong calculation of used memory
  • Fix issue #11: adding friends link missing colon


Download it from the official repository in Github:
    sudo wget -O rpimonitor_2.3-1_all.deb

Install the dependencies by executing the following command:
    sudo apt-get install librrds-perl libhttp-daemon-perl libjson-perl

Installation or upgrade can be done with the command:
    sudo dpkg -i rpimonitor_2.3-1_all.deb


RPi-Monitor is fully configurable so if the displayed information doesn't match you need, customize it.
Everything display in status pages or in statistics pages can be modified, tuned and customized to your needs.

To see how to customize it, use the command
    man rpimonitord
    man rpimonitord.conf

Man pages are also available in the wiki.

You will find some examples of customisation in RPi-Monitor articles.


Once RPi-Monitor is configured as you wished, browse http://RPiIpAddress:8888/ to access to the web interface.

Note: The graphs rendering may have strange behavior on Google-Chrome on Windows while it works fine on Linux. Internet Explorer is even not able to display statistics, it is then advised to use Firefox on Windows or better... switch to Linux! ;-). 


  1. After reboot i have 'Can not get information (dynamic.json) from RPi-Monitor server.' How i can fix it?

    1. The way you report your issue doesn't give me the possibility to help you.

      You will certainly say, Why? And what should I do to have help?

      Good question! :-) First the blog comment is not the best location to report an issue. You should create a new issue in github and write all the detail which will help me to understand your issue and/or reproduce it.

      A good report should contains:
      - The version of the software you installed (I guess 2.3 since you comment this post).
      - The name of the OS you are runnig and its version.
      - The action you made before reaching the issue (steps of the installation, file modification ...).
      - All the details you can find about the issue and all the actions you did to fix it with the detail of the result you had compared to the result you expeted (Browser cache clear, 'sudo service rpimonitord restart',...)

    2. I have the same problem.

      After reboot i get "Can not get information (dynamic.json) from RPi-Monitor server." on the "http://domain/status.html" Page.

  2. Similar problem again. :( I can't repair it with updates and upgrades.

    All Statistics are working, but Status page halted with the "dynamic.json" error message.

    This isn't browser problem, because I tested it with a lot of versions and different devices.

    I tried following commands:

    sudo apt-get update && sudo service rpimonitor update
    sudo apt-get update
    sudo apt-get upgrade
    sudo reboot

    These steps help previously under the same condition. Not now. :(

    All other services are working probably.

    How can I debug it?

    1. I did open an issue in Github with your comment - issue #12 (This will be much more efficient as comment in the blog).
      I also did answer to your comment in this github issue. Could you please have a look to it and answer my question?
      This is a very strange issue, I did reboot and customize RPi-Monitor many time and never had this issue.

    2. same bug here, but if you leave it for a while, next time you visit website it works flawlessly.

    3. Yes. I waited a day and the next day was good (no json error message), ceased to exist a few days ago an error.

      I don't understand... :O

      Unfortunately, I don't understand the management server so i can't find the cause.

  3. Hi,

    so today I had also the error message:
    "Can not get information (dynamic.json) from RPi-Monitor server."
    In my case it is in connection with the use of a proxy server in the browser. When I turned it off, RPi-Monitor works fine again.
    I might have helped with this information someone.

    1. I suppose it's just a matter of luck. I don't use proxy at all, and the error occurs from time to time. I suppose it's neither the RPI-monitor, nor json fault, but rather web browser's fault...

    2. This is very a strange bug. I never experienced it. So it is difficult to understand the root cause and to fix it...

    3. If I see this bug again (example after the next update) then I'm going to save the json output to a binary file. Ok?

    4. Ok, but to be efficient, do it on the Raspberry Pi itself with the command:

      wget -O dynamic.json

      An then add the file to comment on issue #12 on github.

  4. i would like to set the default value to "3" in the mygraph_res selector (default to 31 days), but I can't found it in the ../web/statistics.html file. How it's possible?

    1. This combobox is generated automatically by javascriptrrd.
      Having a look inside this code, let me think that if you modify the value of 'selected_rra' line 84 of file rrdFlot.js, you may acheive your goal (Note: I didn't test it on my side, please let us know if it works).

      I'll see for future version if I can add this as an option.

    2. I tried it with "var selected_rra = 3;", but no changes.

    3. I'm preparing the version 2.4.

      I did redesigned the shared memory management which may cause the issue you saw previously (and I never experienced...)

      You will be happy since I also take the opportunity to add a new parameter in the configuration page to give the possibility to select which timeline should be displayed by default.