Difference between revisions of "Cacti"

From Nuclear Physics Group Documentation Pages
Jump to navigationJump to search
Line 1: Line 1:
 
A web frontend to RRDtool's[http://oss.oetiker.ch/rrdtool/doc/rrdtool.en.html] data storage and graphing functionality.  Can be accessed at ''https://okra.unh.edu/cacti/''.
 
A web frontend to RRDtool's[http://oss.oetiker.ch/rrdtool/doc/rrdtool.en.html] data storage and graphing functionality.  Can be accessed at ''https://okra.unh.edu/cacti/''.
−
== Old okra:/var/www/cacti/log/cacti.log ==
+
== Issue with log filling up ==
 +
Since cacti polls frequently, if a machine or a machine's data source is unresponsive, the log file will fill up rapidly with a lot of this:
 
<pre>06/19/2007 03:10:04 PM - CMDPHP: Poller[0] Host[3] DS[303] WARNING: Result from SNMP not valid.  Partial Result:  
 
<pre>06/19/2007 03:10:04 PM - CMDPHP: Poller[0] Host[3] DS[303] WARNING: Result from SNMP not valid.  Partial Result:  
 
06/19/2007 03:10:04 PM - CMDPHP: Poller[0] Host[3] DS[303] WARNING: Result from SNMP not valid.  Partial Result:  
 
06/19/2007 03:10:04 PM - CMDPHP: Poller[0] Host[3] DS[303] WARNING: Result from SNMP not valid.  Partial Result:  
Line 22: Line 23:
 
06/19/2007 03:10:09 PM - CMDPHP: Poller[0] Host[15] DS[363] WARNING: Result from SNMP not valid.  Partial Result:  
 
06/19/2007 03:10:09 PM - CMDPHP: Poller[0] Host[15] DS[363] WARNING: Result from SNMP not valid.  Partial Result:  
 
06/19/2007 03:10:10 PM - SYSTEM STATS: Time:8.3451 Method:cmd.php Processes:1 Threads:N/A Hosts:11 HostsPerProcess:11 DataSources:202 RRDsProcessed:106
 
06/19/2007 03:10:10 PM - SYSTEM STATS: Time:8.3451 Method:cmd.php Processes:1 Threads:N/A Hosts:11 HostsPerProcess:11 DataSources:202 RRDsProcessed:106
−
</pre>
+
</pre>If there's too much in the log file, the web interface won't load it. "Clear Cacti Log File" under "System Utilities" should take care of this, but it gives an error when I try:
−
The above is just a snippet!  That repeats every five minutes.  The size of the log is ever-increasing. "Clear Cacti Log File" under "System Utilities" is supposed to take care of this, but it gives an error when I try:
 
 
  Clear Cacti Log File
 
  Clear Cacti Log File
 
  Error: Unable to clear log, no write permissions.
 
  Error: Unable to clear log, no write permissions.
−
It was necessary to log into okra and clear the log by running
+
It is necessary to log into okra as root and clear the log by running
 
<pre>sudo -u cacti rm cacti.log
 
<pre>sudo -u cacti rm cacti.log
 
sudo -u cacti touch cacti.log</pre>
 
