[Dpr-development] [ dpr-Feature Requests-2113467 ] Change when checksum checker sends email

[SourceForge.net <no...@so...>]

Feature Requests item #2113467, was opened at 2008-09-16 14:51
Message generated for change (Settings changed) made by acunliffe
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=676459&aid=2113467&group_id=116934

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Checksum Checker
Group: None
>Status: Closed
Resolution: Fixed
Priority: 5
Private: No
Submitted By: John (vombatus)
Assigned to: Allan Cunliffe (acunliffe)
Summary: Change when checksum checker sends email

Initial Comment:
Currently, the checksum checker only sends an email when it starts up.

It would be good if it sent a message at the end of each run through saying that it was successful (or not).

It could give the number of items checked and number of failures (if any) - similar to the results pane.

----------------------------------------------------------------------

>Comment By: Allan Cunliffe (acunliffe)
Date: 2010-01-15 09:50

Message:
Tested in Testing Branch 1.0.6 build 2

An end or run summary email is sent at the end of each run. The following
example shows the information contained:

"Start time: Fri Jan 15 09:23:34 EST 2010
Total run time: 5 seconds
Database URL: jdbc:postgresql://localhost:5432/dr_testing
Repository path: /media/X126/local test repository

The following exception(s) occurred in the rolling checksum checker:
/media/X126/local test
repository/2009/40000009/pf_data/binary/20091020165201800-She's%20A%20Woman.mp3.flac-5ce83baf.xena:
java.io.IOException: Input/output error"

As mentioned in Feature Request ID: 2739667:

* When there are no errors, it has the subject heading of: "End of run
summary"
* When there is an error, it has the subject heading of: "***ROLLING
CHECKSUM CHECKER ERROR***".


----------------------------------------------------------------------

Comment By: Justin Waddell (jwaddell)
Date: 2010-01-13 16:49

Message:
checksum checker will print out the database and repository path it is
using. It will print the time the current run was started, and when
finished will print how long the run took and the time when the next run is
due to start. The checker can also be put in to 'verbose' mode which will
print a log message for every AIP checked.

----------------------------------------------------------------------

Comment By: Justin Waddell (jwaddell)
Date: 2010-01-13 16:46

Message:
This has been implemented - one email is sent when the checker is first
started, one email is sent when the first error in a run is encountered,
and a summary email is sent at the end of the run.

----------------------------------------------------------------------

Comment By: John (vombatus)
Date: 2009-12-10 11:23

Message:
sorry, I just had another thought...

It is particularly important to get some feedback when we are running
checksum checker on the servers - there is currently no easy way to tell if
checksum checker is actually doing anything. If it starts up, then crashes
at some time, there is no indication that things are not working as
expected. No normal person should be forced to go through the logs to see
if things are happening

----------------------------------------------------------------------

Comment By: John (vombatus)
Date: 2009-12-10 11:20

Message:
It would also be useful for the sysadmins to know which database and
filesystem was checked - they do regular restores from backup which are
then checked by checksum checker

Start and finish time would also be useful. At the moment, we do not
really know how long a checking run lasts. It would be nice to know so we
can plan for more data objects. Excessive run times might also point to
problems, but without knowing how long things take, this is hard to detect.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=676459&aid=2113467&group_id=116934