Monitoring Resource Utilization with Cacti on CentOS 5
Updated by Linode
This guide has been deprecated and is no longer being maintained.
The Linode Manager provides some basic monitoring of system resource utilization, which includes information regarding Network, CPU, and Input/Output usage over the last 24 hours and 30 days. While this basic information is helpful for monitoring your system, there are cases where more fine-grained information is useful. The simple monitoring tool Munin is capable of monitoring needs of a small group of machines. In some cases, Munin may not be flexible enough for some advanced monitoring needs.
For these kinds of deployments we encourage you to consider a tool like Cacti, which is a flexible front end for the RRDtool application. Cacti simply provides a framework and a mechanism to poll a number of sources for data regarding your systems, which can then be graphed and presented in a clear web based interface. Whereas packages like Munin provide monitoring for a specific set of metrics on systems which support the Munin plug in, Cacti provides increased freedom to monitor larger systems and more complex deployment by way of its plug in framework and web-based interface.
Before installing Cacti we assume that you have followed our getting started guide. If you are new to Linux server administration, you may be interested in our introduction to Linux concepts guide, beginner’s guide and administration basics guide.
The packages required to install Cacti are not available in the standard CentOS repositories. As a result, in order to install Cacti, we must install the “EPEL” system. EPEL, or “Extra Packages for Enterprise Linux”, is a product of the Fedora Project that attempts to provide enterprise-grade software that’s more current than what is typically available in the CentOS repositories. Enable EPEL with the following command:
rpm -Uvh http://download.fedora.redhat.com/pub/epel/5/i386/epel-release-5-4.noarch.rpm
Now, make sure your package repositories and installed programs are up to date by issuing the following commands:
Set the Timezone
Begin by setting the timezone of your server if it isn’t already set. Set your server to your timezone or to that of the bulk of your users. If you’re unsure which timezone would be best, consider using Universal Coordinated Time (or UTC, ie. Greenwich Mean Time). Keep in mind that Cacti uses the timezone set on the monitoring machine when generating its graphs. To change the time zone, you must find the proper zone file in
/usr/share/zoneinfo/ and link that file to
/etc/localtime. See the example below for common possibilities. Please note that all contents following the double hashes (eg.
##) are comments and need not be copied into your terminal.
1 2 3 4 5 6 7
ln -sf /usr/share/zoneinfo/UTC /etc/localtime ## for Universal Coordinated Time ln -sf /usr/share/zoneinfo/EST /etc/localtime ## for Eastern Standard Time ln -sf /usr/share/zoneinfo/US/Central /etc/localtime ## for American Central time (including DST) ln -sf /usr/share/zoneinfo/US/Eastern /etc/localtime ## for American Eastern (including DST)
Before installing Cacti, we must install a few basic dependencies that are critical to the installation of Cacti. Cacti uses the Simple Network Management Protocol (SNMP) to poll the devices it tracks. We’ll need to install the
snmp packages to allow Cacti to use SNMP. Cacti’s web interface requires a database, web server, and PHP to be installed. Issue the following command to install these prerequisites:
yum install net-snmp net-snmp-utils mysql-server httpd php php-mysql php-cli php-snmp rrdtool-perl wget
You will need to create a password for the
root user of your MySQL database during the installation. After the installation completes, be sure to run
mysql_secure_installation to disable some of MySQL’s less secure components. Also consider reading our MySQL installation guide for configuration recommendations.
The above command will additionally install the Apache web server. Consider our documentation of installing the Apache HTTP Server for more information regarding this server. Additionally, Cacti can function with alternate web server configurations including Apache with PHP running as a CGI process and with nginx running PHP as a FastCGI process.
SNMPD binds to all local interface by default. If you only plan on using Cacti locally to monitor your Linode, you may want to consider modifying
/etc/sysconfig/snmpd.options to limit the exposure of SNMP to the Internet at large. Uncomment the following line and append the addresses you would like the SNMP daemon to “listen” for data on as follows:
OPTIONS=”-Lsd -Lf /dev/null -p /var/run/snmpd.pid -a 192.168.169.170”
In this example SNMPD is configured to listen for data only on the LAN IP address
192.168.169.170. To limit access to SNMPD so that only local data can access the daemon, use
127.0.0.1 as the IP address. If, however, you need to receive data from machines on the Internet at large, do not append any IP addresses to this line.
We’ll create an SNMP “community” to help identify our group of devices for Cacti. In this instance, our hostname is “example.org”, so we’ve named the community “example”. The community name choice is up to the user. Add the following line to the section of
com2sec directives making sure to only grant
com2sec readonly localhost example
If you want a remote machine to connect to Cacti, replace “localhost” with the IP address of the remote machine.
You need to restart snmpd any time
/etc/snmp/snmpd.conf is modified. Run the following commands to start the SNMPD daemon and ensure that it will run following the next boot cycle:
/etc/init.d/snmpd restart chkconfig snmpd on
To install the Cacti package from the distribution software repositories, issue the following command:
yum install cacti
You will need to accept the EPEL repository key, and install all packages as recommended. Before we can begin using Cacti we must first configure MySQL. Use the following commands to start the MySQL server, ensure that it will run following boot, and enter the secure installation configuration process:
1 2 3
/etc/init.d/mysqld start chkconfig mysqld on mysql_secure_installation
Your MySQL instance does not have a root password when installed, but you will want to set a secure password, remove anonymous users, disallow root logins, and remove all of the test databases. Finally accept the invitation to reload all privilege tables and you will return to the root prompt. Issue the following command to enter the MySQL prompt and create a database and MySQL user for Cacti:
mysql -u root -p
Supply the requested password and issue the following SQL statements at the
1 2 3 4 5 6 7
CREATE DATABASE cactidb; CREATE USER 'cactiuser'@localhost IDENTIFIED BY 'c@t1u53r'; GRANT ALL PRIVILEGES ON cactidb.* TO 'cactiuser'@localhost; exit
Before we can begin to configure Cacti in the conventional manner, we must set up the database by issuing the following commands:
1 2 3 4
cd /opt/ wget http://svn.cacti.net/viewvc/cacti/tags/0.8.7e/cacti.sql?view=co mv cacti.sql\?view\=co cacti.sql mysql -u cactiuser -p cactidb < cacti.sql
Enter the password created above (e.g.
c@t1u53r) and press return. Now edit the
/etc/cacti/db.php file to include the relevant settings as in the example below:
1 2 3 4 5 6
$database_type = "mysql"; $database_default = "cactidb"; $database_hostname = "localhost"; $database_username = "cactiuser"; $database_password = "c@t1u53r"; $database_port = "3306";
Issue the following command to start Apache if you have not already:
If you would like to ensure that Apache will start following the next boot cycle, issue the following command:
chkconfig httpd on
From this point we’ll continue the configuration of Cacti through the browser. By default, the Cacti interface only accepts traffic from the local interface. Modify
/etc/httpd/conf.d/cacti.conf to allow traffic to your local machine’s IP address, as in the following example:
- <Directory /usr/share/cacti/>
- Order Deny,Allow Deny from all Allow from 220.127.116.11
18.104.22.168 is the IP address of your local Internet connection. Conversely you can copy the entire contents of the
/etc/httpd/conf.d/cacti.conf into a virtual hosting directive and provide authentication based access control. When you have completed the modification of
cacti.conf be sure to restart Apache to ensure that the settings will take effect. Issue the following command:
Visit the domain you have pointed at your Linode, or your Linode’s IP address, and add
/cacti. If you’ve inserted the contents of
/etc/httpd/conf.d/cacti.conf into a virtual host, visit the location of that virtual host, with
/cacti appended. Follow the instructions shown on each page. Make sure to select
RRDTool 1.2.x in the “RRDTool Utility Version” drop down. You should be able to continue through these pages into the login page without alteration.
At the login screen, enter
admin/admin for the username/password combination. You’ll be prompted to change your password on the next screen. At this point, Cacti is installed and ready to be configured.
At this point Cacti will contain an entry for
localhost, which we’ll need to modify. Click the “Console” tab in the top left corner, and select “Create Devices for network”. Click the “Localhost” entry to begin making the needed changes. Select the Host Template drop down and pick the “ucd/net SNMP Host”. Scroll down to SNMP Options and click the drop down box for SNMP Version, selecting “Version 1”. Enter “public” in the box for the “SNMP Community” field. The “Associated Graph Templates” section allows you to add additional graphs. Hit “Save” to keep the changes.
Click “Settings” under “Configuration” in the left menu bar and set your “SNMP Version” to “Version 1” in the drop down box. Type the name of your community for the “SNMP Community” (in this example, “example”) and save. To run the data poller to collect data for the first time, issue the following command:
Since you want Cacti to collect data automatically, we’ll use the “cron” tool to regularly poll for new data. Issue the following commands to install cron and create a new cron, or regular scheduled task:
yum install vixie-cron vim-minimal crontab -e
Now insert the following line:
/5 * * * /usr/bin/php /usr/share/cacti/poller.php > /dev/null 2>&1
To learn more about using cron to schedule tasks, consider our documentation. The above “cronjob” runs Cacti’s PHP poller every five minutes. If you need to alter the interval of the modify the cron specification and modify the “Poller” settings from within Cacti’s console.
Configuring Client Machines
This section is optional and for those looking to use Cacti to monitor additional devices. These steps are written for other CentOS-based distributions, but with modification, will work on any flavor of Linux. You will need to follow these instructions for each client machine you’d like to monitor with Cacti. Client machines need an SNMP daemon in order to serve Cacti information. First, install
snmpd on the client:
yum install net-snmp
Next we’ll need to modify the
/etc/snmp/snmpd.conf file with the name of our community. Run the following commands to backup your existing
snmpd.conf file and replace the contents with the name of your community:
mv /etc/snmp/snmpd.conf /etc/snmp/old.snmpd.conf echo "rocommunity mycommunity" > /etc/snmp/snmpd.conf
Note that the format is “rocommunity community_name”, where
community_name is the name of the community you originally used with Cacti, e.g.
example. If you’re monitoring a CentOS machine and you need to configure which interface SNMPD binds to you must edit the
/etc/sysconfig/snmpd.options file. Append any IP address needed to the end of the following line, and uncomment it by removing the
# at the beginning if needed. You should not need to edit this file.
OPTIONS=’-Lsd -Lf /dev/null -I -smux -p /var/run/snmpd.pid’
Finally, restart the SNMP daemon to ensure that your changes to these files will take effect:
Issue the following command to ensure that SNMP will restart following the next reboot cycle:
chkconfig snmpd on
At this point your machine is ready for polling. Go into the Cacti interface to add the new “Device”. Under the “Console” tab, select “New Graphs” and then “Create New Host”. Enter the pertinent information in the fields required. Make sure to select “Ping” for “Downed Device Detection”. Additionally, ensure that you’ve entered the correct community name in the “SNMP Community” field. Click the “create” button to save your configuration. On the “save successful” screen, select your newly created device and from the drop down “Choose an Action” select “Place on a Tree” and then click “go”. Hit “yes” on the next screen. On the “New Graphs” screen, you’ll be able to create several different types of graphs of your choice. Follow the on-screen instructions to add these graphs to your tree.
You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.
This guide is published under a CC BY-ND 4.0 license.