Show Posts
46
Kloxo-MR Technical Helps / Re: slow website
« on: 2017-07-24, 15:19:39 »
2017-07-24 17:24:35 7f7987019820 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.6/en/operating-system-error-codes.html
170724 17:24:35 [ERROR] InnoDB: Can't open './ibdata1'
170724 17:24:35 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
170724 17:24:35 [ERROR] Plugin 'InnoDB' init function returned error.
170724 17:24:35 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
170724 17:24:35 [ERROR] mysqld: Can't lock aria control file '/var/lib/mysql/aria_log_control' for exclusive use, error: 11. Will retry for 30 seconds
170724 17:25:06 [ERROR] mysqld: Got error 'Could not get an exclusive lock; file is probably in use by another process' when trying to use aria control file '/var/lib/mysql/aria_log_control'
170724 17:25:06 [ERROR] Plugin 'Aria' init function returned error.
170724 17:25:06 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
170724 17:25:06 [Note] Plugin 'FEEDBACK' is disabled.
170724 17:25:06 [ERROR] Aria engine is not enabled or did not start. The Aria engine must be enabled to continue as mysqld was configured with --with-aria-tmp-tables
170724 17:25:06 [ERROR] Aborting
170724 17:25:06 [Note] /usr/sbin/mysqld: Shutdown complete
170724 17:25:06 mysqld_safe mysqld from pid file /var/lib/mysql/ns1.pattola.com.pid ended
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.6/en/operating-system-error-codes.html
170724 17:24:35 [ERROR] InnoDB: Can't open './ibdata1'
170724 17:24:35 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
170724 17:24:35 [ERROR] Plugin 'InnoDB' init function returned error.
170724 17:24:35 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
170724 17:24:35 [ERROR] mysqld: Can't lock aria control file '/var/lib/mysql/aria_log_control' for exclusive use, error: 11. Will retry for 30 seconds
170724 17:25:06 [ERROR] mysqld: Got error 'Could not get an exclusive lock; file is probably in use by another process' when trying to use aria control file '/var/lib/mysql/aria_log_control'
170724 17:25:06 [ERROR] Plugin 'Aria' init function returned error.
170724 17:25:06 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
170724 17:25:06 [Note] Plugin 'FEEDBACK' is disabled.
170724 17:25:06 [ERROR] Aria engine is not enabled or did not start. The Aria engine must be enabled to continue as mysqld was configured with --with-aria-tmp-tables
170724 17:25:06 [ERROR] Aborting
170724 17:25:06 [Note] /usr/sbin/mysqld: Shutdown complete
170724 17:25:06 mysqld_safe mysqld from pid file /var/lib/mysql/ns1.pattola.com.pid ended
