Bug #12500 | Server crash during "stop slave" | ||
---|---|---|---|
Submitted: | 10 Aug 2005 15:01 | Modified: | 10 Apr 2006 8:07 |
Reporter: | Joerg Bruehe | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S1 (Critical) |
Version: | 5.0.* | OS: | MacOS (OS X (PPC + x86)) |
Assigned to: | Assigned Account | CPU Architecture: | Any |
[10 Aug 2005 15:01]
Joerg Bruehe
[29 Sep 2005 22:03]
Brian Aker
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.
[7 Mar 2006 15:01]
Joerg Bruehe
It re-occurs in several releases, on varying plytforms, with low frequency. Last issue: Release build of 5.0.19, on "osx-imac-x86", build of "cluster". It seems an autosave was not taken, at least none is logged. (Build finished 2006-03-05 09:30:21) ===== rpl_relayspace [ fail ] Errors are (from PATH/mysqltest-time) : mysqltest: At line NNN: query 'stop slave' failed: 2013: Lost connection to MySQL server during query (the last lines may be the most important ones) Ending Tests =====
[5 Apr 2006 21:55]
Elliot Murphy
Duplicate of bug#15671
[6 Apr 2006 6:36]
Greg Lehey
It's not yet clear that this bug is a duplicate of BUG#15171. It affects a different operating system, a different hardware platform, and a different test. Even if it is a duplicate, it may prove simpler to investigate the problem on this platform, since we've had some strangenesses with Apple.
[7 Apr 2006 4:12]
Greg Lehey
Investigated this problem on FreeBSD/x86 and Linux/amd64 (I don't have access to Linux/i686). I was unable to reproduce the problem; it ran in a loop 100 times without a failure. I have also not seen it fail under MacOS X/PPC, though I have not run it as long there. My best bet is that this problem no longer occurs; if it does, it will show up in the test suite, so this report should be closed.
[7 Apr 2006 5:08]
Greg Lehey
Just after sending the previous message, the MacOS X test failed with the same problems described in BUG#15671. I don't see any reason to associate this failure with the present bug report.
[7 Apr 2006 8:30]
Joerg Bruehe
Forgot to change the platform - observed first in 5.0.19, and repeated in 5.0.20, it occurs on OS X only, on both PPC and x86 CPUs ("powermacg5" + "osx-imac-x86").