Bug #27714 mysql_install_db fails with kernel 2.4
Submitted: 9 Apr 2007 11:39 Modified: 4 Jun 2007 8:50
Reporter: Christian Hammers (Silver Quality Contributor) (OCA) Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S2 (Serious)
Version:5.0.36, 5.0.38 OS:Linux (Debian GNU/Linux)
Assigned to:
Tags: qc

[9 Apr 2007 11:39] Christian Hammers
Description:
Hello

Debian 3.1 contains both kernel 2.4 and 2.6 while and our new Debian 4.0 has only kernel 2.6. While testing the upgrade process we found that when kernel 2.4 is still booted, mysql hangs during installation and thus blocks the rest of the upgrade. I cannot reproduce it as my Desktop does not boot with kernel 2.4 but two users confirmed the behaviour.

Could you have a quick look at this one and tell me if there's an easy fix available or if I should upload a last-minute version that just exists the installation until the user has rebootet?

thanks,

-christian-

How to repeat:
Install MySQL >= 5.0.36 on a Linux system with kernel 2.4.

Two strace's, one from kernel 2.4 and one from kernel 2.6 on the same system
are attached.

Suggested fix:
-
[9 Apr 2007 11:40] Christian Hammers
Broken installation using kernel 2.4

Attachment: mysql_install.2.4.27.log (text/x-log), 122.14 KiB.

[9 Apr 2007 11:40] Christian Hammers
Working installation using kernel 2.6

Attachment: mysql_install.2.6.18.log (text/x-log), 122.79 KiB.

[9 Apr 2007 11:42] Christian Hammers
The stace were produced using "strace -f /usr/bin/mysql_install_db --rpm"
[9 Apr 2007 11:42] Christian Hammers
The stace were produced using "strace -f /usr/bin/mysql_install_db --rpm"
[4 May 2007 8:50] Valeriy Kravchuk
Thank you for a problem report. Please, check if this is similar to bug #27970. I mean, do you have different NPTL versions with different kernels booted?
[4 Jun 2007 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".