Differences

This shows you the differences between two versions of the page.

--- wiki:mysql_mariadb_troubleshooting [2025/10/10 09:32] – add mariadb won't start antisa
+++ wiki:mysql_mariadb_troubleshooting [2026/01/16 10:58] (current) – add master replication from impossible position antisa
@@ Line 1: / Line 1: @@
-{{tag>mysql mariadb}}
+{{tag>mysql mariadb replication}}
 ====== mysql/mariadb troubleshooting ======
@@ Line 30: / Line 30: @@
 ===== mariadb won't start =====
 If starting with ''systemctl start mariadb'' times out, try checking if the instance is part of Galera cluster. It might be that other instances need to be started as well.
+===== [ERROR] Error reading packet from server: Client requested master to start replication from impossible position ( server_errno=1236)  =====
+  replication from impossible position; the first event 'mysql-bin.004225' at 14311389, the last event read from 'mysql-bin.004225' at 4, the last byte read from 'mysql-bin.004225' at 4.'
+Happened when master server crashed. The error above showed on slave. Solution is to start replication from the next binlog file after the one in error above.
+First stop slave:
+  MariaDB [(none)]> STOP SLAVE;
+Change binlog and start slave:
+  MariaDB [(none)]> CHANGE MASTER TO MASTER_LOG_FILE='mysql-bin.004226', MASTER_LOG_POS=4;
+  MariaDB [(none)]> START SLAVE;
+  MariaDB [(none)]> show slave status \G
 ====== Tested on ======
@@ Line 38: / Line 55: @@
 ====== References ======
   * https://mariadb.com/docs/server/server-management/starting-and-stopping-mariadb/what-to-do-if-mariadb-doesnt-start
+  * https://mariadb.com/resources/blog/client-requested-master-to-start-replication-from-impossible-position/
+  * https://serverfault.com/questions/1184180/mysql-replication-1236-requested-master-to-start-replication-from-impossible-pos