Zen

Source string Source string

76/10000 · 76

The string is read-only.

English Actions
(Custom)
Failed to open data file, poller may not have run yet
RRA Folder
Root
Unknown RRDtool Error
Attempting to Create Graph from Non-Template
Attempting to Create Graph from Removed Graph Template
Created: %s
ERROR: Whitelist Validation Failed. Check Data Input Method
Graph Not created for %s due to bad data
NOTE: Graph not added for Data Query %s and index %s due to Data Source verification failure
MySQL 5.6+ and MariaDB 10.0+ are great releases, and are very good versions to choose. Make sure you run the very latest release though which fixes a long standing low level networking issue that was causing spine many issues with reliability.
It is STRONGLY recommended that you enable InnoDB in any %s version greater than 5.5.3.
When using Cacti with languages other than English, it is important to use the utf8mb4_unicode_ci collation type as some characters take more than a single byte.
When using Cacti with languages other than English, it is important to use the utf8mb4 character set as some characters take more than a single byte.
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.
Keeping the table cache larger means less file open/close operations when using innodb_file_per_table.
With Remote polling capabilities, large amounts of data will be synced from the main server to the remote pollers. Therefore, keep this value at or above 16M.
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.
When executing subqueries, having a larger temporary table size, keep those temporary tables in memory.
When performing joins, if they are below this size, they will be kept in memory and never written to a temporary file. As this is a per connection memory allocation, care must be taken not to increase it too high. The sum of the join_buffer_size + sort_buffer_size + read_buffer_size + read_rnd_buffer_size + thread_stack + binlog_cache_size + Core MySQL/MariaDB memory should be below 80%. If the recommendation is negative, you must decrease this and or the sort_buffer_size until the recommendation fits within the allowable memory.
When using InnoDB storage it is important to keep your table spaces separate. This makes managing the tables simpler for long time users of %s. If you are running with this currently off, you can migrate to the per file storage by enabling the feature, and then running an alter statement on all InnoDB tables.
When using innodb_file_per_table, it is important to set the innodb_file_format to Barracuda. This setting will allow longer indexes important for certain Cacti tables.
If your tables have very large indexes, you must operate with the Barracuda innodb_file_format and the innodb_large_prefix equal to 1. Failure to do this may result in plugins that can not properly create tables.
InnoDB will hold as much tables and indexes in system memory as is possible. Therefore, you should make the innodb_buffer_pool large enough to hold as much of the tables and index in memory. Checking the size of the /var/lib/mysql/cacti directory will help in determining this value. We are recommending 25%% of your systems total memory, but your requirements will vary depending on your systems size.
This settings should remain ON unless your Cacti instances is running on either ZFS or FusionI/O which both have internal journaling to accomodate abrupt system crashes. However, if you have very good power, and your systems rarely go down and you have backups, turning this setting to OFF can net you almost a 50% increase in database performance.
This is where metadata is stored. If you had a lot of tables, it would be useful to increase this.
Rogue queries should not for the database to go offline to others. Kill these queries before they kill your system.
Maximum I/O performance happens when you use the O_DIRECT method to flush pages.
Setting this value to 2 means that you will flush all transactions every second rather than at commit. This allows %s to perform writing less often.

Loading…

No matching activity found.
Browse all string changes

Things to check

Multiple failing checks

Following checks are failing:

Mismatched full stop
Hindi
PHP format
Chinese (Traditional Han script)

Reset

Glossary

English English
No related strings found in the glossary.

188847 String information

Flags
php-format, read-only
Source string location
lib/utility.php:1004
String age
4 years ago
Last updated
3 months ago
Source string age
4 years ago
Translation file
locales/po/cacti.pot, string 3717