MySQL Bugs: #6830: slave error 'too many connections' corrupts slave relay log

Bug #6830	slave error 'too many connections' corrupts slave relay log
Submitted:	25 Nov 2004 19:57	Modified:	4 Jan 2005 18:03
Reporter:	Mark Swanson	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S1 (Critical)
Version:	4.0.18	OS:	Linux (Linux)
Assigned to:		CPU Architecture:	Any

Description:
Replication works fine, then one day the slave logs show: 
Slave I/O thread: error reconnecting to master 'x@x.com:3306': Error: 'Too many 
connections'  errno: 1040  retry-time: 60  retries: 86400 
041123 12:18:56  Slave I/O thread could not queue event from master 
041123 12:18:56  Slave I/O thread exiting, read up to log 'ns1-bin.013', position 14830410 
 
Next, comes the bad news (on the slave): 
 
Error in Log_event::read_log_event(): 'read error', data_len: 1388633, event_type: 2 
041125 13:44:41  Error reading relay log event: slave SQL thread aborted because of I/O 
error 
041125 13:44:41  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 running 'mysqlbinlog' 
on the relay log), a network problem, or a bug in the master's or slave's MySQL 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. Error_code: 0 
 
mysqlbinlog is not helpful. 
stopping/restarting the client doesn't help. 
 
The only way forward seems to be to shut down the production system to do a proper 
dump and initiate replication from scratch. (?) 
 
 
 

How to repeat:
not sure how to simulate the 'too many connections' error on the slave...

Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at
http://bugs.mysql.com/how-to-report.php

If you can provide more information, feel free to add it
to this bug and change the status back to 'Open'.

Thank you for your interest in MySQL.