110913 23:08:13 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 110913 23:08:13 [Warning] You need to use --log-bin to make --log-slave-updates work. 110913 23:08:13 [Warning] You need to use --log-bin to make --binlog-format work. 110913 23:08:13 [Note] Plugin 'FEDERATED' is disabled. 110913 23:08:13 InnoDB: The InnoDB memory heap is disabled 110913 23:08:13 InnoDB: Mutexes and rw_locks use InnoDB's own implementation 110913 23:08:13 InnoDB: Compressed tables use zlib 1.2.3 110913 23:08:13 InnoDB: Using Linux native AIO 110913 23:08:13 InnoDB: Initializing buffer pool, size = 1.0G 110913 23:08:13 InnoDB: Completed initialization of buffer pool 110913 23:08:14 InnoDB: highest supported file format is Barracuda. 110913 23:08:15 InnoDB: Waiting for the background threads to start 110913 23:08:16 InnoDB: 1.1.8 started; log sequence number 1627711 110913 23:08:16 InnoDB: Error: table 110913 23:08:16 [Warning] Invalid (old?) table or database name '#sql3ebb_1_0' `mysql`. does not exist in the InnoDB internal InnoDB: data dictionary though MySQL is trying to drop it. InnoDB: Have you copied the .frm file of the table to the InnoDB: MySQL database directory from another database? InnoDB: You can look for further help from InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html 110913 23:08:16 [Note] Event Scheduler: Loaded 0 events 110913 23:08:16 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.5.15' socket: '/tmp/mysql.sock' port: 3306 MySQL Community Server (GPL)110913 23:08:45 InnoDB: Operating system error number 22 in a file operation. InnoDB: Error number 22 means 'Invalid argument'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html InnoDB: File name /dev/shm/mysql/#sql4135_1_0.ibd InnoDB: File operation call: 'aio write'. InnoDB: Cannot continue operation. 110913 23:08:45 mysqld_safe Number of processes running now: 0 110913 23:08:45 mysqld_safe mysqld restarted 110913 23:08:45 [Warning] You need to use --log-bin to make --log-slave-updates work. 110913 23:08:45 [Warning] You need to use --log-bin to make --binlog-format work. 110913 23:08:45 [Note] Plugin 'FEDERATED' is disabled. 110913 23:08:45 InnoDB: The InnoDB memory heap is disabled 110913 23:08:45 InnoDB: Mutexes and rw_locks use InnoDB's own implementation 110913 23:08:45 InnoDB: Compressed tables use zlib 1.2.3 110913 23:08:45 InnoDB: Using Linux native AIO 110913 23:08:46 InnoDB: Initializing buffer pool, size = 1.0G 110913 23:08:46 InnoDB: Completed initialization of buffer pool 110913 23:08:47 InnoDB: highest supported file format is Barracuda. InnoDB: Log scan progressed past the checkpoint lsn 1627721 110913 23:08:47 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 1631424 110913 23:08:47 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed InnoDB: We removed now the InnoDB internal data dictionary entry InnoDB: of table 110913 23:08:47 [Warning] Invalid (old?) table or database name '#sql4135_1_0' "mysql".. 110913 23:08:47 InnoDB: 1.1.8 started; log sequence number 1631424 110913 23:08:47 InnoDB: Error: table 110913 23:08:47 [Warning] Invalid (old?) table or database name '#sql4135_1_0' `mysql`. does not exist in the InnoDB internal InnoDB: data dictionary though MySQL is trying to drop it. InnoDB: Have you copied the .frm file of the table to the InnoDB: MySQL database directory from another database? InnoDB: You can look for further help from InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html 110913 23:08:47 [Note] Event Scheduler: Loaded 0 events 110913 23:08:47 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.5.15' socket: '/tmp/mysql.sock' port: 3306 MySQL Community Server (GPL) 110913 23:08:58 InnoDB: Operating system error number 22 in a file operation. InnoDB: Error number 22 means 'Invalid argument'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html InnoDB: File name /dev/shm/mysql/#sql416e_1_0.ibd InnoDB: File operation call: 'aio write'. InnoDB: Cannot continue operation. 110913 23:08:58 mysqld_safe Number of processes running now: 0 110913 23:08:58 mysqld_safe mysqld restarted 110913 23:08:58 [Warning] You need to use --log-bin to make --log-slave-updates work. 110913 23:08:58 [Warning] You need to use --log-bin to make --binlog-format work. 110913 23:08:58 [Note] Plugin 'FEDERATED' is disabled. 110913 23:08:58 InnoDB: The InnoDB memory heap is disabled 110913 23:08:58 InnoDB: Mutexes and rw_locks use InnoDB's own implementation 110913 23:08:58 InnoDB: Compressed tables use zlib 1.2.3 110913 23:08:58 InnoDB: Using Linux native AIO 110913 23:08:58 InnoDB: Initializing buffer pool, size = 1.0G 110913 23:08:58 InnoDB: Completed initialization of buffer pool 110913 23:08:59 InnoDB: highest supported file format is Barracuda. InnoDB: Log scan progressed past the checkpoint lsn 1628181 110913 23:08:59 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 1634726 110913 23:09:00 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed InnoDB: We removed now the InnoDB internal data dictionary entry InnoDB: of table 110913 23:09:00 [Warning] Invalid (old?) table or database name '#sql416e_1_0' "mysql".. 110913 23:09:00 InnoDB: 1.1.8 started; log sequence number 1634726 110913 23:09:00 InnoDB: Error: table 110913 23:09:00 [Warning] Invalid (old?) table or database name '#sql416e_1_0' `mysql`. does not exist in the InnoDB internal InnoDB: data dictionary though MySQL is trying to drop it. InnoDB: Have you copied the .frm file of the table to the InnoDB: MySQL database directory from another database? InnoDB: You can look for further help from InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html 110913 23:09:00 [Note] Event Scheduler: Loaded 0 events 110913 23:09:00 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.5.15' socket: '/tmp/mysql.sock' port: 3306 MySQL Community Server (GPL) 110913 23:09:07 [Note] /usr/sbin/mysqld: Normal shutdown 110913 23:09:07 [Note] Event Scheduler: Purging the queue. 0 events 110913 23:09:07 InnoDB: Starting shutdown... 110913 23:09:08 InnoDB: Shutdown completed; log sequence number 1635162 110913 23:09:08 [Note] /usr/sbin/mysqld: Shutdown complete 110913 23:09:08 mysqld_safe mysqld from pid file /var/lib/mysql/centos55.pid ended