@aaPanel_Jose @aaPanel_Captain @aaPanel_thisyear Can anyone help us? It's very annoying to have several sites and customers calling all the time asking why the site is offline, I'm about to give up everything and go back to any shared hosting that has support.
2022-01-06 07:27:30 3832 [Note] Plugin 'FEDERATED' is disabled.
2022-01-06 07:27:30 3832 [Note] InnoDB: Using atomics to ref count buffer pool pages
2022-01-06 07:27:30 3832 [Note] InnoDB: The InnoDB memory heap is disabled
2022-01-06 07:27:30 3832 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2022-01-06 07:27:30 3832 [Note] InnoDB: Memory barrier is not used
2022-01-06 07:27:30 3832 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-01-06 07:27:30 3832 [Note] InnoDB: Using CPU crc32 instructions
2022-01-06 07:27:30 3832 [Note] InnoDB: Initializing buffer pool, size = 512.0M
2022-01-06 07:27:30 3832 [Note] InnoDB: Completed initialization of buffer pool
2022-01-06 07:27:31 3832 [Note] InnoDB: Highest supported file format is Barracuda.
2022-01-06 07:27:31 3832 [Note] InnoDB: Log scan progressed past the checkpoint lsn 3376836128
2022-01-06 07:27:31 3832 [Note] InnoDB: Database was not shutdown normally!
2022-01-06 07:27:31 3832 [Note] InnoDB: Starting crash recovery.
2022-01-06 07:27:31 3832 [Note] InnoDB: Reading tablespace information from the .ibd files...
2022-01-06 07:27:31 145b84233740 InnoDB: Operating system error number 13 in a file operation.
InnoDB: The error means mysqld does not have the access rights to
InnoDB: the directory.
InnoDB: Error: could not open single-table tablespace file ./newquality_wp/wp_woocommerce_tax_rate_locations.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2022-01-06 07:46:45 9226 [Note] Plugin 'FEDERATED' is disabled.
2022-01-06 07:46:45 9226 [Note] InnoDB: Using atomics to ref count buffer pool pages
2022-01-06 07:46:45 9226 [Note] InnoDB: The InnoDB memory heap is disabled
2022-01-06 07:46:45 9226 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2022-01-06 07:46:45 9226 [Note] InnoDB: Memory barrier is not used
2022-01-06 07:46:45 9226 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-01-06 07:46:45 9226 [Note] InnoDB: Using CPU crc32 instructions
2022-01-06 07:46:45 9226 [Note] InnoDB: Initializing buffer pool, size = 512.0M
2022-01-06 07:46:45 9226 [Note] InnoDB: Completed initialization of buffer pool
2022-01-06 07:46:46 9226 [Note] InnoDB: Highest supported file format is Barracuda.
2022-01-06 07:46:46 9226 [Note] InnoDB: Log scan progressed past the checkpoint lsn 3376836128
2022-01-06 07:46:46 9226 [Note] InnoDB: Database was not shutdown normally!
2022-01-06 07:46:46 9226 [Note] InnoDB: Starting crash recovery.
2022-01-06 07:46:46 9226 [Note] InnoDB: Reading tablespace information from the .ibd files...
2022-01-06 07:46:46 148cbf9e5740 InnoDB: Operating system error number 13 in a file operation.
InnoDB: The error means mysqld does not have the access rights to
InnoDB: the directory.
InnoDB: Error: could not open single-table tablespace file ./newquality_wp/wp_woocommerce_tax_rate_locations.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2022-01-06 07:46:55 9903 [Note] Plugin 'FEDERATED' is disabled.
2022-01-06 07:46:55 9903 [Note] InnoDB: Using atomics to ref count buffer pool pages
2022-01-06 07:46:55 9903 [Note] InnoDB: The InnoDB memory heap is disabled
2022-01-06 07:46:55 9903 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2022-01-06 07:46:55 9903 [Note] InnoDB: Memory barrier is not used
2022-01-06 07:46:55 9903 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-01-06 07:46:55 9903 [Note] InnoDB: Using CPU crc32 instructions
2022-01-06 07:46:55 9903 [Note] InnoDB: Initializing buffer pool, size = 512.0M
2022-01-06 07:46:55 9903 [Note] InnoDB: Completed initialization of buffer pool
2022-01-06 07:46:55 9903 [Note] InnoDB: Highest supported file format is Barracuda.
2022-01-06 07:46:55 9903 [Note] InnoDB: Log scan progressed past the checkpoint lsn 3376836128
2022-01-06 07:46:55 9903 [Note] InnoDB: Database was not shutdown normally!
2022-01-06 07:46:55 9903 [Note] InnoDB: Starting crash recovery.
2022-01-06 07:46:55 9903 [Note] InnoDB: Reading tablespace information from the .ibd files...
2022-01-06 07:46:55 1526edf91740 InnoDB: Operating system error number 13 in a file operation.
InnoDB: The error means mysqld does not have the access rights to
InnoDB: the directory.
InnoDB: Error: could not open single-table tablespace file ./newquality_wp/wp_woocommerce_tax_rate_locations.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2022-01-06 07:49:08 11154 [Note] Plugin 'FEDERATED' is disabled.
2022-01-06 07:49:08 11154 [Note] InnoDB: Using atomics to ref count buffer pool pages
2022-01-06 07:49:08 11154 [Note] InnoDB: The InnoDB memory heap is disabled
2022-01-06 07:49:08 11154 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2022-01-06 07:49:08 11154 [Note] InnoDB: Memory barrier is not used
2022-01-06 07:49:08 11154 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-01-06 07:49:08 11154 [Note] InnoDB: Using CPU crc32 instructions
2022-01-06 07:49:08 11154 [Note] InnoDB: Initializing buffer pool, size = 512.0M
2022-01-06 07:49:09 11154 [Note] InnoDB: Completed initialization of buffer pool
2022-01-06 07:49:09 11154 [Note] InnoDB: Highest supported file format is Barracuda.
2022-01-06 07:49:09 11154 [Note] InnoDB: Log scan progressed past the checkpoint lsn 3376836128
2022-01-06 07:49:09 11154 [Note] InnoDB: Database was not shutdown normally!
2022-01-06 07:49:09 11154 [Note] InnoDB: Starting crash recovery.
2022-01-06 07:49:09 11154 [Note] InnoDB: Reading tablespace information from the .ibd files...
2022-01-06 07:49:09 14cb0a0da740 InnoDB: Operating system error number 13 in a file operation.
InnoDB: The error means mysqld does not have the access rights to
InnoDB: the directory.
InnoDB: Error: could not open single-table tablespace file ./newquality_wp/wp_woocommerce_tax_rate_locations.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2022-01-06 07:49:57 12059 [Note] Plugin 'FEDERATED' is disabled.
2022-01-06 07:49:57 12059 [Note] InnoDB: Using atomics to ref count buffer pool pages
2022-01-06 07:49:57 12059 [Note] InnoDB: The InnoDB memory heap is disabled
2022-01-06 07:49:57 12059 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2022-01-06 07:49:57 12059 [Note] InnoDB: Memory barrier is not used
2022-01-06 07:49:57 12059 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-01-06 07:49:57 12059 [Note] InnoDB: Using CPU crc32 instructions
2022-01-06 07:49:57 12059 [Note] InnoDB: Initializing buffer pool, size = 512.0M
2022-01-06 07:49:57 12059 [Note] InnoDB: Completed initialization of buffer pool
2022-01-06 07:49:57 12059 [Note] InnoDB: Highest supported file format is Barracuda.
2022-01-06 07:49:57 12059 [Note] InnoDB: Log scan progressed past the checkpoint lsn 3376836128
2022-01-06 07:49:57 12059 [Note] InnoDB: Database was not shutdown normally!
2022-01-06 07:49:57 12059 [Note] InnoDB: Starting crash recovery.
2022-01-06 07:49:57 12059 [Note] InnoDB: Reading tablespace information from the .ibd files...
2022-01-06 07:49:57 14c47d5ff740 InnoDB: Operating system error number 13 in a file operation.
InnoDB: The error means mysqld does not have the access rights to
InnoDB: the directory.
InnoDB: Error: could not open single-table tablespace file ./newquality_wp/wp_woocommerce_tax_rate_locations.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2022-01-06 07:52:28 13476 [Note] Plugin 'FEDERATED' is disabled.
2022-01-06 07:52:28 13476 [Note] InnoDB: Using atomics to ref count buffer pool pages
2022-01-06 07:52:28 13476 [Note] InnoDB: The InnoDB memory heap is disabled
2022-01-06 07:52:28 13476 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2022-01-06 07:52:28 13476 [Note] InnoDB: Memory barrier is not used
2022-01-06 07:52:28 13476 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-01-06 07:52:28 13476 [Note] InnoDB: Using CPU crc32 instructions
2022-01-06 07:52:28 13476 [Note] InnoDB: Initializing buffer pool, size = 512.0M
2022-01-06 07:52:29 13476 [Note] InnoDB: Completed initialization of buffer pool
2022-01-06 07:52:29 13476 [Note] InnoDB: Highest supported file format is Barracuda.
2022-01-06 07:52:29 13476 [Note] InnoDB: Log scan progressed past the checkpoint lsn 3376836128
2022-01-06 07:52:29 13476 [Note] InnoDB: Database was not shutdown normally!
2022-01-06 07:52:29 13476 [Note] InnoDB: Starting crash recovery.
2022-01-06 07:52:29 13476 [Note] InnoDB: Reading tablespace information from the .ibd files...
2022-01-06 07:52:29 14eec5a97740 InnoDB: Operating system error number 13 in a file operation.
InnoDB: The error means mysqld does not have the access rights to
InnoDB: the directory.
InnoDB: Error: could not open single-table tablespace file ./newquality_wp/wp_woocommerce_tax_rate_locations.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2022-01-06 07:52:57 14176 [Note] Plugin 'FEDERATED' is disabled.
2022-01-06 07:52:57 14176 [Note] InnoDB: Using atomics to ref count buffer pool pages
2022-01-06 07:52:57 14176 [Note] InnoDB: The InnoDB memory heap is disabled
2022-01-06 07:52:57 14176 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2022-01-06 07:52:57 14176 [Note] InnoDB: Memory barrier is not used
2022-01-06 07:52:57 14176 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-01-06 07:52:57 14176 [Note] InnoDB: Using CPU crc32 instructions
2022-01-06 07:52:57 14176 [Note] InnoDB: Initializing buffer pool, size = 512.0M
2022-01-06 07:52:57 14176 [Note] InnoDB: Completed initialization of buffer pool
2022-01-06 07:52:57 14176 [Note] InnoDB: Highest supported file format is Barracuda.
2022-01-06 07:52:57 14176 [Note] InnoDB: Log scan progressed past the checkpoint lsn 3376836128
2022-01-06 07:52:57 14176 [Note] InnoDB: Database was not shutdown normally!
2022-01-06 07:52:57 14176 [Note] InnoDB: Starting crash recovery.
2022-01-06 07:52:57 14176 [Note] InnoDB: Reading tablespace information from the .ibd files...
2022-01-06 07:52:57 14967755f740 InnoDB: Operating system error number 13 in a file operation.
InnoDB: The error means mysqld does not have the access rights to
InnoDB: the directory.
InnoDB: Error: could not open single-table tablespace file ./newquality_wp/wp_woocommerce_tax_rate_locations.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2022-01-06 07:54:43 15346 [Note] Plugin 'FEDERATED' is disabled.
2022-01-06 07:54:43 15346 [Note] InnoDB: Using atomics to ref count buffer pool pages
2022-01-06 07:54:43 15346 [Note] InnoDB: The InnoDB memory heap is disabled
2022-01-06 07:54:43 15346 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2022-01-06 07:54:43 15346 [Note] InnoDB: Memory barrier is not used
2022-01-06 07:54:43 15346 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-01-06 07:54:43 15346 [Note] InnoDB: Using CPU crc32 instructions
2022-01-06 07:54:43 15346 [Note] InnoDB: Initializing buffer pool, size = 512.0M
2022-01-06 07:54:43 15346 [Note] InnoDB: Completed initialization of buffer pool
2022-01-06 07:54:44 15346 [Note] InnoDB: Highest supported file format is Barracuda.
2022-01-06 07:54:44 15346 [Note] InnoDB: Log scan progressed past the checkpoint lsn 3376836128
2022-01-06 07:54:44 15346 [Note] InnoDB: Database was not shutdown normally!
2022-01-06 07:54:44 15346 [Note] InnoDB: Starting crash recovery.
2022-01-06 07:54:44 15346 [Note] InnoDB: Reading tablespace information from the .ibd files...
2022-01-06 07:54:44 1527113a1740 InnoDB: Operating system error number 13 in a file operation.
InnoDB: The error means mysqld does not have the access rights to
InnoDB: the directory.
InnoDB: Error: could not open single-table tablespace file ./newquality_wp/wp_woocommerce_tax_rate_locations.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.