Now what's up with this? S@h has been saying this for a week or so now, while E@h is crunching merrily on my FC2 server...

Does anyone know why?

---

Here's the full text:

[SETI@home] Message from server: No work sent (daily quota of 1 WU reached)

---

> Here's the full text:
>
> [SETI@home] Message from server: No work sent (daily quota of 1 WU reached)
>
How are yor preferences set? Has your server in fact done 1 WU in a day?.

---

> How are yor preferences set? Has your server in fact done 1 WU in a day?.

I can find nothing wrong with the preferences, but here's a cut-and-paste of my WU log from the machine:

Result ID Work unit ID Sent Time reported or deadline Server state Outcome Client state CPU time (sec) claimed credit granted credit

50346461 12267360 6 Apr 2005 7:47:16 UTC 6 Apr 2005 7:57:19 UTC Over Client error Computing 0.00 0.00 ---
50012318 12193405 5 Apr 2005 7:43:36 UTC 5 Apr 2005 7:53:38 UTC Over Client error Computing 0.00 0.00 ---
49741487 12132305 4 Apr 2005 9:29:36 UTC 4 Apr 2005 9:39:38 UTC Over Client error Computing 0.00 0.00 ---

From when I understand from this is that I'm give a 10-minute deadline, and all the WU's are returned too late (well duh, my XP3200 is fast, but not THAT fast).

---

> From when I understand from this is that I'm give a 10-minute deadline, and
> all the WU's are returned too late (well duh, my XP3200 is fast, but not THAT
> fast).

Ugh, it was a bit early in the morning when I wrote this apparently...

From WHAT I understand from this is that I'm given a 10-minute deadline, and all the WU's are returned too late (well duh, my XP3200 is fast, but not THAT fast).

Everything works fine on my Windows client.

I reset the S@h project, downloaded the AMD Athlon XP optimized BOINC client (from a site I found linked in this forum), but it's still complaining...

---

From what I have read elsewhere in these forums, a machine that returns client errors (in your case, process exited with code 13), the Seti/BOINC servers will reduce bit by bit down to one per day the amount of work they will release to your machine. It will stay that way until you return a good result.

Maybe you should not use the optimized client, and use the current linux 4.19 release instead? And, once again, reset the Seti/BOINC project. It could also be that you have a hardware issue, perhaps overclocking or some other item that the Seti Client doesn't like.

---

> Maybe you should not use the optimized client, and use the current linux 4.19
> release instead? And, once again, reset the Seti/BOINC project. It could
> also be that you have a hardware issue, perhaps overclocking or some other
> item that the Seti Client doesn't like.

Let's see, I used the original BOINC client when this started, so that's not the problem.
I can always reset S@h again, but I doubt it will help.
The PC should be fine, since BOINC ran perfectly on the exact same hardware for months before the problem started.

I think I'm going to terminate BOINC and leave it off for 24-36 hours, then restart it and keep an eye on it untill I see where things fail.

---

> I think I'm going to terminate BOINC and leave it off for 24-36 hours, then
> restart it and keep an eye on it untill I see where things fail.

Well, I'm "closing" this thread now by announcing the following result:

I detached S@h and E@h on my Linux-box, re-attached CP.net (to test wether it was the BOINC client or not), left things to simmer for appx. 36 hrs and the re-attached S@h again... The AMD Atlon XP-optimized client worked fine, and so does S@h too. My conclution is that there probably was a problem of some sort on my side that resulted in a continuous stream of errors reported to S@h, eventually reducing my S@h crunching to zero. Detatching the project (thus forcing my BOINC client to download the S@h client again) and preventing any communication with the S@h project for 24h+ seems to have restored a normal cycle of communication with the S@h project.

My Wintendo client is happily crunching S@h and E@h, my Linux client is happily crunching S@h and CP.net, and I'm just plain happy... :)

---