1. Raspberry Pi Install Python 3

Oct 23, 2015 This Tutorial uses Raspbian OS which is suitable for a B+ or 2B Raspberry Pi. Installing Cacti on Rasberry Pi. Install snmpd snmp sudo apt-get install cacti.

1. In my previous post, I detailed how to install and configure Cacti on a Raspberry Pi. In this post, I’ll show you how to do the same with SmokePing, a latency.
2. Cacti Pi – How To Install Cacti Spine on Raspberry Pi n00badmin 13 Comments In this post we will continue optimizing Cacti with How to install Cacti Spine on Raspberry Pi.

Thanks for your comment GammaRSA! Glad the guide helped! In my experience in over 10 Cacti installs on Ubuntu, Debian and OSX, I have only had to update the php.ini files manually with a local timezone once.

(see my post on Correcting Cact Timezone) I will definitely add the php supported timezones to that post as I also used it to correct that issue I saw where my cacti log and graphs were in UTC rather than EDT causing me to assume it wasn’t graphing. (due to me not looking far enough ahead to see the graphs on the Cacti ‘Graphs’ tab. Needed to change the graph filter preset to applicable UTC time.) Let me know what you utilize Cacti to monitor and how you’ve liked it this far! Love cacti so far! Mostly use it to monitor my few systems at home(Desktop PC, Server, Media center, other PI) but the main goal was for monitoring a private wireless network/hobby of mine that uses Mikrotik routers.

Raspberry Pi Install Python 3

Pi is running fine with about 10 devices with a average load of about 5-10%. But the thing that I am now concerned about is read/write on the SD card I know the more devices I add the greater the I/O is going to be on the SD card since it writes quite a huge amount to log, so now I was wondering, did you add a Flashdisk or external storage for log files to reduce the load on the SD card or do you just leave it to write on the default path on the card? Since SD cards only have a limited read/write before they fail. Hey bitwelder, Posted a reply complete with current graphs over at raspberrypi.org To answer your question, I am storing all data to the /root partition on a 16GB SD card.

I don’t forsee storage being an issue if running only Cacti as unless you are monitoring a large amount of devices and data points you should be fine as it’s very efficient. That being said I’ll likely look into adding a 500GB hard drive in the future. I highly recomment Cacti as it will provide you with endless ability to monitor, troubleshoot and report on you network and it’s elements.

I will be posting on how to install plugins and reporting tools as well to enhance Cacti’s abilities so stay tuned and let me know if I can assist with your install! Thanks for the great tutorial. It helped me install cacti on a Raspberry Pi about a year ago and I’m monitoring the Pi with itself successfully ever since. However, now I want to use the Cacti on this Pi to monitor a second Pi. What are the minimum components that need to be installed from the presented sequence onto the second Pi (which is only being monitored by the first Pi, which runs Cacti)?

So far I tried to install and configure only snmp and snmpd on the second Pi. I can add it as a host to the Cacti running on the first Pi, but it’s unable to run bash scripts as data input methods on it. Also, I can’t get info like memory usage from it. Basically I can’t get anything from it. My goal is to be able to obtain data in two ways from this second Pi: from some bashs scripts and standard SNMP-obtainable info like CPU usage, memory usage, etc. What else do I need to install/configure on this second Pi, except snmp and snmpd? I managed to get the SNMP-based graphs up and running.

I’m only having trouble getting data for those which are based on data input methods which run bash scripts. On the first Pi, which is monitoring itself, this works because I specify the script paths relative to the Cacti path, like this: /scripts/temprpi.sh. For the second Pi, on which Cacti is not installed, I tried specifying the script paths with absolute paths, like this: /soft/scripts/temprpi.sh.

Unfortunately it does not seem to work. If you know why, please let me know.

Hey Andras, What you are trying is definitely doable. Is your script successfully retrieving the data you are after from the other pi when you run it manually?

What I would suggest for best performance is that you run your bash script locally on the second pi, then scp the results to a file back on the pi running cacti. This will allow you to set up data input method that is a script that simply opens the file and presents the results to cacti. Otherwise you need to make sure that your shell script when called can reach the other pi, login, run the commandblah blah blahwhich does work but can be prone to issues.

Let me know how its going.