English Latvian
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.
Reduce MySQL/MariaDB Memory to less than 80% of System Memory. Preserve additional Cache Memory for RRDfiles if the Database is on the same system as the RRDfiles. See Core and Client Totals below for explanation of calculation method.
The Graph Rule has been added to the Device Rule
The Tree Rule has been added to the Device Rule
[ In state since '%s', Uptime since '%s' ]
The Availability/Reachability method used to communicate with the device. In some cases, the Availability/Reachability method will be 'none', which is not uncommon for some devices
Records: %s (ds rows), Time: %s (secs), GetRows: %s (secs), ResultsCycle: %s (secs), FileAndTemplate: %s (secs), LastUpdate: %s (secs), RRDUpdate: %s (secs), Delete: %s (secs)
The Tree Rule has been removed from the Device Automation Rule
Status: <span class="deviceUp"><b>Running</b></span>, Remaining: %s (dses), CurrentRuntime: %s (secs), PrevRuntime: %s (secs), PrevProcessed: %10s (ds rows)
Replace Data Query Suggested Value Patterns
Replace Data Source and Graph Template Suggested Value Records for Data Queries. Graphs and Data Sources will take on new names after either a Data Query Reindex or by using the forced Replace Suggested Values process.
Represents the final desired Device description to be used in Cacti. The following replacement values can be used: |sysName|, |ipAddress|, |dnsName|, |dnsShortName|, |sysLocation|. The following functions can also be used: CONCAT(), SUBSTRING(), SUBSTRING_INDEX(). See the MySQL/MariaDB documentation for examples on how to use these functions. An example would be: CONCAT('|sysName|', SUBSTRING('|sysLocation|',1,3)). Take care to include quoting around the variables names when used in the supported MySQL/MariaDB function examples.
Populate Location with sysLocation
The Main Data Collector has gone to an Offline or Recovering Status
WARNING: 24 hours Poller[%d] avg. run time is %f seconds (more than %d &#37; of time limit)
Current Data Source Item: Least Squares Line Correlation Coefficient
WARNING: In last hour Poller[%d] run time %d times reached more than %d &#37; 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.
Access Points, Controllers