设为首页 收藏本站
查看: 562|回复: 0

[经验分享] MySQL高可用MHA部署 (一主二从)

[复制链接]

尚未签到

发表于 2018-9-30 06:20:56 | 显示全部楼层 |阅读模式
Mon Jan 18 18:05:49 2016 - [warning] Goterror on MySQL select ping: 2006 (MySQL server has gone away)  
Mon Jan 18 18:05:49 2016 - [info] ExecutingSSH check script: save_binary_logs --command=test --start_pos=4--binlog_dir=/data/dbdata/mysqllog/binlog--output_file=/tmp/save_binary_logs_test --manager_version=0.56--binlog_prefix=binlog
  
Creating /tmp if not exists..   ok.
  
Checking output directory is accessible or not..
  
  ok.
  
Binlog found at /data/dbdata/mysqllog/binlog, up to binlog.000003
  
Mon Jan 18 18:05:50 2016 - [info]HealthCheck: SSH to 192.168.6.85 is reachable.
  
Mon Jan 18 18:05:50 2016 - [warning] Goterror on MySQL connect: 2013 (Lost connection to MySQL server at 'readinginitial communication packet', system error: 111)
  
Mon Jan 18 18:05:50 2016 - [warning]Connection failed 2 time(s)..
  
Mon Jan 18 18:05:51 2016 - [warning] Goterror on MySQL connect: 2013 (Lost connection to MySQL server at 'readinginitial communication packet', system error: 111)
  
Mon Jan 18 18:05:51 2016 - [warning]Connection failed 3 time(s)..
  
Mon Jan 18 18:05:52 2016 - [warning] Goterror on MySQL connect: 2013 (Lost connection to MySQL server at 'readinginitial communication packet', system error: 111)
  
Mon Jan 18 18:05:52 2016 - [warning]Connection failed 4 time(s)..
  
Mon Jan 18 18:05:52 2016 - [warning] Masteris not reachable from health checker!
  
Mon Jan 18 18:05:52 2016 - [warning] Master192.168.6.85(192.168.6.85:3306) is not reachable!
  
Mon Jan 18 18:05:52 2016 - [warning] SSH isreachable.
  
Mon Jan 18 18:05:52 2016 - [info]Connecting to a master server failed. Reading configuration file/etc/masterha_default.cnf and /etc/mha/masterha_default.cnf again, and tryingto connect to all servers to check server status..
  
Mon Jan 18 18:05:52 2016 - [warning] Globalconfiguration file /etc/masterha_default.cnf not found. Skipping.
  
Mon Jan 18 18:05:52 2016 - [info] Readingapplication default configuration from /etc/mha/masterha_default.cnf..
  
Mon Jan 18 18:05:52 2016 - [info] Readingserver configuration from /etc/mha/masterha_default.cnf..
  
Mon Jan 18 18:05:52 2016 - [info] GTIDfailover mode = 0
  
Mon Jan 18 18:05:52 2016 - [info] DeadServers:
  
Mon Jan 18 18:05:52 2016 - [info]   192.168.6.85(192.168.6.85:3306)
  
Mon Jan 18 18:05:52 2016 - [info] AliveServers:
  
Mon Jan 18 18:05:52 2016 - [info]   192.168.6.91(192.168.6.91:3306)
  
Mon Jan 18 18:05:52 2016 - [info]   192.168.6.149(192.168.6.149:3306)
  
Mon Jan 18 18:05:52 2016 - [info] AliveSlaves:
  
Mon Jan 18 18:05:52 2016 - [info]   192.168.6.91(192.168.6.91:3306)  Version=5.5.33-log (oldest major versionbetween slaves) log-bin:enabled
  
Mon Jan 18 18:05:52 2016 - [info]     Replicating from192.168.6.85(192.168.6.85:3306)
  
Mon Jan 18 18:05:52 2016 - [info]     Primary candidate for the new Master(candidate_master is set)
  
Mon Jan 18 18:05:52 2016 - [info]   192.168.6.149(192.168.6.149:3306)  Version=5.5.33-log (oldest major versionbetween slaves) log-bin:enabled
  
