我是靠谱客的博主 故意山水,最近开发中收集的这篇文章主要介绍mysql从服务器出问题_MySQL中其中2台从服务器不正常关闭导致,实例启动不起来问题解决...,觉得挺不错的,现在分享给大家,希望可以做个参考。

概述

121211 10:03:27 [Note] /usr/local/MySQL/bin/mysqld: Shutdown complete

121211 10:03:27 mysqld_safe mysqld from pid file /usr/local/mysql/data/CloneSlave01.pid ended

以上的问题,需要剔除ibdata 以及ib_logfile0、ib_logfile1这3个文件便可以正常启动

121211 10:17:37 InnoDB: Completed initialization of buffer pool

InnoDB: The first specified data file ./ibdata1 did not exist:

InnoDB: a new database to be created!

121211 10:17:37 InnoDB: Setting file ./ibdata1 size to 10 MB

InnoDB: Database physically writes the file full: wait...

121211 10:17:37 InnoDB: Log file ./ib_logfile0 did not exist: new to be created

InnoDB: Setting log file ./ib_logfile0 size to 5 MB

InnoDB: Database physically writes the file full: wait...

121211 10:17:38 InnoDB: Log file ./ib_logfile1 did not exist: new to be created

InnoDB: Setting log file ./ib_logfile1 size to 5 MB

InnoDB: Database physically writes the file full: wait...

InnoDB: Doublewrite buffer not found: creating new

InnoDB: Doublewrite buffer created

InnoDB: 127 rollback segment(s) active.

InnoDB: Creating foreign key constraint system tables

InnoDB: Foreign key constraint system tables created

121211 10:17:38 InnoDB: Waiting for the background threads to start

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

121211 10:17:39 InnoDB: 1.1.7 started; log sequence number 0

121211 10:17:39 [ERROR] Can't start server: Bind on TCP/IP port: Address already in use

121211 10:17:39[ERROR] Do you already have another mysqld server running on port: 3306 ?

121211 10:17:39 [ERROR] Aborting

121211 10:17:39 InnoDB: Starting shutdown...

InnoDB: Unable to lock ./ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files

再次启动的时候可以看出有端口占用了3306导致无法启动,由于这是测试无关紧要,就没做端口变更;下面进行查看;

[root@CloneSlave01 data]# netstat -tpln |grep 3306

tcp 0 0 :::3306 :::* LISTEN 3237/mysqld

[root@CloneSlave01 data]# kill 3237

[root@CloneSlave01 data]# netstat -tpln |grep 3306

[root@CloneSlave01 data]# service mysqld restart

MySQL server PID file could not be found! [FAILED]

Starting MySQL.. [ OK ]

[root@CloneSlave01 data]# service mysqld restart

Shutting down MySQL. [ OK ]

Starting MySQL.. [ OK ]

[root@CloneSlave01 data]#

我们提出3306的占用端口,即可重新启动,看上面的效果,另一台的操作方法和步骤和以上大同小异,我就不再次贴出来,当然启动好以后还要测试相关的数据完整性等问题!

总结:我们在关闭服务器的时候,一定要了解服务器的有哪些服务,需要我们提前做好关闭的,才能保证我们数据的安全可靠。0b1331709591d260c1c78e86d0c51c18.png

最后

以上就是故意山水为你收集整理的mysql从服务器出问题_MySQL中其中2台从服务器不正常关闭导致,实例启动不起来问题解决...的全部内容,希望文章能够帮你解决mysql从服务器出问题_MySQL中其中2台从服务器不正常关闭导致,实例启动不起来问题解决...所遇到的程序开发问题。

如果觉得靠谱客网站的内容还不错,欢迎将靠谱客网站推荐给程序员好友。

本图文内容来源于网友提供,作为学习参考使用,或来自网络收集整理,版权属于原作者所有。
点赞(56)

评论列表共有 0 条评论

立即
投稿
返回
顶部