-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
checksum validation failure for vf742yx0561 #1520
Comments
@andrewjbtw / @blalbrit the file being reported appears to be the correct size:
And reported by argo: So we'll have to figure out if the content is correct. A |
It's a bit of a mystery how this object made it to preservation with this checksum error as it seems like the bag validation should have caught it. There are six versions and versions 5 and 6 both have a tar archive. If version 6 is correct, then it seems like the best solution will be to manually edit the manifests so that the v5 checksum matches. |
Confirmed that v6 has the correct content. Editing manifests to make everything match is time consuming, so setting aside time to finish up next week. |
This morning I updated the following manifests so they're consistent with the correct v5 checksums for the tar.gz and the contentMetadata.xml: in v0005: in v0006 (the versionInventory.xml and versionAdditions.xml files do not contain v5 checksums, as far as I can tell): I then re-ran the audit. This time the checksums on the tar.gz were not a problem but I still got an error for the v5 contentMetadata.xml: [1] pry(main)> Audit::Checksum.validate_druid('vf742yx0561')
I, [2020-05-26T11:21:47.980439 #686] INFO -- : 2020-05-26T18:21:47Z CV validate_druid starting for vf742yx0561
D, [2020-05-26T11:21:48.021645 #686] DEBUG -- : Found 1 complete moabs.
E, [2020-05-26T12:06:59.968284 #686] ERROR -- : validate_checksums(vf742yx0561, services-disk16) checksums for /services-disk16/sdr2objects/vf/742/yx/0561/vf742yx0561/v0005/data/metadata/contentMetadata.xm
l version 5 do not match.
** [Honeybadger] Reporting error id=3636e43b-663e-4230-8ba0-ed062a7566d9 level=1 pid=686
I, [2020-05-26T12:07:00.263492 #686] INFO -- : [{:moab_file_checksum_mismatch=>"checksums for /services-disk16/sdr2objects/vf/742/yx/0561/vf742yx0561/v0005/data/metadata/contentMetadata.xml version 5 do n
ot match."}] for vf742yx0561
I, [2020-05-26T12:07:00.263620 #686] INFO -- : 2020-05-26T19:07:00Z CV validate_druid ended for vf742yx0561
=> [#<AuditResults:0x00000000069da408
@actual_version=6,
@check_name="validate_checksums",
@druid="vf742yx0561",
@log_msg_prefix="validate_checksums(vf742yx0561, services-disk16)",
@moab_storage_root=
#<MoabStorageRoot:0x0000000006ab3410
id: 17,
name: "services-disk16",
created_at: Tue, 16 Oct 2018 19:22:02 UTC +00:00,
updated_at: Tue, 16 Oct 2018 19:22:02 UTC +00:00,
storage_location: "/services-disk16/sdr2objects">,
@result_array=[{:moab_file_checksum_mismatch=>"checksums for /services-disk16/sdr2objects/vf/742/yx/0561/vf742yx0561/v0005/data/metadata/contentMetadata.xml version 5 do not match."}],
@string_prefix="validate_checksums (actual location: services-disk16; actual version: 6)">] |
The manifest being used is always the latest signatureCatalog.xml: It appears to have incorrect data for at least the size of v5 of the signatureCatalog.xml:
<entry originalVersion="5" groupId="metadata" storagePath="contentMetadata.xml">
<fileSignature size="479649" md5="4aa570c169ce71c878ba583ea7762d0e" sha1="f3f8717632ee3e2ef954377a3cfb476d9afa235e" sha256="a061505086fd3fd057d17bd5ee17b54d09985b0c2a9e41127e8ce1d127a8c5c8"/>
</entry> |
the size appears to be incorrect in v5 signatureCatalog.xml as well. what the code gets for a newly computed mfs_cm5 = Moab::FileSignature.new.signature_from_file(Pathname('/services-disk16/sdr2objects/vf/742/yx/0561/vf742yx0561/v0005/data/metadata/contentMetadata.xml'))
=> #<Moab::FileSignature:0x0000000008576248 @md5="4aa570c169ce71c878ba583ea7762d0e", @sha1=nil, @sha256=nil, @size=479650> What's from the signatureCatalogs (v5 and v6) for
|
Fixing the file size fixed the problem. This druid just passed the audit: [1] pry(main)> Audit::Checksum.validate_druid('vf742yx0561')
I, [2020-05-26T16:28:11.414732 #20505] INFO -- : 2020-05-26T23:28:11Z CV validate_druid starting for vf742yx0561
D, [2020-05-26T16:28:11.464036 #20505] DEBUG -- : Found 1 complete moabs.
I, [2020-05-26T17:11:03.029445 #20505] INFO -- : validate_checksums(vf742yx0561, services-disk16) checksum(s) match
I, [2020-05-26T17:11:03.029567 #20505] INFO -- : validate_checksums(vf742yx0561, services-disk16) CompleteMoab status changed from invalid_checksum to ok
I, [2020-05-26T17:11:03.324241 #20505] INFO -- : [{:moab_checksum_valid=>"checksum(s) match"}, {:cm_status_changed=>"CompleteMoab status changed from invalid_checksum to ok"}] for vf742yx0561
I, [2020-05-26T17:11:03.324364 #20505] INFO -- : 2020-05-27T00:11:03Z CV validate_druid ended for vf742yx0561
=> [#<AuditResults:0x000000000778eb58
@actual_version=6,
@check_name="validate_checksums",
@druid="vf742yx0561",
@log_msg_prefix="validate_checksums(vf742yx0561, services-disk16)",
@moab_storage_root=
#<MoabStorageRoot:0x0000000007871e08
id: 17,
name: "services-disk16",
created_at: Tue, 16 Oct 2018 19:22:02 UTC +00:00,
updated_at: Tue, 16 Oct 2018 19:22:02 UTC +00:00,
storage_location: "/services-disk16/sdr2objects">,
@result_array=[{:moab_checksum_valid=>"checksum(s) match"}, {:cm_status_changed=>"CompleteMoab status changed from invalid_checksum to ok"}],
@string_prefix="validate_checksums (actual location: services-disk16; actual version: 6)">] |
@andrewjbtw so can this ticket be closed? |
yes |
https://argo.stanford.edu/view/vf742yx0561
one of the parker manuscripts. cc @andrewjbtw and @blalbrit
Backtrace
View full backtrace and more info at honeybadger.io
checksum validation results:
The text was updated successfully, but these errors were encountered: