Message boards : Number crunching : Computation Error
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile CoM

Send message
Joined: 29 Sep 04
Posts: 42
Credit: 10,488,882
RAC: 73
Message 24334 - Posted: 13 Jul 2012, 19:22:35 UTC
Last modified: 13 Jul 2012, 19:28:08 UTC

13/07/2012 16:14:17 LHC@home 1.0 Aborting task w1jul_niebb1d__37__s__64.28_59.31__9.6_9.8__6__28_1_sixvf_boinc64820_1: exceeded elapsed time limit 18257.559888

Thats just one example of the error I get from my machines.
I checked computers of other users and its the same. The only difference is the time after the error kicks in. Seems like it scales to the computer.
The question is, why is there a time limit? REMOVE IT!! Please
The crunching from hours (in case of my main machine 5 hours) gets wasted, without receiving any credit for that WU.
I think I will delete all LHC WUs that now and check later, when the time limit gets removed.

P.S.: After looking through several computers task I got the impression that this happens mainly to SSE3 tasks, some PNI, no SSE2 seen so far.
ID: 24334 · Report as offensive     Reply Quote
Matthias Lehmkuhl

Send message
Joined: 15 Jul 05
Posts: 20
Credit: 1,123,429
RAC: 824
Message 24336 - Posted: 13 Jul 2012, 20:34:59 UTC

got also some results with
<message>
Maximum elapsed time exceeded
</message>
Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Breakpoint Encountered (0x80000003) at address 0x7729280C

Engaging BOINC Windows Runtime Debugger...

http://lhcathomeclassic.cern.ch/sixtrack/result.php?resultid=4162849
http://lhcathomeclassic.cern.ch/sixtrack/result.php?resultid=4166176
http://lhcathomeclassic.cern.ch/sixtrack/result.php?resultid=4166151
Matthias

ID: 24336 · Report as offensive     Reply Quote
Profile Igor Zacharov
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist

Send message
Joined: 16 May 11
Posts: 79
Credit: 111,419
RAC: 0
Message 24352 - Posted: 14 Jul 2012, 1:18:55 UTC - in response to Message 24336.  

Matthias,

what may have happened is that the tasks were downloaded to your computer with the wrong time limit already and me changing this parameter after the download on the server could not prevent this crash.

What may help is to reset the project. You will get new tasks with the correct limit setting. It would be interesting to find out if this is the right recepy.


got also some results with

Maximum elapsed time exceeded

Unhandled Exception Detected...

skype id: igor-zacharov
ID: 24352 · Report as offensive     Reply Quote
Profile CoM

Send message
Joined: 29 Sep 04
Posts: 42
Credit: 10,488,882
RAC: 73
Message 24355 - Posted: 14 Jul 2012, 8:36:35 UTC

Igor, is the error with the SSE3 WUs now removed.
See below that it effects mainly SSE3 WUs:

http://lhcathomeclassic.cern.ch/sixtrack/results.php?hostid=9942772&offset=0&show_names=0&state=5&appid=

CoM
ID: 24355 · Report as offensive     Reply Quote
Profile Igor Zacharov
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist

Send message
Joined: 16 May 11
Posts: 79
Credit: 111,419
RAC: 0
Message 24356 - Posted: 14 Jul 2012, 9:22:07 UTC - in response to Message 24355.  

yes, the work which was send after 7 pm CET on friday 13 of july should have
the correct execution time limit set. All the wus you have listed are from
before the cutoff. If in doubt, reset the project.


Igor, is the error with the SSE3 WUs now removed.
See below that it effects mainly SSE3 WUs:

http://lhcathomeclassic.cern.ch/sixtrack/results.php?hostid=9942772&offset=0&show_names=0&state=5&appid=

CoM


skype id: igor-zacharov
ID: 24356 · Report as offensive     Reply Quote
Matthias Lehmkuhl

Send message
Joined: 15 Jul 05
Posts: 20
Credit: 1,123,429
RAC: 824
Message 24366 - Posted: 14 Jul 2012, 21:34:54 UTC - in response to Message 24356.  

confirm, results with start date 13 that I got have finished correct
Didn't need to reset the project.

http://lhcathomeclassic.cern.ch/sixtrack/result.php?resultid=4176438

Matthias

ID: 24366 · Report as offensive     Reply Quote

Message boards : Number crunching : Computation Error


©2020 CERN