Difference between revisions of "Cacti"
From Nuclear Physics Group Documentation Pages
Jump to navigationJump to search| Line 26: | Line 26: | ||
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 < | + | It was necessary to log into okra and clear the log by running |
| + | <pre>sudo -u cacti rm cacti.log | ||
| + | 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? | ||
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 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. | ||
Revision as of 14:41, 3 July 2007
A web frontend to RRDtool's[1] data storage and graphing functionality. Can be accessed at https://okra.unh.edu/cacti/.
okra:/var/www/cacti/log/cacti.log as of 6/19/2007:
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
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 Error: Unable to clear log, no write permissions.
It was necessary to log into okra and clear the log by running
sudo -u cacti rm cacti.log sudo -u cacti touch cacti.log
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?
Creating a fresh log file exposed some additional functionality in cacti. Now we can view the log file! [2] 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.
