Red Hat Bugzilla – Bug 146867
mysqld init script ignores configured data directory
Last modified: 2013-07-02 23:03:51 EDT
Description of problem:
The data directory configured in /etc/my.cnf is ignored by the
mysqld init script during its startup checks, which assume a data
directory in /var/lib/mysql. If the my.cnf directory is elsewhere,
the checks don't do the required thing and consequently mysqld
fails to start. I get this:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Set the data directory (only) to be different from the default
2. put a valid mysql data directory at the new locn.
3. try to start mysql using service mysqld start
4. watch it fail!
Initializing MySQL database: [ OK ]
*** glibc detected *** double free or corruption (!prev): 0x08cd94a0
Timeout error occurred trying to start MySQL Daemon.
Starting MySQL: [FAILED]
This is repaired as of development tip (mysql 4.1.7-6 and up)
*** This bug has been marked as a duplicate of 76051 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.