Linode Forum
Linode Community Forums
 FAQFAQ    SearchSearch    MembersMembers      Register Register 
 LoginLogin [ Anonymous ] 
Post new topic  Reply to topic
Author Message
PostPosted: Fri Jun 03, 2011 12:05 am 
Offline
Junior Member
User avatar

Joined: Wed Oct 20, 2010 7:10 pm
Posts: 36
Location: Sebastopol, CA
Hi,

I recently started experimenting with creating a MySQL DB using InnoDB tables. I recreated one of my existing databases and then altered the tables to be InnoDB. This was about two weeks ago, and I have done little since.

I noticed today that my /var/log/mysql/error.log file was filling up the volume at about 1.2 GB. The following lines are repeated ad nauseam.

Code:
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.


Any ideas of how to fix this?

I deleted the error.log file (and recreated it), but have not been able to reclaim the disk space. I will be restarting the mysql service when there is less load on the server in a couple hours, and hope that will do it. I also deleted the entire cloned DB with InnoDB tables.

Thanks, Josh


Top
   
 Post subject:
PostPosted: Fri Jun 03, 2011 2:37 am 
Offline
Junior Member
User avatar

Joined: Wed Oct 20, 2010 7:10 pm
Posts: 36
Location: Sebastopol, CA
Running the following did not seem to immediately help release disk space:

Code:
sudo service mysql restart


Top
   
 Post subject:
PostPosted: Fri Jun 03, 2011 3:28 am 
Offline
Senior Member

Joined: Fri May 02, 2008 8:44 pm
Posts: 1121
Just an idea: You might have a zombie process that is holding onto your InnoDB data file as well as the error log. Stop the MySQL server, and run ps aux to check if there are any remaining MySQL processes. Kill them all before starting MySQL again.


Top
   
 Post subject:
PostPosted: Fri Jun 03, 2011 10:09 am 
Offline
Senior Member
User avatar

Joined: Tue May 26, 2009 3:29 pm
Posts: 1691
Location: Montreal, QC
Also, make sure logrotated is working.


Top
   
 Post subject:
PostPosted: Sat Jun 04, 2011 8:26 pm 
Offline
Junior Member
User avatar

Joined: Wed Oct 20, 2010 7:10 pm
Posts: 36
Location: Sebastopol, CA
Thanks using ps aux and killing the remaining processes worked.

The other mysql logs are rotating, just not this error. I will check in to that. Any ideas where to look?

Thanks, Josh


Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic


Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
Jump to:  
RSS

Powered by phpBB® Forum Software © phpBB Group