Continued object checksum calls from CN against LTER

[taojing2002]

I hope this email finds you well and that you are the correct person I should be asking the following question: why does the DataONE CN continually request a checksum verification on a finite set of LTER data objects? This seems to happen on the hour every hour. For example:

128.111.85.180 - - [08/Mar/2022:07:01:05 +0000] "GET /mn/v2/checksum/https:%2F%2Fpasta.lternet.edu%2Fpackage%2Fdata%2Feml%2Fknb-lter-hfr%2F5%2F20%2F687a3dadbbefdfda443345bed5d307da?checksumAlgorithm=SHA-1 HTTP/1.1" 200 807 "-" "Apache-HttpClient/4.3.6 (java 1.5)"

It is somewhat maddening because it really skews our data read statistics for these particular objects and we cannot filter them out because all calls originating from GMN look alike.

Any light you can shed on this processing would be greatly appreciated.

Thanks,
Mark

[taojing2002]

Hi Mark:
I ran the command to get the checksum against the LTER node and it worked well:
curl -E urn_node_CNUCSB1.pem "https://gmn.lternet.edu/mn/v2/checksum/https:%2F%2Fpasta.lternet.edu%2Fpackage%2Fdata%2Feml%2Fknb-lter-hfr%2F5%2F20%2F687a3dadbbefdfda443345bed5d307da?checksumAlgorithm=SHA-1"

It returned:

5653af252444cb867bc201f27f75c735cb2c4d2a

But the system metadata on CN shows the last verified date is "2015-03-10T21:05:58.375+00:00":
https://cn.dataone.org/cn/v2/meta/https:%2F%2Fpasta.lternet.edu%2Fpackage%2Fdata%2Feml%2Fknb-lter-hfr%2F5%2F20%2F687a3dadbbefdfda443345bed5d3

This means somehow the set of the replica verified date failed. I don't know why since I couldn't find the error message.

[taojing2002]

The list of objects which have the issue.
objectReads.txt