Until recently i havent had an issue with restoring large courses however whenever i try to restore a moodle 1.9 course (done plenty so far) i either get an internal server error or a JSON error.
Environment:
Moodle 3.2
Custom Theme (tried with Clean theme and get same issue)
| Apache Version | 2.4.25 |
| PHP Version | 5.6.29 |
| MySQL Version | 5.6.34 |
| Architecture | x86_64 |
| Operating System | linux |
Php options set to
| allow_url_fopen | On |
| display_errors | Off |
| error_reporting | E_ALL |
| file_uploads | On |
| include_path | .:/opt/alt/php56/usr/share/pear:/opt/alt/php56/usr/share/php |
| log_errors | On |
| mail.force_extra_parameters | no value |
| max_execution_time | 3600 |
| max_input_time | 3600 |
| memory_limit | 1000M |
| open_basedir | no value |
| post_max_size | 2000M |
| session.save_path | /tmp |
| short_open_tag | On |
| upload_max_filesize | 2000M |
In debug console i get the following information:
Debug Console
yui_combo.php?rollup/3.17.2/yui-moodlesimple.js&rollup/1488411112/mcore-debug.js:5828
moodle-core-lockscroll: Enabling LockScroll.
yui_combo.php?rollup/3.17.2/yui-moodlesimple.js&rollup/1488411112/mcore-debug.js:5828
moodle-core-lockscroll: Setting the activeScrollLocks count from 0 to 1
yui_combo.php?rollup/3.17.2/yui-moodlesimple.js&rollup/1488411112/mcore-debug.js:5828
moodle-core-lockscroll: LockScroll already active. Ignoring enable
request
INSTANCE.log @ yui_combo.php?rollup/3.17.2/yui-moodlesimple.js&rollup/1488411112/mcore-debug.js:5828
enableScrollLock @ yui_combo.php?3.17.2/plugin/plugin.js&m/1488411112/core/lockscroll/lockscroll-debug.js:326
updateScrollLock @ yui_combo.php?3.17.2/plugin/plugin.js&m/1488411112/core/lockscroll/lockscroll-debug.js:394
makeResponsive @ yui_combo.php?rollup/3.17.2/yui-moodlesimple.js&rollup/1488411112/mcore-debug.js:42934
centerDialogue @ yui_combo.php?rollup/3.17.2/yui-moodlesimple.js&rollup/1488411112/mcore-debug.js:42962
visibilityChanged @ yui_combo.php?rollup/3.17.2/yui-moodlesimple.js&rollup/1488411112/mcore-debug.js:42897
_notify @ yui_combo.php?rollup/3.17.2/yui-moodlesimple.js&rollup/1488411112/mcore-debug.js:13680
notify @ yui_combo.php?rollup/3.17.2/yui-moodlesimple.js&rollup/1488411112/mcore-debug.js:13709
_notify @ yui_combo.php?rollup/3.17.2/yui-moodlesimple.js&rollup/1488411112/mcore-debug.js:13372
_procSubs @ yui_combo.php?rollup/3.17.2/yui-moodlesimple.js&rollup/1488411112/mcore-debug.js:13498
CEProto.fireComplex @ yui_combo.php?rollup/3.17.2/yui-moodlesimple.js&rollup/1488411112/mcore-debug.js:27763
_fire @ yui_combo.php?rollup/3.17.2/yui-moodlesimple.js&rollup/1488411112/mcore-debug.js:13445
fire @ yui_combo.php?rollup/3.17.2/yui-moodlesimple.js&rollup/1488411112/mcore-debug.js:14600
_fireAttrChange @ yui_combo.php?rollup/3.17.2/yui-moodlesimple.js&rollu
Log shows
[01-Mar-2017 23:30:23 Europe/London] PHP Notice: jQuery plugin 'migrate' can not be found in component 'core'.
- line 524 of /lib/outputrequirementslib.php: call to debugging()
- line 50 of /theme/customtheme/lib.php: call to page_requirements_manager->jquery_plugin()
- line 619 of /lib/outputlib.php: call to theme_bowlandbase_page_init()
- line 1033 of /lib/outputrenderers.php: call to theme_config->init_page()
- line 114 of /index.php: call to core_renderer->header()
These types of errors are typically caused by the script that you are running. In this case Moodle is missing important core files or some of the core files are corrupted due to any recent changes that you have made. The result then caused a memory spike on your account.