It can be a timing thing - requesting too frequently can result in some strange, undesirable, effects, so be patient - one of my crunchers was doing the same earlier in the week, but is now bouncing off the limits for both CPU & GPU.

I do know that some of us experienced CPU workfetch backoffs after the server moving outage.
But if Vic has been online all this time, I don't think that should come into play.

I normally do cpu/gpu work from 19:00 to 7:00, I did a repair install of Boinc 6.10.58 x64, I'm still not getting cpu wu's, I have 8 total cpu wu's, 3 that I'm working on and 5 in My cache and that's all, there should be 97 in My cache.

I really suspect that Boinc is not asking for more than that for whatever reason.
The servers are not being stingy about handing work out.

Let me see if I can find the debug info for ya.

---

"Time is simply the mechanism that keeps everything from happening all at once."

OK...
I think this is it.
Add to your cc_config file.

<work_fetch_debug>

Try that, reboot Boinc, and see if it starts giving you more details about the actual workfetch requests.

---

"Time is simply the mechanism that keeps everything from happening all at once."

If there is an issue with the workfetch deferrals, in BOINC 6.10 is very easy to clear them. Just set the project to No New tasks, do a manual update (after the 5 mins delay ended) and then resume the work fetch and wait until the delay is over to do another update (it should start autmatically if your cache is low)...
If this doesn't make you get more tasks, then you will need to debug it using the advanced techniques...

---

State: All (531) · In progress (106) · Validation pending (208) · Validation inconclusive (6) · Valid (211) · Invalid (0) · Error (0)
Application: All (531) · Astropulse v505 (0) · AstroPulse v6 (0) · SETI@home Enhanced (531) · SETI@home v7 (0)

Vics' numbers. Is there something missing in there? They don't add up to me.

Add to your cc_config file.

<work_fetch_debug>

Actually it is:

<work_fetch_debug>1</work_fetch_debug>

and it goes in the flags section, not the options section.

There are some other debug flags that might help, but the output can be verbose and hard to interpret.
http://boincfaq.mundayweb.com/index.php?view=91&sessionID=2e1173778d098ab83bdf76903021b47d

---

Another Fred
Support SETI@home when you search the Web with GoodSearch or shop online with GoodShop.

State: All (531) · In progress (106) · Validation pending (208) · Validation inconclusive (6) · Valid (211) · Invalid (0) · Error (0)
Application: All (531) · Astropulse v505 (0) · AstroPulse v6 (0) · SETI@home Enhanced (531) · SETI@home v7 (0)

Vics' numbers. Is there something missing in there? They don't add up to me.

106 in progress says it all, I think.

---

"Time is simply the mechanism that keeps everything from happening all at once."

Add to your cc_config file.

<work_fetch_debug>

Actually it is:

<work_fetch_debug>1</work_fetch_debug>

and it goes in the flags section, not the options section.

There are some other debug flags that might help, but the output can be verbose and hard to interpret.
http://boincfaq.mundayweb.com/index.php?view=91&sessionID=2e1173778d098ab83bdf76903021b47d

Thanks, Fred. I wondered about that.

Try this, Vic.

---

"Time is simply the mechanism that keeps everything from happening all at once."

State: All (531) · In progress (106) · Validation pending (208) · Validation inconclusive (6) · Valid (211) · Invalid (0) · Error (0)
Application: All (531) · Astropulse v505 (0) · AstroPulse v6 (0) · SETI@home Enhanced (531) · SETI@home v7 (0)

Vics' numbers. Is there something missing in there? They don't add up to me.

106 in progress says it all, I think.

All (531) In progress (106) Validation pending (208)

531 - 106 - 208 = 217 Where's the 217 accounted for?

State: All (531) · In progress (106) · Validation pending (208) · Validation inconclusive (6) · Valid (211) · Invalid (0) · Error (0)
Application: All (531) · Astropulse v505 (0) · AstroPulse v6 (0) · SETI@home Enhanced (531) · SETI@home v7 (0)

Vics' numbers. Is there something missing in there? They don't add up to me.

106 in progress says it all, I think.

All (531) In progress (106) Validation pending (208)

531 - 106 - 208 = 217 Where's the 217 accounted for?

Add in the valid and inconclusives.
217 more.

---

"Time is simply the mechanism that keeps everything from happening all at once."

ok. I wasn't sure if valids were still counted in the total
after validation.

Next straw then.

I think this means it is NOT asking for work......

SETI@home 4/12/2013 1:08:20 PM [wfd] request: 333543.21 sec CPU (0.00 sec, 0.00)

---

"Time is simply the mechanism that keeps everything from happening all at once."

Ok I put up 2 or 3 files in 3 or 4 entries in the following thread:

Problem can't download cpu wu's, gpu's wu's are fine though

Maybe this will help?

