Assignment

Thanks, Leon.

I went back to the previous page, turned on Dev Tools->Networking, then clicked Grade.

Below is a screenshot. It looks like the same info, though doing it from the previous page I now see the XHR info.

I fear this is not what you meant by "work back from ...preferences." Do you mean check the request/response headers of the status 200 entries with the GET method? I am trying to be thorough with this post but feel that it's a swing and a miss if it's just repeating the same information. :\

Yes, I am very confused by what's going on. I feel like it's most likely on my end, but can't think of what I did to cause it. I have been running a Moodle server for around 10 years. I'm no expert, but I'm not without experience. I am stumped at the moment but will keep digging.

Thanks,
Greg

P.S. I cropped off the request headers in order to show that all previous requests were successful. I checked and it looked like the requests the same as the previous pic, but I didn't do a side-by-side comparison.

I gave up on mod_security .... was getting too many false positives and mis-directed errors - but that could have been result of adding rules from OWASP Core Rule Set (CRS) download.

Watch the video ... but ... that only leads to more questions ..

You've given software info and versions but not how you are running php - php as php-fpm?

I recently helped someone that had remi repo and somehow got 2 php-fpm www pools running - one from native and one from remi - would see 'you don't have permission' errors.

From command line:

ps aux |grep php

And the fact you are kicked out and have to login again ... sessions related!!!??? ... moodledata/sessions/ is where those files live.

Any issue with space for moodledata?

Also, how is your cron job running?   From command line?

And another also ... in code/admin/cli/ run check_database_schema

'SoS', Ken

To stop the cron from the looping, add this line to config.php

$CFG->cron_keepalive='0';

Do you have your cron setup with the 'la-la-land' redirect?

You could change that redirect to a log file that is constantly overwritten and be able to watch the log file in realtime with

tail -f /var/log/moodle-cron.log

How to:

touch /var/log/moodle-cron.log

chown apache:apache /var/log/moodle-cron.log

Then in setup of the cron job .... > /var/log/moodle-cron.log

You could do that for all your moodles ... only to different log files.

I have a server with multiple moodles running.

/var/log//mdlandcli-cron.log
/var/log/mdlsamples-cron.log
/var/log/m44sb-cron.log

Can watch those logs via:

tail -f /var/log/m44sb-cron.log

When it runs for the m44sb instance, I see what it is doing in realtime.

Leave setup of cron to run once every minute .... yes, with multiple instances of moodle that will spike memory usage but not for long.

I do multiple moodle sites using a bash shell script that has 3 one liners ... each line runs different moodle instance.

In the setup of cron job, I point to that script ... they each run, 1 at a time.

Not all task in cron will run at same time ... so some runs of cron job are actually less than other runs.   Obviously, the moodle that is used will have more to do and your sandbox instances will have less.

Please run:

cd /path/to/moodle/code/admin/cli/

php check_database_schema.php

'SoS', Ken