| Posted By: ExonHost on May 21, 2015, 9:55 am |
|
Today mysql server gone down then I restarted mysql but now webuzo can't
detect databases and databases user. When I click on the "Manage Databases" and its showing blank. Also I can't login phpmyadmin using mysql root password. Error log ========== files but have forgotten to delete the corresponding .frm files of InnoDB tables, or you have moved .frm files to another database? or, the table contains indexes that this version of the engine doesn't support. See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html how you can resolve the problem. 150521 2:54:49 [ERROR] Cannot find or open table fullmov1_wp7766/wp_term_relationships from the internal data dictionary of InnoDB though the .frm file for the table exists. Maybe you have deleted and recreated InnoDB data files but have forgotten to delete the corresponding .frm files of InnoDB tables, or you have moved .frm files to another database? or, the table contains indexes that this version of the engine doesn't support. See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html how you can resolve the problem. 150521 2:54:49 [ERROR] Cannot find or open table fullmov1_wp7766/wp_commentmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. Maybe you have deleted and recreated InnoDB data files but have forgotten to delete the corresponding .frm files of InnoDB tables, or you have moved .frm files to another database? or, the table contains indexes that this version of the engine doesn't support. See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html how you can resolve the problem. 150521 2:54:49 [Note] /usr/local/apps/mysql/bin/mysqld: Normal shutdown 150521 2:54:49 [Note] Event Scheduler: Purging the queue. 0 events 150521 2:54:51 [Warning] /usr/local/apps/mysql/bin/mysqld: Forcing close of thread 11562 user: 'fullmov1_wp869' 150521 2:54:51 [Warning] /usr/local/apps/mysql/bin/mysqld: Forcing close of thread 11348 user: 'fullmov1_wp869' 150521 2:54:51 [Warning] /usr/local/apps/mysql/bin/mysqld: Forcing close of thread 10902 user: 'fullmov1_wp869' 150521 2:54:51 [Warning] /usr/local/apps/mysql/bin/mysqld: Forcing close of thread 10722 user: 'fullmov1_wp869' 150521 2:54:51 [Warning] /usr/local/apps/mysql/bin/mysqld: Forcing close of thread 10233 user: 'fullmov1_wp869' 150521 2:54:51 [Warning] /usr/local/apps/mysql/bin/mysqld: Forcing close of thread 9389 user: 'fullmov1_wp869' 150521 2:54:51 [Warning] /usr/local/apps/mysql/bin/mysqld: Forcing close of thread 8997 user: 'fullmov1_wp869' 150521 2:54:51 InnoDB: Starting shutdown... 150521 2:54:52 InnoDB: Shutdown completed; log sequence number 44822735 150521 2:54:52 [Note] /usr/local/apps/mysql/bin/mysqld: Shutdown complete 150521 02:54:52 mysqld_safe mysqld from pid file /var/lib/mysql/mysqld.pid ended 150521 02:55:01 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 150521 2:55:01 InnoDB: The InnoDB memory heap is disabled 150521 2:55:01 InnoDB: Mutexes and rw_locks use GCC atomic builtins 150521 2:55:01 InnoDB: Compressed tables use zlib 1.2.3 150521 2:55:01 InnoDB: Initializing buffer pool, size = 128.0M 150521 2:55:01 InnoDB: Completed initialization of buffer pool 150521 2:55:01 InnoDB: highest supported file format is Barracuda. 150521 2:55:02 InnoDB: Waiting for the background threads to start 150521 2:55:03 InnoDB: 5.5.40 started; log sequence number 44822735 150521 2:55:03 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306 150521 2:55:03 [Note] - '0.0.0.0' resolves to '0.0.0.0'; 150521 2:55:03 [Note] Server socket created on IP: '0.0.0.0'. 150521 2:55:03 [ERROR] /usr/local/apps/mysql/bin/mysqld: Can't create/write to file '/var/run/mysqld/mysqld.pid' (Errcode: 2) 150521 2:55:03 [ERROR] Can't start server: can't create PID file: No such file or directory 150521 02:55:03 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended =========== I already opened a ticket but no response. Any help is appreciated. |
| Posted By: divij on May 22, 2015, 5:47 am | Post: 1 |
|
Hi,
We have reply to your ticket. Your database was corrupted. |