English Spanish
The required RRDfile step size is '%s' but observed step is '%s' El tamaño de step RRD requerido es '%s'
The pdp_per_row of '%s' is invalid for RRA '%s' should be '%s'. Consider deleting and allowing Cacti to re-create RRDfile.
The XFF for Cacti RRA id is '%s' but should be '%s' XFF para cacti RRA id '%s' deberia ser '%s'
The number of rows for Cacti RRA id '%s' is incorrect. The number of rows are '%s' but should be '%s' Número de filas para Cacti RRA id '%s' deberia ser '%s'
The RRA '%s' missing in the existing Cacti RRDfile RRA '%s' ausentes en archivo RRD
Errors Found No se encontraron %s
Optional Tuning Recommendations Descripción del Data Source:
RRA (CF=%s, ROWS=%d, PDP_PER_ROW=%d, XFF=%1.2f) removed from RRD file RRA (CF=%s, ROWS=%d, PDP_PER_ROW=%d, XFF=%1.2f) eliminados de archivo RRD
RRA (CF=%s, ROWS=%d, PDP_PER_ROW=%d, XFF=%1.2f) adding to RRD file RRA (CF=%s, ROWS=%d, PDP_PER_ROW=%d, XFF=%1.2f) agregando a archivo RRD
Attempting to Create Graph from Non-Template Crear Aggregate desde plantilla
Attempting to Create Graph from Removed Graph Template Intentar crear un gráfico a partir de una plantilla de gráfico eliminada
Graph Not created for %s due to bad data Creación de gráfico
NOTE: Graph not added for Data Query %s and index %s due to Data Source verification failure
It is STRONGLY recommended that you enable InnoDB in any %s version greater than 5.5.3. Se recomienda que habilites InnoDB en cualquier %s versión superior a 5.1.
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. Si está utilizando Cacti Performance Booster y eligiendo un motor de almacenamiento en memoria, tiene que tener cuidado de vaciar el buffer de Boost antes que su sistema se quede sin espacio en la tabla de memoria. Esto es hecho de dos maneras, primero reduciendo el tamaño de la columna de salida al tamaño correcto. Esta columna está en las tablas poller_output y poller_output_boost. Lo segundo que puede hacer es proporcionar más memoria a las tablas de memoria. Hemos elegido arbitrariamente un valor recomendado del 10% de la memoria del sistema, pero si está usando discos SSD, o tiene un sistema más pequeño, puede ignorar esta recomendación o elegir un motor de almacenamiento diferente. Puede ver el consumo esperado de las tablas de Boost en Consola -> Utilidades de Sistema -> Ver estado de Boost.
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.
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. Cuando se utiliza el archivo_de_innodb_por_tabla, es importante establecer el formato_de_archivo_de_innodb en Barracuda. Esta configuración permitirá índices más largos, importantes para ciertas tablas de Cacti.
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. Si sus tablas tienen índices muy grandes, debe operar con Barracuda innodb_file_format y innodb_large_prefix igual a 1. Si no lo hace, es posible que los complementos no puedan crear tablas correctamente.
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. If you database is very large or remote, you can consider increasing this size. If remote, it can by as high as 80% of the systems memory. However, cautions must be taken to reduce the swapiness of the system, or to remove swap to keep the system from swapping. InnoDB contendrá tantas tablas e índices en la memoria del sistema como sea posible. Para eso, debería incrementar el valor de innodb_buffer_pool lo suficiente como para contener las tablas e índices en memoria. Comprobando el tamaño del directorio /var/lib/mysql/cacti ayudará a determinar este valor. Recomendamos 25% del total de memoria de su sistema, pero los requerimientos pueden variar dependiendo del tamaño del sistema.