Error "InnoDB: Unable to lock <db file>, error: 11" and "InnoDB: using the same InnoDB data or log files. " when trying to start mysqld service or mysql cluster resource in RHEL

Solution Verified - Updated -

Issue

  • A mysql resource in a cluster service fails to start:
  Nov 14 17:29:27 rgmanager [mysql] Starting Service mysql:myDatabase
  Nov 14 17:29:27 rgmanager [mysql] Looking For IP Address > Succeed -  IP Address Found
  Nov 14 17:29:42 rgmanager [mysql] Starting Service mysql:myDatabase > Failed - Timeout Error
  • This message appears in /var/log/mysqld.log file:
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11</code>
  • Cluster failover of mysqld does not happen as expected. I can start the service and relocate it, but when I fence a node the service fails to start.

Environment

  • Red Hat Enterprise Linux (RHEL) 5 or 6
    • As a standalone server, or
    • Using the High Availability Add On
      • Cluster service in /etc/cluster/cluster.conf containing a mysql resource
  • mysql-server package provided by Red Hat

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.