|
The number of rows for Cacti RRA id '%s' is incorrect. The number of rows are '%s' but should be '%s'
|
|
The RRA '%s' missing in the existing Cacti RRDfile
|
|
RRA '%s' missing in Cacti definition
|
|
Round Robin Archive
|
|
Cur Row
|
|
CDP Prep Value (0)
|
|
Errors Found
|
|
rename %s to %s
|
|
ERROR while writing XML file: %s
|
|
ERROR: RRDfile %s not writeable
|
|
RRA (CF=%s, ROWS=%d, PDP_PER_ROW=%d, XFF=%1.2f) removed from RRD file
|
|
RRA (CF=%s, ROWS=%d, PDP_PER_ROW=%d, XFF=%1.2f) adding to RRD file
|
|
Website does not have write access to %s, may be unable to create/update RRDs
|
|
Failed to open data file, poller may not have run yet
|
|
Created: %s
|
|
Graph Not created for %s due to bad data
|
|
It is STRONGLY recommended that you enable InnoDB in any %s version greater than 5.5.3.
|
|
It is recommended that you enable InnoDB in any %s version greater than 5.1.
|
|
Depending on the number of logins and use of spine data collector, %s will need many connections. The calculation for spine is: total_connections = total_processes * (total_threads + script_servers + 1), then you must leave headroom for user connections, which will change depending on the number of concurrent login accounts.
|
|
If using the Cacti Performance Booster and choosing a memory storage engine, you have to be careful to flush your Performance Booster buffer before the system runs out of memory table space. This is done two ways, first reducing the size of your output column to just the right size. This column is in the tables poller_output, and poller_output_boost. The second thing you can do is allocate more memory to memory tables. We have arbitrarily chosen a recommended value of 10%% of system memory, but if you are using SSD disk drives, or have a smaller system, you may ignore this recommendation or choose a different storage engine. You may see the expected consumption of the Performance Booster tables under Console -> System Utilities -> View Boost Status.
|