Mon Jan 18 18:05:52 2016 - [info]     Replicating from192.168.6.85(192.168.6.85:3306)
  
Mon Jan 18 18:05:52 2016 - [info] Checkingslave configurations..
  
Mon Jan 18 18:05:52 2016 - [info]  read_only=1 is not set on slave192.168.6.91(192.168.6.91:3306).
  
Mon Jan 18 18:05:52 2016 - [warning]  relay_log_purge=0 is not set on slave192.168.6.91(192.168.6.91:3306).
  
Mon Jan 18 18:05:52 2016 - [info]  read_only=1 is not set on slave192.168.6.149(192.168.6.149:3306).
  
Mon Jan 18 18:05:52 2016 - [warning]  relay_log_purge=0 is not set on slave192.168.6.149(192.168.6.149:3306).
  
Mon Jan 18 18:05:52 2016 - [info] Checkingreplication filtering settings..
  
Mon Jan 18 18:05:52 2016 - [info]  Replication filtering check ok.
  
Mon Jan 18 18:05:52 2016 - [info] Master isdown!
  
Mon Jan 18 18:05:52 2016 - [info]Terminating monitoring script.
  
Mon Jan 18 18:05:52 2016 - [info] Got exitcode 20 (Master dead).
  
Mon Jan 18 18:05:52 2016 - [warning] Globalconfiguration file /etc/masterha_default.cnf not found. Skipping.
  
Mon Jan 18 18:05:52 2016 - [info] Readingapplication default configuration from /etc/mha/masterha_default.cnf..
  
Mon Jan 18 18:05:52 2016 - [info] Readingserver configuration from /etc/mha/masterha_default.cnf..
  
Mon Jan 18 18:05:52 2016 - [info]MHA::MasterFailover version 0.56.
  
Mon Jan 18 18:05:52 2016 - [info] Startingmaster failover.
  
Mon Jan 18 18:05:52 2016 - [info]
  
Mon Jan 18 18:05:52 2016 - [info] * Phase1: Configuration Check Phase..
  
Mon Jan 18 18:05:52 2016 - [info]
  
Mon Jan 18 18:05:53 2016 - [info] GTIDfailover mode = 0
  
Mon Jan 18 18:05:53 2016 - [info] DeadServers:
  
Mon Jan 18 18:05:53 2016 - [info]   192.168.6.85(192.168.6.85:3306)
  
Mon Jan 18 18:05:53 2016 - [info] Checkingmaster reachability via MySQL(double check)...
  
Mon Jan 18 18:05:53 2016 - [info]  ok.
  
Mon Jan 18 18:05:53 2016 - [info] AliveServers:
  
Mon Jan 18 18:05:53 2016 - [info]   192.168.6.91(192.168.6.91:3306)
  
Mon Jan 18 18:05:53 2016 - [info]   192.168.6.149(192.168.6.149:3306)
  
Mon Jan 18 18:05:53 2016 - [info] AliveSlaves:
  
Mon Jan 18 18:05:53 2016 - [info]   192.168.6.91(192.168.6.91:3306)  Version=5.5.33-log (oldest major versionbetween slaves) log-bin:enabled
  
Mon Jan 18 18:05:53 2016 - [info]     Replicating from192.168.6.85(192.168.6.85:3306)
  
Mon Jan 18 18:05:53 2016 - [info]     Primary candidate for the new Master(candidate_master is set)
  
Mon Jan 18 18:05:53 2016 - [info]   192.168.6.149(192.168.6.149:3306)  Version=5.5.33-log (oldest major versionbetween slaves) log-bin:enabled
  
Mon Jan 18 18:05:53 2016 - [info]     Replicating from192.168.6.85(192.168.6.85:3306)
  
Mon Jan 18 18:05:53 2016 - [info] StartingNon-GTID based failover.
  
Mon Jan 18 18:05:53 2016 - [info]
  
Mon Jan 18 18:05:53 2016 - [info] ** Phase1: Configuration Check Phase completed.
  
