Second attempt at upgrading 1.9 to 2.0 (Part 2)
Posted on April 14th, 2011 in Administration, Moodle 2.0 | 2 Comments »
..continuing on with my 1.9 to 2.0 journey
As I mentioned in my previous post I was stuck on the “migrating courses” page when I tried upgrading from Moodle 1.9.11 to 2.0.2. The two errors coming up were “Incorrect pool file content” and a number of stack trace errors:
I did some Googling and found 2 tracker items regarding these issues but it didn’t seem like it was during the upgrading process. I did find one discussion thread from a few months back about this issue that helped me troubleshoot.
First, I turned on as much debugging, error reporting or messages I could in the config.php file (not sure if there are other debugging settings to turn on?):
The debugging information didn’t help too much and I couldn’t find any error logs regarding this issue, so I continued to Google and research online. I checked out the /lib/filestorage/filestorage.php file because that was the file where the apparent first two errors were happening. I’m no expert at PHP so I wasn’t quite sure how to change or echo any further information when upgrading to see if it gave me anything more to work with.
I continued to read through the discussion thread I mentioned over and over and thought maybe it was corrupt file, too big of a course or file, etc. I looked in my moodledata folder [see path below]
and found a file named with a random string of characters – which was the same string that was displayed in the “incorrect pool file content” error.
There were two other files with a long string of characters that were the same as two long strings of characters which were being displayed in the debugging information (these strings were successful operations). The two files weren’t big, the problem hash named file however was 500 MB. Was this the problem? I didn’t dare change anything via the moodledata folder.
I figured it was a file issue in one or more courses..I went into phpMyAdmin and started deleting courses, hoping a corrupt file would be removed and fix the issue. I had 3 imported courses from our production server that I restored on the 1.9 testing server to test “real life” courses in the upgrade process.
I deleted two of the four courses, same error. Went back and deleted another course. Tried again, boom – worked. Since I had all of the debugging and information set to display it displayed all of the database stuff. Clicked Continue. It displayed tons of new settings, clicked Continue – MOODLE 2.0!
Success! Sort of..well..half way…I was able to upgrade from a 1.9.11 to 2.0.2 but I had to delete a few courses first. I believe I had to delete the courses that I imported from our production server (v 1.9.9). Only one course made it through, which I initially created on that install.
So it looks like the course migration is the issue – something with the files (doesn’t surprise me). I’m going to roll back to 1.9 and import different courses, create a few more courses and try again. I’ll post my results after I try it out again.
Related Posts














