Another DIP Upload Error Code

[Liam Tomkins]

Greetings all, I have run into a new error while uploading from archivematica to atom and would appreciate if anyone has any suggestions.

I have set up archivematica 1.4.0 and atom 2.1.2 on seperate virtual machines, but receive the following when uploading DIPs.

ERROR     archivematica.upload.qubit.log:  [uploadDIP] Target: llgc
ERROR     archivematica.upload.qubit.log:  [uploadDIP] rsync --protect-args -rltz -P --chmod=ugo=rwX /var/archivematica/sharedDirectory/watchedDirectories/uploadDIP/test2-fafb02bb-9c80-429f-afae-e44d1fdf5709 archiv...@152.25.4.185:/tmp
ERROR     archivematica.upload.qubit.log:  [uploadDIP] Rsync output is being saved in /tmp/tmp6insPb
ERROR     archivematica.upload.qubit.log:  [uploadDIP] Sending... 0 (ETA: 0:00:03)
ERROR     archivematica.upload.qubit.log:  [uploadDIP] Sending... 100 (ETA: 0:00:00)
ERROR     archivematica.upload.qubit.log:  [uploadDIP] About to deposit to: http://152.25.4.185/index.php/sword/deposit/llgc
ERROR     archivematica.upload.qubit.log:  [uploadDIP] > Response code: 504
ERROR     archivematica.upload.qubit.log:  [uploadDIP] > Location: None

I've created the archival description within atom, added --version=2 \ to the AM DIP Upload Config page and just increased the nginx timout from 30-60 seconds to no avail.

I can't find any mention of 504 on this forum which seems surprising; as far as I can tell I'm not doing anything too out of the ordinary.

Many thanks in advance,

Liam

[Sarah Romkey]

Hello Liam,

In addition to the necessary configurations on the Archivematica side, can you ensure that in your AtoM installation, the SWORD plugin is enabled, and the Job Scheduling is enabled? Relevant AtoM documentation:

https://www.accesstomemory.org/en/docs/2.1/user-manual/administer/settings/#job-scheduling and

https://www.accesstomemory.org/en/docs/2.1/user-manual/administer/manage-plugins/#manage-plugins

Cheers,

Sarah

Sarah Romkey, MAS,MLIS

Systems Archivist
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 http://groups.google.com/group/archivematica.
For more options, visit https://groups.google.com/d/optout.

[Liam Tomkins]

Hi there Sarah, I can confirm the qtSword plugin and job scheduling are enabled.

Thanks,

Liam

[Hutchinson, Tim]

Hi Liam,

 

Have you configured ssh keys? My understanding that this is required when archivematica and atom are on separate servers. See:

https://www.archivematica.org/en/docs/archivematica-1.4/admin-manual/installation/dashboard-config/#admin-dashboard-atom

 

Tim Hutchinson
Head, University Archives & Special Collections
University Library, University of Saskatchewan

Tel: (306) 966-6028  Fax: (306) 966-6040

Email: tim.hut...@usask.ca

Web: http://library.usask.ca/archives/

[Sarah Romkey]

Yes, Tim is correct- this is another step that needs to be taken if it hasn't already.

Sarah Romkey, MAS,MLIS

Systems Archivist
Artefactual Systems
604-527-2056

@archivematica / @accesstomemory

[Justin Simpson]

From the output Liam posted, I think that he has an ssh key set up and copied to the atom authorized_keys file.  The error is happening after rsync has completedly successfully. The error is coming from AtoM, when Archivematica attempts to POST a message to the sword/deposit endpoint in AtoM. 

The steps that happen in DIP Upload are:

1) archivematica makes a dip

2) archivematica copies that dip from its processing location, to the atom server, using rysnc, by default to the /tmp directory on the atom server.

3) archivematica POSTS a message to AtoM, to tell it that there is a DIP waiting in /tmp.

4) AtoM creates a task that is sent to its gearman server.

5) Gearman looks for a gearman worker process, that is capable of handling this job.

6) Atom has a gearman client, called atom-worker by default, that goes and finds the dip in /tmp and does the work of updating the atom database and copying digital objects to the atom uploads directory, and indexing the new objects in the AtoM elasticsearch index.

I suspect that Liam is missing the atom-worker.  I don't think the dip upload docs are terribly clear about this right now, it is easy to miss.

Liam, take a look at https://www.accesstomemory.org/en/docs/2.1/admin-manual/installation/asynchronous-jobs/#installation-asynchronous-jobs

Make sure you have gearman installed on your atom server and you have a script at /etc/init/atom-worker.conf and that you have started the atom-worker daemon. 

Justin Simpson
Director of Archivematica Technical Services
www.artefactual.com
604-527-2056

[Liam Tomkins]

Hi Justin, that's cracked it! I'm not sure how I missed it but I did. 

Many thanks to all for the suggestions,

Liam

[J Strawn]

Greetings.  I have a related problem which has completely stumped me.  When I login the the Archivematica web dashboard under Administration there is no Administration > AtoM DIP upload page.  That option is simply not there,...

[J Strawn]

I have followed the installation instructions for Archivematica 1.4 and have AtoM 2.1 running, as well.  Is there a step missing in the installation instructions???

Thanks,

James

[Justin Simpson]

Hello,

In the Archivematica dashboard, under the general configuration tab, there is a check box to bide atom DIP upload options.  If you have this checked, you will not see the atom DIP upload configuration tab.  Is that the problem in your case?

--

[J Strawn]

Yes, thanks for the tip!

On Thursday, July 23, 2015 at 10:45:20 AM UTC-4, Liam Tomkins wrote: