archivematica-storage-service icon indicating copy to clipboard operation
archivematica-storage-service copied to clipboard

AIP Storage Location - the full path is not taken?

Open remileduc opened this issue 7 years ago • 0 comments

I have a really weird behavior here... the storage is on a local pipeline setup like this:

  • space (local pipeline)
    • path: /
    • staging path: /
  • location (AIP storage)
    • relative path: path/to/storage/

The ingest fails to archive the AIP with this error:

locations.models.space:space:create_local_directory:482: Could not create storage directory: [Errno 13] Permission denied: '/c5fc'

From what I saw, the location path is not taken in account and it tries to put the AIP directly in the staging path of the space. https://github.com/remileduc/archivematica-storage-service/blob/stable/0.10.x/storage_service/locations/models/space.py#L276 with destination_path coming from https://github.com/remileduc/archivematica-storage-service/blob/stable/0.10.x/storage_service/locations/models/package.py#L412 (from what I can understand, none of them contain the location path)


So, I created a new space just for the AIP storage:

  • space (local pipeline)
    • path: /
    • staging path: /path/to/storage-SPACE/
  • location (AIP storage)
    • relative path: path/to/storage-LOCATION/

and it works, with this really weird log message:

locations.models.space:space:move_rsync:421: Moving from /path/to/storage-LOCATION/.../aip.7z to /path/to/storage-SPACE/.../aip.7z

This trick kind of works but in a really strange way... I don't understand the last move in the logs. There is something that doesn't make sense oO

Note: the lines given in the logs may be a bit different from the ones in master as I've added some lines to log more stuff. Aslo, the logs are all from /var/log/archivematica/storage-service/storage_service.log

remileduc avatar Aug 11 '17 09:08 remileduc