upgrade path?

upgrade path?

by Danny Wahl -
Number of replies: 11
I copied down the VM of our moodle server to my machine, fired it up, and ran a cvs update changing from 19_STABLE to HEAD - it pulled the files, and then I went to 'notifications' but nothing happens.

I just see the "your are running 20100404" and that my site has been registered.

did I miss a step?

if I open up version.php it contains:

// MOODLE VERSION INFORMATION
// This file defines the current version of the core Moodle code being used.// This is compared against the values stored in the database to determine// whether upgrades should be performed (see lib/db/*.php)
 $version = 2010050411; // YYYYMMDD = date of the last version bump // XX = daily increments
 $release = '2.0 Preview 1 (Build: 20100510)'; // Human-friendly version name
Average of ratings: -
In reply to Danny Wahl

Re: upgrade path?

by Danny Wahl -
ok, I got it going but I died half way through the update:

mod_resource

Unknown error upgrading mod_resource to version 2009062600, can not continue.

More information about this error


so now the test environment is dead in the water (not a big deal, that's why it's a test)


so here's the only information that I think may have caused the problem:

I did NOT copy down the data from the moodledata folder, just recreated the folder on the test server b/c it was in the Gb.

So:

copy host environment
copy SQL database
no moodledata

the page worked fine before I attempted upgrade- just no pictures/resources b/c of the broken links to missing moodledata files.
Average of ratings: -
In reply to Danny Wahl

Re: upgrade path?

by Alan Hardy -
Hi Daniel

I am experiencing the same error(Unknown error upgrading mod_resource to version 2009062600, can not continue.) when i try to do a test upgrade from 1.97 to 2.0.

I have the db dump, system root and moodledata files copied to my test server. The 1.97 install was working correctly untill i attempted upgrade. I have run the upgrade several times each to confirm whether it was a one off but i can reproduce it every time.

Is their anyway we can debug this? i am unable to get any debug output even with $CFG->debug = 6143; set in my config.php. Any help would be greatly appreciated as i really need an upgraded version of our system for testing perposes.

Cheers






Average of ratings: -
In reply to Alan Hardy

Re: upgrade path?

by João Filipe Oliveira -

Same error (Unknown error upgrading mod_resource to version 2009062600, can not continue.) trying to upgrade 1.9.5 to 2.0 RC1. I can do clean install.

Average of ratings: -
In reply to João Filipe Oliveira

Re: upgrade path?

by David Hallam -

just a note i am also getting the same error on an upgrade from the latest 1.9 weekly to 2.0 and i have had issues with the database collation which has now all been changed to utf8_unicode_ci, and im still getting this message.

Not too big a deal as this is my test enviroment but when we do upgrade to moodle 2.0 or 2.1 next year will need a fix for this.

i have been testing on a virtuall clone of our working 1.9 server.

Average of ratings: -
In reply to Danny Wahl

Re: upgrade path?

by Martin Dougiamas -
Picture of Core developers Picture of Documentation writers Picture of Moodle HQ Picture of Particularly helpful Moodlers Picture of Plugin developers Picture of Testers
Hmm, are you sure you got the full set of new code?

cvs -q update -dPA

Try putting this in your config.php too, to get full debugging info:

$CFG->debug = 38911;
$CFG->debugdisplay = true;
define('MDL_PERF' , true);
define('MDL_PERFDB' , true);
define('MDL_PERFTOFOOT', true);
Average of ratings: -
In reply to Martin Dougiamas

Re: upgrade path?

by Alan Hardy -
Hi
I have made sure i have the newest version and have set the config variables. The error still occured but this time with the stack trace of

Stack trace:
line 183 of /lib/upgradelib.php: upgrade_exception thrown
line 102 of /mod/resource/db/upgrade.php: call to upgrade_mod_savepoint()
line 510 of /lib/upgradelib.php: call to xmldb_resource_upgrade()
line 294 of /lib/upgradelib.php: call to upgrade_plugins_modules()
line 1266 of /lib/upgradelib.php: call to upgrade_plugins()
line 268 of /admin/index.php: call to upgrade_noncore()


At a first glance it appears that the upgrade_mod_savepoint function is being passed an empty $result variable. I will have a look at to why this is happening and will post my findings soon.

Cheers
Average of ratings: -
In reply to Alan Hardy

Re: upgrade path?

by Alan Hardy -
It appears the empty result is intentional as tracing to the /mod/resource/db/upgrade.php shows that false is passed to generate the error. It appears that the condition occures because old the old record count is 0.

I will continue to investigate and see why this situation can occur.

Cheers
Average of ratings: -
In reply to Alan Hardy

This forum post has been removed

The content of this forum post has been removed and can no longer be accessed.
In reply to Deleted user

Re: upgrade path?

by Jason Turnbull -

Has anyone made any headway with this?

I have successfully upgraded with our staff db, but when I try it on the student one, it fails with the above error.

Average of ratings: -
In reply to Jason Turnbull

Re: upgrade path?

by David Mudrák -
Picture of Core developers Picture of Documentation writers Picture of Moodle HQ Picture of Particularly helpful Moodlers Picture of Peer reviewers Picture of Plugin developers Picture of Plugins guardians Picture of Testers Picture of Translators
As you have copied the site to another machine/VM, do you access the test site using the same URL as the production site is running at? Sorry I am not sitting by my laptop now (blame smartphones ;)) so can't check the source code for details but generally Moodle requires to be accessed using static URL for wwwroot.
Average of ratings: -