Never had a problem getting work until now. Now this is what I get when requesting work:

Project Date Message
GPUGRID 12/27/2008 7:49:26 AM Sending scheduler request: Requested by user. Requesting 157711 seconds of work, reporting 0 completed tasks
GPUGRID 12/27/2008 7:49:31 AM Scheduler request completed: got 0 new tasks
GPUGRID 12/27/2008 7:49:31 AM Message from server: No work sent
GPUGRID 12/27/2008 7:49:31 AM Message from server: Full-atom molecular dynamics on Cell processor is not available for your type of computer.
GPUGRID 12/27/2008 7:49:31 AM Message from server: Full-atom molecular dynamics for Cell processor is not available for your type of computer.
GPUGRID 12/27/2008 7:50:32 AM Sending scheduler request: Requested by user. Requesting 157525 seconds of work, reporting 0 completed tasks
GPUGRID 12/27/2008 7:50:37 AM Scheduler request completed: got 0 new tasks
GPUGRID 12/27/2008 7:50:37 AM Message from server: No work sent
GPUGRID 12/27/2008 7:50:37 AM Message from server: Full-atom molecular dynamics for Cell processor is not available for your type of computer.
GPUGRID 12/27/2008 7:50:37 AM Message from server: Full-atom molecular dynamics on Cell processor is not available for your type of computer.
GPUGRID 12/27/2008 7:51:18 AM Sending scheduler request: Requested by user. Requesting 157401 seconds of work, reporting 0 completed tasks
GPUGRID 12/27/2008 7:51:23 AM Scheduler request completed: got 0 new tasks
GPUGRID 12/27/2008 7:51:23 AM Message from server: No work sent
GPUGRID 12/27/2008 7:51:23 AM Message from server: Full-atom molecular dynamics for Cell processor is not available for your type of computer.
GPUGRID 12/27/2008 7:51:23 AM Message from server: Full-atom molecular dynamics on Cell processor is not available for your type of computer.
GPUGRID 12/27/2008 7:54:06 AM Sending scheduler request: Requested by user. Requesting 156949 seconds of work, reporting 0 completed tasks
GPUGRID 12/27/2008 7:54:11 AM Scheduler request completed: got 0 new tasks
GPUGRID 12/27/2008 7:54:11 AM Message from server: No work sent
GPUGRID 12/27/2008 7:54:11 AM Message from server: Full-atom molecular dynamics for Cell processor is not available for your type of computer.
GPUGRID 12/27/2008 7:54:11 AM Message from server: Full-atom molecular dynamics on Cell processor is not available for your type of computer.
GPUGRID 12/27/2008 7:55:44 AM Sending scheduler request: Requested by user. Requesting 955589 seconds of work, reporting 0 completed tasks
GPUGRID 12/27/2008 7:55:49 AM Scheduler request completed: got 0 new tasks
GPUGRID 12/27/2008 7:55:49 AM Message from server: No work sent
GPUGRID 12/27/2008 7:55:49 AM Message from server: Full-atom molecular dynamics for Cell processor is not available for your type of computer.
GPUGRID 12/27/2008 7:55:49 AM Message from server: Full-atom molecular dynamics on Cell processor is not available for your type of computer.
GPUGRID 12/27/2008 7:56:14 AM Sending scheduler request: Requested by user. Requesting 955612 seconds of work, reporting 0 completed tasks
GPUGRID 12/27/2008 7:56:20 AM Scheduler request completed: got 0 new tasks
GPUGRID 12/27/2008 7:56:20 AM Message from server: No work sent
GPUGRID 12/27/2008 7:56:20 AM Message from server: Full-atom molecular dynamics for Cell processor is not available for your type of computer.
GPUGRID 12/27/2008 7:56:20 AM Message from server: Full-atom molecular dynamics on Cell processor is not available for your type of computer.

No changes here in config. Using BOINC v5.4.1. You can see that it's asking for work but the server isn't sending any.

The server status page says:
Results ready to send 932

What's going on?

Same here

My boxes are running dry too. In 7 hours they'll be sitting idle. I've tried everything from all the other threads and no joy!!!

I'm also dry!
____________

Thanks GDF
Got one
____________

I've tried to get work manually hundreds of times today. Nothing. Tried resetting the project several times, tried several different versions of BOINC. Tried detaching from the project and reattaching. Nothing but the same message:

12/27/2008 2:09:52 PM Sending scheduler request: Requested by user. Requesting 958003 seconds of work, reporting 0 completed tasks
12/27/2008 2:09:57 PM Scheduler request completed: got 0 new tasks
12/27/2008 2:09:57 PM Message from server: No work sent
12/27/2008 2:09:57 PM Message from server: Full-atom molecular dynamics for Cell processor is not available for your type of computer.
12/27/2008 2:09:57 PM Message from server: Full-atom molecular dynamics on Cell processor is not available for your type of computer.

