We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
[Solved] MariaBD status:active but not active in VestaCP
Re: [Solved] MariaBD status:active but not active in VestaCP
It appears that you are facing some issues related to the configuration and compatibility of MariaDB and MySQL in the context of the Vesta control panel. Let's break down the problems and provide solutions with relevant code snippets:
Changing [mysql] to [mysqld] in mysql.cnf:
Open the mysql.cnf file using the nano text editor:
Locate the line that starts with [mysql] and change it to [mysqld]. Save the file and exit the editor.
Invalid mysql type error after upgrading to MariaDB 10.6.9:
Since the commands for MariaDB have changed from version 10.5 onward, you might encounter issues when specifying the DB_SYSTEM value in the vesta.conf file. To avoid the error and keep the MariaDB status active in the web GUI, try the following:
Save the vesta.conf file and restart the Vesta control panel to ensure the changes take effect. See:
DB creation issue with "mariadb" selected as type:
If selecting "mariadb" as the database type during DB creation doesn't work properly later on, you can modify the "v-add-database" script to specify "mariadb" explicitly. Edit the script as follows:
Locate the line with type=${5-mysql} and change it to type=${5-mariadb}. Save the file. See:
Incorrect Vesta version number in vesta.conf:
To correct the Vesta version number in the vesta.conf file, you can manually update it. Open the file using a text editor:
Locate the line that starts with VERSION= and update the value to the correct version number. Save the file.
After making these changes, ensure that you restart the Vesta control panel and any related services for the modifications to take effect See:
Note: It's essential to have proper backups before making any configuration changes to avoid any unexpected data loss or system issues.
Changing [mysql] to [mysqld] in mysql.cnf:
Open the mysql.cnf file using the nano text editor:
Code: Select all
nano /etc/mysql/conf.d/mysql.cnf
Invalid mysql type error after upgrading to MariaDB 10.6.9:
Since the commands for MariaDB have changed from version 10.5 onward, you might encounter issues when specifying the DB_SYSTEM value in the vesta.conf file. To avoid the error and keep the MariaDB status active in the web GUI, try the following:
Code: Select all
DB_SYSTEM='mariadb,mysql'
DB creation issue with "mariadb" selected as type:
If selecting "mariadb" as the database type during DB creation doesn't work properly later on, you can modify the "v-add-database" script to specify "mariadb" explicitly. Edit the script as follows:
Code: Select all
nano /usr/local/vesta/bin/v-add-database
Incorrect Vesta version number in vesta.conf:
To correct the Vesta version number in the vesta.conf file, you can manually update it. Open the file using a text editor:
Code: Select all
nano /usr/local/vesta/conf/vesta.conf
After making these changes, ensure that you restart the Vesta control panel and any related services for the modifications to take effect See:
Code: Select all
service vesta restart