H5P activities preventing course backup - error 500
I have a site where H5P has been installed and has run without problems for around 6 months. However, we then started to experiences problems with not being able to backup courses. The only installations to the system was the addition of the checklist plugin which on other sites has not resulted in problems with H5P. It took a while to workout that H5P was the culprit. If I delete all H5P activities from a course it then backsup without problems.
There are 3 symptoms relating to H5P that may shed light on what might be causing the problem:
- Interactive video and Branching tools partially load and shows the error: [field:group:branchingScenario:branchingScenario].
Presentation and other tools work fine. Directory permissions for hvp are 755.
- On all H5P tools the Reuse content link downloads fine but when you upload the resulting file it shows the error:
Validating h5p package failed. Could not find library.json file with valid json format for library H5P.IVHotspot-1.
This error replicates on other sites where H5P is working as expected.
- The H5P library Plugins> Activity Modules > H5P Libraries lists and shows all the types. Hub is ticked in the settings.
Site admin > H5P > Manage content types lists nothing even after content type is loaded and cache is refreshed.
This is a hosted site so I have limited access to http config files etc. However the provider has compared the server config files to some of my other hosted instances and they see no differences in the files.
The error log files only register a time out without further detail and result in an internal 500 error message.
I have tried automated backups with cron but no backups are created.
I have upgraded the site from 3.7 to 3.8.2 including upgrading all plugins, but the problem persists.
I have run Check on the database and all tables are OK.
I would be grateful for any ideas that might resolve this. I have 5 other Moodle instances of the identical software and plugin configurations running with the same hosting service and these are all running as expected. My gut instinct is that it may be some issue in the moodledata folder, but this folder and how it relates to the system data is is not entirely clear to me yet.