Mailing List
Home
Forum Home
MySQL General - General MySQL discussion
MaxDB - Everything about MaxDB, formerly known as SAP DB
MySQL++ - Programming with the C++ API to MySQL
MySQL on Win32 - Runing MySQL on Windows 9x/Me/NT/2000/XP
ODBC - ODBC with the MySQL Connector/ODBC driver
Java Help - Mostly related to the MySQL Connector/J driver
Perl - Perl support for MySQL with DBI and DBD::mysql
GUI - MySQL GUI Tools
Announcement
Subjects
• mysql openssl Question
• mysql:it 's a db not a dbms how it 's possible?!
• Does the binary log enabling affect the MySQL performances?
• Strange behavior, Table Level Permission
• FULLTEXT query format question
• Preventing Duplicate Entries
• Comparing and writing out BLOBS
• Executing MySQL Commands From Within C Program
• Can 't access mysql after kernel upgrade
• Mysql 4 0 Oracle Stored Procedure Trigger Conversion
• Downgrade Mysql from 4 to 3 23
• MySQL Cluster Software
• mysql test 4 1 fails with the gis test
• ERROR 2002: Can 't connect to local MySQL server through socket
• Getting Identity after INSERT
• Update one field with more fields from another table
• ERROR 1045: Access denied for user: 'root@localhost ' (Using
password: NO)
• mysql have same function mthod as Oracle decode()
 
Help! InnoDB won 't shut down...

Help! InnoDB won 't shut down...

2006-07-04       - By Sergei S

 Back
Hi,

I'm running mysql 4.0.16 on RedHat Linux.

I tried shutting down mysql more than 2 hours ago, by executing
'mysqladmin shutdown', and it's still running. Here is the end of the
log file /var/log/mysqld.log:

060624 09:31:54  mysqld started
060624  9:31:55  InnoDB: Data file /var/lib/mysql/ibdata2 did not
exist: new to be created
060624  9:31:55  InnoDB: Setting file /var/lib/mysql/ibdata2 size to 50 MB
InnoDB: Database physically writes the file full: wait...
060624  9:31:56  InnoDB: Started
/usr/sbin/mysqld-max: ready for connections.
Version: '4.0.16-Max'  socket: '/var/lib/mysql/mysql.sock'  port: 3306
060624 10:40:31  /usr/sbin/mysqld-max: Normal shutdown

060624 10:40:31  InnoDB: Starting shutdown...
060624 10:40:36  InnoDB: Shutdown completed
060624 10:40:36  /usr/sbin/mysqld-max: Shutdown Complete

060624 10:40:37  mysqld ended

060624 10:44:15  mysqld started
060624 10:44:23  InnoDB: Started
/usr/sbin/mysqld-max: ready for connections.
Version: '4.0.16-Max'  socket: '/var/lib/mysql/mysql.sock'  port: 3306
060704 12:16:25  /usr/sbin/mysqld-max: Normal shutdown

060704 12:16:25  InnoDB: Starting shutdown...


The processes mysqld_safe and mysqld-max are still running, both at
0.0% CPU time.

What's unusual and maybe relevant is that recently, 10 days ago to be
precise, is that the innodb tablespace file filled the entire external
drive, where the datadir variable was pointing to. So I had shut down
the database, moved all the files except the ibdata1 to the new
datadir on the internal drive, edited my.cnf and pointed the datadir
the new location, and set the innodb_data_file_path to include the old
file with the space rounded down to the nearest megabyte and the the
new file at the new location. The server came up and ran without any
apparent problems, as can be seen from the log file above. Here is the
data file path variable:

set-variable    =
innodb_data_file_path=/mnt/vault/mysql/ibdata1:129685M;/var/lib/mysql/ibdata2
:50M:autoextend

After that I recycled the server and everything was fine.

What to do now? Killing mysql is probably a bad idea...

Thanks in advance for your help,


Sergei

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/mysql?unsub=mysql@(protected)