InnoDB errors, Unable to lock ./ibdata1 [FIXED]

Some questions about managing server and products with artica.... Ask here...
First unread post • 22 posts • Page 1 of 31, 2, 3

InnoDB errors, Unable to lock ./ibdata1 [FIXED]

New postby chris_c_ » Thu Feb 16, 2012 3:44 am

System / MySQL Parameters / Events:
Code: Select all
/usr/sbin/mysqld: Table 'mysql.plugin' doesn't exist
120215 22:40:07 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
120215 22:40:07 InnoDB: The InnoDB memory heap is disabled
120215 22:40:07 InnoDB: Mutexes and rw_locks use GCC atomic builtins
120215 22:40:07 InnoDB: Compressed tables use zlib 1.2.3.3
120215 22:40:07 InnoDB: Using Linux native AIO
120215 22:40:07 InnoDB: Initializing buffer pool, size = 128.0M
120215 22:40:07 InnoDB: Completed initialization of buffer pool
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.
120215 22:40:07 InnoDB: Retrying to lock the first data file
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
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
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
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
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
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
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
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
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
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
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
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
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
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.


How to fix?
chris_c_
 
Posts: 793
Joined: Wed Oct 20, 2010 7:15 pm
Artica servers number: 1
Linux System: Debian
Technical skills: A Geek

Re: MySQL Events, InnoDB errors, Unable to lock ./ibdata1

New postby admin » Thu Feb 16, 2012 9:44 am

It seems that there is 2 mysql instances that try to use the same file...
User avatar
admin
Site Admin
 
Posts: 11287
Joined: Wed Oct 17, 2007 7:59 am
Location: France

Re: MySQL Events, InnoDB errors, Unable to lock ./ibdata1

New postby chris_c_ » Thu Feb 16, 2012 10:10 am

It looks like 4 mysqld running...?

Is it supposed to ??

Code: Select all
mysql      739  0.2  2.6 527312 54420 ?        Sl   05:05   0:00 /usr/sbin/mysqld --bind-address=127.0.0.1 --pid-file=/var/run/mysqld/mysqld.pid
mysql     1290  0.2  2.6 527312 54424 ?        Sl   05:05   0:00 /usr/sbin/mysqld --bind-address=127.0.0.1 --pid-file=/var/run/mysqld/mysqld.pid
mysql     3985  8.2 15.4 591356 321604 ?       SNl  Feb15 122:08 /usr/sbin/mysqld --bind-address=127.0.0.1 --pid-file=/var/run/mysqld/mysqld.pid
mysql     5926  0.0  2.6 527312 54428 ?        SNl  05:05   0:00 /usr/sbin/mysqld --bind-address=127.0.0.1 --pid-file=/var/run/mysqld/mysqld.pid
root      6076  0.0  0.0   1836   508 tty1     R+   05:05   0:00 grep mysqld
chris_c_
 
Posts: 793
Joined: Wed Oct 20, 2010 7:15 pm
Artica servers number: 1
Linux System: Debian
Technical skills: A Geek

Re: MySQL Events, InnoDB errors, Unable to lock ./ibdata1

New postby admin » Thu Feb 16, 2012 10:30 am

These are threaded mysql instance, it should come from the same process
do

Code: Select all
/etc/init.d/artica-postfix restart mysql
User avatar
admin
Site Admin
 
Posts: 11287
Joined: Wed Oct 17, 2007 7:59 am
Location: France

Re: MySQL Events, InnoDB errors, Unable to lock ./ibdata1

New postby chris_c_ » Thu Feb 16, 2012 1:02 pm

I did /etc/init.d/artica-postfix restart mysql

Code: Select all
Starting......: Mysql version.......:5.5.14

