Message boards :
Number crunching :
workuntits with short deadline
Message board moderation
Author | Message |
---|---|
Sebastian Brack Send message Joined: 22 Aug 99 Posts: 9 Credit: 11,186,556 RAC: 16 |
Hello @all, i got obtained some workunits with realy short deadlines. Is this the normal state for some S@H Workuntis? |
BilBg Send message Joined: 27 May 07 Posts: 3720 Credit: 9,385,827 RAC: 0 |
http://setiathome.berkeley.edu/results.php?hostid=7148977&offset=0&show_names=1&state=6&appid= Since those are all VLAR WUs I would guess: - "they" (people at the lab) turned ON "Resent lost tasks" https://www.google.com/#q=resent+lost+task - those 5 of your tasks were "sent" initially to CPU but never received (become "ghosts") - next request from your BOINC was for GPU tasks, server see 5 "lost tasks" but they are VLAR and can't be sent to GPU so the server makes them expire ("Timed out") Â - ALF - "Find out what you don't do well ..... then don't do it!" :) Â |
Claggy Send message Joined: 5 Jul 99 Posts: 4654 Credit: 47,537,079 RAC: 4 |
- next request from your BOINC was for GPU tasks, server see 5 "lost tasks" but they are VLAR and can't be sent to GPU so the server makes them expire ("Timed out") And the time/date shown is when they timed out, not their deadline, that column is dual use, in english it says 'Time reported or deadline' Claggy |
Sebastian Brack Send message Joined: 22 Aug 99 Posts: 9 Credit: 11,186,556 RAC: 16 |
Thank you, for your fast answer. I did not know, that Ghost exist ;o) Firstonce, i had read some articles about the conflict between VLAR's und the Nvidia-GPU. The question is, how can i prevent to get such a mistake at the future?? |
BilBg Send message Joined: 27 May 07 Posts: 3720 Credit: 9,385,827 RAC: 0 |
The question is, how can i prevent to get such a mistake at the future?? Usually this is caused by bad Internet - the response from the server do not reach your computer. But this "bad Internet" may be somewhere on the path, not near you. In fact nothing really bad happened - you never received those tasks, they will be sent to other computer. If you are curious - you may check/search in Event Log (Ctrl+Shift+E) or in the files stdoutdae.txt and stdoutdae.old (in BOINC Data directory) the string: Scheduler request failed E.g. you may find such lines: 02-Nov-2015 02:58:41 [WUProp@Home] Scheduler request failed: HTTP internal server error 15-Nov-2015 13:51:34 [SETI@home] Scheduler request failed: Server returned nothing (no headers, no data) 18-Nov-2015 13:08:56 [SETI@home] Scheduler request failed: Couldn't connect to server But really important in this case is Timeout was reached - you see the dates are old (I have logs from 13-Nov-2009 till now) and from different projects: 12-Oct-2010 14:51:30 [SETI@home] Scheduler request failed: Timeout was reached 27-Aug-2013 02:38:13 [WUProp@Home] Scheduler request failed: Timeout was reached 06-Oct-2014 15:29:44 [Asteroids@home] Scheduler request failed: Timeout was reached 17-Feb-2015 03:22:01 [WUProp@Home] Scheduler request failed: Timeout was reached  - ALF - "Find out what you don't do well ..... then don't do it!" :)  |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.