Moodle in English: Troubleshooting upgrade from 3.2.9 to 3.3.8, nothing in logs

Troubleshooting upgrade from 3.2.9 to 3.3.8, nothing in logs

by lol code - Tuesday, September 18, 2018, 9:28 PM

I am trying to upgrade a Moodle install from 3.2.8 to 3.3.8. I am pretty new to Moodle but not PHP applications. This is an older installation. It was recently successfully upgraded to 3.2.8 from 3.1. It has a very large database and data folder.

PHP Version => 7.0.30-0ubuntu0.16.04.1 confirmed on command line and in apache. I have also checked that I have all the pre-requisite PHP modules.

After replacing the Moodle code I have tried both visiting the site and the command line version.

Visiting the site redirects to admin/index.php then gives an error 500. Apache access log shows the access and result code 500. Apache error log shows nothing. Apache log_level is set to debug.

Using the command line shows this:

user@d16:/home/web/elearning/moodle$ sudo -u www-data /usr/bin/php admin/cli/upgrade.php

== Upgrading Moodle database from version 3.2.9 (Build: 20180517) (2016120509) to 3.3.8 (Build: 20180910) (2017051508) ==

Your Moodle files have been changed, and you are about to automatically

upgrade your server to this version:

3.3.8 (BUILD: 20180910) (2017051508)

Once you do this you can not go back again. Please note that this process

can take a long time.

Are you sure you want to upgrade this server to this version?

type y (means yes) or n (means no)

I then type "y" and the script exits immediately. Nothing is in the logs.

How can I get more information to start troubleshooting this?

Re: Troubleshooting upgrade from 3.2.9 to 3.3.8, nothing in logs

by lol code - Wednesday, September 19, 2018, 12:15 AM

I have a little more information. I read the code and found the upgrade_log table.

It looks like nothing is happening in there. The last rows refer to the last successful upgrade (in July). There is no "Starting core upgrade" for the current version.

SELECT *,

from_unixtime(timemodified) FROM moodle.mdl_upgrade_log

order by id desc

'5305', '0', 'logstore_standard', '2016120500', '2016120500', 'Plugin upgraded', NULL, '', '0', '1530630822', '2018-07-03 15:13:42'

'5304', '0', 'logstore_standard', '2016120500', '2016120500', 'Upgrade savepoint reached', NULL, '', '0', '1530630822', '2018-07-03 15:13:42'

'5303', '0', 'logstore_standard', '2016052300', '2016120500', 'Starting plugin upgrade', NULL, '', '0', '1530630822', '2018-07-03 15:13:42'

'5302', '0', 'logstore_legacy', '2016120500', '2016120500', 'Plugin upgraded', NULL, '', '0', '1530630822', '2018-07-03 15:13:42'

....

Average of ratings: -

Re: Troubleshooting upgrade from 3.2.9 to 3.3.8, nothing in logs

by Emma Richardson - Wednesday, September 19, 2018, 12:50 AM

Do you have debugging turned on in moodle? If you cannot get in anymore, you can set this in config.php - a quick google will tell you how. Set it to the highest level - then try to run again and see if that helps.

What version of PHP are you running? It could be that your PHP version is not compatible? I believe 3.3 is about where PHP 7 comes in...

Average of ratings: -

Re: Troubleshooting upgrade from 3.2.9 to 3.3.8, nothing in logs

by lol code - Wednesday, September 19, 2018, 2:38 AM

Thanks! I have made some progress. I had just figured out how to show more debug info using config.php when you posted. That gave me an error I could work on which was a theme issue. I am now close. Now to do the same thing but with upgraded module code in place.

Average of ratings: -

Re: Troubleshooting upgrade from 3.2.9 to 3.3.8, nothing in logs

by Ken Task - Wednesday, September 19, 2018, 1:33 AM

From what you have described ... the upgrade stopped right after 'y' ... then nothing - if server has enough resources. If I re-call correctly, the upgrade scripts (web based or CLI) attempts to use 128M more memory if it can it it on upgrades.

Have already stated site has a large DB (how large is sql dump?) and a large moodledata directory.

So what does 'top' look like ... how much free memory do you have? Is DB server on same machine? and how are you running apache?

What are settings for php ... max memory for a script to consume ... max time to execute ... input vars?

And the access log won't tell ya much, but error logs will. Check the error logs of apache.

'spirit of sharing', Ken

Average of ratings: -

Re: Troubleshooting upgrade from 3.2.9 to 3.3.8, nothing in logs

by lol code - Wednesday, September 19, 2018, 2:43 AM

Thanks @Ken Task. Going through Apache was giving me nothing at all in the error logs but that was probably due to the debug settings that I was unaware of.

Once they were turned on I had a theme error on the CLI upgrade. It was related to block_overview_course_renderer. I had to add that legacy block module to the site and change to using the namespaced class name to continue.

Average of ratings: -

Installing and upgrading help

Troubleshooting upgrade from 3.2.9 to 3.3.8, nothing in logs