"Archive not readable"

[Andre Landman]

After successful transfer and ingest, when I try to access the AIP, I get a 7zip message that "Archive not readable" and asks for a password or key. What causes this and how do I rectify it? Using 1.4.1.

Thanks

[Sara - Artefactual]

Hi Andre,

We've never run into this issue before! A bit more information might help us figure out what's going on.

- Does your Archivematica installation diverge at all from our installation instructions? Any local customizations that might be causing this?

- What is in your transfer? What kind of transfer is it (standard, zipped, etc)? Does this happen with every transfer?

One thing you can do - apologies, it'll be tedious - is to check the outputs of all of the microservices by clicking on the gear icon next to the job name to see if there are any STDERRs that Archivematica is failing to report in the transfer or ingest page. If there's an error causing your odd password problem, it would be good to know about!

I'd be interested to see if I can reproduce the problem - if you'd like, you can share your transfer content with me by contacting me off list at sallain [at] artefactual.com.

Regards,

Sara Allain

Systems Archivist

Artefactual Systems, Inc

[Andre Landman]

Hi Sara,

I am waiting to hear from our IT support staff if they tweaked anything post-installation.

It was a standard transfer. The item comprised 4 film clips which together totalled about 1 GB. Maybe it is a file size issue? Smaller transfers woork perfectly.

Regards

Andre

Andre Landman about.me/allandman

--
You received this message because you are subscribed to a topic in the Google Groups "archivematica" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/archivematica/e-3dynULYXI/unsubscribe.
To unsubscribe from this group and all its topics, 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.

[Sarah Romkey]

Hi Andre,

Could it also be a file permissions problem with the source files? Are you able to open those before processing in Archivematica?

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.

[Kayleigh Roos]

Hi André and Sarah

If I'm understanding this issue correctly, it's an issue I picked up with our LIT department a couple months back and is a similar issue discussed on this forum here.

There seems to be an issue with downloading AIPs larger than 1GB from the Archivematica administrator interface (our IT staff can download any size AIPs from the 'back-end'). A few users have solved this by using Owncloud as a local cloud server that mirrors the archival storage server and curators can then download AIPs from Owncloud. It is still an internal issue with the Archivematica software that should be attended to. I'm keen to see if the next version supports the download of AIPs larger than 1GB.

Kayleigh
Digital Curator, UCT Libraries

[Sarah Romkey]

Hi Kayleigh,

In that linked thread they are discussing uncompressed AIPs using version 1.3.1. Are you creating uncompressed AIPs as well? I'm actually not sure that the errors are quite the same either- in that thread, it sound like the download would stop after about 1 GB, in your case it sounds like you can download the whole AIP but then can't open it due to permissions error. The permissions error is a new one to us, we haven't been able to replicate it here. Archivematica is definitely intended to support AIP sizes larger than 1 GB.

If you do try the newest release, let us know if you experience the same issue. There were some backend scalability improvements in this release so maybe that will make a difference in your particular configuration.

Cheers,

Sarah

Sarah Romkey, MAS,MLIS

Archivematica Program Manager
Artefactual Systems
604-527-2056

@archivematica / @accesstomemory

[Justin Simpson]

That thread you posted Kayleigh is probably the correct issue here.  In that link, the problem is coming from uwsgi, a component used in the Archivematica Storage Service. 

Jesús Garcia Crespo (an Artefactual developer) first tried running the storage service with gunicorn and found that this particular problem went away. 

It appears to be an issue that came with a newer version of uwsgi, the problem did not exist 6 months ago, to my knowledge at least.  uwsgi has a pretty fast development cycle, we have not tracked down the exact version where this problem crept in.  Switching to gunicorn solved the problem, and so at Artefactual we have focused on that as a solution.

The 1.5.0 release of Archivematica , when installed using the .deb packages, still uses apache + mod_wsgi for the dashboard, and nginx + uwsgi for the storage service.

We'd like to transition both apps to use nginx+gunicorn by default for the 1.6.0 release.

Hector Akamine, one of the sys admins at Artefactual, added support for gunicorn to the ansible role we use at Artefactual to deploy Archivematica.  If you are using the deploy-pub repo (https://github.com/artefactual/deploy-pub.git ) and you add a couple of variables to your vars_singlenode.yml , like so:

       archivematica_src_ss_gunicorn: "true"
       archivematica_src_am_dashboard_gunicorn: "true"

when doing a fresh install of Archivematica, you will end up with the Storage Service and the dashboard both deployed using nginx + gunicorn.  This has resolved the downloading large aip problem for all the cases we have seen so far.

I'd be interested to hear from anyone that is trying this combination. If you have a current production Archivematica server, and you want to switch, you would have to do a bit of configuration work, but if you follow the examples in the pull requests where support for gunicorn was worked out in the ansible role

https://github.com/artefactual-labs/ansible-role-archivematica-src/pull/54

and
https://github.com/artefactual-labs/ansible-role-archivematica-src/pull/56

it should be possible to switch any Archivematica system over to gunicorn.

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

On Wed, Jun 8, 2016 at 1:23 AM, Kayleigh Roos <kaylei...@gmail.com> wrote:

[Sarah Romkey]

Thanks for the explanation Justin, and Kayleigh sorry I misunderstood the situation in my earlier post!

Cheers,

Sarah

Sarah Romkey, MAS,MLIS

Archivematica Program Manager
Artefactual Systems
604-527-2056

@archivematica / @accesstomemory

[Kayleigh Roos]

Hi Sarah and Justin

So sorry, I've only picked up on your replies now. Justin, thanks for the very descriptive response - I've forwarded it onto my IT colleagues whom I think will understand the technical bits a lot better than myself, and hopefully they can try out your suggestions to see if it helps with this issue.

Sarah, yes we have chosen to go with uncompressed AIPs and I'm hoping we'll have capacity to upgrade to 1.5 soon! Will send feedback thereafter.

Best,

Kayleigh

[vincent....@fr.ch]

Hi,

On my installation I modify the nginx storage configuration and add the following paramter to increase the limit of download:

uwsgi_max_temp_file_size 50000m;

after restarting nginx and uwsgi, it works and I can download AIP larger than 1 GB.

Best regards

Vincent