日韩性视频-久久久蜜桃-www中文字幕-在线中文字幕av-亚洲欧美一区二区三区四区-撸久久-香蕉视频一区-久久无码精品丰满人妻-国产高潮av-激情福利社-日韩av网址大全-国产精品久久999-日本五十路在线-性欧美在线-久久99精品波多结衣一区-男女午夜免费视频-黑人极品ⅴideos精品欧美棵-人人妻人人澡人人爽精品欧美一区-日韩一区在线看-欧美a级在线免费观看

歡迎訪問 生活随笔!

生活随笔

當(dāng)前位置: 首頁 > 运维知识 > 数据库 >内容正文

数据库

MySQL服务器修改主机名后问题解决

發(fā)布時間:2025/7/14 数据库 28 豆豆
生活随笔 收集整理的這篇文章主要介紹了 MySQL服务器修改主机名后问题解决 小編覺得挺不錯的,現(xiàn)在分享給大家,幫大家做個參考.

1、單機(jī)MySQL主機(jī)名修改

今天無事看到自己的主機(jī)名不對,于是改了一下,以便區(qū)分服務(wù)器,那只重啟MySQL時出現(xiàn)下面錯誤:

?

MySQL manager or server PID file could not be found!???????[FAILED]
Starting MySQL.Manager of pid-file quit without updating fi[FAILED]

?

怎么會找不到PID呢,看下面:

[root@daban114.com ~]#??ps aux | grep mysql
mysql????16433??0.0??0.2??36636??5756 ?????????Sl???15:07???0:00 /usr/local/mysql/libexec/mysqld --basedir=/usr/local/mysql --datadir=/usr/local/mysql/var --user=mysql --log-error=/usr/local/mysql/var/hao9goAndSecondWeb.err --pid-file=/usr/local/mysql/var/hao9goAndSecondWeb.pid?--socket=/tmp/mysql.sock --port=3306
root?????16992??0.0??0.0???4020???704 pts/0????S+???15:11???0:00 grep mysql

原來PID還是原來主機(jī)名.pid,運(yùn)行:

kill -9 <mysqlpid> 然后 service mysql start 哈哈看到綠色的OK了,

[root@daban114 ~]# service mysql start
Starting MySQL.????????????????????????????????????????????[??OK??]

?

[mysql@master ~]$ /etc/init.d/mysql restart
MySQL server PID file could not be found! [FAILED]
Starting MySQL..^[[A.......................................[FAILED]....................................................
.The server quit without updating PID file (/usr/local/mysql5.6/data/master.pid).
[mysql@master ~]$ /etc/init.d/mysql restart

mysql 修改主機(jī)名后 ,手動kill進(jìn)程 重啟

?

2、MySQL從庫主機(jī)名修改

環(huán)境:MySQL5.6 + CentOS6.5

  問題描述:從庫修改主機(jī)名后,從庫的同步?jīng)]有自動啟動,用start slave命令開啟失敗

  從庫修改主機(jī)名后,從庫的同步?jīng)]有自動啟動,查看狀態(tài)如下:

  mysql> show slave statusG

  *************************** 1. row ***************************

  Slave_IO_State:

  Master_Host: 192.168.1.2

  Master_User: manager_slave

  Master_Port: 3306

  Connect_Retry: 10

  Master_Log_File: logbin.000053

  Read_Master_Log_Pos: 588641410

  Relay_Log_File: zzstep-relay-bin.000015

  Relay_Log_Pos: 38778474

  Relay_Master_Log_File: logbin.000053

  Slave_IO_Running: No

  Slave_SQL_Running: No

  Replicate_Do_DB:

  Replicate_Ignore_DB: mysql,information_schema,performance_schema

  Replicate_Do_Table:

  Replicate_Ignore_Table:

  Replicate_Wild_Do_Table:

  Replicate_Wild_Ignore_Table: hn.sphinx%

  Last_Errno: 0

  Last_Error:

  Skip_Counter: 0

  Exec_Master_Log_Pos: 588641410

  Relay_Log_Space: 0

  Until_Condition: None

  Until_Log_File:

  Until_Log_Pos: 0

  Master_SSL_Allowed: No

  Master_SSL_CA_File:

  Master_SSL_CA_Path:

  Master_SSL_Cert:

  Master_SSL_Cipher:

  Master_SSL_Key:

  Seconds_Behind_Master: NULL

  Master_SSL_Verify_Server_Cert: No

  Last_IO_Errno: 0

  Last_IO_Error:

  Last_SQL_Errno: 0

  Last_SQL_Error:

  Replicate_Ignore_Server_Ids:

  Master_Server_Id: 0

  Master_UUID: 8ce09c46-a7be-11e4-8e06-0050569f4b5b

  Master_Info_File: /opt/mysql_data/master.info

  SQL_Delay: 0

  SQL_Remaining_Delay: NULL

  Slave_SQL_Running_State:

  Master_Retry_Count: 86400

  Master_Bind:

  Last_IO_Error_Timestamp:

  Last_SQL_Error_Timestamp:

  Master_SSL_Crl:

  Master_SSL_Crlpath:

  Retrieved_Gtid_Set:

  Executed_Gtid_Set:

  Auto_Position: 0

  1 row in set (0.00 sec)

  使用start slave命令開啟失敗:

  mysql> start slave;

  ERROR 1872 (HY000): Slave failed to initialize relay log info structure from the repository

  使用reset slave命令解決:

  mysql> reset slave;

  Query OK, 0 rows affected (0.01 sec)

  mysql> start slave;

  Query OK, 0 rows affected (0.03 sec)

  mysql> show slave statusG

  *************************** 1. row ***************************

  Slave_IO_State: Queueing master event to the relay log

  Master_Host: 192.168.1.2

  Master_User: manager_slave

  Master_Port: 3306

  Connect_Retry: 10

  Master_Log_File: logbin.000021

  Read_Master_Log_Pos: 11215004

  Relay_Log_File: db_mysql_02-relay-bin.000007

  Relay_Log_Pos: 22097

  Relay_Master_Log_File: logbin.000005

  Slave_IO_Running: Yes

  Slave_SQL_Running: Yes

  Replicate_Do_DB:

  Replicate_Ignore_DB: mysql,information_schema,performance_schema

  Replicate_Do_Table:

  Replicate_Ignore_Table:

  Replicate_Wild_Do_Table:

  Replicate_Wild_Ignore_Table: hn.sphinx%

  Last_Errno: 0

  Last_Error:

  Skip_Counter: 0

  Exec_Master_Log_Pos: 21937

  Relay_Log_Space: 13113813

  Until_Condition: None

  Until_Log_File:

  Until_Log_Pos: 0

  Master_SSL_Allowed: No

  Master_SSL_CA_File:

  Master_SSL_CA_Path:

  Master_SSL_Cert:

  Master_SSL_Cipher:

  Master_SSL_Key:

  Seconds_Behind_Master: 1071515

  Master_SSL_Verify_Server_Cert: No

  Last_IO_Errno: 0

  Last_IO_Error:

  Last_SQL_Errno: 0

  Last_SQL_Error:

  Replicate_Ignore_Server_Ids:

  Master_Server_Id: 11

  Master_UUID: 8ce09c46-a7be-11e4-8e06-0050569f4b5b

  Master_Info_File: /opt/mysql_data/master.info

  SQL_Delay: 0

  SQL_Remaining_Delay: NULL

  Slave_SQL_Running_State: creating table

  Master_Retry_Count: 86400

  Master_Bind:

  Last_IO_Error_Timestamp:

  Last_SQL_Error_Timestamp:

  Master_SSL_Crl:

  Master_SSL_Crlpath:

  Retrieved_Gtid_Set:

  Executed_Gtid_Set:

  Auto_Position: 0

  1 row in set (0.00 sec)

  mysql>

  總結(jié):

  由于修改主機(jī)名后,relay-log的名稱發(fā)生變化,導(dǎo)致文件IO失敗,reset slave可以重新定位。

