You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Verify AIP job verifies the contents of the AIP bag and does not show failed MySQL queries in the user interface.
Current behaviour
The Verify AIP job is supposed to:
extract (for compressed AIPs) and validate the AIP bag
iterate its contained files and verify their checksums match the checksums recorded at the beginning of the transfer
on success write an AIP-level fixity check PREMIS event to the database that is sent to the Storage Service to be added to the pointer file
on error write an AIP-level fixity check PREMIS event to the database, raise and log an error that stops processing of the transfer
On this last point (4.) you could argue about how useful the PREMIS event might be because the METS file has already been created so the event is not recorded there and the AIP is not going to be sent to the Storage Service.
Furthermore, each PREMIS event needs to be associated with an existing File in the Dashboard database. The Verify AIP job tries to associate its event with a File created for the AIP in the Compress AIP job.
But for uncompressed AIPs the Compress AIP job does not create such corresponding File which prevents the Verify AIP from recording any event. So if all verifications are successful, the job fails to write the Pass event and the error is handled gracefully (the job does not fail) but logged to the user interface with a MySQL error:
If something is wrong with the contents of the bag the user interface also shows a MySQL error and doesn't provide any details of what really went wrong:
Compare that VerifyChecksumsError(None) error with an error produced in a compressed AIP which provides context about the problem:
Steps to reproduce
Set the Select compression algorithm option of your processing configuration to Uncompressed.
Start a Standard transfer using the SampleTransfers/Images/pictures folder
The AIP should be stored in the Storage Service, but check the output of the Verify AIP job and you should see a MySQL error like the first screenshot above
For getting bag content errors (the last two screenshots) I artificially inserted a 2 minutes pause at the beginning of the Verify AIP job and when it hit I modified all the checksum values in the Files table to be 123.
Your environment (version of Archivematica, operating system, other relevant details)
Expected behaviour
The
Verify AIP
job verifies the contents of the AIP bag and does not show failed MySQL queries in the user interface.Current behaviour
The
Verify AIP
job is supposed to:fixity check
PREMIS event to the database that is sent to the Storage Service to be added to the pointer filefixity check
PREMIS event to the database, raise and log an error that stops processing of the transferOn this last point (4.) you could argue about how useful the PREMIS event might be because the METS file has already been created so the event is not recorded there and the AIP is not going to be sent to the Storage Service.
Furthermore, each PREMIS event needs to be associated with an existing
File
in the Dashboard database. TheVerify AIP
job tries to associate its event with aFile
created for the AIP in theCompress AIP
job.But for uncompressed AIPs the
Compress AIP
job does not create such correspondingFile
which prevents theVerify AIP
from recording any event. So if all verifications are successful, the job fails to write thePass
event and the error is handled gracefully (the job does not fail) but logged to the user interface with a MySQL error:If something is wrong with the contents of the bag the user interface also shows a MySQL error and doesn't provide any details of what really went wrong:
Compare that
VerifyChecksumsError(None)
error with an error produced in a compressed AIP which provides context about the problem:Steps to reproduce
Select compression algorithm
option of your processing configuration toUncompressed
.Standard
transfer using theSampleTransfers/Images/pictures
folderVerify AIP
job and you should see a MySQL error like the first screenshot aboveFor getting bag content errors (the last two screenshots) I artificially inserted a 2 minutes pause at the beginning of the
Verify AIP
job and when it hit I modified all the checksum values in theFiles
table to be123
.Your environment (version of Archivematica, operating system, other relevant details)
artefactual/archivematica@61e5ca1
For Artefactual use:
Before you close this issue, you must check off the following:
The text was updated successfully, but these errors were encountered: