If MySQL or its associated daemon process cannot start,
or a post-startup INSTALL PLUGIN
statement fails,
look at the MySQL error log (usually named
and located in the MySQL machine_name
.errdata
directory) for the
detailed error message.
The log is in chronological order, so look at the end of the file.
Try to resolve the problem based on other information in the
message.
Error Condition or Message | Possible Solution |
---|---|
Can't open shared library |
Diagnose the cause from the following message details. |
API version for STORAGE ENGINE plugin is too different |
The version of the Plugin is not compatible with the version of the MySQL server. Consult the compatibility chart . |
No such file or directory |
Check that the file ha_innodb_plugin.so
or .dll
was copied to the
correct location. Confirm that you specified the right file name
(ha_innodb_plugin.so
or .dll
for the library from the InnoDB web site;
ha_innodb_plugin.so
or .dll
for the library supplied along with
MySQL 5.1.38 and up.)
|
Permission denied |
Check that the directory and file access
permissions are set properly, or change them using
chmod on Unix-like systems . The
mysqld process must have permission
to read (r ) the file
ha_innodb_plugin.so and to access files
(x ) in the plugin directory. |
wrong ELF class
or any other message |
Ensure that ha_innodb_plugin.so is
for the same system platform as
mysqld . In particular, note
that a 32-bit mysqld is unable to
load a 64-bit plugin, and vice versa. Be sure to
download an InnoDB Plugin that is compatible with your
platform. |
The Information Schema tables are themselves plugins to the MySQL server, but they depend on having the InnoDB storage engine plugin installed as well. These tables will appear to be empty if the storage engine is not installed.
This is the User’s Guide for InnoDB Plugin 1.0.6 for MySQL 5.1, generated on March 4, 2010 (rev 673:680M).