My moodle version, from version.php is
$version = 2018051705.03; // 20180517 = branching date YYYYMMDD - do not modify!
// RR = release increments - 00 in DEV branches.
// .XX = incremental changes.
$release = '3.5.5+ (Build: 20190322)'; // Human-friendly version name
$branch = '35'; // This version's branch.
$maturity = MATURITY_STABLE; // This version's maturity level.
I just updated this yesterday. Previously I was running another version of 3.5 but with same problems I'm about to describe.
I'm running it on Centos OS 6.10 with php 7.1.27 and mariadb 5.5.63-1
Up until couple of months ago when I was running 3.4 something everything was great. Now the problem is whenever a student submits an assignment moodle is unresponsive. They upload a file, click save changes and the site is unresponsive. The file does get uploaded. They can't access the site until about 20mins later or with a different browser. I've verified this with a test account and switching my role to a student. I'm guessing this is the timeout for sessions.
I've enabled debug setting in moddle and verified in the config.php file the debug settings are on
@error_reporting(E_ALL | E_STRICT); // NOT FOR PRODUCTION SERVERS!
@ini_set('display_errors', '1'); // NOT FOR PRODUCTION SERVERS!
$CFG->debug = (E_ALL | E_STRICT); // === DEBUG_DEVELOPER - NOT FOR PRODUCTION SERVERS!
$CFG->debugdisplay = 1; // NOT FOR PRODUCTION SERVERS!
but I don't see any error messages in my apache webserver's error log.
I've tried purging all caches several times.
I've verified that in the moodle data directory there are files being created in the cache and localcache subdirectory. My moodle data dir. is separate from the moodle web directory.
Thanks for any help. I'm a bit wary of upgrading to 3.6 in the middle of the semester.