Hi Visvanath
Thanks for the reply.
>So you didn't do a 'dist-upgrade', reinstalled Ubuntu instead, right? If you did a 'dist-upgrade' you could have left Moodle untouched.
I didn't do dist-upgrade because my moodle server has been running for many years and extra packages have been installed at times along the way and I wanted a clean install to match exactly what I had tested on my test server. I had successfully fully restored my live moodle onto 14.04 on the test server a couple of weeks before I did the rebuilt. Unfortunately, I'm not able to access the test server now as it's only available on my internal network and I'm now out of the office.
>> Sorry, the requested file could not be found
.>
.> More information about this error
>What those "More information" were, could be interesting. ;)
'more information' was simply the link to moodledocs provided by the moodle error message at https://docs.moodle.org/26/en/error/moodle/filenotfound sorry, I thought I had pasted the link not just the text.
>Unless you know exactly what you are doing, a Moodle site should have _one_ URL, the one in config.php! (There are advanced configurations and hacks to do anything, you can't ask those things here.)
I wasn't doing any crazy hacks - just my apache 2.2 setup had an alias in the virtual host for
alias /moodle /usr/share/moodle
which worked. My apache 2.4 has the same alias but it doesn't appear to work.
I have been able to confirm that my first restore of moodledata did not copy completely and have been to locate missing files in the database and backed up moodledata using NathanFriend's advice: http://www.nathanfriend.co.uk/find-where-moodle-2-has-put-your-file/
> A backup which was not restored is not a good backup!
very true. If I had my time over, I would have completely repeated the process one more time on my test server with the very latest backup and let it run for a while. However, I gave in to time pressure and now I'm here.
Having said that, I had checked backup sizes and times before starting the process and having found the files last night, I am confident that the backups were correctly taken and can be restored. My next move will be to restore onto a server running apache 2.2 but I can't do this until I can get into the office on Monday
I think the problem must be with my new configuration of apache 2.4 (also now using php-fpm) or else some permissions problem on moodledata. I've done
chown -R www-data:www-data moodledata
chmod -R 0770 moodledata
which I believe are the best settings and the ones I was using beforehand.
I'm just sure I've missed something and was hoping a second person could look on with a cool head and spot it
Carol
One more piece of information: I have submitted a file to an assignment since the 'upgrade' and the link to it appears as expected but the file itself is inaccessible. Again, the file exists in moodledata (I found it using the method I mentioned above) and can be downloaded direct from the server.