Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

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!

share|improve this question
    
What filesystem are these files stored on? –  David Schwartz Nov 4 '11 at 23:47
    
in dev they are on NFS... mysql user has right to access the log files, etc –  CMag Nov 4 '11 at 23:48

1 Answer 1

up vote 1 down vote accepted

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.

share|improve this answer
    
no go, have tried this already :( –  CMag Nov 5 '11 at 0: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 5 '11 at 0:14
    
wow... ok! Will give that a shot! thanks! –  CMag Nov 5 '11 at 0:20

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.