Howard Miller

Check Site administration > Server > Task logs

Filter to find the failing tasks. What do the logs say?

The default student role cannot change their own grades. So it's *something* you changed. The capability is moodle/grade:edit which the student role (again by default) does not have.

In your course, go to Participants and then change the dropdown at the top-left to 'Check permissions'. Pick a user who you believe can change their own grades (and should not) and check whether or not they have this capability. We can go from there.

If it helps, here is the basics of my docker compose file that is currently running my 5.0 test/dev environment. You'll need to fill in some of the details, but it shouldn't be too hard. Use in production is obviously a different matter but I don't think you'd build a production site like this...

services:

webserver:
    image: "moodlehq/moodle-php-apache:${PHP_VERSION}"
    container_name: "${PROJECT_NAME}_webserver"
    ports:
        - '${WEBSERVER_PORT}:80'
    volumes:
        - ./web:/var/www
        - ./config/php/php.ini:/usr/local/etc/php/conf.d/my_apache2_php.ini

mariadb:
    image: mariadb:latest
    container_name: "${PROJECT_NAME}_db"
    environment:
        MYSQL_ROOT_PASSWORD: $DB_ROOT_PASSWORD
        MYSQL_DATABASE: $DB_NAME
        MYSQL_USER: $DB_USER
        MYSQL_PASSWORD: $DB_PASSWORD
    volumes:
        - ./mariadb/:/var/lib/mysql
    ports:
        - '${DATABASE_PORT}:3306'

redis:
    image: redis:latest

Personally... I would put your site into maintenance mode and then completely delete the 'temp' folder in your 'moodledata' folder. Then bring it out of maintenace. It will recreate automatically. Clear the faildelay on the tasks page and see what happens.

It can't hurt to install Redis - it's generally very simple to setup a Redis server. Make sure you understand the Cache configuration page. The UI isn't the most obvious. You need to set up a new Redis instance at the top and then go all the way to the bottom of the long page to configure default caches (to point them to Redis). Don't try to edit each, individual cache instance.

Other than that, you're going to have to do more monitoring and testing to find where the bottleneck is.