No work available |
![]() |
| log in |
Questions and Answers : Getting started : No work available
| Author | Message |
|---|---|
|
I keep getting an error about no work available to process. I'm fully connected to the internet. I downloaded and signed up last night and I've only gotten 3 work units. I cancelled two because they were not working. I was able to complete one. Now I cannot get any, any help? Thank you. | |
| ID: 906847 · | |
I keep getting an error about no work available to process... That's not an error message, it just informs you that there is no work available at the server: 12/06/2009 15:45:50|SETI@home|Message from server: (Project has no jobs available) I have received two tasks some time after that message though (UTC+2), so stay tuned.Gruß, Gundolf ____________ Computer sind nicht alles im Leben. (Kleiner Scherz) SETI@home classic workunits 3,758 SETI@home classic CPU time 66,520 hours | |
| ID: 906863 · | |
That's not an error message, it just informs you that there is no work available at the server: In a way it is an error message but not on our end. Looks like it's an error on the server's side. A lot of people are talking about not getting work so we just have to be patient. I'm sure the guys at Berkeley are working on it. As for the two WUs you aborted, what was wrong with them? One was an Astropulse which takes a long time to complete. The other was a mid range MB that appeared to be going along fairly well. The work unit you finished was a shorty, they don't take very long. There are different angle ranges for the multibeam work that take differing amounts of time to complete. If you have any more trouble with a work unit when they start to flow again come on back in and ask us about it. We can see what kind of trouble you are having and may be able to help you through it. ____________ PROUD MEMBER OF Team Starfire World BOINC | |
| ID: 906897 · | |
The astropulse one was probably some kind of problem on my side, for it was running oddly. I probably should have let that one run. My apologies. The other one refused to start. It hung at the beginning and never even started. | |
| ID: 907110 · | |
Sometimes a restart of BOINC (the daemon, not the manager) will fix this problem. ____________ BOINC WIKI | |
| ID: 909738 · | |
Questions and Answers : Getting started : No work available
| Copyright © 2013 University of California |