42 4/12/2013 1:07:05 PM [wfd]: work fetch start
43 4/12/2013 1:07:05 PM [wfd] ------- start work fetch state -------
44 4/12/2013 1:07:05 PM [wfd] target work buffer: 345600.00 + 0.00 sec
45 4/12/2013 1:07:05 PM [wfd] CPU: shortfall 994090.56 nidle 0.00 saturated 9450.33 busy 0.00 RS fetchable 0.00 runnable 100.00
46 Einstein@Home 4/12/2013 1:07:05 PM [wfd] CPU: fetch share 0.00 LTD 0.00 backoff dt 0.00 int 0.00 (no new tasks)
47 SETI@home 4/12/2013 1:07:05 PM [wfd] CPU: fetch share 0.00 LTD 0.00 backoff dt 0.00 int 0.00 (comm deferred)
48 4/12/2013 1:07:05 PM [wfd] NVIDIA GPU: shortfall 333557.59 nidle 0.00 saturated 12009.79 busy 0.00 RS fetchable 0.00 runnable 100.00
49 Einstein@Home 4/12/2013 1:07:05 PM [wfd] NVIDIA GPU: fetch share 0.00 LTD 0.00 backoff dt 0.00 int 0.00 (no new tasks) (blocked by prefs)
50 SETI@home 4/12/2013 1:07:05 PM [wfd] NVIDIA GPU: fetch share 0.00 LTD 0.00 backoff dt 0.00 int 0.00 (comm deferred)
51 Einstein@Home 4/12/2013 1:07:05 PM [wfd] overall LTD 0.00
52 SETI@home 4/12/2013 1:07:05 PM [wfd] overall LTD -236995.78
53 4/12/2013 1:07:05 PM [wfd] ------- end work fetch state -------

Have you already tried the set Use NVIDIA GPU to no and do some requests trick yet?

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

I think this means it is NOT asking for work......

SETI@home 4/12/2013 1:08:20 PM [wfd] request: 333543.21 sec CPU (0.00 sec, 0.00)

I make it that Boinc is only asking for a day's work, try increasing the cache setting to 5 days.

(345600.00 seconds devided by 60 makes 5,760 minutes, devided by 60 makes 96 hours, devided by four cores makes 24 hours.)

Claggy

Why can't I do both cpu and gpu work? Is it now forbidden to do both?

And no I haven't, I don't see that as a problem.

Maybe I should just detach...

Oh, Jesus, Vic. Folks are just trying to help you sort things.
If you wanna go, just do it without fanfare.

Unless I misread you and you are just talking about a detach and reattach.

Sorry if I overreacted in that case.

---

"Time is simply the mechanism that keeps everything from happening all at once."

Why can't I do both cpu and gpu work? Is it now forbidden to do both?

And no I haven't, I don't see that as a problem.

Maybe I should just detach...

Oh, Jesus, Vic. Folks are just trying to help you sort things.
If you wanna go, just do it without fanfare.

Unless I misread you and you are just talking about a detach and reattach.

Sorry if I overreacted in that case.

I'm a bit frustrated, I don't see anything on My end wrong, I mean we are allowed to download 100 wu's for the cpu and 100 wu's for the gpus aren't We?

Yes...and actually, now that I think about it, a detach and reattach might not be a bad thing to try.

Given that the download speed is so fast, and work availability is so good now, that might not be a bad gamble, Vic.

You have little to lose in trying, and your GPU will be full of work in no time at all. Whatcha think?

I really am on your side, my friend.

---

"Time is simply the mechanism that keeps everything from happening all at once."

Actually I don't think that will help any, I'm getting 94 cpu wu's now, I disabled the gpu(ati and nvidia) settings here on Seti and I'm getting/downloaded work.

Wonderful....
Hopefully you have broken the logjam then.

What's important to remember, Vic, is that there is no end of potential help here when you ask for it.

I KNOW how frustrating it can be when things are broken.

But, just look at how many posts there are to this thread since you first reported your problem 3 hours ago.

---

"Time is simply the mechanism that keeps everything from happening all at once."

Ok I put up 2 or 3 files in 3 or 4 entries in the following thread:

Problem can't download cpu wu's, gpu's wu's are fine though

Maybe this will help?

