[Hardy SRU] dash bug causes mysqld_safe to spin at 100% CPU
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MariaDB |
Fix Released
|
Medium
|
Kristian Nielsen | ||
Percona Server moved to https://jira.percona.com/projects/PS |
Invalid
|
Medium
|
Ignacio Nin | ||
5.1 |
Invalid
|
Undecided
|
Ignacio Nin | ||
5.5 |
Invalid
|
Medium
|
Ignacio Nin | ||
dash (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
mysql-5.1 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Symptoms are: After mysql server upgrades + restarts the old mysqld_safe keeps running and consumes 100% cpu, strace shows:
wait4(4294967295, 0x7fffb3b3d59c, 0, NULL) = -1 ECHILD (No child ...
wait4(4294967295, 0x7fffb3b3d59c, 0, NULL) = -1 ECHILD (No child ...
wait4(4294967295, 0x7fffb3b3d59c, 0, NULL) = -1 ECHILD (No child ...
For more info see the dupes, particularily bug 105457. Does not happen always, for reliable test case see below.
This is a bug (race condition) in dash, partly fixed by http://
TEST CASE: Script in the commit message (link above). Allows to reproduce this always, even on Karmic still.
(Proposed fix of using #!/bin/bash instead of #!/bin/sh is not as straigtforward as expected. bash called as sh goes into sh compatibility mode, called as bash it may behave subtle differently)
NOTES: mysqld_safe was replaced by an upstart job in Lucid. But Hardy has support for 3 more years, justifiying a fix.
tags: | added: patch |
Changed in maria: | |
status: | New → In Progress |
assignee: | nobody → Kristian Nielsen (knielsen) |
importance: | Undecided → Medium |
Changed in maria: | |
milestone: | none → 5.1 |
affects: | mysql-dfsg-5.0 (Ubuntu) → mysql-5.1 (Ubuntu) |
Changed in percona-server: | |
importance: | Undecided → Medium |
tags: | added: testcase |
description: | updated |
Changed in dash (Ubuntu): | |
status: | New → Invalid |
Thanks for the patch, can you follow the process outlined by:
https:/ /wiki.ubuntu. com/StableRelea seUpdates
thanks
chuck