Missing output files
21 Feb 2012 8:15:12 UTC
Topic 196190
(moderation:
My BOINC client repeatedly produces errors as shown by the following extract of stdoutdae.txt:
Quote:
21-Feb-2012 06:30:11 [Einstein@Home] Output file p2030.20110602.G39.59-00.57.S.b1s0g0.00000_2384_0_0 for task p2030.20110602.G39.59-00.57.S.b1s0g0.00000_2384_0 absent
21-Feb-2012 06:30:11 [Einstein@Home] Output file p2030.20110602.G39.59-00.57.S.b1s0g0.00000_2384_0_1 for task p2030.20110602.G39.59-00.57.S.b1s0g0.00000_2384_0 absent
21-Feb-2012 06:30:11 [Einstein@Home] Output file p2030.20110602.G39.59-00.57.S.b1s0g0.00000_2384_0_2 for task p2030.20110602.G39.59-00.57.S.b1s0g0.00000_2384_0 absent
21-Feb-2012 06:30:11 [Einstein@Home] Output file p2030.20110602.G39.59-00.57.S.b1s0g0.00000_2384_0_3 for task p2030.20110602.G39.59-00.57.S.b1s0g0.00000_2384_0 absent
21-Feb-2012 06:30:11 [Einstein@Home] Output file p2030.20110602.G39.59-00.57.S.b1s0g0.00000_2384_0_4 for task p2030.20110602.G39.59-00.57.S.b1s0g0.00000_2384_0 absent
21-Feb-2012 06:30:11 [Einstein@Home] Output file p2030.20110602.G39.59-00.57.S.b1s0g0.00000_2384_0_5 for task p2030.20110602.G39.59-00.57.S.b1s0g0.00000_2384_0 absent
21-Feb-2012 06:30:11 [Einstein@Home] Output file p2030.20110602.G39.59-00.57.S.b1s0g0.00000_2384_0_6 for task p2030.20110602.G39.59-00.57.S.b1s0g0.00000_2384_0 absent
21-Feb-2012 06:30:11 [Einstein@Home] Output file p2030.20110602.G39.59-00.57.S.b1s0g0.00000_2384_0_7 for task p2030.20110602.G39.59-00.57.S.b1s0g0.00000_2384_0 absent
21-Feb-2012 06:30:11 [Einstein@Home] Starting task p2030.20110602.G39.59-00.57.S.b1s0g0.00000_2216_0 using einsteinbinary_BRP4 version 100
21-Feb-2012 06:30:25 [Einstein@Home] Computation for task p2030.20110602.G39.59-00.57.S.b1s0g0.00000_2216_0 finished
21-Feb-2012 06:30:25 [Einstein@Home] Output file p2030.20110602.G39.59-00.57.S.b1s0g0.00000_2216_0_0 for task p2030.20110602.G39.59-00.57.S.b1s0g0.00000_2216_0 absent
The initial error is missing output files of a certain BRP4 task. As a consequence the next task finishes only a few seconds after it had started. Of course there are no output files computed which initiates the next task being aborted some seconds after its start. This way the error propagates like a cascade. At the end every task BOINC schedules (there are only E@h tasks on my machine) is "done" and BOINC is running idle. In addition BOINC is in such an unstable state after all, I have to reboot the computer.
What could it be a reason BOINC looses output files or rather BRP3CUDA32.exe doesn't produce any? Why does BOINC get stuck and cannot go on ignoring the previous error?
Gruß
Heinrich
