|
NOTE: Graph not added for Data Query %s and index %s due to Data Source verification failure
|
|
|
Key Generation Required to Use Plugin
|
|
|
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.
|
|
|
Package Key Information Not Found
|
|
|
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.
|
|
|
In order to use this Plugin, you must first run the <b><i class="deviceUp">genkey.php</i></b> script in the plugin directory. Once that is complete, you will have a public and private key used to sign your packages.
|
|
|
You have not Trusted this Package Author. If you wish to import, check the Automatically Trust Author checkbox
|
|
|
The Package %s Import 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 "%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
|
|
|
The XML files appears to be invalid. Please contact the package author
|
|
|
Check the package repository file for files that should exist and find the one that is missing
|
|
|
The XML files for the package does not exist
|
|
|
The Graph Rule has been added to the Device Rule
|
|
|
The Tree Rule has been added to the Device Rule
|
|
|
Import Package Filenames [ None selected imports all, Check to import selectively ]
|
|
|
[ In state since '%s', Uptime since '%s' ]
|
|
|
Differences
|
|
