|
NOTE: Graph not added for Data Query %s and index %s due to Data Source verification failure
|
|
|
If this number is negative, reduce the innodb_buffer_pool_size until the join_buffer_size turns positive, but allocate approximately from between 25%-50% of memory to the innodb_buffer_pool_size if the database is hosted on the Cacti server, or upto 80% of the systems memory if the database is separate from the Cacti web server. However, try to not go below the default of 262,144. 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 database is hosted on the Cacti web server and less if you intend to have very large RRDfiles or hundreds of thousands to millions long term.
|
|
|
If this number is negative, reduce the innodb_buffer_pool_size until the sort_buffer_size turns positive, but allocate approximately from between 25%-50% of memory to the innodb_buffer_pool_size if the database is hosted on the Cacti server, or upto 80% of the system memory if the database is separate from the Cacti web server. However, try to not go below the default setting of 2,097,152. A sort buffer performs sorts for some queries using ORDER BY or GROUP BY. Configuring sort_buffer_size decides how much memory will be allocated for sort queries. The sort_buffer_size may need to be adjusted from the default if the workload requires a significant number of sort queries. The sort_buffer_size is defined on a per-session variable. Use the same equation as that of the join_buffer_size to determine the per connection possible memory.
|
|
|
Key Generation Required to Use Plugin
|
|
|
You have not Trusted this Package Author. If you wish to import, check the Automatically Trust Author checkbox
|
|
|
See the cacti.log for more information. It could be that you had either an API Key error or the package was tamered with, or the location is not available.
|
|
|
The package "%s" download or validation failed
|
|
|
See the cacti.log for more information. It could be that you had either an API Key error or the package was tamered with, or the location is not available
|
|
|
The package download or validation failed
|
|
|
Check the package repository file for files that should exist and find the one that is missing
|
|
|
If checked, Cacti will automatically Trust the Signer for this and any future Packages by that author.
|
|
|
Replace Data Source and Graph Template Suggested Value Records. Graphs and Data Sources will take on new names after either a Data Query Reindex or by using the forced Replace Suggested Values process.
|
|
|
WARNING: 24 hours Poller[%d] avg. run time is %f seconds (more than %d % of time limit)
|
|
|
WARNING: In last hour Poller[%d] run time %d times reached more than %d % of time limit
|
|
|
In Cases where you need to perform debugging for a single Data Collector Only, you can change it's log level here.
|
|
|
Provides a way to disable verification of the server's SSL certificate Common Name against the server's hostname when connecting. This verification is enabled by default.
|
|
|
RRD check is disabled, please enable in Configuration -> Settings -> Data
|
|
|
Changing Permission Model Warning
|
|
|
Changing Permission Model will alter a users effective Graph permissions.
|
|
|
After you change the Graph Permission Model you should audit your Users and User Groups Effective Graph permission to ensure that you still have adequate control of your Graphs. NOTE: If you want to restrict all Graphs at the Device or Graph Template Graph Permission Model, the default Graph Policy should be set to 'Deny'.
|
|