mysqld crashed websites

coolemail · **Posted:** Fri Jun 08, 2012 7:54 am

Can someone help? We had an issue where something with mysqld prevented SSH access to the server. When we eventually got it, logs on the server show things like:

Quote:

InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
120608 12:31:18 InnoDB: Unable to open the first data file
InnoDB: Error in opening ./ibdata1
120608 12:31:18 InnoDB: Operating system error number 11 in a file operation.
InnoDB: Error number 11 means 'Resource temporarily unavailable'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/ ... codes.html
120608 12:31:18 InnoDB: Could not open or create data files.
120608 12:31:18 InnoDB: If you tried to add new data files, and it failed here,
120608 12:31:18 InnoDB: you should now edit innodb_data_file_path in my.cnf back
120608 12:31:18 InnoDB: to what it was, and remove the new ibdata files InnoDB created
120608 12:31:18 InnoDB: in this failed attempt. InnoDB only wrote those files full of
120608 12:31:18 InnoDB: zeros, but did not yet use them in any way. But be careful: do not
120608 12:31:18 InnoDB: remove old data files which contain your precious data!
120608 12:31:18 [ERROR] Plugin 'InnoDB' init function returned error.
120608 12:31:18 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
120608 12:31:18 [ERROR] Unknown/unsupported storage engine: InnoDB
120608 12:31:18 [ERROR] Aborting

120608 12:31:18 [Note] /usr/libexec/mysqld: Shutdown complete

120608 12:31:18 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
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

...

120608 12:32:01 InnoDB: Unable to open the first data file
InnoDB: Error in opening ./ibdata1
120608 12:32:01 InnoDB: Operating system error number 11 in a file operation.
InnoDB: Error number 11 means 'Resource temporarily unavailable'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/ ... codes.html
120608 12:32:01 InnoDB: Could not open or create data files.
120608 12:32:01 InnoDB: If you tried to add new data files, and it failed here,
120608 12:32:01 InnoDB: you should now edit innodb_data_file_path in my.cnf back
120608 12:32:01 InnoDB: to what it was, and remove the new ibdata files InnoDB created
120608 12:32:01 InnoDB: in this failed attempt. InnoDB only wrote those files full of
120608 12:32:01 InnoDB: zeros, but did not yet use them in any way. But be careful: do not
120608 12:32:01 InnoDB: remove old data files which contain your precious data!
120608 12:32:01 [ERROR] Plugin 'InnoDB' init function returned error.
120608 12:32:01 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
120608 12:32:01 [ERROR] Unknown/unsupported storage engine: InnoDB
120608 12:32:01 [ERROR] Aborting

120608 12:32:01 [Note] /usr/libexec/mysqld: Shutdown complete

120608 12:32:01 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

We then had to reboot the router and then the log is now showing:

Quote:

120608 12:47:24 [Note] /usr/libexec/mysqld: Normal shutdown

120608 12:47:26 [Note] Event Scheduler: Purging the queue. 0 events
120608 12:47:28 [Warning] /usr/libexec/mysqld: Forcing close of thread 3590735 user: 'tortix'

120608 12:47:28 InnoDB: Starting shutdown...
120608 12:51:04 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
120608 12:51:05 [Note] Plugin 'FEDERATED' is disabled.
120608 12:51:05 InnoDB: The InnoDB memory heap is disabled
120608 12:51:05 InnoDB: Mutexes and rw_locks use GCC atomic builtins
120608 12:51:05 InnoDB: Compressed tables use zlib 1.2.3
120608 12:51:05 InnoDB: Using Linux native AIO
120608 12:51:05 InnoDB: Initializing buffer pool, size = 128.0M
120608 12:51:05 InnoDB: Completed initialization of buffer pool
120608 12:51:05 InnoDB: highest supported file format is Barracuda.
120608 12:51:07 InnoDB: Waiting for the background threads to start
120608 12:51:08 InnoDB: 1.1.8 started; log sequence number 20163833365
120608 12:51:08 [Note] Server hostname (bind-address): '(null)'; port: 3306
120608 12:51:08 [Note] - '(null)' resolves to '::';
120608 12:51:08 [Note] - '(null)' resolves to '0.0.0.0';
120608 12:51:08 [Note] Server socket created on IP: '0.0.0.0'.
120608 12:51:09 [Note] Event Scheduler: Loaded 0 events
120608 12:51:09 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.5.24-cll' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL) by Atomicorp

Can someone give us a clue of what might have caused this and what we could do in future to prevent it as we did not have SSH access for a while and a reboot is not ideal.

Edit: If it helps, we have a number of mysql processes - is this normal or could it be part of the cause if something is not right?

Quote:

[root@plesk3 ~]# rpm -qa mysql\*
mysqlclient16-5.1.59-2.el5.art
mysql-server-5.5.24-6.el5.art
mysql-libs-5.5.24-6.el5.art
mysqlclient15-5.0.90-2.el5.art
mysql-connector-odbc-3.51.26r1127-2.el5
mysql-5.5.24-6.el5.art
[root@plesk3 ~]#

mysqld crashed websites

Who is online