Error reading from Data base

Asked By 20 points N/A Posted on -

Hi friends,

I was running Moodle 2.3.1 (using Build: 20120726).

While I was attempting to restore a course backup I was greeted with the following error

Moodle 2.3.1 (using: 20120726) more information link error reading from database

I proceeded to click on the "More information" link, and was faced with the following message:

Purge all cache

Purge all caches

MoodIe can cache themes, JavaScript, language strings, filtered text, RSS feeds and many other pieces of calculated data.

Purging these caches will delete that data from the server and force browsers to refetch data, so that you can be sure you are

seeing the most up-to-date values produced by the current code. There is no danger in purging caches, but your site may

appear slower for a while until the server and clients calculate new information and cache it.

Purge all caches Cancel

I Chose to purge all the caches, but the problem still persisted.

I have successfully restored other backup files in the past using the current install of Moodle.

The problematic backup file has also previously been used successfully a number of times.

I found that this same error also shows up when I select Site Registration/Administration:

Does anyone have a clue about this error and how to deal with it?

Best Answer by Edmund Joseph
Answered By 0 points N/A #192713

Error reading from Data base


Hello Jhon,

Could you by chance be restoring as well as changing course name/details in order to replicate? And if so at what point in the restore process does are doing that? That could be the cause of the issue.

You can try debugging and see if that will resolve the issue.



Best Answer
Best Answer
Answered By 5 points N/A #192714

Error reading from Data base


Hi there user:

You need to check the Moodle data folder/temp/backup/for.log, and also files and Apache error logs.  

Files with zero (0) byte means were successfully restores or backed-up, and dot log files with 0 byte above are the ones are your concerns.

Find a hash-named (folder or file with #) folder that contain it. Then you may ‘safe to remove’ these manually.

Thanks for posting here at

Best regards,

Login/Register to Answer

Related Questions