It appears that this could be a permissions issue. First some initial questions:
Have you installed both AtoM and Archivematica (which I'll refer to as AM) following our recommended installation instructions? If yes, did you use Ubuntu 14.04 or 16.04? If no, what changes did you make?
There are several configuration steps that are also necessary for the 2 systems to work together in conjunction - I'll list them here, so you can double-check they are in place properly.
First, you must have the job scheduler properly installed and configured in AtoM. See:
Then you have to confirm that settings for your AtoM instance are added in AM's administration page, so AM has the necessary credentials to make the deposit. See:
Finally, make sure you are following all the necessary instructions for DIP upload to AtoM, as outlined in the documentation here:
There is also a reminder about firewalls, and what ports you need to ensure are open for communication (as well as a checklist summary of the above) here:
If you have double-checked all of that, and you are still having issues, then it may be a problem with the filesystem permissions. We set these in AtoM during installation here:
You can always try re-running the command listed there to ensure that AtoM's www-data user has all the necessary permissions. I'm not as sure about the AM permissions (I believe they are all assigned to the archivematica:archivematica user, but not sure), but if set properly, they shouldn't conflict: we've definitely had other users successfully install on the same server.
If that still didn't work, then there are 2 final things you can try doing to collect more information.
The first is to see if anything was captured in AtoM's webserver logs. They may not have been but it's worth taking a look. See:
Check the time stamps on any error message - or try repeating the action that caused the error with the log open, to see if it generates a message (to make sure you are not viewing old, unrelate error messages). If you do find something relevant that is generated by this, please share the error message here.
You can also see if there is more information in the atom-worker error logs. In 14.04, the location of this log file is defined in your atom.conf configuration file, place in /etc/init/ - if you copied the example straight out of our documentation, then the log file would be at /usr/share/nginx/atom/log/atom-worker.log
In Ubuntu 16.04, you can use the following command to view the log:
- sudo journalctl -f -u atom-worker
Again, if none of the above steps helped you to locate the problem, then please share any related message you find in the log.