Hi Ying,
I know you posted this some time ago, but we are also having a similar
issue. Did you find out the cause of your issue?
We are finding that the checker is reporting false BITSTREAM_NOT_FOUND
errors. When I investigate the errors, I find that the files exist, and if
I remove the bitstream entry from the most_recent_checksum table and re-run
the checker process, the checker finds the bitstream successfully and does
not report an error.
This seems to happen frequently, so cannot use the checker script with any
confidence.
dspace=# select * from checksum_history where bitstream_id = 62155;
check_id | bitstream_id | process_start_date | process_end_date |
checksum_expected | checksum_calculated | resul
t
----------+--------------+-------------------------+-------------------------+----------------------------------+----------------------------------+------------
---------
623801 | 62155 | 2016-08-07 04:42:41.265 | 2016-08-07 04:42:41.352 |
285fb3b1e467cdbec08c40ec39eecd87 | 285fb3b1e467cdbec08c40ec39eecd87 |
CHECKSUM_MA
TCH
753127 | 62155 | 2016-10-02 04:24:12.066 | 2016-10-02 04:24:12.092 |
285fb3b1e467cdbec08c40ec39eecd87 | |
BITSTREAM_N
OT_FOUND
765312 | 62155 | 2016-10-04 10:59:13.071 | 2016-10-04 10:59:13.119 |
285fb3b1e467cdbec08c40ec39eecd87 | 285fb3b1e467cdbec08c40ec39eecd87 |
CHECKSUM_MA
TCH
Any ideas?
Thanks in advance,
Stuart Loose
University of Adelaide
On Wednesday, January 6, 2016 at 9:26:35 AM UTC+10:30, [email protected] wrote:
>
> 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.
