|
The "Distinguished Name" syntax, applicable for both OpenLDAP and Windows AD configurations, offers flexibility in defining user identity. For OpenLDAP, the format follows this structure: <i>"uid=<username>,ou=people,dc=domain,dc=local"</i>. Windows AD provides an alternative syntax: <i>"<username>@win2kdomain.local"</i>, commonly known as "userPrincipalName (UPN)". In this context, "<username>" represents the specific username provided during the login prompt. This is particularly pertinent when operating in "No Searching" mode, or "Require Group Membership" enabled.
|
|
|
Use a separate subfolder for each hosts RRD files. The naming of the RRDfiles will be one of the following:<br><ul><li><path_cacti>/rra/host_id/local_data_id.rrd,</li><li><path_cacti>/rra/device_id/data_query_id/local_data_id.rrd,</li><li><path_cacti>/rra/device_hash/device_id/local_data_id.rrd,</li><li><path_cacti>/rra/device_hash/device_id/data_query_id/local_data_id.rrd.</li></ul><br>You can make this change after install by running the CLI script <b>structure_rra_paths.php</b> after you make the change. NOTE: If you change Max Directories value to decrease the number of directories, or if you change the Directory Pattern, empty directories will not be pruned after you rerun the <b>structure_rra_paths.php</b> script.
|
|
|
%s Version %s or above is required for %s.
|
|
|
The Plugin in the directory '%s' does not include an install function '%s()'. This function must exist for the plugin to be installed.
|
|
|
Device '%s' successfully added to Report.
|
|
|
The pdp_per_row of '%s' is invalid for RRA '%s' should be '%s'. Consider deleting and allowing Cacti to re-create RRDfile.
|
|
|
The number of rows for Cacti RRA id '%s' is incorrect. The number of rows are '%s' but should be '%s'
|
|
|
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 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.
|
|
|
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.
|
|
|
Key Generation Required to Use Plugin
|
|
|
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
|
|
|
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.
|
|
|
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 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
|
|
|
Import Package Filenames [ None selected imports all, Check to import selectively ]
|
|
|
Import Package Templates [ None selected imports all, Check to import selectively ]
|
|
