Home aaPanel Fix the “Aria engine is not enabled or did not start” error on aaPanel

Fix the “Aria engine is not enabled or did not start” error on aaPanel

by Thạch Phạm

In the process of using aaPanel, I encountered quite a few problems, but most of the problems had solutions. And you may get an error that MariaDB could not be started with the full error log as follows:

AZDIGI Tutorial
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
    
Aria engine is not enabled or did not start

I. Recognizing

This error is difficult to recognize when you only use the aaPanel interface because in the aaPanel interface, the MySQL/MariaDB service still says it is working normally, even if you restart this service, the aaPanel interface still says the same.

However, websites will still show Error establishing a database connection error as shown below:

There is also another way to know that you will not be able to access phpMyadmin even if you have entered the correct information.

mysqli_real_connect(): (HY000/2002): No such file or directory

II. How to fix the “Aria engine is not enabled or did not start” error

To fix the “Aria engine is not enabled or did not start” error, you need to do the following 3 steps.

Step 1: SSH into your aaPanel server

To fix the “Aria engine is not enabled or did not start” error, we first need to SSH or access your VPS/server with root privileges. If you do not know how to SSH into your VPS/Server, you can refer to the following tutorial:

After successfully SSHing, we continue with step 2 to check the log what is the cause of the error.

Step 2: Check MySQL/MariaDB error log on aaPanel

To check the MySQL/MariaDB error log on aaPanel, we use the following command:

AZDIGI Tutorial
tailf /www/server/data/.err
    

Remember to change hostname.com to the hostname of your server.

In addition, you need to open another SSH window to run the command to restart the MySQL/MariaDB service with the command:

AZDIGI Tutorial
service mysql restart
    

After restarting with the above command, we see the error log generated a lot and in it there is the Aria engine is not enabled or did not start, as shown below:

You can open the image with a new tab to see it clearly.

Note: At (1), after I start MySQL/MariaDB, I get a generic error. And in the error log file, the error is very detailed and complete as follows:

AZDIGI Tutorial
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
    

So seeing the problem, we continue with step 3 to fix it.

Step 3: Handling “Aria engine is not enabled or did not start” error on aaPanel

To handle this error, we execute the following two commands:

AZDIGI Tutorial
mv /www/server/data/aria_log_control /www/server/data/aria_log_control_bak
service mysql restart
    

Explanation of the two commands above:

  • Command 1: Change the filename aria_log_control to aria_log_control_bak.
  • Command 2: Restart the MySQL/MariaDB service.

After executing the above two commands, MySQL/MariaDB has worked properly.

Aria engine is not enabled or did not start

III. Summary

Through this article, you have found a way to handle the error MySQL/MariaDB that cannot start. Hope the article is useful to you.

Wishing you success.

Đánh giá

Bài viết cùng chuyên mục

AZDIGI – Không chỉ là đơn vị hàng đầu trong lĩnh vực Web Hosting và Máy chủ, chúng tôi mong muốn mang lại những kiến thức bổ ích nhất và luôn cập nhật thường xuyên cho cộng đồng người đam mê thiết kế website, công nghệ,…

Vui lòng không sao chép nội dung nếu chưa xin phép. Designed and Developed by PenciDesign