Cacti is all configured up and includes some plugins, which are not installed by default. It also has some additional host templates for Palo Alto firewalls, Cisco It turns out there has been some development in Smokeping after almost 4 years of quiet! New v2.7.2 is available, so I created a new Smokeping. A big strength of Cacti is its possibility to use other tools into plugins in its web interface. The plugins will be useful if you want to group some network related softwares into one interface. On the cactiusers.org website, you can find and download all the available plugins.
This virtual appliance is based on CentOS 7 and is designed to be lightweight, and stable. It has only a minimum of tools installed to make work. The OS is set to DHCP, and is installed. The username at the console, and passwords set for everything should be ‘cacti’ this will include root and mysql.With the exception of the Cacti web ui “admin” user, which has the password “Cactipw1!” (no quotes) The web UI username and password are “admin” and “Cactipw1!” (no quotes) is all configured up and includes some plugins, which are not installed by default.
It also has some additional host templates for Palo Alto firewalls, Cisco ASA Firewalls, F5 BIG-IP load balancers, and a few other things I have found useful over the years. There is not a ton of documentation, as I simply have not had time. I have put together a minimal troubleshooting section below.
If you are already familiar with Cacti it should be a breeze. If there are any questions, please leave a comment, and I can assist and update as needed.
Update 12/4/2018 It turns out there has been some development in Smokeping after almost 4 years of quiet! New v2.7.2 is available, so I created a new Smokeping update routine and added it to the script.
This will check if you have Smokeping installed, and offer to upgrade if you wish. This can be run via the same routine as the Cacti upgrade from Github below. Update I have a first working version of an automated update routine for the cacti-template you can get here. You can get the instructions on how to run it here Update Hello anyone who is listening!
The is working on the new v1.2 of Cacti which is now in it’s 2nd beta release. I am working on updating the template along with this and there are a lot of changes! I’m also building an upgrade script that can be used to upgrade the appliance with little effort. (Sorry, for now it will only work on the new v1.2.x appliance) More to follow as things progress. Update 4/2/2018. Upgraded to new Cacti and Spine v1.1.37 released 3/25/2018.
Updated all plugins, OVA is 2.2g Update 2/7/2018. Upgraded to new Cacti and Spine v1.1.34 released 2/5/2018. Updated all plugins. Upgraded CentOS. Upgraded PHP to v7 LEGACY –, OVA is 2.2g Update 1/31/2018. Upgraded to new Cacti and Spine v1.1.33 released 1/22/2018. Updated all plugins.
Misc other tweaks LEGACY –, OVA is 1.9g Update 1/5/2018. Upgraded to new Cacti and Spine v1.1.30 released 1/3/2018.
Back by popular request! Added syslog plugin.
Configured to log to new syslog db. Updated all plugins.
Added a few misc officially supported plugins. Misc other tweaks LEGACY –, OVA is 1.9g Update.
Upgraded to new Cacti and Spine v1.1.29 released. Downgraded VM hardware version to v8 for compatibility all the way down to ESX v5.0. Let me know if there are any issues but it is working in ESX v6.5 for me. I am not a smokeping expert, and I installed it into the template as an aside, the main point is Cacti. That said we can try a couple of things. To get the status of the smokeping service try systemctl status smokeping.service (to restart or stop the serive change the ‘status’ to whatever you need) This should give you some info regarding what is happening with the service. If the service is running ok, then try pasting the relevant part of the config you changed and I can do a stare and compare.
I deployed your last ova (CentOS7 Appliance with v1.1.37 Cacti) from here:, your version(?) is “UPDATE ”. It started without a hassle, than i changed the smokeping hosts and i got no graphs anymore. I copied myhost3 and changed only ip.
It had only smokepingcgi running from perl, and looked hardly saw how smokeping had to be started or debugged. I checked my changes and added space befor and after the ‘=’ for the host and title. Than i started smokeping from /etc/init and i run.
I am still wondering if there is a strict identitation on the smokeping config, or if the spaces are strictly needed. Some help on quick debugging of restarting the services cacti and smokeping would be appreciated, so i can go on configuring more hosts for my needs.
Hi Kevin, I thought I was able to extend the existing logical partition with details as below, to about 40GB. Any one with little experience with Linux, has to be ultra careful to not lose any data. So they should better snapshot the VM and / or take DB backup etc., if they will try to follow my process.
Shut down the Cacti VM. Under edit settings of VM, I then changed hard drive size from 8GB to 40GB, selecting hard disk, change provisioned size to 40GB thick. I also increased CPU to 2 vCPUs and RAM to 2GB.
Power on the Cacti VM and SSH into it using root. Vgdisplay to check existing filesystem size allocation. Fdisk /dev/sda Press p to print the existing partition table details and note it, Press d and then 2 to delete existing second partition. Press n and then p and then 2 to create new second partition. Enter to accept default for first sector and then again Enter to accept default for last sector. Press t then 2 then 8e to change system partition 2, Linux LVM, and then w to write / save.
Now physical drive has been expanded. To add this extra available size to the logical drive, lvextend -L39G /dev/mapper/centoscactitemplate-root 9. Vgdisplay and lvdisplay to verify. This shows new expanded partition size, but somehow df -h still showed me the same. I am not sure if I simply add the second drive to the OS, it can be used by Cacti.
Hi Alvaro Arbuet, With virtual machines, on CentOS7, you will not see ifcfg-eth0 file. Instead you will see ifcfg-esp0s3 and ifcfg-lo0. And if you will do ifconfig, you may not find esp0s3, instead there may be ens160 etc. To do static IP, you will create a file under /etc/sysconfig/network-scripts named ifcfg-ens160. If you will do vi ifcfg-ens160 from within network-scripts directory, it will auto create this file, which will be blank. Then press i and you will see at the bottom –insert–, so now you can type following (the Hwaddr is the mac address as you will see under cacti VM settings for the NIC, this is virtual mac assigned by ESXi or KVM etc.
TYPE=Ethernet HWADDR=00:0c:29:ec:12:34 BOOTPROTO=”static” IPADDR=172.16.30.200 PREFIX=24 DNS1=8.8.8.8 GATEWAY=172.16.30.1 NMCONTROLLED=no ONBOOT=yes Now press Esc and then press:wq! To save and exist. Technically now you are supposed to restart the service via “system restart network” but I get error.
So I just did a reboot at the command line and when it restarts, you will be pinging the new static IP. Hope this helps,.
I'm reconfigured it! root@free smokeping-2.6.9#./configure -prefix=/opt/smokeping checking build system type.
X8664-unknown-linux-gnu checking host system type. X8664-unknown-linux-gnu checking target system type.
X8664-unknown-linux-gnu checking for gcc. Gcc checking whether the C compiler works.
Yes checking for C compiler default output file name. A.out checking for suffix of executables. Checking whether we are cross compiling.
No checking for suffix of object files. O checking whether we are using the GNU C compiler. Yes checking whether gcc accepts -g. Yes checking for gcc option to accept ISO C89. None needed checking how to run the C preprocessor. Gcc -E checking for grep that handles long lines and -e.
/usr/bin/grep checking for egrep. /usr/bin/grep -E checking for ANSI C header files. Yes checking for sys/types.h. Yes checking for sys/stat.h. Yes checking for stdlib.h.
Yes checking for string.h. Yes checking for memory.h. Yes checking for strings.h. Yes checking for inttypes.h.
Yes checking for stdint.h. Yes checking for unistd.h. Yes checking minix/config.h usability. No checking minix/config.h presence. No checking for minix/config.h. No checking whether it is safe to define EXTENSIONS.
Yes checking for a BSD-compatible install. /usr/bin/install -c checking whether build environment is sane. Yes checking for a thread-safe mkdir -p. /usr/bin/mkdir -p checking for gawk.
Gawk checking whether make sets $(MAKE). Yes checking for style of include used by make. GNU checking dependency style of gcc. None checking whether to enable maintainer-specific portions of Makefiles.
No checking whether make supports nested variables. Yes checking for perl. /usr/bin/perl checking for sed. /usr/bin/sed checking for grep. (cached) /usr/bin/grep checking for echo. /usr/bin/echo checking for ln. /usr/bin/ln checking for cp.
/usr/bin/cp checking for rm. /usr/bin/rm checking for rmdir. /usr/bin/rmdir checking for mkdir. /usr/bin/mkdir checking for find. /usr/bin/find checking for sendmail. /usr/sbin/sendmail checking for gnroff.
/usr/bin/gnroff checking for gnumake. No checking for gmake. /usr/bin/gmake checking checking for gnu make availablility. /usr/bin/gmake is GNU make checking checking for perl module 'RRDs'. Ok checking checking for perl module 'FCGI'. Ok checking checking for perl module 'CGI'.
Ok checking checking for perl module 'CGI::Fast'. Ok checking checking for perl module 'Config::Grammar'. Ok checking checking for perl module 'Digest::HMACMD5'. Ok checking checking for perl module 'LWP'. Ok configure: creating./config.status config.status: creating Makefile config.status: creating bin/Makefile config.status: creating doc/Makefile config.status: creating htdocs/Makefile config.status: creating etc/Makefile config.status: creating lib/Makefile config.status: creating etc/config.dist config.status: executing depfiles commands. Ready to install Smokeping.
Settings: PERL5LIB = not set PERL = /usr/bin/perl The Smokeping Makefiles use GNU make functionality. Continue installation with /usr/bin/gmake install root@free smokeping-2.6.9#.