[Bug 675185] Re: [Hardy SRU] dash bug causes mysqld_safe to spin at 100% CPU

Jakob Unterwurzacher jakobunt at gmail.com
Thu Sep 20 08:03:12 UTC 2012


** Description changed:

  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://git.kernel.org/?p=utils/dash/dash.git;a=commit;h=3800d4934391b144fd261a7957aea72ced7d47ea
  . This fixes the test case and mysqld_safe, but introduces another
  regression: http://eeek.borgchat.net/lists/dash/msg00268.html (patch for
  that in the thread)
  
  TEST CASE: Script in the commit message (link above). Allows to
  reproduce this always, even on Karmic still.
  
- SRU JUSTIFICATION: Obviously safe patch.
- 
- PATCH: Attached, run mysqld_safe in bash instead of dash.
- 
- REGRESSION POTENTIAL: Minimal. 1) Bash is a superset of dash. 2) Before
- dash became the default sh, bash was used, we just revert that change.
+ (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.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to dash in Ubuntu.
https://bugs.launchpad.net/bugs/675185

Title:
  [Hardy SRU] dash bug causes mysqld_safe to spin at 100% CPU

Status in Maria:
  Fix Released
Status in Percona Server with XtraDB:
  Invalid
Status in Percona Server 5.1 series:
  Invalid
Status in Percona Server 5.5 series:
  Invalid
Status in “dash” package in Ubuntu:
  New
Status in “mysql-5.1” package in Ubuntu:
  Confirmed

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://git.kernel.org/?p=utils/dash/dash.git;a=commit;h=3800d4934391b144fd261a7957aea72ced7d47ea
  . This fixes the test case and mysqld_safe, but introduces another
  regression: http://eeek.borgchat.net/lists/dash/msg00268.html (patch
  for that in the thread)

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maria/+bug/675185/+subscriptions




More information about the foundations-bugs mailing list