Installing and upgrading help

Issues Upgrading to Moodle 3.4

 
Picture of Sonya Saywell
Issues Upgrading to Moodle 3.4
 

Hi,

I have gone through the process of upgrading to Moodle 3.4 and have one by one ticked off all the required server settings and am now down to one last check that I can't seem to get to pass so I can finish the upgrade, being as follows:

InformationReportPluginStatus
mysql_full_unicode_support#File_format

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.

Check

I have been through my web host support and they have run the moodle tool for converting the tables and it confirms that the database is compliant and yet my moodle upgrade install won't pass this test so that we can finish the upgrade.

I have no idea where to go from here and I need to get our moodle install working ASAP... if anyone has any suggestions or help I would be very appreciative! 

Thank-you!

 
Average of ratings: -
Picture of Howard Miller
Re: Issues Upgrading to Moodle 3.4
 
Average of ratings: Useful (1)
Picture of Sonya Saywell
Re: Issues Upgrading to Moodle 3.4
 
Thank-you for your help Howard.

I wasn't able to locate my.cnf  so I tried the mysql commands, but trying to run them just threw an error, so I've bee waiting for my host's support team to have a look...
 
Average of ratings: -
Picture of Rick Jerz
Re: Issues Upgrading to Moodle 3.4
Particularly helpful Moodlers

Have your hosting team give you a copy of my.cnf so that you can see if the line for Barracuda is in it.

Where did you look for my.cnf?

 
Average of ratings: -
Picture of Ken Task
Re: Issues Upgrading to Moodle 3.4
Particularly helpful Moodlers

Ask the hosting provider folks to run the mysql_compressed_rows.php script located in

cd /yourcode/admin/cli/

then

php mysql_compressed_rows.php -i

That will show the global setup of the databases on the db server ... which, in your hosting, is probably a dedicated DB server NOT on the same server as your code (but I could be wrong).

Also ask them to run the same command with a different switch:

php mysql_compressed_rows.php -s

The -s should show the SQL needed to get your DB in compliance.

The reason this is happening I suspect is that the environment check looks at the global setup for the entire DB server as opposed to the setup of the specific database your Moodle is setup to use.

'spirit of sharing', Ken


 
Average of ratings: -