Problems with DIP upload from Archivematica to Atom

[Dale Patterson]

Good morning everyone -
I have three questions. 

First - I have Archivematica 1.3.2 running on Ubuntu 12.04 and AtoM  - version 2.2.0-123 - on a separate ubuntu box  running 14.04

I have set up the DIP upload to AtoM process following the instructions on the Archivematica site.   My problem is that the upload fails because AtoM wants a password from Archivematica.  But according to the instructions, which I'm pretty sure I followed religiously, it shouldn't need.  While I can get rsync to work from the CLI for my account, if I attempt to log in using archivematica it also fails.  I've recreated the account on the AtoM box once already.  Any suggestions? 

Thanks.

Second - once I've had a reported failure while processing in Archivematica, how do I make a correction and then pick up the process?  Or is my only remedy to make any corrections and then start the entire transfer/ingest process over again? 

Third - Since I'm just an office of one, is it possible to get some training / instructions on Archivematica.  I could probably even arrange to come out to BC (who wouldn't want to go there!)  if that what it takes.  I've got the basics down, more or less, just want to become more familiar with the various options that the system offers me.  Feeling a little adrift. 

Thanks.

Dale Patterson

[Sarah Romkey]

Hello Dale,

AtoM does need a password for an Archivematica user in order to be able to receive DIPs. You configure this in your Administration tab of the Archivematica dashboard (documentation here: https://www.archivematica.org/en/docs/archivematica-1.3/admin-manual/installation/dashboard-config/#admin-dashboard-atom). Did you complete that step? What error are you receiving when you attempt to upload a DIP?

Your second question depends on exactly which failure you're talking about. If you're talking about the DIP upload failure, there isn't a way from the user interface to pick it back up. But, if you copy your DIP directory out of the failed directory and back into the uploadDIP directory, it will re-appear in the dashboard.

Your third question is totally understandable :) Have you checked out your screencast recordings on our Youtube channel? https://www.youtube.com/user/ArtefactualSystems

Pop me a line of-list if you'd like and we can discuss options for help.

Cheers,

Sarah

Sarah Romkey, MAS,MLIS

Archivematica Program Manager
Artefactual Systems
604-527-2056

@archivematica / @accesstomemory

--
You received this message because you are subscribed to the Google Groups "archivematica" group.
To unsubscribe from this group and stop receiving emails from it, send an email to archivematic...@googlegroups.com.
To post to this group, send email to archiv...@googlegroups.com.
Visit this group at https://groups.google.com/group/archivematica.
For more options, visit https://groups.google.com/d/optout.

[Dale Patterson]

Sarah -
Thanks for the reply. It has taken me a bit to get to this challenge.  I appreciate your input.    Here is where I got confused by the instructions. Right at  the beginning of the Atom Server Configuration it says:
"This server configuration step is necessary to allow Archivematica to log in to the AtoM server without passwords, "

So when I did the command :

sudo passwd -l archivematica

I did not enter a password.  Perhaps I should???

On the parameters I did the following: 
url : the url where AtoM is setting
email: the email id I use to log into AtoM - 
password: the password that I use with the above email to log into AtoM
uuid  "%SIPUUID%"  that text unchanaged
rysnc-target  the url where AtoM sits along with the /tmp directory
debug left as is

When I wrote my  original note I had found a error statement which said I needed a password.  This morning 
I can't find that log - probably need more coffee.  I did find error logs associated with the failure however. 

The error statement associated with the failed microservice upload of DIP  that appears in the dashboard stated: 
ERROR:__main__:[uploadDIP] Target: accessin-2013-007
ERROR:__main__:[uploadDIP] rsync --protect-args -rltz -P --chmod=ugo=rwX /var/archivematica/sharedDirectory/watchedDirectories/uploadDIP/Ruach2013-afa5eaa0-84db-4f9c-9620-bba47b218454 archivematica@[our url]:/tmp
ERROR:__main__:[uploadDIP] Rsync output is being saved in /tmp/tmpKOpHzs
WARNING:py.warnings:/usr/local/lib/python2.7/dist-packages/django/db/models/fields/__init__.py:827: RuntimeWarning: DateTimeField received a naive datetime (2016-01-15 13:55:48) while time zone support is active.
  RuntimeWarning)

[uploadDIP] Rsync quit unexpectedly (exit 255), the upload script will be stopped here

+++
I went to the /tmp directory file as listed above and found the following: 
 /tmp/tmpKOpHzs file

Host key verification failed.
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: unexplained error (code 255) at io.c(605) [sender=3.0.9]

It appears I don't have my host key set correctly.  
I generated the ssh-keygen as described and left it under the 
/var/lib/archivematica/.ssh/id_rsa.pub on the archivematica server

and also placed a copy  at
/home/archivematica/.ssh/authorized_keys 
as described.  Should I make new keys?  

Thanks for any observations. I appreciate it. 

Dale

[Sarah Romkey]

Hello Dale,

Apologies for not responding sooner. Did you try any further troubleshooting in the meantime?

I just noticed that in your parameters in the Admin tab for AtoM DIP upload it looks like you are missing the version number. The last line should read

--version=2

to indicate that you are uploading to an AtoM 2.x site.

Cheers,

Sarah

Sarah Romkey, MAS,MLIS

Archivematica Program Manager
Artefactual Systems
604-527-2056

@archivematica / @accesstomemory

[Kari R Smith]

Thanks Sarah.  I did try it again and this time, although the Archivematica site just whirled away with no stopping for the upload to atom, the files were uploaded to the correct description stub in atom.  So that’s good.  I’ll do another set of tests today.

 

Another question I’ve had is this:  from the Transfer tab, is it possible to obtain the transfer manifest as a discrete document?  If I don’t put the SIP into Transfer backlog is it possible to get this?

 

Kari