AM 1.11.2 Error re-ingesting package: Error in approve reingest API... No schema supplied...

100 views
Skip to first unread message

Arthur Trip

unread,
Jul 12, 2020, 12:17:45 PM7/12/20
to archivematica
Hi all,
in a brand new AM 1.11.2, scaled with separated hosts for Storage Service and MCPServer, if I try to reingest an AIP, anyway I try partial, full or metadata only, I always receive:

Error re-ingesting package: Error in approve reingest API. Invalid URL 'api/ingest/reingest': No schema supplied. Perhaps you meant http://api/ingest/reingest?


I don't see errors in the MCPServer/Dashboard/MCPClient, while in the Storage Service log there's...
INFO 2020-07-12 08:33:50 locations.models.package:package:extract_file:1568: Extracting file with: ['7z', 'x', '-bd', '-y', '-o/var/archivematica/storage_service/tmpVaE8G_', u'/AIPStore/2700/1796/32bb/4dc6/ad4e/45e6/f21c/3274/{OMISSIS}-27001796-32bb-4dc6-ad4e-45e6f21c3274.7z'] to /var/archivematica/storage_service/tmpVaE8G_/{OMISSIS}-27001796-32bb-4dc6-ad4e-45e6f21c3274
INFO
2020-07-12 08:33:50 locations.models.package:package:start_reingest:2158: Reingest: files: [u'tmpVaE8G_/{OMISSIS}-27001796-32bb-4dc6-ad4e-45e6f21c3274']
INFO
2020-07-12 08:33:50 locations.models.space:space:move_rsync:550: Moving from /var/archivematica/storage_service/tmpVaE8G_/{OMISSIS}-27001796-32bb-4dc6-ad4e-45e6f21c3274 to /var/archivematica/storage_service/tmpVaE8G_/{OMISSIS}-27001796-32bb-4dc6-ad4e-45e6f21c3274
INFO
2020-07-12 08:33:50 locations.models.space:space:move_rsync:550: Moving from /var/archivematica/storage_service/tmpVaE8G_/{OMISSIS}-27001796-32bb-4dc6-ad4e-45e6f21c3274/ to /var/archivematica/sharedDirectory-1/tmp/tmpVaE8G_/{OMISSIS}-27001796-32bb-4dc6-ad4e-45e6f21c3274
INFO
2020-07-12 08:33:50 locations.models.space:space:move_rsync:592: rsync command: ['rsync', '-t', '-O', '--protect-args', '-vv', '--chmod=Fug+rw,o-rwx,Dug+rwx,o-rwx', '-r', '/var/archivematica/storage_service/tmpVaE8G_/{OMISSIS}-27001796-32bb-4dc6-ad4e-45e6f21c3274/', '/var/archivematica/sharedDirectory-1/tmp/tmpVaE8G_/{OMISSIS}-27001796-32bb-4dc6-ad4e-45e6f21c3274']
ERROR
2020-07-12 08:33:50 locations.models.pipeline:pipeline:_request_api:208: Unable to connect to pipeline Archivematica on {OMISSIS}mcpsrv-1 (e504cd0f-f480-4aa4-9e5f-4346287f2f6e).
Traceback (most recent call last):
 
File "/usr/lib/archivematica/storage-service/locations/models/pipeline.py", line 205, in _request_api
 verify
=verify,
 
File "/usr/share/archivematica/virtualenvs/archivematica-storage-service/lib/python2.7/site-packages/requests/api.py", line 60, in request
 
return session.request(method=method, url=url, **kwargs)
 
File "/usr/share/archivematica/virtualenvs/archivematica-storage-service/lib/python2.7/site-packages/requests/sessions.py", line 519, in request
 prep
= self.prepare_request(req)
 
File "/usr/share/archivematica/virtualenvs/archivematica-storage-service/lib/python2.7/site-packages/requests/sessions.py", line 462, in prepare_request
 hooks
=merge_hooks(request.hooks, self.hooks),
 
File "/usr/share/archivematica/virtualenvs/archivematica-storage-service/lib/python2.7/site-packages/requests/models.py", line 313, in prepare
 
self.prepare_url(url, params)
 
File "/usr/share/archivematica/virtualenvs/archivematica-storage-service/lib/python2.7/site-packages/requests/models.py", line 387, in prepare_url
 
