Bug #37841 rpl.rpl_row_sp007_innodb/row failed to start mysqld 0
Submitted: 3 Jul 2008 17:03 Modified: 6 Aug 2008 15:08
Reporter: Alexander Nozdrin Email Updates:
Status: Duplicate Impact on me:
None 
Category:Tests: Replication Severity:S3 (Non-critical)
Version:6.0-BK OS:Any
Assigned to: Assigned Account CPU Architecture:Any
Tags: pushbuild, reason unknown, test failure

[3 Jul 2008 17:03] Alexander Nozdrin 
Description:
rpl.rpl_row_sp007_innodb 'row' [ fail ]

ERROR: Failed to start slave mysqld 0

How to repeat:
https://intranet.mysql.com/secure/pushbuild/xref.pl?testname=rpl.rpl_row_sp007_innodb+
[7 Jul 2008 19:17] Sven Sandberg 
Likely a dup of BUG#37944
[6 Aug 2008 15:08] Sven Sandberg 
The message "failed to start mysqld" just indicates that a server has crashed. It is usually not related to a specific test. The xref page above likely does not identify a unique error: many errors can have these symptoms. We have several bugs reported where the symptom is "failed to start mysqld".

So I'm closing this as a duplicate (of, e.g., Bug#37714, BUG#38555, or Bug#38286).

If you think that a particular failure is different from any of these, please provide:
 - an url to the push that fails (identifying not only the tree, but also the push number)
 - the host where it fails (e.g., sapsrv1)
 - the suite where it fails (e.g., ps_row)