MySQL error

MySQL error

am 08.06.2009 16:02:18 von Malka Cymbalista

We are running MySQL 5.0.45 on a Linux machine.
Today, when I tried to go into MySQL via the command line, I got an error
message:
Can't connect to local MySQL server through socket
'/usr/local/mysql/tmp/mysql.sock'

The error log was full of the following messages:
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.

We stopped MySQL and started it again and everything seems to be working.
However, we would like to understand what happened.
The strange thing here is that we are not using InnoDB tables so we don't
understand why we are getting InnoDB errors and what it is trying to do
with the ibdata1 file.

We do have an ibdata1 file and ib_logfile files. Could it be that we are
using InnoDB tables and we don't realize it? Could we have made a mistake
somewhere? Is there a way to check this? Can we erase these files?

Any help will be appreciated.

Malki Cymbalista
Webmaster, Weizmann Institute of Science
Rehovot, Israel 76100
Internet: Malki.Cymbalista@weizmann.ac.il

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql-2@m.gmane.org

RE: MySQL error

am 08.06.2009 17:20:22 von Rolando Edwards

If you do not want to use InnoDB at all, add this line to /etc/my.cnf under=
the [mysqld] section
skip_innodb

Then do the following
service mysql stop
rm -f /var/lib/mysql/ibdata1 /var/lib/mysql/ib_logfile[01]
service mysql start

This will totally and cleanly disable InnoDB on the DB server

Give it a try !!!

Rolando A. Edwards
MySQL DBA (CMDBA)

155 Avenue of the Americas, Fifth Floor
New York, NY 10013
212-625-5307 (Work)
201-660-3221 (Cell)
AIM & Skype : RolandoLogicWorx
redwards@logicworks.net

-----Original Message-----
From: Malki.Cymbalista@weizmann.ac.il [mailto:Malki.Cymbalista@weizmann.ac.=
il]=20
Sent: Monday, June 08, 2009 10:02 AM
To: mysql@lists.mysql.com
Cc: shlomit.afgin@weizmann.ac.il
Subject: MySQL error

We are running MySQL 5.0.45 on a Linux machine.
Today, when I tried to go into MySQL via the command line, I got an error=20
message:
Can't connect to local MySQL server through socket=20
'/usr/local/mysql/tmp/mysql.sock'

The error log was full of the following messages:
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.

We stopped MySQL and started it again and everything seems to be working.=20
However, we would like to understand what happened.
The strange thing here is that we are not using InnoDB tables so we don't=20
understand why we are getting InnoDB errors and what it is trying to do=20
with the ibdata1 file.

We do have an ibdata1 file and ib_logfile files. Could it be that we are=20
using InnoDB tables and we don't realize it? Could we have made a mistake=
=20
somewhere? Is there a way to check this? Can we erase these files?

Any help will be appreciated.

Malki Cymbalista
Webmaster, Weizmann Institute of Science
Rehovot, Israel 76100
Internet: Malki.Cymbalista@weizmann.ac.il

--=20
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=3Dredwards@logicworks=
..net


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=3Dgcdmg-mysql-2@m.gmane.o rg