Hello, trying to save hd-space we configured a 4.0.17-Replicationclient in my.cnf as shown below:
max_relay_log_size = 250M relay_log_space_limit = 1000M After restarting Mysql a new relay_log was created correctly every 250M, so we thought everything was working well. The disaster occured when the relay_log_space_limit of 1.000M was reached cause replication stopped right at this moment. The error message leaded us into a wrong direction, so we didn't recognize immediately that the "space_limit" was the reason of our problems. Below you see the error message we found in the mysql.error-log: ========= Slave: 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 r unning 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MySQL code. If you want to che ck 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: 0 ========= Finally we commented the entries out, re-synchronised the databases manually and restarted replication. The ultimate question for us now is "why didn't mysql delete old relay-logs to get space to continue logging, like it is described in the Mysql documentattion"? Is this a bug and, if so, is it solved in the actual version of mysql 4.0? Greetings Lutz Maibach EasyCom GmbH -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
