Unable to upgrade from 3.6.4 to 3.7 using git

Re: Re: Unable to upgrade from 3.6.4 to 3.7 using git

by Ken Task -
Number of replies: 5
Picture of Particularly helpful Moodlers

Well, having nothing important to do today ... joined the ranks of 'omicron' testers.

Installed a 3.6.highest via git and got that setup (minimal), checked it out, ok.

Then upgraded it via git to 3.7+ ... 'pluses' mean there has already been some fix applied.

Clip from upgrade process ... via command line ...

up to 3.7

Your site is currently in CLI maintenance mode, no web access is allowed.
Branch MOODLE_37_STABLE set up to track remote branch MOODLE_37_STABLE from origin.
Switched to branch 'MOODLE_37_STABLE'

then ran through the DB updates ...

-->System
++ Success (1.24 seconds) ++
-->antivirus_clamav
++ Success (0.02 seconds) ++
-->availability_completion
++ Success (0.02 seconds) ++
-->availability_date
++ Success (0.02 seconds) ++

Then

== Setting new default values ==

A bunch of new settings getting just defaults ...


New setting: optionalsubsystems_enablecoursepublishing
New setting: optionalsubsystems_enableasyncbackup

and so on ...

Command line upgrade from 3.6.4+ (Build: 20190524) (2018120304.04) to 3.7+ (Build: 20190524) (2019052000.01) completed successfully.

FireFox ... latest ...

logout
log back in again
Correct creds
get
Secure Connection Failed

An error occurred during a connection to my server.

    The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
    Please contact the website owners to inform them of this problem.

same issues when 37 tried to setup moble.
Try again
Resend ... logged on.

Checked on Mobile settings ...

** It seems that the HTTPS certificate is self-signed or not trusted. The mobile app will only work with trusted sites.

Now am not sure what ssl checker code is using but using LetsEncrypt and Qualsys SSL Labs test of server grades out as A

Ciphers could use a little tweaking but nothing major.

Bottom line though ... doable - with minor hickup at end for Mobile.

'SoS', Ken


Average of ratings: -
In reply to Ken Task

Re: Re: Re: Unable to upgrade from 3.6.4 to 3.7 using git

by Ray Havlin -
So the short story is that I am keeping Moodle as pristine as possible to allow the development cycles to be natively progressed. Other than configuring Moodle via the application, I am not altering the base installation.

So... I originally started with a clean install of 3.5.0 and have been doing the minor upgrades up to 3.6.4 with no problems whatsoever. Now that I'm upgrading to 3.7.0+ I was expecting a typical upgrade process.

Here's what I've been doing:
Put into Maintenance Mode
(Backup all Moodle and Data directories along with SQL backups, of course)

Use git to pull the latest stable build...
# git branch --track MOODLE_37_STABLE origin/MOODLE_37_STABLE
Branch 'MOODLE_37_STABLE' set up to track remote branch 'MOODLE_37_STABLE' from 'origin'
# git pull
(This is all there is to it - right? Or am I not using git correctly here?)

Then simply login back into Moodle with Admin account to trigger the upgrade process.
This process has always worked flawlessly for all previous upgrades.

In this case with 3.7.X, the server can't run the upgrade for some reason and it drops back to my html directory and executes the base index.html. So I see the home page instead of the Moodle login screen.

I read about the new upgrade via the command line, but I wasn't sure that would provide a different result. So, I will roll back to 3.6.4 and attempt another upgrade using the command line approach.




Average of ratings: -
In reply to Ray Havlin

Re: Re: Re: Re: Unable to upgrade from 3.6.4 to 3.7 using git

by Ken Task -
Picture of Particularly helpful Moodlers

To upgrade ... from the root of the moodle code directory ... where you can see the hidden .git directory ..

git branch --track MOODLE_37_STABLE origin/MOODLE_37_STABLE

git checkout MOODLE_37_STABLE

php admin/cli/upgrade.php non-interactive

Above shows executing as root user so you will have to chown on all directories/files in code.

chown apache:apache * -R

To check version ... fgrep '$release' version.php from root of code directory.

To check which branch one is following:

git branch -a

* should be at desired version.

upgrading via command line takes your web service out of the loop during the upgrade,   It will still show errors if there are any.

'SoS', Ken

Average of ratings: -
In reply to Ray Havlin

Re: Re: Re: Re: Unable to upgrade from 3.6.4 to 3.7 using git

by Ken Task -
Picture of Particularly helpful Moodlers

Also ...

"In this case with 3.7.X, the server can't run the upgrade for some reason and it drops back to my html directory and executes the base index.html. So I see the home page instead of the Moodle login screen."

Also ... appears you have a WordPress ... using any conflicting .htaccess settings?

You could add the debug lines from config-dist.php to config.php to see what Moodle might be reporting and also check apache error logs.

'SoS', Ken

Average of ratings: -
In reply to Ken Task

Re: Re: Re: Re: Unable to upgrade from 3.6.4 to 3.7 using git

by Ray Havlin -
Ken

The email notification for your last two posts when into my Junk mail - not idea why!

I will apply your steps and get back to you with the results.

Thanks for this - really helps!

Ray
Average of ratings: -
In reply to Ken Task

Re: Re: Re: Re: Unable to upgrade from 3.6.4 to 3.7 using git

by Ray Havlin -
Great News! Using the command line instead of the browser worked just fine!

Thanks again for help.

Ray
Average of ratings: -