Menu
▾
▴
Re: [cacti-user] forced to install wizard after patching CentOS 6
|
From: Robert T. <rob...@ho...> - 2017-07-19 19:15:28
|
It now fails most pre-checks. Weird. Patching shouldn't be this painful. Pre-installation Checks MySQL TimeZone Support ERROR: Your Cacti database login account does not have access to the MySQL TimeZone database. Please provide the Cacti database account "select" access to the "time_zone_name" table in the "mysql" database, and populate MySQL's TimeZone information before proceeding. collation_server latin1_swedish_ci ??!!! MySQL Tuning (/etc/my.cnf) - [ Documentation<https://dev.mysql.com/doc/refman/5.1/en/server-system-variables.html> ] Note: Many changes below require a database restart Variable Current Value Recommended Value Comments version 5.1.73 >= 5.6 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 casuing spine many issues with reliability. collation_server latin1_swedish_ci utf8mb4_unicode_ci 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. character_set_client latin1 utf8mb4 When using Cacti with languages other than English, it is important ot use the utf8mb4 character set as some characters take more than a single byte. max_connections 151 >= 100 Depending on the number of logins and use of spine data collector, MySQL 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. max_heap_table_size 16M >=98M 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. max_allowed_packet 1048576 >= 16777216 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. tmp_table_size 16M >= 64M When executing subqueries, having a larger temporary table size, keep those temporary tables in memory. join_buffer_size 0.125M >= 64M When performing joins, if they are below this size, they will be kept in memory and never written to a temporary file. innodb_file_per_table OFF ON When using InnoDB storage it is important to keep your table spaces separate. This makes managing the tables simpler for long time users of MySQL. 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_buffer_pool_size 8M >=488M 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. innodb_doublewrite ON OFF With modern SSD type storage, this operation actually degrades the disk more rapidly and adds a 50% overhead on all write operations. innodb_additional_mem_pool_size 1M >= 80M This is where metadata is stored. If you had a lot of tables, it would be useful to increase this. innodb_lock_wait_timeout 50 >= 50 Rogue queries should not for the database to go offline to others. Kill these queries before they kill your system. ________________________________ From: Robert Threet <rob...@ho...> Sent: Wednesday, July 19, 2017 3:01 PM To: cac...@li... Subject: [cacti-user] forced to install wizard after patching CentOS 6 I have a Cacti installation that is several years old. Once, several years ago, after patching my installation was blanked. I think I found there were some php or apache modules not loading and I was able to find an old config file and fix. I cannot remember what the issue was but it has happened again. When I click on my cacti installation, I get dumped into the installation/setup wizard screen. This must be a common occurrence as a result of either php, Apache or MySQL patches. Does anyone have a quick fix for this? I do not want to lose my historical data. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ cacti-user mailing list cac...@li... https://lists.sourceforge.net/lists/listinfo/cacti-user |
