Vesta Control Panel - Forum

When will Vesta integrate the MariaDB v10 on vst-install.sh script ?

If you install Ubuntu 16, Debian 9, or CentOS 7, the default MySQL installed is MariaDB only. Vesta installs default *available* pkg version in the default repos of the OS...

Pls be aware Debian 9 is still not supported officially

My experience on Ubuntu 16 was that mysql was installed by default. This caused problems, as mysql was version 5.7, and mariadb 10.x corresponds to mysql 5.6. There are substantial differences in the table structure between 5.6 and 5.7, so effectively downgrading from mysql 5.7 to mariadb 10.1 was a lot of hassle.

I think your best approach is to manually install mariadb first, and then run the vesta install script, with the "no mysql, no postgresql" option. (Update: I tried this recently on a new install, and it didn't work, as phpmyadmin and roundcube were not installed: they require a database to operate, and they think there isn't one available. Maybe the installer should check for the mysql executable instead).

And to answer your question 'when', its been proposed as a feature, but not yet accepted.
https://github.com/serghey-rodin/vesta/issues/1204

I'll try to install mariadb 10 before VESTA

Thanks

I have performed a snap-in migration, simply do the install will remove mysql and install mariadb and ask you if you want to migrate data, everything worked fine on Debian 8.

I upgraded to mariadb because of the username length, but VestaCP still prevent longer names than 16 character, anything I missed?

Fchen wrote:I have performed a snap-in migration ... everything worked fine on Debian 8.

This will work on Debian as the migration is from mysql 5.5 to mariadb 10. For Ubuntu 16 and above, its much trickier as you're going from 5.7.

Re. Username size, you can check what your database is expecting with "show create table mysql.user;" which will display something like this. In my case the username can clearly be 80 characters. If you get the same and its still not working, I'd guess there's some check in the vestacp code which is not allowing longer names. https://github.com/serghey-rodin/vesta/issues/860

I have also 80 character per username, so there must be something in the VestaCP code.