Mon Jan 18 18:05:53 2016 - [info]
  
Mon Jan 18 18:05:53 2016 - [info] * Phase2: Dead Master Shutdown Phase..
  
Mon Jan 18 18:05:53 2016 - [info]
  
Mon Jan 18 18:05:53 2016 - [info] Forcingshutdown so that applications never connect to the current master..
  
Mon Jan 18 18:05:53 2016 - [warning]master_ip_failover_script is not set. Skipping invalidating dead master IPaddress.
  
Mon Jan 18 18:05:53 2016 - [warning] shutdown_scriptis not set. Skipping explicit shutting down of the dead master.
  
Mon Jan 18 18:05:53 2016 - [info] * Phase2: Dead Master Shutdown Phase completed.
  
Mon Jan 18 18:05:53 2016 - [info]
  
Mon Jan 18 18:05:53 2016 - [info] * Phase3: Master Recovery Phase..
  
Mon Jan 18 18:05:53 2016 - [info]
  
Mon Jan 18 18:05:53 2016 - [info] * Phase3.1: Getting Latest Slaves Phase..
  
Mon Jan 18 18:05:53 2016 - [info]
  
Mon Jan 18 18:05:53 2016 - [info] Thelatest binary log file/position on all slaves is binlog.000003:107
  
Mon Jan 18 18:05:53 2016 - [info] Latestslaves (Slaves that received relay log files to the latest):
  
Mon Jan 18 18:05:53 2016 - [info]   192.168.6.91(192.168.6.91:3306)  Version=5.5.33-log (oldest major versionbetween slaves) log-bin:enabled
  
Mon Jan 18 18:05:53 2016 - [info]     Replicating from192.168.6.85(192.168.6.85:3306)
  
Mon Jan 18 18:05:53 2016 - [info]     Primary candidate for the new Master(candidate_master is set)
  
Mon Jan 18 18:05:53 2016 - [info]   192.168.6.149(192.168.6.149:3306)  Version=5.5.33-log (oldest major versionbetween slaves) log-bin:enabled
  
Mon Jan 18 18:05:53 2016 - [info]     Replicating from192.168.6.85(192.168.6.85:3306)
  
Mon Jan 18 18:05:53 2016 - [info] Theoldest binary log file/position on all slaves is binlog.000003:107
  
Mon Jan 18 18:05:53 2016 - [info] Oldestslaves:
  
Mon Jan 18 18:05:53 2016 - [info]   192.168.6.91(192.168.6.91:3306)  Version=5.5.33-log (oldest major versionbetween slaves) log-bin:enabled
  
Mon Jan 18 18:05:53 2016 - [info]     Replicating from 192.168.6.85(192.168.6.85:3306)
  
Mon Jan 18 18:05:53 2016 - [info]     Primary candidate for the new Master(candidate_master is set)
  
Mon Jan 18 18:05:53 2016 - [info]   192.168.6.149(192.168.6.149:3306)  Version=5.5.33-log (oldest major versionbetween slaves) log-bin:enabled
  
Mon Jan 18 18:05:53 2016 - [info]     Replicating from192.168.6.85(192.168.6.85:3306)
  
Mon Jan 18 18:05:53 2016 - [info]
  
Mon Jan 18 18:05:53 2016 - [info] * Phase3.2: Saving Dead Master's Binlog Phase..
  
Mon Jan 18 18:05:53 2016 - [info]
  
Mon Jan 18 18:05:53 2016 - [info] Fetchingdead master's binary logs..
  
Mon Jan 18 18:05:53 2016 - [info] Executingcommand on the dead master 192.168.6.85(192.168.6.85:3306): save_binary_logs--command=save --start_file=binlog.000003 --start_pos=107 --binlog_dir=/data/dbdata/mysqllog/binlog--output_file=/tmp/saved_master_binlog_from_192.168.6.85_3306_20160118180552.binlog--handle_raw_binlog=1 --disable_log_bin=0 --manager_version=0.56
  
Creating /tmp if not exists..   ok.
  
