Berichten gepost door Alain Raap

Here are the trackers I found that are still open and are about locking issues:

https://tracker.moodle.org/browse/MDL-77851
https://tracker.moodle.org/browse/MDL-77852

Is the CFG->session_redis_acquire_lock_timeout = 120 value too low or is there something else that's causing the
cache locking problems? I also see that there are a lot of session keys in Redis that aren't deleted and still are in
the database.
Gemiddelde van de beoordelingen: Useful (1)
Both bugs work on our Moodle site in 4.1.6, the semi-colon problem in filenames wasn’t fun for teachers making courses droevig
I’ll have a look for the open trackers about locking problems next week
Gemiddelde van de beoordelingen:  -
We hoped that Moodle 4.1.6 would be the solution to our problems, but it still goes wrong.

There are several trackers about locking problems that aren’t resolved yet I saw on the Moodle Tracker site, on course level, but also in other parts of Moodle code.

Gemiddelde van de beoordelingen:  -
We are using Redis in a Moodle 4.1 environment and have the same problem (error ex_unabletolock) with tasks that
take a long responsetime. Is it a session or muc problem that this problem occurs? I can't see the error in our logfiles,
and I'm not able to debug in our environment.

In our config file we use these settings for Redis:

$CFG->session_redis_acquire_lock_timeout = 120;
$CFG->session_redis_lock_expire = 7200;
Gemiddelde van de beoordelingen:  -
I ran a fix today to remove the ';' in the filename in the mdl_files table with this query:

update mdl_files SET filename = REPLACE(filename, ';', ' ') WHERE filename LIKE '%;%';

(I replaced the ; with a space character, don't use a ':', Windows doesn't accept this character in a filename.)

After running the query the problem was solved and we could change and delete courses with the
filenames that were involved again.
Gemiddelde van de beoordelingen: Useful (1)