| # | Server Name | Port | Slave IO | Slave SQL | Seconds Behind | Position | Status | Last Error |
|---|---|---|---|---|---|---|---|---|
| 1 | NS13 | 3313 | Yes | No | N/A | mysql-bin.000272 | FAIL | 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 MariaDB 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. |
| 2 | NS7 | 3307 | No | Yes | N/A | mysql-bin.000028 | FAIL | Got fatal error 1236 from master when reading data from binary log: 'log event entry exceeded max_allowed_packet; Increase max_allowed_packet on master; the first event 'mysql-bin.000028' at 918169802, the last event read from 'mysql-bin.000028' at 918169802, the last byte read from 'mysql-bin.000028' at 918169821.' |
| 3 | NS17 | 3317 | Yes | No | N/A | mysql-bin.000013 | FAIL | 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 MariaDB 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. |