On mine and my wifes P4 HT machines, which mostly crunch Seti, I noticed this in the BOINC log this morning,

7/9/2005 6:31:06 AM|SETI@home|Message from server: No work sent
7/9/2005 6:31:06 AM|SETI@home|Message from server: (reached daily quota of 4 results)

Wifes computer has same message, then I went to the computer summary pages:
P4b 3.06
and
p4c 2.6 and saw the 2/day per CPU for these two hungry seti crunchers.

Any ideas on how to fix this?

---

<br>
Mars <br>
<img src='http://www.boincstats.com/stats/banner.php?cpid=7d22d5f982e9096d95fa085d6ee2c1bc'>

Welcome to the club. Are you only using Boinc CC4.45 or another one as well?

---

Welcome to the club. Are you only using Boinc CC4.45 or another one as well?

BOINC is ver 4.45 on both machines. Seti app is optimized, but the CC isn't, as I do run other projects on all my machines.

---

<br>
Mars <br>
<img src='http://www.boincstats.com/stats/banner.php?cpid=7d22d5f982e9096d95fa085d6ee2c1bc'>

Okay, well for now there is no real fix. I must say it's a weird thing, I went from 100 units/day to 1 unit/day overnight. I've already reported it to the developers list, but thought it was a side effect of CC4.70

If you're saying that you're using CC4.45, with no overly extra amount of errors in the past 2 weeks, then it's something to do with Seti (and Seti Beta).

For dev's, check V&M's results at this page, those No Reply units, is that it?

---

I would say that the reason the daily quota has dropped is because of the workunits that have just expired on both Ageless's and Venus and Mars computers. It doesn't seem right that, eventhough all computers have been returning results reliably since those workunits were downloaded, that the daily quota should drop that much.

Hmm, I have it at 1 a day per cpu for my PowerMac G5 ... interesting ... especially as I have 9 open Results in my buffer. AND, I have successes going way back to the turn of the month where we had that sour spot. So, does not make sense to me ...

I looked for the code that did this and was not able to find it ... maybe I will look again today ... really odd ...

---

I looked at one of their computers, and I would say that the cause is that string of 'no reply' units that are going overdue today...

http://setiathome.berkeley.edu/results.php?hostid=220878&offset=260

I've had it happen to me... Once that bunch has all gone 'overdue', you should recover rather quickly as valid results are returned.

Moral of this story is that one should be VERY careful about dumping work into the bit bucket.

---

https://youtu.be/iY57ErBkFFE

#Texit

Don't blame me, I voted for Johnson(L) in 2016.

Truth is dangerous... especially when it challenges those in power.

You know, I noticed those workunits that are now starting to time out on the two computers. I can't find any record that they actually made it onto my machines for crunching. Could these possibly be "ghost wu's" I saw a post about a while ago?

EDIT: argh, I just noticed that all those non-completed wu's came from the day I switched the seti app to the optimized one. Doh, I should have drained the cache first it seems. It must have threw them away when I restarted BOINC. Lesson learned.

EDIT: and even further strangeness after the message earlier this morning that prompted my post,

7/9/2005 6:31:06 AM|SETI@home|Message from server: No work sent
7/9/2005 6:31:06 AM|SETI@home|Message from server: (reached daily quota of 4 results)

my machine just finished two WU's, sent them back and got four new wus downloaded,

7/9/2005 9:15:53 AM|SETI@home|Requesting 87498 seconds of work, returning 2 results
7/9/2005 9:15:55 AM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
7/9/2005 9:15:56 AM|SETI@home|Started download of 01no03aa.12221.16369.1028410.188
7/9/2005 9:15:56 AM|SETI@home|Started download of 01no03aa.12221.16369.1028410.138
7/9/2005 9:16:14 AM|SETI@home|Finished download of 01no03aa.12221.16369.1028410.188
7/9/2005 9:16:14 AM|SETI@home|Throughput 21595 bytes/sec
7/9/2005 9:16:14 AM|SETI@home|Finished download of 01no03aa.12221.16369.1028410.138
7/9/2005 9:16:14 AM|SETI@home|Throughput 21268 bytes/sec
7/9/2005 9:16:14 AM|SETI@home|Started download of 01no03aa.12221.16369.1028410.177
7/9/2005 9:16:14 AM|SETI@home|Started download of 01no03aa.12221.16369.1028410.205

The code that decrements is in the Transitioner. SO, I had a LONG string of no returns for several days at the turn of the month. So, the count is decremented for each one of those that is transitioned as expired.

In theory, the fact that you had a long string of success should mitigate that down check, but, in fact, you are capped at 100 (or what ever the project uses) per CPU (max 4) per day ... so, the PowerMac has a "real" lower limit of 2 peer day ... as the remainder of the string of bad results are processed out and I continue to return good results, well that number should recover (though I have not found the place where it increases.

So, since we are all running multiple projects it is not that big of a deal, now is it? :)

---

Venus & Mars.

If i remember correctly the "max WU/day" will double every time you return a result on time, up to the Max of 100/day.
You are now on 8 a day for the 3Ghz machine, and 2 for the 2.6Ghz.

8 results returned successfully will put you back to 100/day, once they are all in.

2 returned will get you to 8 tomorrow, and then back to 100 the next day.

(But I guess you allready know this.)

Not too long to wait, but iritating, none the less...

---

Foamy is "Lord and Master".
(Oh, + some Classic WUs too.)

On mine and my wifes P4 HT machines, which mostly crunch Seti, I noticed this in the BOINC log this morning,

7/9/2005 6:31:06 AM|SETI@home|Message from server: No work sent
7/9/2005 6:31:06 AM|SETI@home|Message from server: (reached daily quota of 4 results)

Wifes computer has same message, then I went to the computer summary pages:
P4b 3.06
and
p4c 2.6 and saw the 2/day per CPU for these two hungry seti crunchers.

Any ideas on how to fix this?

If you look back to work issued to you on June 25th, there are several results that you never returned. When they timed-out, your quota go chopped.
You don't need do anything to fix this, except return some good results.
Every time you return a good resukt, your quota will double again 1,2,4,8,16 etc. Very quickly you'll be back to a quota of 100.
Took about 10hrs to sort for me (8 results).

---

Yeah, I am back to 4, but I have a lot of bad WU that will have to time out, so, I will be bouncing up and down for at least the next week ...

---

Yeah, I am back to 4, but I have a lot of bad WU that will have to time out, so, I will be bouncing up and down for at least the next week ...

If you had lots of errors, I can see the bouncy thing. But having had only around 4 errors, two weeks ago and immediately penalizing so I have 1 unit a day? It's a tad harsh.

Do you know how long it'll take me to recover? At least 8 days, if I run Seti only. Too bad I've got 7 other projects attached. ;)

---

check this out
Here is am example of the validater error?
Wu sent out on the 4 July the file was uploaded on completion but the 'ready to report' was not return [because of the system was down due to mantenance] untill the 9 July and report Validate state Result was reported too late to validate, but the "Report deadline 18 Jul 2005 18:38:22 UTC".
Is this just an Alpha project problem or all projects.
Maybe the report should be sent with the uploading of the results.

http://isaac.ssl.berkeley.edu/alpha/result.php?resultid=23779


Result ID 23779
Name wu_1119511766_769_2
Workunit 3630
Created 4 Jul 2005 7:23:02 UTC
Sent 4 Jul 2005 18:38:22 UTC
Received 9 Jul 2005 8:59:46 UTC
Server state Over
Outcome Success
Client state Done
Exit status 0 (0x0)
Computer ID 441
Report deadline 18 Jul 2005 18:38:22 UTC
CPU time 10577.53125
stderr out
4.70
Validate state Result was reported too late to validate
Claimed credit 27.5310917142842
Granted credit 0
application version 4.18

---

Fred
BOINC Alpha, BOINC Beta, LHC Alpha, Einstein Alpha

The daily quota decreases really fast. Here's an example:

http://setiweb.ssl.berkeley.edu/show_host_detail.php?hostid=332174

A home computer that isn't on very much with ISDN dial-up net access. I missed deadline of two work units recently. The daily quota was 100/day previously and it's 4 now.

Well, to get this number, one would have to take square root of previous daily quota for each invalid result: 10=sqrt(100), 4 is more or less equal to 3.16=sqrt(10) ...

---

Metod ...