Translation

English
Graph Not created for %s due to bad data
4/400 · 40
English Chinese (Simplified)
ERROR while writing XML file: %s 写入XML 文件时出错: %s
ERROR: RRDfile %s not writeable ERROR: RRD 文件 %s 不可写入
Error while parsing the XML of RRDtool dump 解析RRDtool 转储的XML 时出错
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) 从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)添加到RRD 文件
Website does not have write access to %s, may be unable to create/update RRDs 网站没有 %s 的写入权限,可能无法创建/更新RRD
(Custom) (自定义)
Failed to open data file, poller may not have run yet 无法打开数据文件,poller 可能尚未运行
RRA Folder RRA 文件夹
Root 根目录
Unknown RRDtool Error 未知的RRDtool 错误
Attempting to Create Graph from Non-Template 从模板创建聚合
Attempting to Create Graph from Removed Graph Template 尝试从已删除的图形模板创建图形
Created: %s 已创建图形: %s
ERROR: Whitelist Validation Failed. Check Data Input Method ERROR: 白名单验证失败.请检查数据输入方法
Graph Not created for %s due to bad data 图形创建
NOTE: Graph not added for Data Query %s and index %s due to Data Source verification failure
MySQL 5.6+ and MariaDB 10.0+ are great releases, and are very good versions to choose. Make sure you run the very latest release though which fixes a long standing low level networking issue that was causing spine many issues with reliability. MySQL 5.6+ 和MariaDB 10.0+ 都是很棒的版本,并且是非常好的可供选择的版本.请确保运行的是最新的版本,它们修复了一个长期存在的底层网络问题,那个问题会导致spine 遭遇很多可靠性问题.
It is STRONGLY recommended that you enable InnoDB in any %s version greater than 5.5.3. 建议在任何版本大于5.1的 %s 中启用InnoDB.
When using Cacti with languages other than English, it is important to use the utf8mb4_unicode_ci collation type as some characters take more than a single byte. 当Cacti 用于非英语的其它语言环境时, 数据库使用utf8mb4_general_ci 排序规则非常重要,因为某些字符的值不止一个字节.
When using Cacti with languages other than English, it is important to use the utf8mb4 character set as some characters take more than a single byte. 当Cacti 用于非英语的其它语言环境时,数据库使用utf8mb4 字符集非常重要,因为某些字符会使用不止一个字节.
It is recommended that you enable InnoDB in any %s version greater than 5.1. 建议在任何版本大于5.1的 %s 中启用InnoDB.
Depending on the number of logins and use of spine data collector, %s will need many connections. The calculation for spine is: total_connections = total_processes * (total_threads + script_servers + 1), then you must leave headroom for user connections, which will change depending on the number of concurrent login accounts. 根据登录次数和使用spine 数据采集器, %s 将需要许多连接. spine的计算是:total_connections = total_processes *(total_threads + script_servers + 1),那么您必须留下用于用户连接的空间,这取决于并发登录的帐户数.
Keeping the table cache larger means less file open/close operations when using innodb_file_per_table. 使用innodb_file_per_table 时,使用更大的表缓存意味着更少的文件打开/关闭操作.
With Remote polling capabilities, large amounts of data will be synced from the main server to the remote pollers. Therefore, keep this value at or above 16M. 通过远程poller 功能,大量数据将从主服务器同步到远程poller. 因此,请将此值保持在16M 或以上.
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. 如果使用Cacti Performance Booster并选择内存存储引擎，则在系统内存表空间用完之前，必须小心刷新Performance Booster缓冲区。 这通过两种方式完成，首先将输出列的大小减小到合适的大小。 此列位于表poller_output和poller_output_boost中。 你可以做的第二件事是分配更多的内存到内存表中。 我们已经任意选择了系统内存10％的建议值，但是如果您使用的是SSD磁盘驱动器，或者系统较小，则可以忽略此建议或选择其他存储引擎。 您可以在Console - > System Utilities - > View Boost Status下看到Performance Booster表的预期消耗量。
When executing subqueries, having a larger temporary table size, keep those temporary tables in memory. 执行具有较大临时表大小的子查询时,请将这些临时表保存在内存中.
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 storage it is important to keep your table spaces separate. This makes managing the tables simpler for long time users of %s. If you are running with this currently off, you can migrate to the per file storage by enabling the feature, and then running an alter statement on all InnoDB tables. 使用InnoDB 存储引擎时,保持表空间的独立性很重要. 对于 %s 的长期用户,表管理会变得更简单.如果您尚未开启此功能, 可以通过在所有InnoDB 表上运行alter 语句来开启此功能.
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. 使用innodb_file_per_table时，将innodb_file_format设置为Barracuda非常重要。此设置将允许更长的索引对某些Cacti表很重要。
Component Translation Difference to current string
This translation Propagated Needs editing Cacti/core
The following string has the same context and source.
Propagated Translated Cacti/core (v1.2.x)

Loading…

No matching activity found.

Browse all component changes

Things to check

PHP format

Following format strings are missing: %s

Reset

Glossary

English Chinese (Simplified)
No related strings found in the glossary.

String information

Flags
php-format
Source string location
lib/template.php:2191
String age
4 months ago
Source string age
4 months ago
Translation file
locales/po/zh-CN.po, string 4076