42 4/12/2013 1:07:05 PM [wfd]: work fetch start
43 4/12/2013 1:07:05 PM [wfd] ------- start work fetch state -------
44 4/12/2013 1:07:05 PM [wfd] target work buffer: 345600.00 + 0.00 sec
45 4/12/2013 1:07:05 PM [wfd] CPU: shortfall 994090.56 nidle 0.00 saturated 9450.33 busy 0.00 RS fetchable 0.00 runnable 100.00
46 Einstein@Home 4/12/2013 1:07:05 PM [wfd] CPU: fetch share 0.00 LTD 0.00 backoff dt 0.00 int 0.00 (no new tasks)
47 SETI@home 4/12/2013 1:07:05 PM [wfd] CPU: fetch share 0.00 LTD 0.00 backoff dt 0.00 int 0.00 (comm deferred)
48 4/12/2013 1:07:05 PM [wfd] NVIDIA GPU: shortfall 333557.59 nidle 0.00 saturated 12009.79 busy 0.00 RS fetchable 0.00 runnable 100.00
49 Einstein@Home 4/12/2013 1:07:05 PM [wfd] NVIDIA GPU: fetch share 0.00 LTD 0.00 backoff dt 0.00 int 0.00 (no new tasks) (blocked by prefs)
50 SETI@home 4/12/2013 1:07:05 PM [wfd] NVIDIA GPU: fetch share 0.00 LTD 0.00 backoff dt 0.00 int 0.00 (comm deferred)
51 Einstein@Home 4/12/2013 1:07:05 PM [wfd] overall LTD 0.00
52 SETI@home 4/12/2013 1:07:05 PM [wfd] overall LTD -236995.78
53 4/12/2013 1:07:05 PM [wfd] ------- end work fetch state -------

Have you already tried the set Use NVIDIA GPU to no and do some requests trick yet?

Why can't I do both cpu and gpu work? Is it now forbidden to do both?

And no I haven't, I don't see that as a problem.

Maybe I should just detach...

It is a known issue with BOINC. Where it will fill the GPU cache over the CPU cache. I think there was some work done server side to try and correct this, but it may only be effective with newer versions of BOINC. Once you have CPU tasks again reenable GPU fetch and then see how it goes. With the 100 task limits you might have to lower your queue settings to prevent it from doing it again.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Also important to remember is that these forums
are not exactly real time. The person that might have been able to
correctly answer his first post may have been in bed and might not
see it for another couple of hours. I think it's best to wait a day
for all time zones to have time to read the forum before going into
antsy frustrated mode.

Ok I put up 2 or 3 files in 3 or 4 entries in the following thread:

Problem can't download cpu wu's, gpu's wu's are fine though

Maybe this will help?

42 4/12/2013 1:07:05 PM [wfd]: work fetch start
43 4/12/2013 1:07:05 PM [wfd] ------- start work fetch state -------
44 4/12/2013 1:07:05 PM [wfd] target work buffer: 345600.00 + 0.00 sec
45 4/12/2013 1:07:05 PM [wfd] CPU: shortfall 994090.56 nidle 0.00 saturated 9450.33 busy 0.00 RS fetchable 0.00 runnable 100.00
46 Einstein@Home 4/12/2013 1:07:05 PM [wfd] CPU: fetch share 0.00 LTD 0.00 backoff dt 0.00 int 0.00 (no new tasks)
47 SETI@home 4/12/2013 1:07:05 PM [wfd] CPU: fetch share 0.00 LTD 0.00 backoff dt 0.00 int 0.00 (comm deferred)
48 4/12/2013 1:07:05 PM [wfd] NVIDIA GPU: shortfall 333557.59 nidle 0.00 saturated 12009.79 busy 0.00 RS fetchable 0.00 runnable 100.00
49 Einstein@Home 4/12/2013 1:07:05 PM [wfd] NVIDIA GPU: fetch share 0.00 LTD 0.00 backoff dt 0.00 int 0.00 (no new tasks) (blocked by prefs)
50 SETI@home 4/12/2013 1:07:05 PM [wfd] NVIDIA GPU: fetch share 0.00 LTD 0.00 backoff dt 0.00 int 0.00 (comm deferred)
51 Einstein@Home 4/12/2013 1:07:05 PM [wfd] overall LTD 0.00
52 SETI@home 4/12/2013 1:07:05 PM [wfd] overall LTD -236995.78
53 4/12/2013 1:07:05 PM [wfd] ------- end work fetch state -------

Have you already tried the set Use NVIDIA GPU to no and do some requests trick yet?

Why can't I do both cpu and gpu work? Is it now forbidden to do both?

And no I haven't, I don't see that as a problem.

Maybe I should just detach...

It is a known issue with BOINC. Where it will fill the GPU cache over the CPU cache. I think there was some work done server side to try and correct this, but it may only be effective with newer versions of BOINC. Once you have CPU tasks again reenable GPU fetch and then see how it goes. With the 100 task limits you might have to lower your queue settings to prevent it from doing it again.

Well I run the anonymous platform which I think is still not supported under the beta v7 or am I wrong? Seems kind of unfair to Me, it's like no v7, no cpu work...

This sucks.

Anonymous/3rd party apps work with BOINC v7. I'm not sure where you might have gotten the idea they don't.
I don't know if the issue doesn't exist when using 6.12.xx or 7.0.xx, but I have not seen anyone talking about having this issue for quite a while.
I think it is suggested you run dry before switching to BOINC v7 if you are thinking about that.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

This is the reason to at least run down your GPU work

http://setiathome.berkeley.edu/forum_thread.php?id=71160

---