We currently have Archivematica (1.4) and Atom (2.2) on the same machine (different ports). We have configured AtoM DIP upload in Archivematica as below. We know that Atom Worker is running.
--url="http://###.###.###.##:8080/index.php" \
--email="
em...@gmail.com" \
--password="pwd" \
--uuid="%SIPUUID%" \
--rsync-target="/tmp"
We created a slug (an Archival Description) in the Atom (ex: test123). We then give the slug in the upload dialog as described here:
https://www.archivematica.org/en/docs/archivematica-1.4/user-manual/access/access/It tries to process it, then fails. We see that the tmp file has been created. However, we are not sure why it fails to upload the DIP.
ERROR archivematica.upload.qubit.log: [uploadDIP] Target: test123
ERROR archivematica.upload.qubit.log: [uploadDIP] rsync --protect-args -rltz -P --chmod=ugo=rwX /var/archivematica/sharedDirectory/watchedDirectories/uploadDIP/book9-faac6543-1ec8-414a-a054-ba0ef9fbc5ee /tmp
ERROR archivematica.upload.qubit.log: [uploadDIP] Rsync output is being saved in /tmp/tmpyM8HGm
ERROR archivematica.upload.qubit.log: [uploadDIP] About to deposit to: http://###.###.###.##:8080/index.php/;sword/deposit/test123
ERROR archivematica.upload.qubit.log: [uploadDIP] > Response code: 404
ERROR archivematica.upload.qubit.log: [uploadDIP] > Location: None
[uploadDIP] Response code not expected
It is a 404 error, thus the error may be in the Atom configuration!. But, we are not sure what that could be.