Upgrade to 21.04.1 fails with file ".../embedly/lib.php" does not exist

Bug #1930998 reported by hermannkm
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mahara
New
Undecided
Unassigned

Bug Description

**History**
Yesterday I tried to upgrade from 20.04 to 21.04.1 which failed when as usual trying to run

sudo -u www-data php cli/upgrade.php

I sadly did not manage to copy the message, it was somewhat about a missing file named

...embedly/lib.php

leaving the upgrade non functional.
Today I ran cron on my 20.04 and got a very similar message:

[WAR] c7 (lib/mahara.php:1616) File /var/www/mahara-20.04.0/htdocs/artefact/outcome/lib.php did not exist
Call stack (most recent first):
  * safe_require(string(size 8), string(size 7)) at /var/www/mahara-20.04.0/htdocs/lib/mahara.php:4415
  * recalculate_quota() at /var/www/mahara-20.04.0/htdocs/lib/cron.php:198

A nonrecoverable error occurred. This probably means you have encountered a bug in the system

**Problem**
Both files mentioned (...outcome/lib.php and ...embedly/lib.php) DO NOT exist. But why does the script try to get them? Did not find any hint in database or file system.

**Versions**

Mahara 20.04.0
Ubuntu 16.04.4
mariadab 10.4.18

hermannkm (h-klocker)
summary: - Error when starting cron or upgrade on command line .../lib.php not
- found
+ Upgrade to 21.04.1 fails with File .../embedly/lib.php does not exist
summary: - Upgrade to 21.04.1 fails with File .../embedly/lib.php does not exist
+ Upgrade to 21.04.1 fails with file ".../embedly/lib.php" does not exist
Revision history for this message
Robert Lyon (robertl-9) wrote :

Hi hermannkm,

Can you check to see if those directories exist ?

The way Mahara works is if it spots a subdirectory in certain folders, like artefact or module it will expect there to be a plugin to install and so tries to read the lib.php file to find out more information.

If the directories exist but not the lib.php files then it's safe to assume there was an old plugin there but now has been partially removed. So feel free to delete those directories and things should work as expected again.

Hope that helps
Robert

Revision history for this message
hermannkm (h-klocker) wrote (last edit ):

Thank you, I managed to eliminate this problem with your hint.

Alas, my upgrade procedure fails again with another problem. As this seems to be a very different problem I filed it separately as https://bugs.launchpad.net/mahara/+bug/1934871.

I could think of force-restarting the upgrade procedure after the previous failure could be the culprit but I don't have a clue how to deal with that.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.