Cacti (home)ForumsDocumentation

Differences

This shows you the differences between two versions of the page.

userplugin:fix64bit [2014/03/11 02:43]
Shade [fix64bit]
userplugin:fix64bit [2014/03/11 02:44] (current)
Shade [Possible Bugs?]
Line 64: Line 64:
 ===== Possible Bugs? ===== ===== Possible Bugs? =====
 Some users report problems when mass fix doesn't work. Problem is caused by the old version cacti where thold plugin doesn't allow to run everything after itself. Problem reported with cacti version 0.8.7e. Either disable thold plugin before mass fix and reenable it after or update cacti to the latest version. 0.8.7g doesn't have that problem. Some users report problems when mass fix doesn't work. Problem is caused by the old version cacti where thold plugin doesn't allow to run everything after itself. Problem reported with cacti version 0.8.7e. Either disable thold plugin before mass fix and reenable it after or update cacti to the latest version. 0.8.7g doesn't have that problem.
- 
-After switching from 32bit to 64bit counters, the graphs are having a huge traffic peak in them before returning to normal levels.  This is happening because the previous 32bit value is being compared with the new 64bit value and a gigantic number is the result.  I have worked around this by changing "setup.php" lines 316-325 adding (changes start with the line BEGIN CHANGES) :  
-<code> 
-      if($fix64bit_success) { 
-        cacti_log("Updating poller cache for ". $host_description .".".  $ds['local_data_id'], false, "FIX64BIT"); 
-        ######### BEGIN CHANGES 
-        # Problem: After switching to 64bit counters, the the counter last value is 32bit "12345" 
-        #          When we read the new 64bit number, the value to be inserted is 64bit "1234512345" 
-        #          resulting in a gigantic peak (20 Tbit in some cases) of traffic during the next poling cycle 
-        # Workaround:Insert a "NaN" into the graph now to force a counter reset 
-        # TODO:    This assumes that the graph is only 3 values large. This will error out if the rrd is expecting 
-        #          4 values. Count the foreach loop above and add a :U for each iteration. 
-        cacti_log("SM: updating ". addslashes($rrd) .".", false, "FIX64BIT"); 
-        rrdtool_execute("update ". addslashes($rrd) ." N:U:U:U ", FALSE, RRDTOOL_OUTPUT_STDOUT); 
-</code> 
- 
-Additionally, in version 0.8.8a the update_poller_cache is no longer working.  It appears the argument to update_poller_cache is now "commit" which would need to be true to commit the changes.  Right below the above lines, I have also added: 
-<code> 
-        # This was orginally: 
-        # update_poller_cache($ds['local_data_id'], false); 
-        # but it seems that update_poller_cache's second argument has changed from "truncate_performed" to "commit changes" 
-        # since we want to commit this, changing to true 
-        update_poller_cache($ds['local_data_id'], true); 
-        ######### SM END CHANGES 
-        db_execute("DELETE from plugin_fix64bit WHERE local_data_id=". $ds['local_data_id']); 
-      } 
-</code> 
- 
-I have tested the above changes on a few of our hosts and these seem to be working.  If I get time I will modify the plugin and submit the changes for a new version.  Doing the above changes should make it work in case you are struggling with the problem (but test this for your systems first - these are working for our installation) 
- 
 ===== Screenshots ===== ===== Screenshots =====
  





Personal Tools