Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 110593 - InnoDB warnings in /var/log/mysqld.log
InnoDB warnings in /var/log/mysqld.log
Product: Fedora
Classification: Fedora
Component: mysql (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Patrick Macdonald
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2003-11-21 11:22 EST by Joseph Tate
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-11-21 13:01:13 EST
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 Joseph Tate 2003-11-21 11:22:51 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5)

Description of problem:
When I start mysqld, the following appears in my /var/log/mysqld.log
Cannot initialize InnoDB as 'innodb_data_file_path' is not set.
If you do not want to use transactional InnoDB tables, add a line
to the [mysqld] section of init parameters in your my.cnf
or my.ini. If you want to use InnoDB tables, add to the [mysqld]
section, for example,
innodb_data_file_path = ibdata1:10M:autoextend
But to get good performance you should adjust for your hardware
the InnoDB startup options listed in section 2 at
/usr/libexec/mysqld: ready for connections

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

How reproducible:

Steps to Reproduce:
1. service mysqld stop
2. service mysqld start


Actual Results:  See above.

Expected Results:
No message about InnoDB in the log.

Additional info:
my.conf is the default installed.  Adding skip-innodb to the [mysqld]
section stops the warning message.  However it would disable any
innodb databases if I had any.
Comment 1 Patrick Macdonald 2003-11-21 13:01:13 EST
These are just warning/informational messages that have been
in MySQL for some time.  MySQL is built with InnoDB support and the
user has to do a little setup work.

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