This is getting extremely frustrating. Everything seemed to go rotten after v6.56 got pulled back.
Now it says there's 1150 WUs ready to send. I sure can't get any.

More info: Project priority is set very high (999). Set to DL 3 days of work. Tried suspending the CPU project for a while so GPUGRID was the only project. Nothing. Rebooted. Nothing. Said 50 hail marys and 50 our fathers. Nothing. Painted a pentagram on the floor and danced around it 7 times blowing a horn. Nothing.

Now there's:
Results ready to send 1,192
Results in progress 1,896

More info: Project priority is set very high (999). Set to DL 3 days of work. Tried suspending the CPU project for a while so GPUGRID was the only project. Nothing. Rebooted. Nothing. Said 50 hail marys and 50 our fathers. Nothing. Painted a pentagram on the floor and danced around it 7 times blowing a horn. Nothing.

Now there's:
Results ready to send 1,192
Results in progress 1,896

Same here.

Now all of a sudden on my 871st manual update I got 1 WU. I think it was the 42nd reiteration of the Namo Uvajjhâyanam that finally did it.

For the first time today the available WUs are actually decreasing, so maybe somebody fixed something:

Results ready to send 1,138
Results in progress 1,950

Same here. This problem started back on the 10 or 11th of December right about the same time the WU's got split into three catagories 850k, and 2x500k steps.

Maybe it's time to go back to single WU of 850k steps and 6.3.21 with ACEMD 6.55.

Could also have something to do with the DCF. My 8800GT's are around 10.5 while my GTX280's are around 9.9 after reset and about 1 week of work to balance them out. I believe the 8800GT was the 1x factor for the project, so there could be a problem in the code(like someone shifted the period) and we now have 10x. This could be affecting all other GPU to throw the whole project off.

My 2 cents!!

Pat

I just filled all my Caches again, probably will have to go thru the same thing tomorrow sometime but hopefully not.

Not to discount people's problems, but remember, we are in early days here with this new technology. We know there are issues with the various BOINC Manager versions and there are likely issues with the server software (feeder and scheduler) ...

As I have stated before, though I don't know if the project folks have picked up on it, is that I think we are getting the one single message instead of the variaety that we should for various client server interaction failures. In other words, we are having several different problems but we all get the one message. Kinda like the early days in window with the ubiquitous General Protection Fault message. Because almost all crashes puked up the one message it was difficult to figure out what was happening ...

Anyway, be of good cheer ...

We are getting work even if we are missing at times ...

And, just think, not THAT long ago we were wasting all those GPU cycles completely 24/7 ... now we are wasting them only SOME of the time ... in other words, the cup is really half full ...

.... managed to fill all my caches manually - used the suspend all other projects workaround. I think I'm over my 'excitement' at the state the project is in and accept that at this time is will not run unattended/automatically for me.

It'll come good.


P.

More info: Project priority is set very high (999). Set to DL 3 days of work. Tried suspending the CPU project for a while so GPUGRID was the only project. Nothing. Rebooted. Nothing. Said 50 hail marys and 50 our fathers. Nothing. Painted a pentagram on the floor and danced around it 7 times blowing a horn. Nothing.

Now there's:
Results ready to send 1,192
Results in progress 1,896

Completed work on one box and received a work unit[9:30pm EST]in a normal boinc fashion...must have been the salt:)

And, just think, not THAT long ago we were wasting all those GPU cycles completely 24/7 ... now we are wasting them only SOME of the time ... in other words, the cup is really half full ...

The pentagram goes on the ceiling, a ring of salt on the floor:D

You say "set to DL 3 days of work". Do you mean the cache is set for 3 days? GPUGRID has short turn around times and typically will want work back within 3-4 days so that might be the reason why you can't get any (as well as BOINC 6.4.5 not working properly). Try setting the cache a bit lower to say 2 days, that way BOINC should think it can complete the work in time.

I use v6.4.5 on Ubuntu and a 1.5 day cache. The system has worked as it is supposed to for the second day in a row. When work is completed, it gets one more unit. No intervention on my part.

Of course, now that I have said that....everything will fall apart.:D

Need more salt.

mike

And, just think, not THAT long ago we were wasting all those GPU cycles completely 24/7 ... now we are wasting them only SOME of the time ... in other words, the cup is really half full ...

Look @ it this way Paul, for some people the Cup is never full or even half full, if they had full Caches they would just find something else to Whine about ... :)

My last manual update now dates back to two days ago when I managed to get 4 WUs. Since then work fetch works again automatically, my cache being kept at 3 WUs almost continuously with one running. Great! And just in time for me since I am leaving in an hour for a week to visit my parents.

Just one remark though. I noticed in BOINCVIEW that my waiting WUs have a completion time of 11 days and almost 16 hours. As soon as a WU starts it immediately jumps to a completion time of 7 hr 50 min, which is BTW pretty accurate for my GTX260.

Kind regards and happy crunching.

Alain

