Title: Message Title
|
|
Issue Type:
|
Improvement
|
Affects Versions:
|
1.8.3, 1.7.3, 4.0, 3.2
|
Assignee:
|
Unassigned
|
Components:
|
DSpace API
|
Created:
|
22/Jan/14 4:00 PM
|
Priority:
|
Minor
|
Reporter:
|
Tim Donohue
|
|
While the Checksum Checker Emailer ([dspace]/bin/dspace checker-emailer) is a nice feature, it's limited in its usefulness/trustworthiness as it fails to report errors that may be occurring behind the scenes. In DSpace 4.0 and below, an email with a subject of ""0 Bitstreams found with POSSIBLE issues" from the CheckSum Checker Emailer can mean one of several things: (a) Things are OK and all bitstream checksums are verified, OR (b) The checksum checker is throwing an error behind the scenes, so no bitstreams are being processed, OR (c) The checksum checker has not been re-enabled, so no bitstreams are being processed. Obviously, the latter two (b and c) results should be reported as errors or warnings to DSpace Administrators. Currently, the only way to determine what is actually going on with the CheckSum checker is by also analyzing the [dspace]/log/checker.log.YYYY-MM-DD log files. Ideally, this Emailer should report checksum checker errors to administrators. We also may want it to occasionally "check in" and verify that everything is OK & running smoothly (e.g. send an "everything's OK" email once per month). This is semi-related to DS-1873, but details issues that may require enhancements to the Checksum checker & emailer.
|
|
|
|
|
|
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel