I'm having difficulties uploading large (200MB-1.9GB) SCORM files to my Moodle (2.4.1-weekly on a 6GB Linux VPS).
It appears to be successfully uploading the SCORM file, through the file picker. This was the first hurdle I overcame - by tweaking the PHP settings, e.g. upload_max_filesize, etc. The problem occurs when I get to the final "Save and Return" button. It spends 1-2 mins loading/processing/thinking about it, but finally ends up returning an "Error: zero-sized reply" message.
This issue affects all the large (200MB+) SCORMs I have, including from different producers. SCORMs smaller than 150MB have been successfully installed, including on the most recent Moodle 2.4.1+.
I've been trying to debug this for so long I cannot see the wood for the trees anymore. It's an issue that gets raised again and again on the Moodle forum, but never properly answered. Does anyone have an insight into this problem, or have any helpful suggestions.
I've been having the same issue on 2.3 - the upload works fine then it takes ages to unpack it.
My theory is its because they changed from the unzip utility in the O/S to a php one that doesn't seem as efficient.
The 'workaround' (assuming you php.ini is correct) is just to leave it unpacking and letting it error - it does eventually unpack larger SCORM files.
You might need to increase the time you allow scripts to run as well.
post_max_size is 2048M
upload_max_filesize is 2048M
max_execution_time is 60
I'm not sure the max_execution_time is applicable though, because it definitely spends longer than 60-secs before it times out. As I'm already clutching at straws, I will try doubling the execution time.
I kept increasing max_execution_time, until it worked. I'm on about 15min now!
You might also hit problems with files approaching 2GB due to PHP's x86 limitations.
We suffer many headaches with courses exceeding 2GB!
I followed CyberNerd's advice and kept increasing the max_execution_time until it worked. 15mins was correct.
CyberNerd (22nd January 2013)
Thanks - that looks like a much better fix.
There are currently 1 users browsing this thread. (0 members and 1 guests)