Mariadb Replication broken Error in Log_event::read_log_event()

Mariadb Replication broken Error in Log_event::read_log_event()

2024-07-01 0:30:20 26 [ERROR] Error in Log_event::read_log_event(): 'Found invalid event in binary log', data_len: 414, event_type: 19
2024-07-01 0:30:20 26 [ERROR] Error reading relay log event: slave SQL thread aborted because of I/O error
2024-07-01 0:30:20 26 [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 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. Internal MariaDB error code: 1594
2024-07-01 0:30:20 26 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165370' position 3859
2024-07-01 0:30:20 26 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165370' at position 24017, master: 10.76.24.77:3306
2024-07-01 0:32:17 25 [ERROR] Could not use ./db1-relay.063683 for logging (error 11). Turning logging off for the whole duration of the MariaDB server process. To turn it on again: fix the cause, shutdown the MariaDB server and restart it.
2024-07-01 0:32:17 25 [ERROR] Slave I/O: Relay log write failure: could not queue event from master, Internal MariaDB error code: 1595
2024-07-01 0:32:17 25 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165371', position 4, master 10.76.24.77:3306

MariaDB [(none)]> show all slaves status\G;
Connection_name:
Slave_SQL_State:
Slave_IO_State:
Master_Host: 10.76.24.77
Master_User: gtid
Master_Port: 3306
Connect_Retry: 60
Master_Log_File: db2-binary.165371
Read_Master_Log_Pos: 4
Relay_Log_File: db1-relay.063683
Relay_Log_Pos: 21243
Relay_Master_Log_File: db2-binary.165370
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: 44704
Relay_Log_Space: 209692647
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: 0
Slave_Non_Transactional_Groups: 0
Slave_Transactional_Groups: 12
Retried_transactions: 0
Max_relay_log_size: 67108864
Executed_log_entries: 63
Slave_received_heartbeats: 0
Slave_heartbeat_period: 30.000
Gtid_Slave_Pos: 0-2-18649928423,1-1-1095522539,2-2-200638781,4-4-1258363533,5-5-242105