Bug 588090
Summary: | "Timeout error occurred trying to start MySQL Daemon." - When starting mysqld after increasing innodb_log_file_size | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Ahmed Medhat <ultimatetux> |
Component: | mysql | Assignee: | Tom Lane <tgl> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | qe-baseos-daemons |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 5.0 | CC: | byte, hhorak, wnefal+redhatbugzilla |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | mysql-5.0.95-2.el5 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-03-20 09:00:22 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
Ahmed Medhat
2010-05-02 15:51:24 UTC
The error is only cosmetic, so I can't get too excited about this. (FWIW, we did increase the timeout to 120 seconds in later versions.) Glad to hear it, but why make it statically defined in the first place ? Well, the example you give is a poor argument for making it user-configurable --- by the time the user figures out that he could have changed the timeout, his need will be gone. It's not like anybody reconfigures such a thing on a routine basis. Well, I agree its a weak debate but still would confuse someone less experienced sooner or later and takes him time to figure it out. But the bright side so far, setting the timeout to 120sec. in future releases makes more sense anyway and is enough considering the size of the DBs I am running, actually a value more than 60 fixed my problem while I had DBs with multiple hundred millions records. (In reply to comment #1) > The error is only cosmetic, so I can't get too excited about this. I think it's not only cosmetic because /var/lock/subsys/mysqld will not created. Consequently the init script is not able to stop, status etc. because it thinks mysqld is not running. I've realized, that this bug has been fixed as a part of bug #703476, which means the variable is increased to 120 in mysql-5.0.95-2.el5 and later releases. Therefore I'm closing this as CURRENTRELEASE. |