宁波微网站建设,百度上广告怎么搞上去的,网站建设方案页面设计分析,wordpress主题结合Yum升级mysql5.1到5.6有一些虚拟机、云主机提供商仍然使用的是老版本的安装套件。预装的应用软件版本很低。比如 techbrood.com 使用的云服务器#xff0c;其中MySQL预装版本为老版本5.1.x。而最新的mysql版本在性能、功能、安全性等方面都有了很多的改进。要从最新版本获益其中MySQL预装版本为老版本5.1.x。而最新的mysql版本在性能、功能、安全性等方面都有了很多的改进。要从最新版本获益你需要把现有系统升级到5.5(最新的版本是5.7)我保守一点升级到5.6.37。有相关测试数据说明从5.1到5.5MySQL性能会有明显的提升具体的需要自己建立测试环境去实践下。首先更新rpm从MySQL Yum仓库下载最新的rpm文件http://dev.mysql.com/downloads/repo/yum/(需要Oracle帐号以及填写一些使用信息才能进入下载页面)我需要下载的是mysql-community-release-el6-5.noarch.rpm安装这个发布包yum localinstall mysql-community-release-el6-5.noarch.rpm可以通过下面的命令来确认这个仓库被成功添加yum repolist enabled | grep mysql.-community.安装MySQL服务器yum install mysql-community-server新版本的目标文件是/usr/bin/mysql如果原预装路径在/bin下面则需要进行替换最好是使用软链接比如ln -s /usr/bin/mysql /bin/这样在需要的时候可以方便的在不同版本之间进行切换。(有时候需要版本回退来定位问题)重启服务器就可以了service mysqld restart确认版本信息[rootwest195246 bin]# mysql -Vmysql Ver 14.14 Distrib 5.6.20, for Linux (x86_64) using EditLine wrapper在我进行过的几次软件升级之后总会在 MySQL 的日志中见到“[ERROR] Missing system table mysql.proxies_priv; please run mysql_upgrade to create it”之类的错误。虽然这个错误修复起来很简单却不容易引起注意。可以按如下方法修复错误日志如下[ERROR] InnoDB: auto-extending data file ./ibdata1 is of a different size 640 pages (rounded down to MB) than specified in the .cnf file: initial 16384 pages, max 0 (relevant if non-zero) pages!2017-09-01 09:15:06 5588 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!2017-09-01 09:15:06 5588 [ERROR] Plugin InnoDB init function returned error.2017-09-01 09:15:06 5588 [ERROR] Plugin InnoDB registration as a STORAGE ENGINE failed.2017-09-01 09:15:06 5588 [ERROR] Unknown/unsupported storage engine: InnoDB2017-09-01 09:15:06 5588 [ERROR] Aborting错误提示如下[ERROR] Missing system table mysql.proxies_priv; please run mysql_upgrade to create it[ERROR] Native table performance_schema.events_waits_current has the wrong structure[ERROR] Native table performance_schema.events_waits_history has the wrong structure[ERROR] Native table performance_schema.events_waits_history_long has the wrong structure[ERROR] Native table performance_schema.setup_consumers has the wrong structure[ERROR] Native table performance_schema.setup_instruments has the wrong structure[ERROR] Native table performance_schema.setup_timers has the wrong structure[ERROR] Native table performance_schema.performance_timers has the wrong structure[ERROR] Native table performance_schema.threads has the wrong structure[ERROR] Native table performance_schema.events_waits_summary_by_thread_by_event_name has the wrong structure[ERROR] Native table performance_schema.events_waits_summary_by_instance has the wrong structure[ERROR] Native table performance_schema.events_waits_summary_global_by_event_name has the wrong structure[ERROR] Native table performance_schema.file_summary_by_event_name has the wrong structure[ERROR] Native table performance_schema.file_summary_by_instance has the wrong structure[ERROR] Native table performance_schema.mutex_instances has the wrong structure[ERROR] Native table performance_schema.rwlock_instances has the wrong structure[ERROR] Native table performance_schema.cond_instances has the wrong structure[ERROR] Native table performance_schema.file_instances has the wrong structure[Note] Event Scheduler: Loaded 0 events[Note] /usr/libexec/mysqld: ready for connections.Version: 5.5.20-log socket: /var/lib/mysql/mysql.sock port: 0处理方法#cd /var/lib/mysql#rm -rf ib*#service mysqld restart需要按照如下的格式在 Linux 的 —— 而不是 MySQL 的 —— 命令提示符下运行#mysql_upgrade -u root -p然后根据提示输入 mysql 的 root 帐户密码修复过程就可自动运行。此时会有如下形式的提示信息输出mysql_upgrade -u root -pEnter password:Looking for mysql as: mysqlLooking for mysqlcheck as: mysqlcheckRunning mysqlcheck with connection arguments: --port3306 --socket/var/lib/mysql/mysql.sockRunning mysqlcheck with connection arguments: --port3306 --socket/var/lib/mysql/mysql.sockwp_commentmeta OKwp_comments OKwp_links OKwp_options OKwp_postmeta OKwp_posts OKwp_term_relationships OKwp_term_taxonomy OKwp_terms OKwp_usermeta OKwp_users OKmysql.columns_priv OKmysql.db OKmysql.event OKmysql.func OKmysql.general_log OKmysql.help_category OKmysql.help_keyword OKmysql.help_relation OKmysql.help_topic OKmysql.host OKmysql.ndb_binlog_index OKmysql.plugin OKmysql.proc OKmysql.procs_priv OKmysql.servers OKmysql.slow_log OKmysql.tables_priv OKmysql.time_zone OKmysql.time_zone_leap_second OKmysql.time_zone_name OKmysql.time_zone_transition OKmysql.time_zone_transition_type OKmysql.user OKRunning mysql_fix_privilege_tables... OK##service mysqld restart
