Bug #8811 mysqld will not stop on Mac OS X if configured as replication slave

• Submitted: 25 Feb 2005 16:45
• Modified: 31 Oct 2005 23:33
• Reporter: Shawn Hogan
• Status: Closed
• Category: MySQL Server
• Severity: S3 (Non-critical)
• Version: 4.1.10
• OS: MacOS (Mac OS X 10.3.8)
• Assigned to: Jim Winstead
• CPU Architecture: Any

[25 Feb 2005 16:45] Shawn Hogan

Description:
The mysqld process does not respond to the kill command, so the mysql.server script is not able to shut down the process.  This of course also causes a problem if you shutdown or reboot the system, as the tables are open on a system shutdown.

This was checked on 3 machines running Mac OS X Server 10.3.8 and one running Mac OS X Desktop 10.3.8

This was also mentioned by someone else on the list:

http://lists.mysql.com/mysql/180014

How to repeat:
Setup a simple slave like so:

server-id = 10
master-host = 10.0.0.1
master-user = repl

Then try to kill the mysqld process with the kill function (as root of course).

Suggested fix:
Manually shutdown mysqld with mysqladmin shutdown when needed.  Killing the slave threads manually or using mysqladmin stop-slave first does not help.

[11 Sep 2005 22:00] Lachlan Mulcahy

Verified with 5.0.11 on Max OSX 10.4.2 -- kill command succeeds if slave options are removed but fails if they are put in as specified.

[15 Sep 2005 18:49] Jim Winstead

This is probably just another manifestation of the problem in Bug #9712 and Bug #8731.

[31 Oct 2005 23:33] Jim Winstead

The fix for Bug #8731 also fixed this problem, so it will be fixed as of 4.1.16.