sudo -u cacti touch cacti.log</pre>
−
I made a copy, though, just in case.  The warnings go back as far as January 2006.  Has the issue with jalapeno, etc. been going on that long?  <font color="blue">7/4/2007:</font> The data sources that aren't working were disabled (''not'' deleted), so that the log stops filling up with garbage.
+
To reduce the noise, '''disable''' the non-functioning data sources (''don't'' delete them).
  
−
Creating a fresh log file exposed some additional functionality in cacti. Now we can view the log file! [https://okra.unh.edu/cacti/utilities.php?action=view_logfile] Apparently the old one was too big.  The big benefit of this is that now we can see which host numbers corespond to which machines, among other things, just by clicking the links.  For example, host 3 is einstein, and we can see from the log that it's sending invalid responses from one of its hard disk data sources.
+
Creating a fresh log file exposes some additional functionality in cacti. The big benefit of this is that now we can see which host numbers corespond to which machines, among other things, just by clicking the links.  This is mainly useful for finding out what data sources aren't working, so that they can be disabled.
  
 
== External Links ==
 
== External Links ==

Revision as of 15:04, 17 January 2008

A web frontend to RRDtool's[1] data storage and graphing functionality. Can be accessed at https://okra.unh.edu/cacti/.

Issue with log filling up

Since cacti polls frequently, if a machine or a machine's data source is unresponsive, the log file will fill up rapidly with a lot of this: 

06/19/2007 03:10:04 PM - CMDPHP: Poller[0] Host[3] DS[303] WARNING: Result from SNMP not valid.  Partial Result: 
06/19/2007 03:10:04 PM - CMDPHP: Poller[0] Host[3] DS[303] WARNING: Result from SNMP not valid.  Partial Result: 
06/19/2007 03:10:05 PM - CMDPHP: Poller[0] Host[6] DS[310] WARNING: Result from SNMP not valid.  Partial Result: 
06/19/2007 03:10:05 PM - CMDPHP: Poller[0] Host[6] DS[311] WARNING: Result from SNMP not valid.  Partial Result: 
06/19/2007 03:10:05 PM - CMDPHP: Poller[0] Host[6] DS[321] WARNING: Result from SNMP not valid.  Partial Result: 
06/19/2007 03:10:05 PM - CMDPHP: Poller[0] Host[6] DS[322] WARNING: Result from SNMP not valid.  Partial Result: 
06/19/2007 03:10:05 PM - CMDPHP: Poller[0] Host[6] DS[323] WARNING: Result from SNMP not valid.  Partial Result: 
06/19/2007 03:10:05 PM - CMDPHP: Poller[0] Host[6] DS[324] WARNING: Result from SNMP not valid.  Partial Result: 
06/19/2007 03:10:05 PM - CMDPHP: Poller[0] Host[6] DS[324] WARNING: Result from SNMP not valid.  Partial Result: 
06/19/2007 03:10:05 PM - CMDPHP: Poller[0] Host[6] DS[348] WARNING: Result from SNMP not valid.  Partial Result: 
06/19/2007 03:10:05 PM - CMDPHP: Poller[0] Host[6] DS[322] WARNING: Result from SNMP not valid.  Partial Result: 
06/19/2007 03:10:05 PM - CMDPHP: Poller[0] Host[6] DS[321] WARNING: Result from SNMP not valid.  Partial Result: 
06/19/2007 03:10:05 PM - CMDPHP: Poller[0] Host[6] DS[323] WARNING: Result from SNMP not valid.  Partial Result: 
06/19/2007 03:10:05 PM - CMDPHP: Poller[0] Host[6] DS[348] WARNING: Result from SNMP not valid.  Partial Result: 
06/19/2007 03:10:07 PM - CMDPHP: Poller[0] Host[13] DS[195] WARNING: Result from SNMP not valid.  Partial Result: 
06/19/2007 03:10:07 PM - CMDPHP: Poller[0] Host[13] DS[196] WARNING: Result from SNMP not valid.  Partial Result: 
06/19/2007 03:10:08 PM - CMDPHP: Poller[0] Host[13] DS[349] WARNING: Result from SNMP not valid.  Partial Result: 
06/19/2007 03:10:09 PM - CMDPHP: Poller[0] Host[13] DS[350] WARNING: Result from SNMP not valid.  Partial Result: 
06/19/2007 03:10:09 PM - CMDPHP: Poller[0] Host[15] DS[362] WARNING: Result from SNMP not valid.  Partial Result: 
06/19/2007 03:10:09 PM - CMDPHP: Poller[0] Host[15] DS[363] WARNING: Result from SNMP not valid.  Partial Result: 
06/19/2007 03:10:10 PM - SYSTEM STATS: Time:8.3451 Method:cmd.php Processes:1 Threads:N/A Hosts:11 HostsPerProcess:11 DataSources:202 RRDsProcessed:106

If there's too much in the log file, the web interface won't load it. "Clear Cacti Log File" under "System Utilities" should take care of this, but it gives an error when I try: 

Clear Cacti Log File
Error: Unable to clear log, no write permissions.

It is necessary to log into okra as root and clear the log by running 

sudo -u cacti rm cacti.log
sudo -u cacti touch cacti.log

To reduce the noise, disable the non-functioning data sources (don't delete them).

Creating a fresh log file exposes some additional functionality in cacti. The big benefit of this is that now we can see which host numbers corespond to which machines, among other things, just by clicking the links. This is mainly useful for finding out what data sources aren't working, so that they can be disabled.

External Links

Retrieved from "https://nuclear.unh.edu/wiki/index.php?title=Cacti&oldid=3403"