I got the now work message from a call 12/29/2008 4:59:50 (California time) and I think the situation was caused THIS TIME by having one task in my queue that was rated at 30+ hours. Now, that was from having that 2 plus day task the other day and still thinking that the computer has a 9800 GT vs the new GTX 280 ... I am 36 minutes in, 9.8% done and the time is dropping rapidly from 30 hours and is currently at 26:06 and falling.

*SO*, what that tells me is that the "generic" message we are getting for all sorts of cases is probably related to the scheduler thinking that I have plenty to do and there is no need to give me more work ... my request asked for 56,124 seconds of work, my queue is set to 0.50 days extra work, I have 6 projects on the computer with two out of work (Pirates and LHC) with work from Cosmology and WCG, I don't know why Malaria is dry ...

So, I have 9 tasks in progress, one GPU Grid, 4 WCG, and 4 Cosmology... I have 7 cosmology queued and 4 additional WCG ... runtimes span 2 hours remaining to 20 hours to complete from cold start ...

Thumbnail look seems like I only have about half a days work in hand ... though I may be just on the other side at 0.6 days in hand...

I need a nap ... it is likely I will be back up in a couple hours and I will report if anything changes ...

Oh, when I looked there were 700 plus tasks in the feeder queue ...

That's similar to the situation here. To get new work I have to stop the other projects. I think it's a problem with the handling of the scheduler and the high prio mode for the core to feed the GPU in the background, hidden for the user. Only if all other tasks are stopped and the system makes a call for more than 250,000, I get new work. Here are running: CPDN (over 800 hours), PrimeGrid and MilkyWay with work for the workcache of 0.5 days, LHC and Pirates calling for work without success.
____________

Ok, up from my nap, one task nearing completion I asked for more work and got two tasks.

Yes there are issues with the work fetch policy in that it has not been generalized. Worse ... well, I posted another thread where you can see the discussion as it stands at the moment...

But, yes, there are issues and the current policy as coded in the BOINC Manager may let the CUDA resource go idle ... oops ... :)

I always had these messages :
Full-atom molecular dynamics for Cell processor is not available for your type of computer.
Full-atom molecular dynamics on Cell processor is not available for your type of computer.

They irrate me a lot now. I tried reattaching project and all of the options available but nothing solve the problem.
These messages happened on host 6362, 5716 and 15576.
I am really tired of this situation.
Fix it rapidly please.

I had the problem for a couple hours this morning but just got two more (whew!) ...

Are you feeding PS3 and Nvidia systems off of the same feeder?

I wonder if the pull rate is such that the feeder gets "clogged" with tasks for the other platform ...

Other projects have had issues like this ... in the dark past ...

Looking at the server status it seems there's only one feeder for all platforms...
____________

pixelicious.at - my little photoblog

No work again. Second day in a row. (As my 280's sit idly by contemplating their existance!!)

Pat

When is this "Atom Not available " Problem Going to be fixed? It Has been going on for about 2 weeks now.... Is Any one addressing this problem? I have tried 6.4.2, 6.5.0 versions, Reset project several times , Reloaded drivers Etc..and nothing works... Please help... Thanks.
____________

When is this "Atom Not available " Problem Going to be fixed? It Has been going on for about 2 weeks now.... Is Any one addressing this problem? I have tried 6.4.2, 6.5.0 versions, Reset project several times , Reloaded drivers Etc..and nothing works... Please help... Thanks.

This is really a problem for us as well. There was a change of scheduler policy a couple of weeks ago in the BOINC server which is buggy. Please post on the BOINC dev forums as well. The holiday period is slowing them down in fixing it.


gdf

Not able to get any new WU's even with manual priming...5 machines... old "Atom Not Available" message...server problems???

Same here, got the last WU at 4:44 UTC, now 3 machines will running dry in the next 4 to 8 hours.
____________

When is this "Atom Not available " Problem Going to be fixed? It Has been going on for about 2 weeks now.... Is Any one addressing this problem? I have tried 6.4.2, 6.5.0 versions, Reset project several times , Reloaded drivers Etc..and nothing works... Please help... Thanks.

At this point why is the project continuing to keep short deadlines,1 task per core, and 24 hour back-offs???????

If they could flood us with work even once while all these problems are going on they would be getting work back while now they get none or very little and we could be happily crunching????

I don't understand the logic of letting us starve while the scheduler/feeder is broken!!!!!

Did somebody just kick a server?

I manually updated my boxes using Boincview and half of my dry machines downloaded new WU's! Unfortunately, the others are stuck again in the normal cycle....it seems the kick was not hard enough ;-)

/edit

that did it! The second kick must have pushed the server network cable back in properly....all machines back running again :-)
____________

Stop the other projects and make a manually update, than you should also get work for the other boxes.
____________

It is because I just got back up and started chanting ....

Stop the other projects and make a manually update, than you should also get work for the other boxes.

I am managing to get new WU's via manual priming again...

It is because I just got back up and started chanting ....