When upgrading from 3.5.1 to 3.5.17 we have had multiple issues with plugins. In our latest attempt we updated the plugins and then ran the Moodle upgrade. After installing the two available updates "course_overview" block and "adminer" local plugin and the pressing the "Upgrade Moodle database now" button it seems to hang. I load the /admin/index.php page again and see this below. Pressing the button just goes to a blank screen. It seems like it is hanging up on one of the updates.
Think it would help if you gave some info about your setup.
Also ... check your web server error logs. Blank pages should record something in a log somewhere!
Reverting back to old version on same server should work - that would include restoring a DB dump to new blank DB + reverted code (plugins and all) + change to config.php to point to new reverted DB.
Once that's done ... suggest clearing server caches in moodledata/cache/ moodledata/muc/ moodledata/localcache/ manually ... safe to do as moodle will repopulate upon use.
- 4 CPUs, Dynamic Memory - Max: 4GB, 200GB Disk space/100GB Free
Ubuntu version: 16.04.16
Apache Version: 2.4.18
MySQL Version: 5.7.33
PHP Version: 7.0.33
Moodle Version: 3.5.1 (Build: 20180709)
MySQL is using UTF8 instead of UTF8MB4
PHP memory limit 2GB
We have been taking snapshots via Hyper-V and reverting back to 3.5.1 and then trying the update over and over. This is just a DEV version of the server, to test it we can do it our production server.
I will look for logs after we try again and post more info.
uname -an as root - looking to see the ubuntu distro - they distrib one especially built to run in guest OS of a HyperV (Windows) - me thinks.
Ubuntu 16.04.16 - when does that reach EoL? ".... will no longer be supported by April 30, 2021".
Have a repo for PHP versions 7.2,.3.4? You will be upgrading PHP.
That's all that's in my.cnf?
Suggest installing mysqltuner ... perl script and run it with superuser creds to DB server.
Suggest logging in as admin level, going to Server -> Environment -> update component. Then choose higher versions of Moodle in drop down pick list as well as noting what it says about 'full compliance' concerning DB (innodb/Baracuda/utf8mb4 character set and utf8mb4_unicode_ci)
And a blog that will help with versions during your march of Moodle:
Something else to think about while practicing this 'march' of Moodle to destination version .. using git.
Following the old directions for updating or upgrading has too many moving parts .... git doesn't - much less prone to human error.
Well ... above is a start!