Concat binary/relay logs from binlog.000003pos 107 to binlog.000003 EOF into/tmp/saved_master_binlog_from_192.168.6.85_3306_20160118180552.binlog ..
  
Dumping binlog format description event, from position 0 to 107.. ok.
  
Dumping effective binlog data from /data/dbdata/mysqllog/binlog/binlog.000003position 107 to tail(126).. ok.
  
Concat succeeded.
  
Mon Jan 18 18:05:54 2016 - [info] scp fromroot@192.168.6.85:/tmp/saved_master_binlog_from_192.168.6.85_3306_20160118180552.binlogto local:/var/tmp/saved_master_binlog_from_192.168.6.85_3306_20160118180552.binlogsucceeded.
  
Mon Jan 18 18:05:54 2016 - [info]HealthCheck: SSH to 192.168.6.91 is reachable.
  
Mon Jan 18 18:05:55 2016 - [info]HealthCheck: SSH to 192.168.6.149 is reachable.
  
Mon Jan 18 18:05:55 2016 - [info]
  
Mon Jan 18 18:05:55 2016 - [info] * Phase3.3: Determining New Master Phase..
  
Mon Jan 18 18:05:55 2016 - [info]
  
Mon Jan 18 18:05:55 2016 - [info] Findingthe latest slave that has all relay logs for recovering other slaves..
  
Mon Jan 18 18:05:55 2016 - [info] Allslaves received relay logs to the same position. No need to resync each other.
  
Mon Jan 18 18:05:55 2016 - [info] Searchingnew master from slaves..
  
Mon Jan 18 18:05:55 2016 - [info]  Candidate masters from the configurationfile:
  
Mon Jan 18 18:05:55 2016 - [info]   192.168.6.91(192.168.6.91:3306)  Version=5.5.33-log (oldest major versionbetween slaves) log-bin:enabled
  
Mon Jan 18 18:05:55 2016 - [info]     Replicating from192.168.6.85(192.168.6.85:3306)
  
Mon Jan 18 18:05:55 2016 - [info]     Primary candidate for the new Master(candidate_master is set)
  
Mon Jan 18 18:05:55 2016 - [info]  Non-candidate masters:
  
Mon Jan 18 18:05:55 2016 - [info]  Searching from candidate_master slaves whichhave received the latest relay log events..
  
Mon Jan 18 18:05:55 2016 - [info] New masteris 192.168.6.91(192.168.6.91:3306)
  
Mon Jan 18 18:05:55 2016 - [info] Startingmaster failover..
  
Mon Jan 18 18:05:55 2016 - [info]
  
From:
  
192.168.6.85(192.168.6.85:3306) (currentmaster)
  
+--192.168.6.91(192.168.6.91:3306)
  
+--192.168.6.149(192.168.6.149:3306)
  

  
To:
  
192.168.6.91(192.168.6.91:3306) (newmaster)
  
+--192.168.6.149(192.168.6.149:3306)
  
Mon Jan 18 18:05:55 2016 - [info]
  
Mon Jan 18 18:05:55 2016 - [info] * Phase3.3: New Master Diff Log Generation Phase..
  
Mon Jan 18 18:05:55 2016 - [info]
  
Mon Jan 18 18:05:55 2016 - [info]  This server has all relay logs. No need togenerate diff files from the latest slave.
  
Mon Jan 18 18:05:55 2016 - [info] Sendingbinlog..
  
Mon Jan 18 18:05:55 2016 - [info] scp fromlocal:/var/tmp/saved_master_binlog_from_192.168.6.85_3306_20160118180552.binlogtoroot@192.168.6.91:/tmp/saved_master_binlog_from_192.168.6.85_3306_20160118180552.binlogsucceeded.
  
Mon Jan 18 18:05:55 2016 - [info]
  
Mon Jan 18 18:05:55 2016 - [info] * Phase3.4: Master Log Apply Phase..
  
Mon Jan 18 18:05:55 2016 - [info]
  
Mon Jan 18 18:05:55 2016 - [info] *NOTICE:If any error happens from this phase, manual recovery is needed.
  
