#Cannot create syncback touch directory install
#Cannot create syncback touch directory upgrade
#Cannot create syncback touch directory code
#Cannot create syncback touch directory trial

Note the 400:Bad Request when looking up info on the new files being created. Touch: failed to close ‘test123.txt’: No such file or directory

I can also see that the file size is exactly the same when publishing from my company computer and from my home pc.I get this when trying to create a new file using touch test123.txt.

So now it's safe to say that when publishing from Articulate with our standard issue computers and build (software), the publishing is not working.

#Cannot create syncback touch directory trial

I then downloaded I Articulate trial version on my home pc and published again - I was also able to successfully upload this file.

Then asked someone outside of our company with Articulate 2 to also publish the file (same source file) This file I was able to successfully upload.

So now I started thinking it's the source file.

Went on like this with another 3 authors - same results.

I then asked another author to re-publish - same results.

I've asked the author to re-publish the file as in previous case this worked.

I am also able to load a much larger scorm file to our site without issues.

So now I now it's something with the scorm file. Find information on deployment error codes, exit codes, and error messages that appear in Photoshop Elements and Premiere Elements installation log files. I then used the same activity to upload a scorm file I know works this was successful. Also created a new course to see if it's not perhaps something wrong with my course.

We are using Moolde 2.6.2 - I've tried uploading the scorm to other activities to try and figure out if the problem is on Moodle.

I have done the following trouble shooting: When I click save I get the error message. I am trying to upload a scorm 1.2 file of 24mb. I am also getting this error message 'Can not create local file pool file, please verify permissions in dataroot and available disk space'.

#Cannot create syncback touch directory install

Regards the second point, you do not need to actually install Moodle, just look at the first step of the installation where it asks you to confirm the directory paths.

what results you see when running clean installs of 2.4 and 2.5.

To test this further it would be good to know:

#Cannot create syncback touch directory code

It seems to me that somewhere else in the code Moodle 2.5 may be picking the alternative path again, possibly retrieving it from code (as it does during the installation process) as opposed to using the correct $CFG->dataroot the config dataroot setting.Īt least that is my best guess at this time. This may be coincidental, but I doubt it. It does not matter whether you create the file manually or copy it over from 2.4 - 2.5, the point is it is pre-created and does NOT use Moodle 2.5 to build it.

#Cannot create syncback touch directory upgrade

If you upgrade from 2.4 > 2.5 it should work as that config file was already correctly created by the 2.4 install and copied back over, but you will (are) hitting the same file upload issue after upgrade.

You can get 2.5 to install by manually creating config.php, at which point you will see the file upload error.

When you run a clean install Moodle 2.5 it uses a the alternative subdomain.domain path which does not work.

When you run a clean install of Moodle 2.4 it picks up the correct paths.

So, back to the three cases I gave earlier: You can therefore resolve the moodle directory on TWO possible paths: Notice the /y/ and /m/ letters in the paths generated by the first letter of the domain AND the subsequent creation of the sub domain.

Moodle -> /var/sites/m//public_htmlīut the main directory for the site would be You will see sub domains are added with a pointer: If you enable SSH / Shell access on your host and run (from the relevant point): The difference between the two clean installs is that Moodle 2.4 and 2.5 auto detect different paths for the dataroot. Upgrade 2.4 > 2.5 'should' work (I have not tested this) on the same basis, that the config.php has already been created and copied over from your 2.4 installation

I can install Moodle 2.5 by manually creating config.php but then hit the same file upload error you report.

Clean 2.5 install fails as it cannot read / write data directory.

What I notced relates to installing moodle on a sub domain I was setting this up for a friend so they can play with Moodle, in the end I just rolled back to 2.4 and doubt I will spend too much time on it. Ok I think I have some information which may be of use to you.