Starting......: Mysql my.cnf........: Total memory 2027MB
Starting......: Mysql 1 specific tokens
Starting......: Mysql binary version :505014
Starting......: [Note] Mysql return cached content
Starting......: Mysql Updating "/etc/mysql/my.cnf" success 854 bytes
Shutdown mysql daemon...
Stopping mysql...............: Already stopped
Stopping syslog-ng...........: Already stopped
Starting......: cannot found value for log_bin
Starting......: defautl value for log_bin ""
Starting......: cannot found value for log
Starting......: defautl value for log ""
Starting......: cannot found value for bind-address
Starting......: defautl valuStarting......: Mysql version.......:5.5.14

Starting......: Mysql my.cnf........: Total memory 2027MB
Starting......: Mysql 1 specific tokens
Starting......: Mysql binary version :505014
Starting......: [Note] Mysql return cached content
Starting......: Mysql Updating "/etc/mysql/my.cnf" success 854 bytes
e for bind-address ""
Starting......: tuning /etc/mysql/my.cnf
Starting......: Mysql my.cnf........:/etc/mysql/my.cnf
Starting......: Mysql init.d........:/etc/init.d/mysql
Starting......: Mysql Pid path......:/var/run/mysqld/mysqld.pid
Starting......: Mysql log-bin.......:
Starting......: datadir.............:/var/lib/mysql
Starting......: syslog..............:/var/log/syslog
Starting......: socket..............:/var/run/mysqld/mysqld.sock
Starting......: user................:mysql
Starting......: pid-file............:/var/run/mysqld/mysqld.pid
Starting......: LOGS ENABLED........:0
Starting......: Daemon..............:/usr/sbin/mysqld
Starting......: Bind address........:127.0.0.1
Starting......: Mysql Checking :/var/lib/mysql/mysql/host.frm
Starting......: Mysql using innodb file per table feature
Starting......: Mysql (timeout!!!)
Starting......: Mysql "/usr/sbin/mysqld --bind-address=127.0.0.1 --pid-file=/var/run/mysqld/mysqld.pid  >/var/log/mysql/mysql.start.log 2>&1 &"
Starting......: Mysql failed with command line /usr/sbin/mysqld --bind-address=127.0.0.1 --pid-file=/var/run/mysqld/mysqld.pid  >/var/log/mysql/mysql.start.log 2>&1 &
Starting......: cannot found value for log_bin
Starting......: defautl value for log_bin ""
Starting......: cannot found vStarting......: Mysql version.......:5.5.14

Starting......: Mysql my.cnf........: Total memory 2027MB
Starting......: Mysql 1 specific tokens
Starting......: Mysql binary version :505014
Starting......: [Note] Mysql return cached content
Starting......: Mysql Updating "/etc/mysql/my.cnf" success 854 bytes
alue for log
Starting......: defautl value for log ""
Starting......: cannot found value for bind-address
Starting......: defautl value for bind-address ""
Starting......: tuning /etc/mysql/my.cnf
Starting......: Mysql my.cnf........:/etc/mysql/my.cnf
Starting......: Mysql init.d........:/etc/init.d/mysql
Starting......: Mysql Pid path......:/var/run/mysqld/mysqld.pid
Starting......: Mysql log-bin.......:
Starting......: datadir.............:/var/lib/mysql
Starting......: syslog..............:/var/log/syslog
Starting......: socket..............:/var/run/mysqld/mysqld.sock
Starting......: user................:mysql
Starting......: pid-file............:/var/run/mysqld/mysqld.pid
Starting......: LOGS ENABLED........:0
Starting......: Daemon..............:/usr/sbin/mysqld
Starting......: Bind address........:127.0.0.1
Starting......: Mysql Checking :/var/lib/mysql/mysql/host.frm
Starting......: Mysql using innodb file per table feature
Starting......: Mysql (timeout!!!)
Starting......: Mysql "/usr/sbin/mysqld --bind-address=127.0.0.1 --pid-file=/var/run/mysqld/mysqld.pid  >/var/log/mysql/mysql.start.log 2>&1 &"
Starting......: Mysql failed with command line /usr/sbin/mysqld --bind-address=127.0.0.1 --pid-file=/var/run/mysqld/mysqld.pid  >/var/log/mysql/mysql.start.log 2>&1 &



