No Work?
18 Jul 2008 21:14:08 UTC
Topic 193771
(moderation:
I just got a message saying that I had no new work because I had reached my limit of seven wu results per day. In fact I had no reults today at all, and on average, take 2 1/2 days to finish one unit. Obviously a glitch, but how do I get more work?
No Work?
)
You've been returning only errors 99 since today. You may want to reset the Einstein project to see if that fixes things.
The first error was this,
)
The first error was this, [url="http://einsteinathome.org/task/102019017"]The previous ownership of this semaphore has ended. (0x69) - exit code 105 (0x69).[/url]
RE: I just got a message
)
Because of the 9 tasks that have errored out, you wont be able to get new work until a "new day" starts (00:00:00 UTC). If you review the messages in BOINC manager, you should see that you have indeed had many new tasks today :-).
It seems highly likely that your machine has suffered a hardware failure that caused the initial task to error out with the exit code 105, as noted by Holmis. Unfortunately there is a problem with his link so here is a replacement that should work. You can see the information that Holmis mentioned near the top of the page but if you scroll right down to the bottom you will see some further information that shows that there was a function call that failed. I know very little about this but it seems to me that since calling a function involves jumping to a new location in memory, the hardware problem is likely to be flakey RAM.
This seems to be plausible if you look at all the following tasks which all errored out in the early initialisation stages - all at approximately 15 seconds into each task. Once again you can look at the stderr.out for one of these tasks and if you scroll down a little you will see things like "Reading SFTs and setting up stacks ... Memeory reallocation for SFTs failed: nSFT:56001, length:56000, add:8000" and later on "Status code 14: Out of memory" which seem to me to be indicating a RAM problem.
If I were you, I'd investigate the memory stick(s) you have in your computer and try reseating and/or cleaning the contacts and/or replacing with known good stick(s). If you are feeling adventurous, get yourself a copy of memtest86 and thoroughly test your RAM. You can run memtest from a bootable DOS diskette but I find the easiest thing is to grab a Linux live CD or something like the ultimate boot CD for Windows which usually has memtest as one of the options you can select when booting the CD.
Good luck with the troubleshooting :-).
Cheers,
Gary.