MariaDB Index column size too large. The maximum column size is 767 bytes.

Centmin Mod is provide as is, so short of scripted related bugs or issues, any further optimisation to the web stack components - nginx, php-fpm, mariadb mysql, csf firewall etc or web app specific configurations are left to the Centmin Mod user to deal with. So I do not provide any free support for such.

However, Centmin Mod users are free to help each other out and ask questions or give answers on this community forum. My hopes are that this community forum evolves so that more veteran long time Centmin Mod users help new Centmin Mod users out

Are you using latin1, utf8 or utf8mb4 charset for MariaDB MySQL. If using utf8mb4 read official documentation for why you need to carefully go through all databases and ensure the max key prefix index sizes are within InnoDB limits outlined at MySQL :: MySQL 5.6 Reference Manual :: 14.8.8 Limits on InnoDB Tables

Latest 123.09beta01 already adds to /etc/my.cnf the relevant settings to support larger InnoDB index prefixes as outlined at MySQL :: MySQL 5.6 Reference Manual :: 10.1.9.8 Converting Between 3-Byte and 4-Byte Unicode Character Sets

Code (Text):

egrep 'format|large' /etc/my.cnf | uniq  
innodb_large_prefix=1
innodb_file_format = Barracuda

Again, only do this if you're know what you're doing and always backup all mysql databases on server before hand.

 

best to follow the instructions outlined to 'contact vBulletin support for assistance' as they would best know the index adjustments for utf8mb4 support (if they support it)

 

nothing wrong with MariaDB it's your web app's mysql data structure when using innodb + utf8mb4

and MySQL :: MySQL 5.6 Reference Manual :: 10.1.9.8 Converting Between 3-Byte and 4-Byte Unicode Character Sets

 

AFAIK, MySQL before 5.6 silently failed on that error but after 5.6+ it reports the error now. That's the difference. The solution is listed in my above linked documentation and will require you contacting vB tech support as I believe there's a few bugs still in vB5 installer's mysql-schema.php for a few tables to address innodb + utf8mb4 + max key index prefix limits issues.

Centmin Mod is provide as is, so short of scripted related bugs or issues, any further optimisation to the web stack components - nginx, php-fpm, mariadb mysql, csf firewall etc or web app specific configurations are left to the Centmin Mod user to deal with. So I do not provide any free support for such - this is clearly a problem with vB5's mysql schema and how it's dealing with utf8/utf8mb4 and max key index prefix limits.

However, Centmin Mod users are free to help each other out and ask questions or give answers on this community forum. My hopes are that this community forum evolves so that more veteran long time Centmin Mod users help new Centmin Mod users out

 

For folks who run across this thread and error, just know for Centmin Mod 123.09beta01 installs after April 29, 2018 this InnoDB column index length issue and occurrence should be lessened as Centmin Mod 123.09beta01 has updated MariaDB 10.1/10.2 my.cnf templates to add new innodb_default_row_format variable and set it to default to DYNAMIC instead of COMPACT row formats as per Beta Branch - update MariaDB 10.1 & 10.2 default /etc/my.cnf default for innodb_default_row_format. So now all the required pieces are in place to support the larger 3072 bytes limit instead of 767 bytes limit with Barracuda file format, innodb_large_prefer and innodb_default_row_format=dynamic all configured