API tools faq
paste
Guest User

Untitled

a guest
Jan 28th, 2018
336
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 12.61 KB | None | 0 0
raw download clone embed print report
  1. mysql> SHOW SLAVE STATUSG;
  2. *************************** 1. row ***************************
  3. Slave_IO_State: Waiting for master to send event
  4. Master_Host: Master_Host-FQDN.TLD
  5. Master_User: Master_User-REPL
  6. Master_Port: 3306
  7. Connect_Retry: 60
  8. Master_Log_File: mysql-bin.000057
  9. Read_Master_Log_Pos: 247673142
  10. Relay_Log_File: mysql:PR_DB-relay-bin.000041
  11. Relay_Log_Pos: 5537565
  12. Relay_Master_Log_File: mysql-bin.000044
  13. Slave_IO_Running: Yes
  14. Slave_SQL_Running: No
  15. Replicate_Do_DB: RDD1,RDD2,RDDX
  16. Replicate_Ignore_DB: information_schema,mysql
  17. Replicate_Do_Table:
  18. Replicate_Ignore_Table:
  19. Replicate_Wild_Do_Table:
  20. Replicate_Wild_Ignore_Table:
  21. Last_Errno: 1594
  22. Last_Error: Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MySQL code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave.
  23. Skip_Counter: 0
  24. Exec_Master_Log_Pos: 25338679
  25. Relay_Log_Space: 2190669763
  26. Until_Condition: None
  27. Until_Log_File:
  28. Until_Log_Pos: 0
  29. Master_SSL_Allowed: No
  30. Master_SSL_CA_File:
  31. Master_SSL_CA_Path:
  32. Master_SSL_Cert:
  33. Master_SSL_Cipher:
  34. Master_SSL_Key:
  35. Seconds_Behind_Master: NULL
  36. Master_SSL_Verify_Server_Cert: No
  37. Last_IO_Errno: 0
  38. Last_IO_Error:
  39. Last_SQL_Errno: 1594
  40. Last_SQL_Error: Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MySQL code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave.
  41. 1 row in set (0.00 sec)
  42.  
  43. ERROR:
  44. No query specified
  45.  
  46. mysql>
  47.  
  48. 140630 9:10:53 [ERROR] Error in Log_event::read_log_event(): 'read error', data_len: 255, event_type: 2
  49. 140630 9:10:53 [ERROR] Error reading relay log event: slave SQL thread aborted because of I/O error
  50. 140630 9:10:53 [ERROR] Slave SQL: Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MySQL code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave. Error_code: 1594
  51. 140630 9:10:53 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'mysql-bin.000044' position 25338679
  52.  
  53. mysql> show slave statusG
  54. *************************** 1. row ***************************
  55. Slave_IO_State: Waiting for master to send event
  56. Master_Host: 10.4.0.4
  57. Master_User: replicator
  58. Master_Port: 3306
  59. Connect_Retry: 60
  60. Master_Log_File: gtc-master-bin.000022
  61. Read_Master_Log_Pos: 163183335
  62. Relay_Log_File: gtc-relay-bin.000195
  63. Relay_Log_Pos: 37830249
  64. Relay_Master_Log_File: gtc-master-bin.000022
  65. Slave_IO_Running: Yes
  66. Slave_SQL_Running: No
  67. Replicate_Do_DB:
  68. Replicate_Ignore_DB:
  69. Replicate_Do_Table:
  70. Replicate_Ignore_Table:
  71. Replicate_Wild_Do_Table:
  72. Replicate_Wild_Ignore_Table:
  73. Last_Errno: 1594
  74. Last_Error: Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MySQL code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave.
  75. Skip_Counter: 0
  76. Exec_Master_Log_Pos: 74792622
  77. Relay_Log_Space: 163184965
  78. Until_Condition: None
  79. Until_Log_File:
  80. Until_Log_Pos: 0
  81. Master_SSL_Allowed: No
  82. Master_SSL_CA_File:
  83. Master_SSL_CA_Path:
  84. Master_SSL_Cert:
  85. Master_SSL_Cipher:
  86. Master_SSL_Key:
  87. Seconds_Behind_Master: NULL
  88. Master_SSL_Verify_Server_Cert: No
  89. Last_IO_Errno: 0
  90. Last_IO_Error:
  91. Last_SQL_Errno: 1594
  92. Last_SQL_Error: Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MySQL code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave.
  93. Replicate_Ignore_Server_Ids:
  94. Master_Server_Id: 1
  95. Master_UUID: 793997ad-6398-11e6-a062-000d3aa1879f
  96. Master_Info_File: /var/lib/mysql/master.info
  97. SQL_Delay: 0
  98. SQL_Remaining_Delay: NULL
  99. Slave_SQL_Running_State:
  100. Master_Retry_Count: 86400
  101. Master_Bind:
  102. Last_IO_Error_Timestamp:
  103. Last_SQL_Error_Timestamp: 170506 19:50:05
  104. Master_SSL_Crl:
  105. Master_SSL_Crlpath:
  106. Retrieved_Gtid_Set:
  107. Executed_Gtid_Set:
  108. Auto_Position: 0
  109. Replicate_Rewrite_DB:
  110. Channel_Name:
  111. Master_TLS_Version:
  112. 1 row in set (0.00 sec)
  113.  
  114. 2017-05-06T19:02:52.678039Z 0 [Note] InnoDB: page_cleaner: 1000ms intended loop took 15056ms. The settings might not be optimal. (flushed=2 and evicted=0, during the time.)
  115. 2017-05-06T19:10:27.232249Z 2 [ERROR] Disk is full writing './gtc-relay-bin.000195' (Errcode: 15180656 - No space left on device). Waiting for someone to free space...
  116. 2017-05-06T19:10:27.232689Z 2 [ERROR] Retry in 60 secs. Message reprinted in 600 secs
  117. 2017-05-06T19:10:27.362769Z 18007 [Note] Aborted connection 18007 to db: 'unconnected' user: 'backup' host: 'localhost' (Got an error reading communication packets)
  118. 2017-05-06T19:20:27.244649Z 2 [ERROR] Disk is full writing './gtc-relay-bin.000195' (Errcode: 15180656 - No space left on device). Waiting for someone to free space...
  119. 2017-05-06T19:20:27.264895Z 2 [ERROR] Retry in 60 secs. Message reprinted in 600 secs
  120. 2017-05-06T19:30:27.417753Z 2 [ERROR] Disk is full writing './gtc-relay-bin.000195' (Errcode: 15180656 - No space left on device). Waiting for someone to free space...
  121. 2017-05-06T19:30:27.419691Z 2 [ERROR] Retry in 60 secs. Message reprinted in 600 secs
  122. 2017-05-06T19:40:27.864058Z 2 [ERROR] Disk is full writing './gtc-relay-bin.000195' (Errcode: 15180656 - No space left on device). Waiting for someone to free space...
  123. 2017-05-06T19:40:27.864800Z 2 [ERROR] Retry in 60 secs. Message reprinted in 600 secs
  124. 2017-05-06T19:49:40.947589Z 0 [Warning] Changed limits: max_open_files: 1024 (requested 5000)
  125. 2017-05-06T19:49:40.948741Z 0 [Warning] Changed limits: ta2017-05-06T19:49:49.121921Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
  126. 2017-05-06T19:49:49.121958Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
  127. 2017-05-06T19:49:49.122016Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
  128. 2017-05-06T19:49:53.758747Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
  129. 2017-05-06T19:49:53.759413Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
  130. 2017-05-06T19:49:53.759422Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
  131. 2017-05-06T19:49:53.775719Z 0 [Note] InnoDB: Waiting for purge to start
  132. 2017-05-06T19:49:53.828518Z 0 [Note] InnoDB: page_cleaner: 1000ms intended loop took 6720ms. The settings might not be optimal. (flushed=0 and evicted=0, during the time.)
  133. 2017-05-06T19:49:53.829030Z 0 [Note] InnoDB: 5.7.13 started; log sequence number 15543585458
  134. 2017-05-06T19:49:53.830064Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
  135. 2017-05-06T19:49:53.830640Z 0 [Note] Plugin 'FEDERATED' is disabled.
  136. 2017-05-06T19:49:53.912376Z 0 [Note] Recovering after a crash using gtc-slave-bin
  137. 2017-05-06T19:49:53.912476Z 0 [Note] Starting crash recovery...
  138. 2017-05-06T19:49:53.912579Z 0 [Note] Crash recovery finished.
  139. 2017-05-06T19:49:55.163266Z 0 [Note] InnoDB: Buffer pool(s) load completed at 170506 19:49:55
  140. 2017-05-06T19:49:58.665294Z 0 [Warning] Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key
  141. 2017-05-06T19:49:58.665321Z 0 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
  142. 2017-05-06T19:49:58.665330Z 0 [Note] - '127.0.0.1' resolves to '127.0.0.1';
  143. 2017-05-06T19:49:58.665368Z 0 [Note] Server socket created on IP: '127.0.0.1'.
  144. 2017-05-06T19:50:05.480733Z 0 [ERROR] Error in Log_event::read_log_event(): 'read error', data_len: 367, event_type: 2
  145. 2017-05-06T19:50:05.480765Z 0 [Warning] Error reading GTIDs from relaylog: -1
  146. 2017-05-06T19:50:05.620202Z 2 [Warning] Storing MySQL user name or password information in the master info repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START SLAVE; see the 'START SLAVE Syntax' in the MySQL Manual for more information.
  147. 2017-05-06T19:50:05.621524Z 1 [Warning] Slave SQL for channel '': If a crash happens this configuration does not guarantee that the relay log info will be consistent, Error_code: 0
  148. 2017-05-06T19:50:05.621572Z 1 [Note] Slave SQL thread for channel '' initialized, starting replication in log 'gtc-master-bin.000022' at position 74792622, relay log './gtc-relay-bin.000195' position: 37830249
  149. 2017-05-06T19:50:05.630830Z 2 [Note] Slave I/O thread for channel '': connected to master 'replicator@10.4.0.4:3306',replication started in log 'gtc-master-bin.000022' at position 74792800
  150. 2017-05-06T19:50:05.651022Z 1 [ERROR] Error in Log_event::read_log_event(): 'read error', data_len: 367, event_type: 2
  151. 2017-05-06T19:50:05.651066Z 1 [ERROR] Error reading relay log event for channel '': slave SQL thread aborted because of I/O error
  152. 2017-05-06T19:50:05.651117Z 1 [ERROR] Slave SQL for channel '': Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MySQL code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave. Error_code: 1594
  153. 2017-05-06T19:50:05.651138Z 1 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'gtc-master-bin.000022' position 74792622
  154. 2017-05-06T19:50:05.797632Z 0 [Note] Event Scheduler: Loaded 0 events
  155. 2017-05-06T19:50:05.797742Z 0 [Note] /usr/sbin/mysqld: ready for connections.
  156. Version: '5.7.13-0ubuntu0.16.04.2-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
  157. 2017-05-06T19:50:05.836873Z 4 [Note] Access denied for user 'root'@'localhost' (using password: NO)
  158.  
  159. mysql> stop slave;
  160. Query OK, 0 rows affected (0.06 sec)
  161. mysql> reset slave;
  162. Query OK, 0 rows affected (0.52 sec)
  163. mysql> change master to master_log_file='gtc-master-bin.000022',master_log_pos=74792622;
  164. Query OK, 0 rows affected (0.49 sec)
  165. mysql> start slave;
Add Comment
Please, Sign In to add comment
Public Pastes
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!