Hi
Since we upgraded to DSpace 5, the checksum checker has been reporting
bitstream not found errors for bistreams that actually still exist. I found
following information in checksum_history table for a bitstream reported
missing-
============================================================
select * from checksum_history where bitstream_id=1123888;
check_id | bitstream_id | process_start_date | process_end_date
| checksum_expected | checksum_calculated |
result
----------+--------------+-------------------------+-------------------------+----------------------------------+----------------------------------+---------------------
71571839 | 1123888 | 2015-12-20 04:00:05.98 | 2015-12-20
04:00:05.98 | d4adcf541126223e6a4c47d4352968ee |
d4adcf541126223e6a4c47d4352968ee | CHECKSUM_MATCH
71572607 | 1123888 | 2015-12-20 04:00:09.26 | 2015-12-20
04:00:10.067 | d4adcf541126223e6a4c47d4352968ee |
d4adcf541126223e6a4c47d4352968ee | CHECKSUM_MATCH
71575659 | 1123888 | 2015-12-20 04:21:46.986 | 2015-12-20
04:21:47.082 | d4adcf541126223e6a4c47d4352968ee |
d4adcf541126223e6a4c47d4352968ee | CHECKSUM_MATCH
71578711 | 1123888 | 2015-12-20 04:29:27.613 | 2015-12-20
04:29:27.614 | d4adcf541126223e6a4c47d4352968ee |
| BITSTREAM_NOT_FOUND
(4 rows)
=============================================================
Our checker is scheduled to run weekly at 4am Sunday for an hour. I am
wondering why we got 4 entries for a single bitstream and with 3 indicate
MATCH and one says not found? Does anyone have the similar issue? Is this a
bug?
Thanks in advance for any clue!
Best,
Ying
--
You received this message because you are subscribed to the Google Groups
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.
