Hello there,
I need to upgrade my moodle site from version 3.6.8 to version 4, yes, it is a huge gap.
My question is, can I jump directly from 3.6.8 to version 4?
or I should update gradually 3.6 >3.7>3.8>3.9>3.10>3.11>4 ?
I understand that the PHP version has to be set according to the version requirement. Is there anything else I should be looking into before I apply the updates?
Thanks in advance.
+1 to Howards advice ... in addition ...
get a listing of the plugins you have installed now. Check Moodle plugins to see if there is a compat version of the plugin for destination version.
Themes are plugins ... when you begin your 'march' or 'hyperjump' (ugh!) might want to set theme to boost as that comes stock with -> 3.6.x.
When it comes to 'hyperjumps' a plan to jump to LTS versions between 3.6.x and destination might be best.
Have we seen 4? or are we just wanting to get to latest and greatest?
Me thinks hops and backups are good strategy ... and as usual, best done with a test clone of current to assure no catch 22's and gotcha's!
When it comes to backups ... code + database at each successful hop and only one moodledata/filedir to begin as most of what is in moodledata is cached and will be rebuilt upon use next hop upwards.
Depending upon time factors and platform and if one can do a test platform setup, might be the perfect time to move acquiring code using git - especially if destination is 4 ... git will allow easy point release updates.
Plus ... consider using scripts provided in code/admin/cli/ for the 'march' including the CLI checks.php script.
'SoS', Ken
All of series 3.x is very similar ... not much change in look and feel. Is your site using a 3rd party theme (not boost)?
Version 4 is all about a 'new UI/UX' ... even advertised as such.
Since you have seen a 4 then what difference would my opinion make? None! It's your judgement of your students/teachers acceptance of that counts! Got a sandbox? Make that one a 4 and invite a couple of your power users in there!
How far you go in your march is totally up to you!
Please see:
https://docs.moodle.org/dev/Releases#Version_support
and note that when 4.1 (next LTS) is released, all other supported versions fall into non-supported (for security fixes - 13 November 2023).
That to say you will be on a 4 before Nov. 2023 ... period.
I would, however, encourage the use of git - regardless of version!
'SoS', Ken
Hi,
I have decided to go from 3.6>3.9 LTS.
Can you please help me understand which one is the LTS version of Moodle 3.9 (refer to image)?
Moodle 3.9.17+ (or) Moodle 3.9.17
I think it is 3.9.17+, am I right?
@Sona
In addition ... or just in case ...
Full site backup before you begin.
Check your plugins - especially the additional plugins. See if all of those have a compatible version for destination version of moodle.
Themes are plugins ... default theme for moodle is usually boost. If you are using a 3rd party theme site wide, might want to set via config.php the default theme to be boost before you begin your 'march' or 'hyperjumps'.
If you 'march', upgrade to X, then check, then make a backup consisting of code/sqldump and minimal moodledata/filedir/ Don't want to loose ground if the next step in march fails for some reason.
At that version, also check plugins. Moodle admin check Environment. Update component. Check there. All OK? Then next step in the 'march'.
It would be wise to clone production to a dev site and do the upgrades there first.
'SoS', Ken
And 2 more 'sense' if marching and using a dev clone.
Perfect time to get core code under git versioning system and learn how to 'march' via command line git. Moodle core code provides all the php scripts to accomplish that via command line ... advantages ... takes web service out of the loop ... has fewer moving parts (thus less prone to human error) ... + others.
And, with the additional cli only utility called moosh. for the dev instance, one could also upgrade plugins from moodle.org plugins.
Anyhoo ... thought I'd mention.
'SoS', Ken
Does your current code directory have a hidden .git directory as well as a hidden .github directory ... along with related hidden git files: .gitignore and .gitattributes
IF not, you will first have to perform what has been called a 'side load' or a 'direct load' of the above hidden directories/files to use git versioning of core code in your 'upgrade' plan - march or hyperjump. That will take your site to the highest version of 3.6 - which is 3.6.10.
Use of git to anything higher will get the highest point release of the version you point to using git.
And, so you don't get the wrong impression ... while use of git without -b does include all branches it doesn't mean that one can use git to upgrade or 'downgrade' (otherwise called 'roll back') a site. Git used when going from lower version of moodle core code to higher version of moodle core code ... not from higher to lower.
IF an upgrade fails, safest to restore the backup you made prior to upgrade attempt ... at minimum, restore of .sql file to a new database (change to config.php then is required) and restore of code directory.
'SoS', Ken
Answer question with a question, cause ultimately, you will admin your server!
What research have you done already in comparison of MySQL to MariaDB?
Having asked that ... have seen more than one article that mentions MariaDB has better performance (one resource below) ... though I've not found any research article that proves that beyond any doubt. [maybe I've not found it!]
https://www.opc-router.com/what-is-mariadb-a-comparison-with-mysql/
Performance
The biggest feature and therefore the biggest advantage of MariaDB is its speed and performance. When it comes to performing queries or replication, MariaDB is faster than MySQL. So if you need a high-performance relational database solution, MariaDB is a good choice. In addition, MariaDB also easily supports a high concurrent number of connections without much performance degradation. So if you have many data sources, this could be another reason to prefer MariaDB over MySQL.
https://mariadb.com/resources/blog/how-to-migrate-from-mysql-to-mariadb-on-linux-in-five-steps/
However ...
https://docs.moodle.org/400/en/Performance_recommendations#Database_performance
Maybe you should install MySQLTuner now and get some reads on what you have.
and one more ... for a deeper dive from Percona ...
https://www.percona.com/blog/2017/11/02/mysql-vs-mariadb-reality-check/
So ??????
'SoS', Ken
After re-reading ... 'if I have to update my database' - you mean version of what you are currently running, right?
With what you have to do right now with a 'march' a database change would be in addition to php version and Moodle core code also ... right?
The advice of 'don't change multiples at the same time', to me, has always been good. If something were to go wrong with your 'march' one might be left wondering what caused. So you could concentrate on the 'march' and all that is involved with that, and afterwards, if you should see need or decide, switch DB.
'SoS', Ken
EoL
MySQL
https://www.mysql.com/support/supportedplatforms/database.html
MariaDB
https://endoflife.date/mariadb
Mr. V's chart:
http://www.syndrega.ch/blog/#php-and-dbms-compatibility-of-major-moodle-releases
that shows ? for both DB - version 4.1 of moodle (next long term support version)
but things change ...
Go to admin - Server - Environment ... update component ... set drop down for
highest version of Moodle in the drop down pick list.
Would think LTS is the goal ... can stay longer at that version ... becomes more stable over time. IF ... BIG IF ... you keep up-to-date with the point releases. Comment: am guessing that your hyper jump to current version was done without git.
So what did you find in your research of MySQL vs MariaDB?
Uhhh ... why do I get the feeling that 'we' are gonna wait another 4 years to get Moodle version x.x to whatever is latest and greatest [or close] at that time?
By then ... ?????
'SoS', Ken
Start with disclosing where you ended up with DB - which and version. And did you take it all the way to 4.0.4+?
Did the 'more info' link take you to a page?
Turn on debugging to see if there is more info when attempting add a user manually.
'SoS', Ken
Lots to do when marching a moodle.
On this response:
https://moodle.org/mod/forum/discuss.php?d=438365#p1767201
"At that version, also check plugins. Moodle admin check Environment. Update component. Check there. All OK? Then next step in the 'march'."
Had you done that, at the bottom of the check, moodle would have warned about not being 'fully compliant with recommended database settings' ... something like that.
Same exact error? That thread was about upgrading to 4! IF so, maybe you didn't check Environment, update component and check to see what moodle might be complaining about.
Series 3 of moodle, although not a requirement, highly recommended, some settings
for DB (MySQL or MariaDB):
Barracuda + InnoDB + character set utf8mb4 with collation utf8mb4_unicode_ci.
If you had done the checks you would have seen that at the bottom of the check output.
Barracuda should be default for newer DB version - MySQL or MariaDB.
Character set/collation easily fixed from command line with scripts in code/admin/cli/
At least you've caught it now ... before upgrading to 4.
'SoS', Ken
Well... I could respond to some of your responses (actually argue that you didn't) ... but I won't.
Anyhoo ...
First, make a backup of your DB.
If you don't suffer from 'clas' (command line avoidance syndrome), you can fix.
ssh into server and ...
In code/admin/cli/
php mysql_collation.php
will bring up a help screen
suggest you do php mysql_collation.php -a
to see the collations needed are available.
Looking for utf8mb4_unicode_ci in that list
IF there, now up arrow
and change the ending of that command to:
php mysql_collation.php --collation=utf8mb4_unicode_ci
See * below ...
Now:
php mysql_compressed_rows.php -i to get info on DB
-f the fix switch *Attempt to fix all tables (requires SUPER privilege)*
Do you know super user crews?
or
-s shows the sql that you could use logging onto the DB using client
and creds (user/password) seen in config.php
* edit config.php at code root file and make this change:
'dbcollation' => 'utf8mb4_unicode_ci',
The php sodium ... not installed?
What OS is this? and do you have root access?
To install php sodium using package manager yum, dnf, or apt-get ... depending on OS.
You might need to contact hosting provider support for that!
'SoS', Ken
Sorry ... had to comment on this one:
"The upgrade should be simple with few things to look for and then you forget and do the actual work that is ...... use Moodle."
Let's remember you are upgrading from an old un-supported (should have been upgraded already) version of Moodle. Newer versions of moodle have different requirements (php/extensions/DB/ and so on an so forth) ... so things aren't so simple.
If you have been the admin of this site all along, think when you looked at how to upgrade and what was required, you decided to postpone - for years. Thus, you are where you are! :|
But ... you've finally decided to upgrade ... good!
Hope there will be some 'take aways' from this experience.
'SoS', Ken
$ php admin/cli/mysql_collation.php
MySQL collation conversions script.
It is strongly recommended to stop the web server before the conversion.
This script may be executed before the main upgrade - 1.9.x data for example.
Options:
--collation=COLLATION Convert MySQL tables to different collation
-l, --list Show table and column information
-a, --available Show list of available collations
-h, --help Print out this help
Example:I believe, your original question "MySQL or MariaDB" has been solved. If you have been using MySQL there is no urgent (technical) need to switch to MariaDB. Yes, you need to be careful about the compatible versions. Here is the usual summary: http://www.syndrega.ch/blog/#php-and-dbms-compatibility-of-major-moodle-releases.
$ sudo -u www-data /usr/bin/php admin/cli/mysql_collation.php --collation=utf8mb4_unicode_ci