??? 文章來源:http://huangfuff.blog.51cto.com/2632203/1610429

?

如果修改了從庫的主機(jī)名,而從庫又忘了做relay-log和relay-log-index的配置,估計(jì)會導(dǎo)致從庫同步失敗。由于公司剛改了主機(jī)名,寫個博客,后續(xù)出問題好進(jìn)行改進(jìn)。方案測試通過。

步驟如下:

1: 從庫先停止主從復(fù)制

????stop slave;

2: 記錄下主從同步的信息(主要是以下兩個信息)

????show slave status\G

????Master_Log_File: mysql-bin.000085

????Read_Master_Log_Pos: 120

3: 重置數(shù)據(jù)庫

????reset slave;

????????--> 在這里,最好設(shè)置一個兩個參數(shù),預(yù)防后續(xù)再改主機(jī)名

????????????relay-log = relay-log

????????????relay-log-index = relay-log.index

4: 如果主庫設(shè)置給從庫的用戶名和密碼忘記了話,再grant一次(記得就跳過這步了)

????grant replication slave on *.* to 'replication'@'192.168.1.2' identified by 'xxx';

5: 從庫設(shè)置slave

????change master to master_log_file='mysql-bin.000085',master_log_pos=120,master_user='replication',master_password='xxx', master_host='192.168.1.1';

6: 開啟從庫

????start slave;

另外,再reset slave后感覺得配置下relay-log和relay-log-index,然后重啟下數(shù)據(jù)。再從第5步開始,這樣后續(xù)改主機(jī)名就不會影響到了。

?

如果是主庫沒指定bin-log和bin-log-index,那修改主機(jī)名后會怎么樣,不知道會產(chǎn)生什么樣的問題和應(yīng)對方案該怎么樣。暫時方案如下:

????1: 在mysql上找到主的位置,應(yīng)該是一開始的。位置:4

????????show master status\G

????????--> 其實(shí)這里,如果改了主機(jī)名,最好在配置里面指定兩個參數(shù)(后續(xù)改主機(jī)就沒事了)

????????????log-bin=master-bin

????????????log-bin-index = masters-bin.index

????2: 先把從庫停止

????????stop slave;

????3: 把之前從庫的同步信息全部去掉

????????reset slave;

????4: 然后指向主的第一個位置開始同步

????????change master to master_log_file='master-bin.000001',master_log_pos=4,master_user='replication',master_password='xxx', master_host='192.168.1.1';

????5: 再開啟從應(yīng)該就可以了

????????start slave;

?

轉(zhuǎn)載于:https://www.cnblogs.com/paul8339/p/6908989.html

《新程序員》:云原生和全面數(shù)字化實(shí)踐50位技術(shù)專家共同創(chuàng)作,文字、視頻、音頻交互閱讀

總結(jié)

以上是生活随笔為你收集整理的MySQL服务器修改主机名后问题解决的全部內(nèi)容,希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網(wǎng)站內(nèi)容還不錯,歡迎將生活随笔推薦給好友。