0

Gents, Have a mysql cluster down right now... in dev, but down nonetheless. This occurred after a hostname change on both nodes. 

InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock /usr/local/mysql/data/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 /usr/local/mysql/data/ibdata1, error: 11

MyISAM tables load fine...

What do I need to do to get the mysql back in order? thansk!

CMag
  • 707
  • 2
  • 11
  • 32

1 Answers1

1

There is a known issue with stale locks on NFS. Try this:

/etc/init.d/portmap restart
/etc/init.d/nfslock restart

See this bug report and this success report.

David Schwartz
  • 31,449
  • 2
  • 55
  • 84
  • no go, have tried this already :( – CMag Nov 05 '11 at 00:07
  • Then the lock is stuck on the NFS server. You can either restart the lock manager on the server or replace the files with copies of themselves. (`cp foo foo.bak; rm foo; mv foo.bak foo;` -- If paranoid, keep the copies and use 'mv' instead of 'rm'.) – David Schwartz Nov 05 '11 at 00:14