My two Quad Q9550 are overclocked to 3.8 gig and each has a 260/216 video card they are overclocked as well. All systems and video cards are optimized also.

I get the No work available response and the exceeds the 500 per day quota. But I am completing in excess of 700 work units a day as a matter of fact I uploaded 721 work units in one shot in under 24 hours and still received the no work reply. Using Boinc 6.2.20

---

Come and Visit Us at
BBR TeamStarFire


****My 9th year of Seti****A Founding Member of the Original Seti Team Starfire at Broadband Reports.com ****

My two Quad Q9550 are overclocked to 3.8 gig and each has a 260/216 video card they are overclocked as well. All systems and video cards are optimized also.

I get the No work available response and the exceeds the 500 per day quota. But I am completing in excess of 700 work units a day as a matter of fact I uploaded 721 work units in one shot in under 24 hours and still received the no work reply. Using Boinc 6.2.20

Taking a quick look, it looks like you have a ton of error returns on a couple of your machines. I suspect you have over clocked too much.

FYI BOINC will limit work when there are too many error returns.

---

My two Quad Q9550 are overclocked to 3.8 gig and each has a 260/216 video card they are overclocked as well. All systems and video cards are optimized also.

I get the No work available response and the exceeds the 500 per day quota. But I am completing in excess of 700 work units a day as a matter of fact I uploaded 721 work units in one shot in under 24 hours and still received the no work reply. Using Boinc 6.2.20

Taking a quick look, it looks like you have a ton of error returns on a couple of your machines. I suspect you have over clocked too much.

FYI BOINC will limit work when there are too many error returns.

5/2/2009 12:57:16 AM SETI@home Message from server: No work sent
5/2/2009 12:57:16 AM SETI@home Message from server: No work is available for SETI@home Enhanced
5/2/2009 12:57:16 AM SETI@home Message from server: No work is available for Astropulse
5/2/2009 12:57:16 AM SETI@home Message from server: (reached daily quota of 495 results)
5/2/2009 12:57:16 AM SETI@home Message from server: (Project has no jobs available)



They are the rejects from Raistmer's opp Killing VLAR CUDA workunits.

Computer error for a Cuda WU.

CPU time 0.515625
stderr out <core_client_version>6.6.20</core_client_version>
<![CDATA[
<message>
- exit code -6 (0xfffffffa)
</message>
<stderr_txt>

VLAR WU (AR: 0.132888 )detected... autokill initialised
SETI@home error -6 Bad workunit header

File: ..\worker.cpp
Line: 144


</stderr_txt>
]]>


I posted about them earlier and was informed about the Kill command.

What would cause this error?

---

Come and Visit Us at
BBR TeamStarFire


****My 9th year of Seti****A Founding Member of the Original Seti Team Starfire at Broadband Reports.com ****

My two Quad Q9550 are overclocked to 3.8 gig and each has a 260/216 video card they are overclocked as well. All systems and video cards are optimized also.

I get the No work available response and the exceeds the 500 per day quota. But I am completing in excess of 700 work units a day as a matter of fact I uploaded 721 work units in one shot in under 24 hours and still received the no work reply. Using Boinc 6.2.20

You must have had a bucket-load of "shorties" to crunch through that volume in 24 hours; this can't happen regularly, surely?
I'd suggest enabling Astropulse (optimised, of course). That will cut down the numbers and increase the RAC (if the latter has any relevance).

F.

---

Actually you didn't 'complete' 700 work units, maybe 1/2 of those were errored out and returned after 1 sec of crunching ( autokill of troublesome VLAR work units it would seem)

The BOINC system is working as designed to prevent a rouge PC from going haywire and hogging / aborting tens of thousands of work units and the resulting bandwidth.

It's not the systems fault that YOUR PC decided to abort and return 1/2 the work units uncrunched, and then got restricted on new work untis. It's supposed to do that.

In the overall scheme of things it's not a problem for you either as your cache will refill as it gets a normal mix of work units. 200-300 per day would be the normal turnover for your rig, and well within your 500 limit.

Ian

Actually you didn't 'complete' 700 work units, maybe 1/2 of those were errored out and returned after 1 sec of crunching ( autokill of troublesome VLAR work units it would seem)

The BOINC system is working as designed to prevent a rouge PC from going haywire and hogging / aborting tens of thousands of work units and the resulting bandwidth.

It's not the systems fault that YOUR PC decided to abort and return 1/2 the work units uncrunched, and then got restricted on new work untis. It's supposed to do that.

In the overall scheme of things it's not a problem for you either as your cache will refill as it gets a normal mix of work units. 200-300 per day would be the normal turnover for your rig, and well within your 500 limit.

Ian

Ahhh... Why didn't I think of the obvious explanation!!

F.

---

Thanks for the replies guys I mis-spoke it should of said that there were 721 returns reported that day not that it completes 721 units a day.

Sorry for the wrong info.

---

Come and Visit Us at
BBR TeamStarFire


****My 9th year of Seti****A Founding Member of the Original Seti Team Starfire at Broadband Reports.com ****