DocMoto server doesn't start after a Yosemite upgrade

Occasionally the DocMoto server will fail to start after a Mavericks to Yosemite upgrade.

This can be caused by the upgrade changing the ownership of various files that the DocMoto server needs to own before it can start.

To see if this problem is affecting your DocMoto server the first place to look is the Console.

You can find the Console in the Utilities folder in the Application section of Finder.

Open Console and you will see a list of system messages. You might find it helpful to filter them. Do this by typing docmoto in the search field, top right hand corner. You are looking for an entry similar to the one below

21/10/2014 11:09:22.414[1]: (chs.docmoto.serverd[13000]) Service could not initialize: 14A389: xpcproxy + 14045 [1344][1016C726-9ACF-3A24-9C51-A279F5C6B167]: 0xd

The fix

If you find such an entry (there should be a new one appearing every few seconds as the DocMoto server repeatedly tries to start) then follow the procedure below.

If you don't find such an entry then take a look at this article for possible causes and remedies.

  1. Open terminal (in the Utilities folder under Applications in Finder)

  2. Log in as the superuser by typing the following:

    sudo -s

    The password you must enter will be same one you use when making changes on your Mac.

  3. Move to the folder /var/log by typing the following:

    cd /var/log
  4. Change the ownership of the folder docmoto to the user docmoto by typing the following:

    chown -R docmoto docmoto
  5. Now go to System Preferences, click on the DocMoto Server item, click "Refresh" and you should find the DocMoto server now running.

Still have a question?

If you still can't find the answer to your question or need more information, please contact the DocMoto team on +44 (0)1242 225230 or email us

We value your privacy

We use Cookies to make using our website easy and meaningful for you, and to better understand how it is used by our customers. By using our website, you are agreeing to our privacy policy.

I agree