120504 01:39:46 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
120504  1:39:46 [Note] Plugin 'FEDERATED' is disabled.
120504  1:39:46 InnoDB: The InnoDB memory heap is disabled
120504  1:39:46 InnoDB: Mutexes and rw_locks use GCC atomic builtins
120504  1:39:46 InnoDB: Compressed tables use zlib 1.2.5
120504  1:39:46 InnoDB: Using Linux native AIO
120504  1:39:46 InnoDB: Initializing buffer pool, size = 256.0M
120504  1:39:46 InnoDB: Completed initialization of buffer pool
120504  1:39:46 InnoDB: highest supported file format is Barracuda.
120504  1:39:47  InnoDB: Waiting for the background threads to start
120504  1:39:48 InnoDB: 1.1.8 started; log sequence number 4332108592
120504  1:39:48 [Note] Event Scheduler: Loaded 0 events
120504  1:39:48 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.5.23'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Community Server (GPL)
120504 19:23:25 [Note] /usr/libexec/mysqld: Normal shutdown

120504 19:23:25 [Note] Event Scheduler: Purging the queue. 0 events
120504 19:23:38  InnoDB: Starting shutdown...
120504 19:23:53  InnoDB: Shutdown completed; log sequence number 4443282590
120504 19:23:53 [Note] /usr/libexec/mysqld: Shutdown complete

120504 19:23:54 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
120504 19:23:55 [Note] Plugin 'FEDERATED' is disabled.
120504 19:23:55 InnoDB: The InnoDB memory heap is disabled
120504 19:23:55 InnoDB: Mutexes and rw_locks use GCC atomic builtins
120504 19:23:55 InnoDB: Compressed tables use zlib 1.2.5
120504 19:23:55 InnoDB: Using Linux native AIO
120504 19:23:55 InnoDB: Initializing buffer pool, size = 256.0M
120504 19:23:55 InnoDB: Completed initialization of buffer pool
120504 19:23:55 InnoDB: highest supported file format is Barracuda.
120504 19:24:19  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
120504 19:24:19  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './database/wproot_commentmeta.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
120504 19:24:19  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
120504 19:24:19  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './database/wproot_comments.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
120504 19:24:19  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
120504 19:24:19  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './database/wproot_links.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
120504 19:24:19  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
120504 19:24:19  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './database/wproot_options.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
120504 19:24:19  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
120504 19:24:19  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './database/wproot_postmeta.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
120504 19:24:19  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
120504 19:24:19  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './database/wproot_posts.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
120504 19:24:19  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
120504 19:24:19  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './database/wproot_term_relationships.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
120504 19:24:19  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
120504 19:24:19  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './database/wproot_term_taxonomy.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
120504 19:24:19  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
120504 19:24:19  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './database/wproot_terms.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
120504 19:24:19  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
120504 19:24:19  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './database/wproot_usermeta.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
120504 19:24:19  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
120504 19:24:19  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './database/wproot_users.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
120504 19:24:20  InnoDB: Waiting for the background threads to start
120504 19:24:21 InnoDB: 1.1.8 started; log sequence number 4443282590
120504 19:24:21 [Note] Event Scheduler: Loaded 0 events
120504 19:24:21 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.5.23'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Community Server (GPL)