Mon Jan 18 18:05:55 2016 - [info] Startingrecovery on 192.168.6.91(192.168.6.91:3306)..
  
Mon Jan 18 18:05:55 2016 - [info]  Generating diffs succeeded.
  
Mon Jan 18 18:05:55 2016 - [info] Waitinguntil all relay logs are applied.
  
Mon Jan 18 18:05:55 2016 - [info]  done.
  
Mon Jan 18 18:05:55 2016 - [info] Gettingslave status..
  
Mon Jan 18 18:05:55 2016 - [info] Thisslave(192.168.6.91)'s Exec_Master_Log_Pos equals toRead_Master_Log_Pos(binlog.000003:107). No need to recover fromExec_Master_Log_Pos.
  
Mon Jan 18 18:05:55 2016 - [info]Connecting to the target slave host 192.168.6.91, running recover script..
  
Mon Jan 18 18:05:55 2016 - [info] Executingcommand: apply_diff_relay_logs --command=apply --slave_user='root'--slave_host=192.168.6.91 --slave_ip=192.168.6.91  --slave_port=3306--apply_files=/tmp/saved_master_binlog_from_192.168.6.85_3306_20160118180552.binlog--workdir=/tmp --target_version=5.5.33-log --timestamp=20160118180552--handle_raw_binlog=1 --disable_log_bin=0 --manager_version=0.56--slave_pass=xxx
  
Mon Jan 18 18:05:56 2016 - [info]
  
Applying differential binary/relay logfiles /tmp/saved_master_binlog_from_192.168.6.85_3306_20160118180552.binlog on192.168.6.91:3306. This may take long time...
  
Applying log files succeeded.
  
Mon Jan 18 18:05:56 2016 - [info]  All relay logs were successfully applied.
  
Mon Jan 18 18:05:56 2016 - [info] Gettingnew master's binlog name and position..
  
Mon Jan 18 18:05:56 2016 - [info]  binlog.000003:107
  
Mon Jan 18 18:05:56 2016 - [info]  All other slaves should start replicationfrom here. Statement should be: CHANGE MASTER TO MASTER_HOST='192.168.6.91',MASTER_PORT=3306, MASTER_LOG_FILE='binlog.000003', MASTER_LOG_POS=107,MASTER_USER='repl', MASTER_PASSWORD='xxx';
  
Mon Jan 18 18:05:56 2016 - [warning]master_ip_failover_script is not set. Skipping taking over new master IPaddress.
  
Mon Jan 18 18:05:56 2016 - [info] **Finished master recovery successfully.
  
Mon Jan 18 18:05:56 2016 - [info] * Phase3: Master Recovery Phase completed.
  
Mon Jan 18 18:05:56 2016 - [info]
  
Mon Jan 18 18:05:56 2016 - [info] * Phase4: Slaves Recovery Phase..
  
Mon Jan 18 18:05:56 2016 - [info]
  
Mon Jan 18 18:05:56 2016 - [info] * Phase4.1: Starting Parallel Slave Diff Log Generation Phase..
  
Mon Jan 18 18:05:56 2016 - [info]
  
Mon Jan 18 18:05:56 2016 - [info] -- Slavediff file generation on host 192.168.6.149(192.168.6.149:3306) started, pid:32132. Check tmp log /var/tmp/192.168.6.149_3306_20160118180552.log if it takestime..
  
Mon Jan 18 18:05:56 2016 - [info]
  
Mon Jan 18 18:05:56 2016 - [info] Logmessages from 192.168.6.149 ...
  
Mon Jan 18 18:05:56 2016 - [info]
  
Mon Jan 18 18:05:56 2016 - [info]  This server has all relay logs. No need togenerate diff files from the latest slave.
  
Mon Jan 18 18:05:56 2016 - [info] End oflog messages from 192.168.6.149.
  
Mon Jan 18 18:05:56 2016 - [info] --192.168.6.149(192.168.6.149:3306) has the latest relay log events.
  
Mon Jan 18 18:05:56 2016 - [info]Generating relay diff files from the latest slave succeeded.
  
