Bug #2145 mysqld becomes unreliable if unable to create a relay log when replic starts
Submitted: 17 Dec 2003 14:28 Modified: 17 Dec 2003 14:35
Reporter: Guilhem Bichot Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Replication Severity:S3 (Non-critical)
Version:4.0 OS:Any (all)
Assigned to: Guilhem Bichot CPU Architecture:Any

[17 Dec 2003 14:28] Guilhem Bichot 
Description:
See how-to-repeat

How to repeat:
Start the slave mysqld with
--relay-log=/alkjzlkdjzlkdj/aaa
assuming /alkjzlkdjzlkdj/ is a directory which does not exist on your system.
Then mysqld will say (in the error log) that it could not create the relay log,
and then any of STOP SLAVE, START SLAVE, RESET SLAVE, SHOW SLAVE STATUS will hang forever.

Suggested fix:
The cause is that when there is an error creating the relay log when replication starts, the code forgets to release a mutex.
Will fix this now.
[17 Dec 2003 14:35] Guilhem Bichot 
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

ChangeSet@1.1664.1.1, 2003-12-17 23:29:11+01:00, guilhem@mysql.com
which will be in 4.0.18