mysql_full_unicode_support#File_format issue while installing Moodle with MariaDB. Your database uses Antelope as the file format. 'innodb_large_prefix' to 'ON'

-



this test must pass
Your database uses Antelope as the file format. Full UTF-8 support in MySQL and MariaDB requires the Barracuda file format. Please switch to the Barracuda file format. See the documentation MySQL full unicode support for details.
Checkmysql_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.
Check


If you get the above mention error. Try the following solution.

Login to mysql and run the following command.

mysql> SET GLOBAL innodb_file_format = barracuda 
mnysql> SET GLOBAL innodb_file_per_table = 1 
mnysql> SET GLOBAL innodb_large_prefix = 'on' 

And refresh the browser. 

Comments

Post a Comment

Popular posts from this blog

(Solved) (Fixed )MariaDB Unmet Dependencies on Ubuntu 20.04.

-
Error or Issue : Unmet Dependencies:  # sudo apt install mariadb-server Reading package lists... Done Building dependency tree        Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies:  mariadb-server : Depends: mariadb-server-10.3 (>= 1:10.3.25-0ubuntu0.20.04.1) but it is not going to be installed E: Unable to correct problems, you have held broken packages. Solution or Fix : Remove the different version of MySQL/MariaDB. To check the version run the following command. #  dpkg -l | grep -E 'mysql|mariadb' output:  ii  libdatetime-format-mysql-perl          0.06-1                            all          module to parse and format MySQL dates and times i
Read more

Solution to Moodle Error: Coding error detected, it must be fixed by a programmer: Failed to unserialise data from file. Either failed to read, or failed to write.

-
Image
Did you ever come across the following error when you try to access Moodle, "Coding error detected, it must be fixed by a programmer: Failed to unserialise data from file. Either failed to read, or failed to write." This usually happens when cache files are corrupted, one probable cause can be improper shutdown of Moodle system. Here is the solution to fix the issue. 1. Go to Moodle root directory     #cd /var/www/html/moodle   2. Run the command      #php admin/cli/purge_caches.php 3. Go to moodledata/cache directory   #cd /var/moodledata/cache    4. Remove the cache store directory, DO NOT remove of change the core_component.php file    # rm -rf cachestore_file/ 5. Refresh the Moodle Page. Its should work.
Read more

ACTION_FAILED:OU_INVALID: Solution for GoogleApps bulk user upload issue, username@domainname.com:ACTION_FAILED:OU_INVALID. This error is because you have not specified the Org Unit Path properly.

-
To upload bulk users to GoogleApps, you will require a following required fileds, other fields are optional:-               First Name               Last Name               Email Address               Password               Org Unit Path What is 'Org Unit Path'? This field was not their earlier. This is the path to place users in an organizational unit. For example if your domain has different organization unit like , staff, students, guest etc.. then the Org Unit Path would be just :  /
Read more