This is the result in the mysql events:

Code: Select all
/usr/sbin/mysqld: Table 'mysql.plugin' doesn't exist
120216 7:56:07 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
120216 7:56:07 InnoDB: The InnoDB memory heap is disabled
120216 7:56:07 InnoDB: Mutexes and rw_locks use GCC atomic builtins
120216 7:56:07 InnoDB: Compressed tables use zlib 1.2.3.3
120216 7:56:07 InnoDB: Using Linux native AIO
120216 7:56:07 InnoDB: Initializing buffer pool, size = 128.0M
120216 7:56:07 InnoDB: Completed initialization of buffer pool
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.
120216 7:56:07 InnoDB: Retrying to lock the first data file
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
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
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
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
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
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
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
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
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
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
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
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
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
chris_c_
 
Posts: 793
Joined: Wed Oct 20, 2010 7:15 pm
Artica servers number: 1
Linux System: Debian
Technical skills: A Geek

Re: MySQL Events, InnoDB errors, Unable to lock ./ibdata1

New postby Friend7 » Thu Feb 16, 2012 2:10 pm

@chris_c_

see here:
http://forum.artica.fr/viewtopic.php?f=10&t=5196

Code: Select all
/etc/init.d/artica-postfix restart


Code: Select all
/etc/init.d/artica-postfix restart mysql
Best Regards,
Friend7
 
Posts: 2373
Joined: Sun Feb 06, 2011 3:41 pm
Artica servers number: 1
Linux System: Debian
Technical skills: A newbee

Re: MySQL Events, InnoDB errors, Unable to lock ./ibdata1

New postby chris_c_ » Thu Feb 16, 2012 5:30 pm

Hi Friend7,

The steps you gave - restart artica, then restart mysql - didn't work. It still gives the error about unable to lock ./ibdata1

Any suggestion what else to try ??
chris_c_
 
Posts: 793
Joined: Wed Oct 20, 2010 7:15 pm
Artica servers number: 1
Linux System: Debian
Technical skills: A Geek

Re: MySQL Events, InnoDB errors, Unable to lock ./ibdata1

New postby Friend7 » Thu Feb 16, 2012 9:08 pm

Did you read this post?

http://forum.artica.fr/viewtopic.php?f=10&t=5196

Hello abolinhas,

This issue was solved by Artica.
I did not do anything.


just add your DBs into instance and Artica will fix it.

or

do:

Code: Select all
# hostname -f
> server.domain.com

# cat /var/lib/mysql/server.err

# cat /var/lib/mysql-1/error.log

# cat /var/lib/mysql-2/error.log

# cat /var/lib/mysql-3/error.log

# cat /var/lib/mysql-4/error.log
Best Regards,
Friend7
 
Posts: 2373
Joined: Sun Feb 06, 2011 3:41 pm
Artica servers number: 1
Linux System: Debian
Technical skills: A newbee

Re: MySQL Events, InnoDB errors, Unable to lock ./ibdata1

New postby admin » Fri Feb 17, 2012 1:12 am

have you created a mysql instance ?
User avatar
admin
Site Admin
 
Posts: 11287
Joined: Wed Oct 17, 2007 7:59 am
Location: France

Re: MySQL Events, InnoDB errors, Unable to lock ./ibdata1

New postby Friend7 » Fri Feb 17, 2012 1:26 am

Confirm that you have this file.

/var/lib/mysql-1/ibdata1
Best Regards,
Friend7
 
Posts: 2373
Joined: Sun Feb 06, 2011 3:41 pm
Artica servers number: 1
Linux System: Debian
Technical skills: A newbee

Next

22 posts • Page 1 of 31, 2, 3

Return to Management console

Who is online

Users browsing this forum: No registered users and 2 guests