Bug 472222 - Mysqld first start timeouting when using InnoDB data files
Mysqld first start timeouting when using InnoDB data files
Product: Fedora
Classification: Fedora
Component: mysql (Show other bugs)
All Linux
medium Severity low
: ---
: ---
Assigned To: Tom Lane
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-11-19 09:13 EST by Tobias Reineke
Modified: 2013-07-02 23:20 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-07-14 10:43:48 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Tobias Reineke 2008-11-19 09:13:34 EST
Description of problem:
When in my.cnf is set something like:
innodb_data_file_path = ibdata1:2000M;ibdata2:10M:autoextend
The first start of mysqld takes a long time because these files need to be created. The STARTTIMEOUT of 30 seconds set in /etc/init.d/mysqld is too low for this, so the script fails.

Version-Release number of selected component (if applicable):

Steps to Reproduce:
1. yum install mysql
2. echo "innodb_data_file_path = ibdata1:2000M;ibdata2:10M:autoextend" >> /etc/my.cnf
3. service mysqld start

Maybe integrate a mechanism that mysqld gets more time when it starts the first time?
Comment 1 Tom Lane 2009-05-15 20:15:52 EDT
This failure seems fairly cosmetic to me --- the database will start anyway, you just get a gripe in the system log.  So I'm not excited about putting a lot of effort into avoiding it.  But it would be easy enough to just increase STARTTIMEOUT.  Do you think 60 seconds is enough?
Comment 2 Tobias Reineke 2009-05-19 10:17:47 EDT
The problem is that the script exits before the database is ready. If another service is started after mysql which needs a running database it will also get in trouble. But I think increasing STARTTIMEOUT is a good step.. we have already worked around the problem.
Comment 3 Bug Zapper 2009-06-09 23:18:30 EDT
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 4 Bug Zapper 2009-07-14 10:43:48 EDT
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.