Posts made by Jerry Lau

having problems trying to reinstall a plugin after an upgrade to our moodle to 3.6.5. and holding our upgrade up

Tool_ally is refusing to install and holding things up. I read that one possible solution is to purge all cache, but I am unable to get to that screen from the loop I’m caught up in. I usually get back to the installation screen with this URL, but that doesn’t help me in this particular case, since I need to try purging all cache.

How can we run via CLI the purge cache feature?

thanks

Average of ratings: -

So we upgraded our production moodle last night from 3.4.9 to 3.6.5 (latest one) and saw this in my cron log
RHEL 7.5 64-bit, MySQL 5.7 and php 7.1.8
Never saw this error before ...
Server Time: Wed, 24 Jul 2019 00:33:01 -0700Execute scheduled task: Synchronise users task (auth_db\task\sync_users)
... started 00:33:01. Current memory use 14MB.
User entries to add: 16
Default exception handler: Exception - Call to undefined method cachestore_dummy::find_by_prefix() Debug:
Error code: generalexceptionmessage
* line 1796 of /cache/classes/loaders.php: Error thrown
* line 131 of /user/lib.php: call to cache_session->purge_current_user()
* line 465 of /auth/db/auth.php: call to user_create_user()
* line 60 of /auth/db/classes/task/sync_users.php: call to auth_plugin_db->sync_users()
* line 105 of /lib/cronlib.php: call to auth_db\task\sync_users->execute()
* line 67 of /lib/cronlib.php: call to cron_run_inner_scheduled_task()
* line 61 of /admin/cli/cron.php: call to cron_run() !!! Exception - Call to undefined method cachestore_dummy::find_by_prefix() !!!
PHP Fatal error: Uncaught coding_exception: Coding error detected, it must be fixed by a programmer: A lock was created but not released at:
/our/moodle/site/lib/classes/task/manager.php on line 520 Code should look like: $factory = \core\lock\lock_config::get_lock_factory('type');
$lock = $factory->get_lock(Resource id #1021);
$lock->release(); // Locks must ALWAYS be released like this. in /our/moodle/site/lib/classes/lock/lock.php:117
Stack trace:
#0 [internal function]: core\lock\lock->__destruct()
#1 {main}
thrown in /our/moodle/site/lib/classes/lock/lock.php on line 117
thoughts?






Average of ratings: Useful (1)
This maybe a caching result so I will purge the cache and see what happens tomorrow.. it only runs once a day... I've already deleted the contents in 5 temp folders before this happened so that is not the cause... #crossfingers

https://tracker.moodle.org/browse/MDLQA-12282?jql=project%20%3D%20MDLQA%20AND%20component%20%3D%20%22Moodle%20Package%22

I tried to export it as CSV but the formatting does not render properly and the Word only shows part of the description (not fully list).

I want to go through the same test cases when we do an upgrade annually.

Thanks!

Average of ratings: -