[root@ALEPO-MONITORING-ILB ~]# mmm_control show
  db1(10.76.24.71) master/REPLICATION_FAIL. Roles:
  db2(10.76.24.77) master/ONLINE. Roles: writer(10.76.24.100)
  db3(10.76.24.83) slave/ONLINE. Roles:
  




MariaDB [(none)]> show slave status\G;
*************************** 1. row ***************************
                Slave_IO_State:
                   Master_Host: 10.76.24.77
                   Master_User: gtid
                   Master_Port: 3306
                 Connect_Retry: 60
               Master_Log_File: db2-binary.231674
           Read_Master_Log_Pos: 4
                Relay_Log_File: db1-relay.272125
                 Relay_Log_Pos: 58163882
         Relay_Master_Log_File: db2-binary.231673
              Slave_IO_Running: No
             Slave_SQL_Running: No
          Replicate_Rewrite_DB:
               Replicate_Do_DB:
           Replicate_Ignore_DB:
            Replicate_Do_Table:
        Replicate_Ignore_Table: crmdb.quartz_scheduler_state,aaadb.quartz_scheduler_state,mysql.gtid_slave_pos,aaadb.systemconfigurations,pcrfdb.quartz_scheduler_state,activemq.activemq_lock,activemq.activemq_acks
       Replicate_Wild_Do_Table:
   Replicate_Wild_Ignore_Table:
                    Last_Errno: 1594
                    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 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.
                  Skip_Counter: 0
           Exec_Master_Log_Pos: 125272617
               Relay_Log_Space: 209717208
               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: 1595
                 Last_IO_Error: Relay log write failure: could not queue event from master
                Last_SQL_Errno: 1594
                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 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.
   Replicate_Ignore_Server_Ids: 4, 5
              Master_Server_Id: 2
                Master_SSL_Crl:
            Master_SSL_Crlpath:
                    Using_Gtid: No
                   Gtid_IO_Pos:
       Replicate_Do_Domain_Ids:
   Replicate_Ignore_Domain_Ids:
                 Parallel_Mode: optimistic
                     SQL_Delay: 0
           SQL_Remaining_Delay: NULL
       Slave_SQL_Running_State:
              Slave_DDL_Groups: 12
Slave_Non_Transactional_Groups: 0
    Slave_Transactional_Groups: 1139522808
1 row in set (0.000 sec)