Hi Gail, We are on dspace 6.2 and begin to experience the same issue as yours. Would you mind to share the code for your own checksum checker and reports?
Thanks, Ying Rice University @ Fondren Library On Friday, August 10, 2018 at 10:59:01 AM UTC-5, Gail Steinhart wrote: > > Hi Bram, > > > > We have two problems, actually. > > > > Checksum checker: runs, but we get no reports, ever, even though it’s set > to “report everything.” And bitstream deletions happen often enough that > that should definitely trigger a report. > > > > Health check reports: Runs, but only a fraction of bistreams checked. > There may or may not be an error (a hibernate error) but even without an > error, not all bitstreams are checked. > > > > We’ve gone ahead and written our own checksum checker and are running our > own reports. > > > > Thanks for the follow up, > > Gail > > > > *From:* Bram Luyten <[email protected] <javascript:>> > *Sent:* Thursday, August 09, 2018 11:39 AM > *To:* Gail Steinhart <[email protected] <javascript:>> > *Cc:* [email protected] <javascript:> > *Subject:* Re: [dspace-community] Checksum checking and reporting in > DSpace > > > > Hi Gail, > > > > we've very recently seen that the checksum checker fails in DSpace 6.x > with large repositories. > > More details: https://jira.duraspace.org/browse/DS-3975 > > > > Could this also be what's affecting you? Are the logs giving you any > indication that the job succesfully completes? > > > > best regards, > > > > Bram > > > > [image: logo] > > *Bram Luyten* > *250-B Lucius Gordon Drive, Suite 3A, *West Henrietta, NY 14586 > * Gaston Geenslaan 14, 3001 Leuven, Belgium * > atmire.com > <http://atmire.com/website/?q=services&utm_source=emailfooter&utm_medium=email&utm_campaign=braml> > > > > On 20 July 2018 at 20:05, Gail Steinhart <[email protected] <javascript:>> > wrote: > > Greetings all, > > > > Before we upgraded to DSpace 6.2, we ran nightly checksum reporting jobs, > which were sent to our system programmer. Since upgrading to 6.2, we no > longer receive the reports. Logs indicate the checksum checker runs, but no > reports are mailed. We have been unable to get reports to send by changing > options or running jobs manually. We’ve also tried the health check > reports, which run, but don’t check all of our bitstreams. > > > > We’re at a loss. We’re very uncomfortable with the notion that not > receiving checksum reports means there are no errors to report. The absence > of a report could just as easily mean the checking or reporting function is > broken and not that there are no errors. We’re wondering how others in the > DSpace community are handling checksum checking and reporting? Are you > having the same issues? Are there any tools out there that you are using, > or other suggestions you might have? Any other workarounds? > > > > Thanks so much for any suggestions, > > Gail > > > > Gail Steinhart > > Scholarly Communication Librarian | arXiv Program Associate > > Digital Scholarship & Preservation Services | Cornell University Library > > 229 Olin Library | 607.255.7251 > > http://orcid.org/0000-0002-2441-1651 | @gailst > <https://twitter.com/gailst> > > she/hers > > > > -- > All messages to this mailing list should adhere to the DuraSpace Code of > Conduct: https://duraspace.org/about/policies/code-of-conduct/ > --- > You received this message because you are subscribed to the Google Groups > "DSpace Community" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > To post to this group, send email to [email protected] > <javascript:>. > Visit this group at https://groups.google.com/group/dspace-community. > For more options, visit https://groups.google.com/d/optout. > > > -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- You received this message because you are subscribed to the Google Groups "DSpace Community" 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-community. For more options, visit https://groups.google.com/d/optout.
