Can not read file, either file does not exist or there are permission problems

Can not read file, either file does not exist or there are permission problems

autor Howard Bates -
Počet odpovědí: 6

Hello,

I have upgraded from Moodle 1.9 to 2.1.1. Whenever I try to back up one of my courses (others work fine) I get the "Can not read file, either file does not exist or there are permission problems" error.

I am using Fedora 15 with Apache & MySql.

Thanks for any insight you may have!

Průměr hodnocení: -
V odpovědi na Howard Bates

Re: Can not read file, either file does not exist or there are permission problems

autor Jonathan Newman -

Can you restore courses that were backed up before the upgrade?

On our installation the files.xml in the .mbz is not being created properly by the backup tool. We have not found a resolution but it is something you can look into.

V odpovědi na Howard Bates

Re: Can not read file, either file does not exist or there are permission problems

autor Colin Fraser -

This error has turned up before, here is one look at it, and you might have a look here for a possible solution. If that change is already made to your Moodle then you might want to provide as much information as you can and create a new Moodle Tracker item. 

V odpovědi na Colin Fraser

Re: Can not read file, either file does not exist or there are permission problems

autor Howard Bates -

The solution you provide is for Windows servers. Do you think it will work on Linux installations?

Thanks!

V odpovědi na Howard Bates

Re: Can not read file, either file does not exist or there are permission problems

autor Howard Bates -
V odpovědi na Howard Bates

Re: Can not read file, either file does not exist or there are permission problems

autor Colin Fraser -

Sorry Howard, I had not picked up on this earlier, but the changes are to Moodle, not the environment. Moodle is a PHP Application and PHP is platform independent, as I understand the term to mean. So yes, this fix should work in any environment. However, having said that, the original fix was for an issue that was occurring in Windows and not Linux environments. What changed, I wonder.