General developer forum

Error while installing moodle 3.3.2

 
Picture of neha pal
Error while installing moodle 3.3.2
 
mysql_full_unicode_support#File_format :  this test must pass Your database has tables using Antelope as the file format. Full UTF-8 support in MySQL and MariaDB requires the Barracuda file format. Please convert the tables to the Barracuda file format. See the documentation Administration via command line for details of a tool for converting InnoDB tables to Barracuda. 


mysql_full_unicode_support#Large_prefix: this test must pass For full support of UTF-8 both MySQL and MariaDB require you to change your MySQL setting 'innodb_large_prefix' to 'ON'. See the documentation for further details. 

site not https : if this test fails, it indicates a potential problem It has been detected that your site is not secured using HTTPS. It is strongly recommended to migrate your site to HTTPS for increased security and improved integration with other systems.



kindly help me to solve this errors.

 
Average of ratings: -
Richard Jones
Re: Error while installing moodle 3.3.2
Particularly helpful MoodlersPlugin developersTesters

If you have access to your command line try this:

https://dba.stackexchange.com/questions/14246/innodb-file-format-barracuda (use the commands in bold, below):

you can try this on a test environment first. 

mysql> SET GLOBAL innodb_file_format = barracuda;
     Query OK, 0 rows affected (0.00 sec)

mysql> SET GLOBAL innodb_file_format_max = barracuda;
          Query OK, 0 rows affected (0.00 sec)

mysql> show variables like "%innodb_file%";
       +--------------------------+-----------+
       | Variable_name            | Value     |
       +--------------------------+-----------+
       | innodb_file_format       | Barracuda |
       | innodb_file_format_check | ON        |
       | innodb_file_format_max   | Barracuda |
       | innodb_file_per_table    | ON        |
       +--------------------------+-----------+
        4 rows in set (0.00 sec)

Also: 

>set global innodb_large_prefix = on;

If you don't have access then try the documentation (as suggested) and tell us what happens.  Possibly you are in the wrong forum as well (seems like an installation issue).


HTH
 
Average of ratings: -