[639] in Tooltime
Please check for duplicate logs
daemon@ATHENA.MIT.EDU (Debi Fuchs)
Tue Dec 2 16:36:20 1997
Date: Tue, 2 Dec 1997 16:36:02 -0500
To: hd@MIT.EDU, tooltime@MIT.EDU
From: Debi Fuchs <debi@MIT.EDU>
Hello,
If you notice that a duplicate log has been created (same info, different
log number), please send us a detailed report of your actions directly
preceding the duplicate log creation to tooltime@mit.edu Please include
log numbers, machine type[s], etc.
We are finding many duplicated logs after crashes and after strange record
locking problems. In order to help us troubleshoot and fix this problem,
we need to figure out what actions are causing this to happen. If it
happens to you, please let us know. The following report is a good example
of the detail we need.
Cheers,
-Debi
-----------
>X-Sender: cwood@hesiod
>Date: Tue, 02 Dec 1997 11:11:49 -0500
>To: tooltime@MIT.EDU
>From: Carol Wood <cwood@MIT.EDU>
>Subject: scopus bug?
>Mime-Version: 1.0
>
>Hi,
>I was updating a log this morning and some strange things happened, here's
>what happened:
>
>I am working on an NT machine. The log I was updating was number 101058.
>I changed the status from NEW to PENDING, then I changed the software from
>unknown to BrioQuery. I then selected the Add Entry pull down and chose
>"Left message for callback". Then I typed in the text of the message.
>Then I clicked on the Exit Log button. The message box came up about
>exiting without saving so I selected No. The message box appeared again
>and I selected No again. Then I clicked on Save. At which point there was
>an application error and Scopus crashed.
>
>I then restarted the machine and repeated the above steps exactly to see if
>I could duplicate the problem - which I did (very easily). After the
>second time it crashed, I brought the log up again and changed the status
>field, the software field, used the Add entry pulldown to select "Left
>message...", added my text - but this time I just selected the save
>button. At this point there was an application error and Scopus crashed
>again.
>
>I went to another machine and repeated the above steps, using just the save
>button (not the exit log button) and it got an application error and
>crashed again. At this point Rob tried accessing the log from his machine
>and was successful in saving. I tried again on the second machine and was
>able to successfully update the log and save it.
>
>A while later one of the Student Consultants noticed that there were
>several copies of the same log in the database. It appeared that each time
>it crashed it did actually save the changes - but it created a new log
>number. Log numbers 101114, 101115, 101116, 101119, and 101120 are all
>copies of that same log. The modified date and time were the same as the
>created by date and time (they now are changed because the student then
>cancelled the logs).
>
>Anyway, I hope this makes sense. I'd be happy to explain it in more detail
>if necessary.
>
>Carol
>
-------------
Debi Fuchs, Consultant
MIT Information Systems
Computing Help Desk Group
77 Massachusetts Avenue, 11-319
Cambridge, MA 02139
(617) 253-7812
debi@mit.edu
