Task exited with zero status
28 Apr 2007 22:03:18 UTC
Topic 192635
(moderation:
I am getting this message for both SETI and Einstein. I have reset both projects several times but the same error for the same jobs keeps coming back up. Any guidance from anyone?
Sample from my log
4/28/2007 11:36:07 AM|SETI@home|Restarting task 24fe05aa.11170.12176.722160.3.63_2 using setiathome_enhanced version 515
4/28/2007 12:31:13 PM|SETI@home|Task 24fe05aa.11170.12176.722160.3.63_2 exited with zero status but no 'finished' file
4/28/2007 12:31:13 PM|SETI@home|If this happens repeatedly you may need to reset the project.
4/28/2007 12:31:13 PM|SETI@home|Restarting task 24fe05aa.11170.12176.722160.3.63_2 using setiathome_enhanced version 515
4/28/2007 1:31:30 PM|Einstein@Home|Restarting task h1_0326.70_S5R2__75_S5R2c_1 using einstein_S5R2 version 417
4/28/2007 3:30:05 PM|Einstein@Home|Task h1_0326.70_S5R2__75_S5R2c_1 exited with zero status but no 'finished' file
4/28/2007 3:30:05 PM|Einstein@Home|If this happens repeatedly you may need to reset the project.
I hope that I did that correctly.
Thank you for any and all help!!
Gary
Task exited with zero status
)
I had something like that on an NForce2 board, it happened exactly every 6 hours.
I modified more than one setting so I cannot tell exactly what fixed it - I think removing FSB Spread Spectrum (BIOS setting) was the breakthrough. In some hardware message boards I have seen that there is a timer chip issue with those boards that - together with Spread Spectrum - can cause those things.
Check fan and coolers too, if they are too dusty, they cannot cool down the CPU enough.
It can also be caused merely
)
It can also be caused merely by your machine getting very busy with something else you are doing with it (like gaming). This can cause the science to miss a heartbeat signal from the CC, which will force the app to exit and results in the message you're seeing.
Generally this is not a big deal unless it's happening very frequently, in which case it can result in virtually no progress depending on how frequently the app checkpoints and/or what you have set for the write to disk interval. Typically the last thing you want to do is reset the project until you have ruled out all other possibilities.
HTH,
Alinator
The FAQ lists this as a known
)
The FAQ lists this as a known BOINC bug:
http://einstein.phys.uwm.edu/faq.php#exited_with_zero_status
I've only seen it once happen, and that was in a situation where the host was under heavy load, see the previous message.
CU
BRM