Mon Jan 18 18:05:56 2016 - [info]
  
Mon Jan 18 18:05:56 2016 - [info] * Phase4.2: Starting Parallel Slave Log Apply Phase..
  
Mon Jan 18 18:05:56 2016 - [info]
  
Mon Jan 18 18:05:56 2016 - [info] -- Slaverecovery on host 192.168.6.149(192.168.6.149:3306) started, pid: 32134. Checktmp log /var/tmp/192.168.6.149_3306_20160118180552.log if it takes time..
  
Mon Jan 18 18:05:57 2016 - [info]
  
Mon Jan 18 18:05:57 2016 - [info] Log messagesfrom 192.168.6.149 ...
  
Mon Jan 18 18:05:57 2016 - [info]
  
Mon Jan 18 18:05:56 2016 - [info] Sendingbinlog..
  
Mon Jan 18 18:05:56 2016 - [info] scp fromlocal:/var/tmp/saved_master_binlog_from_192.168.6.85_3306_20160118180552.binlogto root@192.168.6.149:/tmp/saved_master_binlog_from_192.168.6.85_3306_20160118180552.binlogsucceeded.
  
Mon Jan 18 18:05:56 2016 - [info] Startingrecovery on 192.168.6.149(192.168.6.149:3306)..
  
Mon Jan 18 18:05:56 2016 - [info]  Generating diffs succeeded.
  
Mon Jan 18 18:05:56 2016 - [info] Waitinguntil all relay logs are applied.
  
Mon Jan 18 18:05:56 2016 - [info]  done.
  
Mon Jan 18 18:05:56 2016 - [info] Gettingslave status..
  
Mon Jan 18 18:05:56 2016 - [info] Thisslave(192.168.6.149)'s Exec_Master_Log_Pos equals to Read_Master_Log_Pos(binlog.000003:107).No need to recover from Exec_Master_Log_Pos.
  
Mon Jan 18 18:05:56 2016 - [info]Connecting to the target slave host 192.168.6.149, running recover script..
  
Mon Jan 18 18:05:56 2016 - [info] Executingcommand: apply_diff_relay_logs --command=apply --slave_user='root'--slave_host=192.168.6.149 --slave_ip=192.168.6.149  --slave_port=3306--apply_files=/tmp/saved_master_binlog_from_192.168.6.85_3306_20160118180552.binlog--workdir=/tmp --target_version=5.5.33-log --timestamp=20160118180552--handle_raw_binlog=1 --disable_log_bin=0 --manager_version=0.56--slave_pass=xxx
  
Mon Jan 18 18:05:57 2016 - [info]
  
Applying differential binary/relay logfiles /tmp/saved_master_binlog_from_192.168.6.85_3306_20160118180552.binlog on192.168.6.149:3306. This may take long time...
  
Applying log files succeeded.
  
Mon Jan 18 18:05:57 2016 - [info]  All relay logs were successfully applied.
  
Mon Jan 18 18:05:57 2016 - [info]  Resetting slave 192.168.6.149(192.168.6.149:3306)and starting replication from the new master 192.168.6.91(192.168.6.91:3306)..
  
Mon Jan 18 18:05:57 2016 - [info]  Executed CHANGE MASTER.
  
Mon Jan 18 18:05:57 2016 - [info]  Slave started.
  
Mon Jan 18 18:05:57 2016 - [info] End oflog messages from 192.168.6.149.
  
Mon Jan 18 18:05:57 2016 - [info] -- Slaverecovery on host 192.168.6.149(192.168.6.149:3306) succeeded.
  
Mon Jan 18 18:05:57 2016 - [info] All newslave servers recovered successfully.
  
Mon Jan 18 18:05:57 2016 - [info]
  
Mon Jan 18 18:05:57 2016 - [info] * Phase5: New master cleanup phase..
  
Mon Jan 18 18:05:57 2016 - [info]
  
Mon Jan 18 18:05:57 2016 - [info] Resettingslave info on the new master..
  
