Bug 172426
Summary: | Timeout error occurred trying to start MySQL daemon | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Remy Chibois <rchibois> |
Component: | mysql | Assignee: | Tom Lane <tgl> |
Status: | CLOSED RAWHIDE | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | CC: | deisenst, hhorak, redhat-bugzilla |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-11-15 04:06:08 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Remy Chibois
2005-11-04 10:14:35 UTC
I've put a loop similar to this into the latest updates (4.1.15 and 5.0.15). Not sure why the issue hasn't come up before; perhaps recent versions of MySQL take longer to shut down than they used to? Thanks for this fix. Concerning shutdown/restart speed, the machine was not that powerfull (an old PIII) and somewhat loaded. This might explain this "special" case. Does this affect FC3 as well? I think the Fedora Legacy guys already took care of it --- see bug #152531 Fedora Legacy guys have not taken care of this bug. At this moment, Legacy maintains RHL7.3, RHL9, FC1 and FC2. FC3 is not on the Fedora Legacy project's maintanence list yet. I'll open a new bug for this. Thanks, Tom. |