Skip to main content
We are aware of an issue after updating to cPanel versions 11.110.0.65, 11.126.0.21, or 11.128.0.11, some cPanel plugins or features are no longer functioning properly including WP Toolkit. Presently, updates for releases are temporarily disabled while we continue working on a solution for the missing addon features directory. Please see the following article for more information and updates:
Update to latest cPanel 110, 126, or 128 versions removes "addonfeatures" directory.

crashes every few hours, i think something to do with innodb

Nishant80
Hello, I have been facing this problem since past week. Server would randomly stopped working even though it doesn't now have high load average. Couldn't find anything in logs, I think it is because of the mysql crashes. There are about 4 sties whos databases are not working anymore, (even though they exist). They all went to "internal server error" all of a sudden, after restarting mysql, some of them came back and some shows no sign of database connection in wordpress. Here is my my.cnf #[mysqld] #innodb_file_per_table=1 [mysqld] max_allowed_packet=64M log_slow_queries="/var/log/mysql-slow.log" innodb_file_per_table=1 open_files_limit=50000 query_cache_size=16777216 long_query_time=1 thread_cache_size=2 default-storage-engine=MyISAM [mysqld_safe] log-error="/var/log/mysqld.log" Here's are the last lines of mysql logs. root@server [~]# tail /var/log/mysqld.log 140301 7:29:21 [ERROR] Cannot find or open table xeramein_phpfox/phpfox_custom_field 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 [url=http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html]MySQL :: MySQL 5.5 Reference Manual :: 14.3.19 InnoDB Troubleshooting how you can resolve the problem. Any help would be highly appreciated as I am loosing a lot of clients because of this.

Comments

2 comments

Date Votes
  • Nishant80
    Also, the /tmp dir is getting piled on very very reapidly. In 10 minutes it reaches to 100% which is about 4GB. It usually used to take like 10-15 days earlier.
    0
  • cPanelMichael
    Hello :) The following document referenced in the error log you provided should provide you with some help: [url=http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html]MySQL :: MySQL 5.5 Reference Manual :: 14.3.19 InnoDB Troubleshooting As for the /tmp partition, try using the "du" utility to determine which files are taking up the most space. Thank you.
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post