raise MissingSchema(error)
MissingSchema: Invalid URL 'api/transfer/reingest': No schema supplied. Perhaps you meant http://api/transfer/reingest?
ERROR
2020-07-12 08:33:50 locations.models.package:package:start_reingest:2205: Error approving reingest in pipeline for package 27001796-32bb-4dc6-ad4e-45e6f21c3274
Traceback (most recent call last):
 
File "/usr/lib/archivematica/storage-service/locations/models/package.py", line 2201, in start_reingest
 resp
= pipeline.reingest(relative_path, self.uuid, reingest_target)
 
File "/usr/lib/archivematica/storage-service/locations/models/pipeline.py", line 242, in reingest
 resp
= self._request_api("POST", url, fields=fields)
 
File "/usr/lib/archivematica/storage-service/locations/models/pipeline.py", line 205, in _request_api
 verify
=verify,
 
File "/usr/share/archivematica/virtualenvs/archivematica-storage-service/lib/python2.7/site-packages/requests/api.py", line 60, in request
 
return session.request(method=method, url=url, **kwargs)
 
File "/usr/share/archivematica/virtualenvs/archivematica-storage-service/lib/python2.7/site-packages/requests/sessions.py", line 519, in request
 prep
= self.prepare_request(req)
 
File "/usr/share/archivematica/virtualenvs/archivematica-storage-service/lib/python2.7/site-packages/requests/sessions.py", line 462, in prepare_request
 hooks
=merge_hooks(request.hooks, self.hooks),
 
File "/usr/share/archivematica/virtualenvs/archivematica-storage-service/lib/python2.7/site-packages/requests/models.py", line 313, in prepare
 
self.prepare_url(url, params)
 
File "/usr/share/archivematica/virtualenvs/archivematica-storage-service/lib/python2.7/site-packages/requests/models.py", line 387, in prepare_url
 
raise MissingSchema(error)
MissingSchema: Invalid URL 'api/transfer/reingest': No schema supplied. Perhaps you meant http://api/transfer/reingest?

The Transfers, Ingests and DIPUploads work well so, I can't figure out what may be wrong in some configuration.

Please, any idea?

Thanks

Arthy

vinrich...@gmail.com

unread,
Aug 29, 2020, 10:37:20 AM8/29/20
to archivematica
Hi all,

I also experienced trouble with re-ingests in (several) Archivematica v1.11.2 instances. I was not able to succeed performing a metadata-reingest (the system then simply says: "Error re-ingesting package: An unknown error occurred.") and when trying to run a partial re-ingest I get this error: "Error re-ingesting package: Error in approve reingest API. Max retries exceeded with url: /api/ingest/reingest (Caused by NewConnectionError(': Failed to establish a new connection: [Errno -2] Name or service not known',))".

Any help would be appreciated.

Regards,

Vin

Op zondag 12 juli 2020 om 18:17:45 UTC+2 schreef arth...@gmail.com:

Tessa Walsh

unread,
Aug 31, 2020, 11:49:13 AM8/31/20
to archivematica
Hi Arthy,

From the logs you provided, I think the issue is that the remote name for the pipeline is missing in the Storage Service, so the base URL is missing from the reindex request. In the Storage Service, you can go to the "Pipelines" tab, and then click "Edit" next to the pipeline. You'll want to add the URL for the associated Archivematica dashboard/pipeline in the Remote name field, as in this example from the Docker Compose dev environment:

Screenshot_2020-08-31 Archivematica Storage Service.png

I think editing that field and then restarting the Storage Service should resolve both of your issues. Would you want to try and report back?

You'll want to make sure that the Storage Service URL is also properly configured in the Administration->General page of the pipeline that you are trying to start a reingest from (I suspect that's already properly configured if you're able to create and storage AIPs).

All the best,

Tessa

Arthur Trip

unread,
Sep 1, 2020, 4:20:31 AM9/1/20
to archivematica
Hi Tessa,
thanks so much for your suggestion.
The "Remote name" in the Pipeline configuration was really blank.
After filling in the field and restarting the archivematica-storage-service I was able to perform correctly a full reingest.

Thanks again!

Arthy

Tessa Walsh

unread,
Sep 1, 2020, 10:32:33 AM9/1/20
to archivematica
I'm glad to hear that worked for you!

Cheers,
Tessa
Reply all
Reply to author
Forward
0 new messages