Non-CUDA computers not receiving wu's
8 Dec 2009 20:44:12 UTC
Topic 194665
(moderation:
It appears to be somewhat sort sighted to move over to CUDA processing and leaving computers that don't have CUDA without work or a means to set the type of work. My newly self built computer has notched up 70,000 credits in less than six months, So am I going to be forced out of my account because I DONT have a graphics card that CUDA compliant?
08/12/2009 19:09:03 Einstein@Home Sending scheduler request: To fetch work.
08/12/2009 19:09:03 Einstein@Home Requesting new tasks for GPU
08/12/2009 19:09:08 Einstein@Home Scheduler request completed: got 0 new tasks
08/12/2009 19:09:08 Einstein@Home Message from server: No work sent
08/12/2009 19:09:08 Einstein@Home Message from server: Your computer has no NVIDIA GPU
08/12/2009 19:22:35 Poem@Home Starting data_427_1260287052_121357705_0
08/12/2009 19:22:35 Poem@Home Starting task data_427_1260287052_121357705_0 using poem version 100
08/12/2009 19:29:09 Einstein@Home Sending scheduler request: To fetch work.
08/12/2009 19:29:09 Einstein@Home Requesting new tasks for GPU
08/12/2009 19:29:14 Einstein@Home Scheduler request completed: got 0 new tasks
08/12/2009 19:29:14 Einstein@Home Message from server: No work sent
08/12/2009 19:29:14 Einstein@Home Message from server: Your computer has no NVIDIA GPU
08/12/2009 20:09:30 Einstein@Home Sending scheduler request: To fetch work.
08/12/2009 20:09:30 Einstein@Home Requesting new tasks for GPU
08/12/2009 20:09:35 Einstein@Home Scheduler request completed: got 0 new tasks
08/12/2009 20:09:35 Einstein@Home Message from server: No work sent
08/12/2009 20:09:35 Einstein@Home Message from server: Your computer has no NVIDIA GPU
"All man born has a right to life and no man born has the right to take that life"
Non-CUDA computers not receiving wu's
)
I've seen something similar, which I've reported as a bug in BOINC. My belief is that BOINC's "long term debt" (which it uses to help manage Resource Share) is - wrongly - being frozen when you select "Don't use CUDA". Look in BOINC Manager - projects tab - select 'Einstein' - click 'Properties'. Look for "CPU work fetch priority": if it's more negative than -86,400 (one day in seconds), BOINC won't ask for work.
Assuming you're dry - no Einstein work in progress or waiting to report - try resetting the project. That should clear everything.
RE: I've seen something
)
Resetting the project has done nothing.
09/12/2009 01:01:51 Einstein@Home Scheduler request completed: got 0 new tasks
09/12/2009 01:01:51 Einstein@Home Message from server: No work sent
09/12/2009 01:01:51 Einstein@Home Message from server: Your computer has no NVIDIA GPU
09/12/2009 01:03:12 Einstein@Home Sending scheduler request: To fetch work.
09/12/2009 01:03:12 Einstein@Home Requesting new tasks for GPU
09/12/2009 01:03:17 Einstein@Home Scheduler request completed: got 0 new tasks
09/12/2009 01:03:17 Einstein@Home Message from server: No work sent
09/12/2009 01:03:17 Einstein@Home Message from server: Your computer has no NVIDIA GPU
09/12/2009 01:10:59 Einstein@Home Sending scheduler request: To fetch work.
09/12/2009 01:10:59 Einstein@Home Requesting new tasks for GPU
09/12/2009 01:11:04 Einstein@Home Scheduler request completed: got 0 new tasks
09/12/2009 01:11:04 Einstein@Home Message from server: No work sent
09/12/2009 01:11:04 Einstein@Home Message from server: Your computer has no NVIDIA GPU
09/12/2009 01:16:04 Einstein@Home Sending scheduler request: To fetch work.
09/12/2009 01:16:04 Einstein@Home Requesting new tasks for GPU
09/12/2009 01:16:09 Einstein@Home Scheduler request completed: got 0 new tasks
09/12/2009 01:16:09 Einstein@Home Message from server: No work sent
09/12/2009 01:16:09 Einstein@Home Message from server: Your computer has no NVIDIA GPU
However, "Propeties" show "CPU work fetch priorities" is set to 0.00. This could be the reason for no work. Can anyone tell me how to change the setting?
"All man born has a right to life and no man born has the right to take that life"
RE: It appears to be
)
Ah! We are now getting work. Ether there was no work for non-cuda's or a temporary server error.
"All man born has a right to life and no man born has the right to take that life"
RE: However, "Propeties"
)
0.00 is actually good.
This is scaled with zero at the top - so you should have been requesting CPU work from Einstein first, when work was needed.
Anything negative but small means that another project has precedence, but Einstein should be OK too.
Below -86,400 you'll only get work if your CPUs are idle and it can't find work anywhere else.
RE: RE: However,
)
Problem now solved. It was due to server being down "properties" show "CPU work fetch properties" as -1731.56.
"All man born has a right to life and no man born has the right to take that life"