Mon Jan 18 18:05:57 2016 - [info]  192.168.6.91: Resetting slave info succeeded.
  
Mon Jan 18 18:05:57 2016 - [info] Masterfailover to 192.168.6.91(192.168.6.91:3306) completed successfully.
  
Mon Jan 18 18:05:57 2016 - [info] Deletedserver1 entry from /etc/mha/masterha_default.cnf .
  
Mon Jan 18 18:05:57 2016 - [info]
  

  
----- Failover Report -----
  

  
masterha_default: MySQL Master failover192.168.6.85(192.168.6.85:3306) to 192.168.6.91(192.168.6.91:3306) succeeded
  

  
Master 192.168.6.85(192.168.6.85:3306) isdown!
  

  
Check MHA Manager logs at slave2 fordetails.
  

  
Started automated(non-interactive)failover.
  
The latest slave192.168.6.91(192.168.6.91:3306) has all relay logs for recovery.
  
Selected 192.168.6.91(192.168.6.91:3306) asa new master.
  
192.168.6.91(192.168.6.91:3306): OK:Applying all logs succeeded.
  
192.168.6.149(192.168.6.149:3306): Thishost has the latest relay log events.
  
Generating relay diff files from the latestslave succeeded.
  
192.168.6.149(192.168.6.149:3306): OK:Applying all logs succeeded. Slave started, replicating from192.168.6.91(192.168.6.91:3306)
  
192.168.6.91(192.168.6.91:3306): Resettingslave info succeeded.
  
Master failover to192.168.6.91(192.168.6.91:3306) completed successfully.



运维网声明 1、欢迎大家加入本站运维交流群:群②:261659950 群⑤:202807635 群⑦870801961 群⑧679858003
2、本站所有主题由该帖子作者发表,该帖子作者与运维网享有帖子相关版权
3、所有作品的著作权均归原作者享有,请您和我们一样尊重他人的著作权等合法权益。如果您对作品感到满意,请购买正版
4、禁止制作、复制、发布和传播具有反动、淫秽、色情、暴力、凶杀等内容的信息,一经发现立即删除。若您因此触犯法律,一切后果自负,我们对此不承担任何责任
5、所有资源均系网友上传或者通过网络收集,我们仅提供一个展示、介绍、观摩学习的平台,我们不对其内容的准确性、可靠性、正当性、安全性、合法性等负责,亦不承担任何法律责任
6、所有作品仅供您个人学习、研究或欣赏,不得用于商业或者其他用途,否则,一切后果均由您自己承担,我们对此不承担任何法律责任
7、如涉及侵犯版权等问题,请您及时通知我们,我们将立即采取措施予以解决
8、联系人Email:admin@iyunv.com 网址:www.yunweiku.com

所有资源均系网友上传或者通过网络收集,我们仅提供一个展示、介绍、观摩学习的平台,我们不对其承担任何法律责任,如涉及侵犯版权等问题,请您及时通知我们,我们将立即处理,联系人Email:kefu@iyunv.com,QQ:1061981298 本贴地址:https://www.yunweiku.com/thread-605947-1-1.html 上篇帖子: mysql5.6忘记密码的恢复方法 下篇帖子: mysql root权限优化后没有grant权限
您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

扫码加入运维网微信交流群X

扫码加入运维网微信交流群

扫描二维码加入运维网微信交流群,最新一手资源尽在官方微信交流群!快快加入我们吧...

扫描微信二维码查看详情

客服E-mail:kefu@iyunv.com 客服QQ:1061981298


QQ群⑦:运维网交流群⑦ QQ群⑧:运维网交流群⑧ k8s群:运维网kubernetes交流群


提醒:禁止发布任何违反国家法律、法规的言论与图片等内容;本站内容均来自个人观点与网络等信息,非本站认同之观点.


本站大部分资源是网友从网上搜集分享而来,其版权均归原作者及其网站所有,我们尊重他人的合法权益,如有内容侵犯您的合法权益,请及时与我们联系进行核实删除!



合作伙伴: 青云cloud

快速回复 返回顶部 返回列表