I have one machine that has crunched for Albert in the past two weeks but now REFUSES to get ANY new gpu tasks at all! The server status is Tasks to send 2,480 yet all I get is:
8/8/2012 9:29:27 AM | Albert@Home | Scheduler request completed: got 0 new tasks
8/8/2012 9:29:27 AM | Albert@Home | No tasks sent
8/8/2012 9:29:27 AM | Albert@Home | Tasks for CPU are available, but your preferences are set to not accept them

I let Collatz get new taks, it was suspended and I had NO tasks on the pc, and got this:
8/8/2012 9:29:40 AM | Collatz Conjecture | update requested by user
8/8/2012 9:29:43 AM | Collatz Conjecture | Sending scheduler request: Requested by user.
8/8/2012 9:29:43 AM | Collatz Conjecture | Requesting new tasks for ATI
8/8/2012 9:29:45 AM | Collatz Conjecture | Scheduler request completed: got 66 new tasks

I have now detached the pc from Albert!!! I have ONE pc still attached, PLEASE fix this!!! I am using Boinc version 7.0.31 and have NO other problems!!!

I have one machine that has crunched for Albert in the past two weeks but now REFUSES to get ANY new gpu tasks at all! The server status is Tasks to send 2,480 yet all I get is:
8/8/2012 9:29:27 AM | Albert@Home | Scheduler request completed: got 0 new tasks
8/8/2012 9:29:27 AM | Albert@Home | No tasks sent
8/8/2012 9:29:27 AM | Albert@Home | Tasks for CPU are available, but your preferences are set to not accept them

I let Collatz get new taks, it was suspended and I had NO tasks on the pc, and got this:
8/8/2012 9:29:40 AM | Collatz Conjecture | update requested by user
8/8/2012 9:29:43 AM | Collatz Conjecture | Sending scheduler request: Requested by user.
8/8/2012 9:29:43 AM | Collatz Conjecture | Requesting new tasks for ATI
8/8/2012 9:29:45 AM | Collatz Conjecture | Scheduler request completed: got 66 new tasks

I have now detached the pc from Albert!!! I have ONE pc still attached, PLEASE fix this!!! I am using Boinc version 7.0.31 and have NO other problems!!!

Thanks for reporting this. This was a transient failure to provide BRP4 work, it should be back to normal now.

Cheers
HBE

---

I have one machine that has crunched for Albert in the past two weeks but now REFUSES to get ANY new gpu tasks at all! The server status is Tasks to send 2,480 yet all I get is:
8/8/2012 9:29:27 AM | Albert@Home | Scheduler request completed: got 0 new tasks
8/8/2012 9:29:27 AM | Albert@Home | No tasks sent
8/8/2012 9:29:27 AM | Albert@Home | Tasks for CPU are available, but your preferences are set to not accept them

I let Collatz get new taks, it was suspended and I had NO tasks on the pc, and got this:
8/8/2012 9:29:40 AM | Collatz Conjecture | update requested by user
8/8/2012 9:29:43 AM | Collatz Conjecture | Sending scheduler request: Requested by user.
8/8/2012 9:29:43 AM | Collatz Conjecture | Requesting new tasks for ATI
8/8/2012 9:29:45 AM | Collatz Conjecture | Scheduler request completed: got 66 new tasks

I have now detached the pc from Albert!!! I have ONE pc still attached, PLEASE fix this!!! I am using Boinc version 7.0.31 and have NO other problems!!!

Thanks for reporting this. This was a transient failure to provide BRP4 work, it should be back to normal now.

Cheers
HBE

Glad you got it fixed, THANKS!!

Hello, if I looked correct on the server status there should be work, however I get these messages:

4/28/2014 7:31:11 PM | Albert@Home | Sending scheduler request: To fetch work.
4/28/2014 7:31:11 PM | Albert@Home | Requesting new tasks for NVIDIA
4/28/2014 7:31:13 PM | Albert@Home | Scheduler request completed: got 0 new tasks
4/28/2014 7:31:13 PM | Albert@Home | Project has no tasks available

Is my card, a Quadro FX 4600 (driver version 332.21, CUDA version 6.0, compute capability 1.0, 768MB, 661MB available, 346 GFLOPS peak), no longer usable here?

It did until a few weeks ago.

Thanks.

---

Greetings from,
TJ.

Albert is a beta project that means sometimes there is no work available. If you look on the server status page you can see that all work generators a currently not running - thus no workunits are getting created.
I suppose it's due to the announced drupal migration.