Looks like the splitters have all run out of AP workunits. As a result, downloads are taking less bandwidth hence the dip in the cricket graph. Everything else OK though, plenty of MB WUs available and uploads and reporting still going through OK

---

Looks like the splitters have all run out of AP workunits. As a result, downloads are taking less bandwidth hence the dip in the cricket graph.

Nope- there was a problem for a few hours there where work wasn't being allocated when requested, but it appears to have sorted itself out for now.

---

Grant
Darwin NT

Looks like the splitters have all run out of AP workunits. As a result, downloads are taking less bandwidth hence the dip in the cricket graph.

Nope- there was a problem for a few hours there where work wasn't being allocated when requested, but it appears to have sorted itself out for now.

I think that the problem was more with part of the connection going dickie again than the servers as as soon as I selected another proxy things cleared up real quickly.

Cheers.

---

Never mind SETI problems, a very happy new year to all the people here from the Greenwich Meridian :).

Looks like the splitters have all run out of AP workunits. As a result, downloads are taking less bandwidth hence the dip in the cricket graph.

Nope- there was a problem for a few hours there where work wasn't being allocated when requested, but it appears to have sorted itself out for now.

I think that the problem was more with part of the connection going dickie again than the servers as as soon as I selected another proxy things cleared up real quickly.

Co-incidence.
If you look at the graphs you can see that both uploads & downloads went goofy.
Also the connection you use has no effect on whether work is allocated or not. I had no problems with Scheduler requests or uploads, but i was unable to download anything because nothing was allocacted when requested- just "Project has no tasks available" messages. Those are system related mesages, not network.

---

Grant
Darwin NT

Looks like the splitters have all run out of AP workunits. As a result, downloads are taking less bandwidth hence the dip in the cricket graph.

Nope- there was a problem for a few hours there where work wasn't being allocated when requested, but it appears to have sorted itself out for now.

I think that the problem was more with part of the connection going dickie again than the servers as as soon as I selected another proxy things cleared up real quickly.

Co-incidence.
If you look at the graphs you can see that both uploads & downloads went goofy.
Also the connection you use has no effect on whether work is allocated or not. I had no problems with Scheduler requests or uploads, but i was unable to download anything because nothing was allocacted when requested- just "Project has no tasks available" messages. Those are system related mesages, not network.

I know that it went goofy but as I said before, as soon I changed back to using proxies the problems stopped for me even though the graphs stayed goofy for a few hours after that but during that time I was uploading, reporting and downloading as usual using proxies (I also use a different proxy for each rig).

Cheers.

---

Looks like the splitters have all run out of AP workunits. As a result, downloads are taking less bandwidth hence the dip in the cricket graph.

Nope- there was a problem for a few hours there where work wasn't being allocated when requested, but it appears to have sorted itself out for now.

I think that the problem was more with part of the connection going dickie again than the servers as as soon as I selected another proxy things cleared up real quickly.

Co-incidence.
If you look at the graphs you can see that both uploads & downloads went goofy.
Also the connection you use has no effect on whether work is allocated or not. I had no problems with Scheduler requests or uploads, but i was unable to download anything because nothing was allocacted when requested- just "Project has no tasks available" messages. Those are system related mesages, not network.

I know that it went goofy but as I said before, as soon I changed back to using proxies the problems stopped for me even though the graphs stayed goofy for a few hours after that but during that time I was uploading, reporting and downloading as usual using proxies (I also use a different proxy for each rig).

Cheers.

Every morning around 8 or 9, I see 3 hosts, all with a large DLoad qeue and some 8
hours, before a retry. But 1 push almost everytime is enough to download the qeue, at 10-35Kbit and some additional work.
Almost Standard Procedure for 3 hosts, 2 CUDA/OpenCL* (GTX470*&480) and 1 (CAL)ATI OpenCL, 2x5870GPUs;CPU is an I7-2600(stock;DDR3-1333)

Also use a small cache, why big, you'll have a hardtime filling it, depending on which version of BOINC, 6.10.60 is more "consistent in getting work" and 6.12.34,
if you let it run, does supply you enough work, although no cache is build.
First In---> First Out,(FIFO) .
The use of a Proxy, shouldn't be necessary, but can depend on a lot of reasons, why
you have to use them.
I still have a 'FIXED' IP adress and a 'SmartModemRouter', it operates with an embedded version of *NUX/NIX. (As does my Digital TV STB, only uses different Coding/DECoding algoritmes)!

Two problems, Banwidth and Telescope time, very expensive, so SETI@home
"piggi-backs" and so changes position.
Anotherthing, when looking at the date of the work Result 2239662802, is quite Up to Date.
(A 'crunching farm' near Arecibo or a WLAN Transmitter to the Berkeley Lab!?).

Here, it's already 3 1/2 hours 2012, wishing you the best of health, bright future, opportunities, luck........

---

AP's may be being split but, I dont think we are going to get many.

SLWS010
1/1/2012 21:11:39 Requesting new tasks for CPU
1/1/2012 21:12:49 Scheduler request failed: Failure when receiving data from the peer
1/1/2012 21:12:50 Project communication failed: attempting access to reference site
1/1/2012 21:12:51 Internet access OK - project servers may be temporarily down.
1/1/2012 21:12:58 update requested by user
1/1/2012 21:12:59 Sending scheduler request: Requested by user.
1/1/2012 21:12:59 Requesting new tasks for CPU
1/1/2012 21:13:21 Scheduler request failed: Failure when receiving data from the peer
1/1/2012 21:13:22 Project communication failed: attempting access to reference site
1/1/2012 21:13:23 Internet access OK - project servers may be temporarily down.
1/1/2012 21:13:41 update requested by user
1/1/2012 21:13:46 Sending scheduler request: Requested by user.
1/1/2012 21:13:46 Requesting new tasks for CPU
1/1/2012 21:14:10 Project communication failed: attempting access to reference site
1/1/2012 21:14:10 Scheduler request failed: Failure when receiving data from the peer
1/1/2012 21:14:11 Internet access OK - project servers may be temporarily down.

---

Dave

I've got no problems contacting the Scheduler, it just doesn't want to give me any work.
"Project has no tasks available" is the usual response.

---

Grant
Darwin NT

I'm getting none available also.

I have gotten a couple of AP's.

---

Dave

I just got this

02/01/2012 06:12:17 SETI@home Scheduler request completed: got 0 new tasks
02/01/2012 06:12:17 SETI@home Message from server: No tasks sent
02/01/2012 06:12:17 SETI@home Message from server: No tasks are available for Astropulse v505

john3760

I got this a few minutes ago:

2012-01-02 00:55:41|SETI@home|Sending scheduler request: To fetch work. Requesting 179988 seconds of work, reporting 0 completed tasks
2012-01-02 00:55:46|SETI@home|Scheduler request succeeded: got 2 new tasks
2012-01-02 00:55:49|SETI@home|Started download of ap_15oc11ac_B1_P1_00213_20120101_29547.wu
2012-01-02 00:55:49|SETI@home|Started download of ap_18oc11ag_B0_P0_00231_20120101_23563.wu

GMT-5.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

Its looking good, sitting on the GPU limits and not ONE shorty in sight.

---

Kevin

Today I am getting 05/01/2012 07:10:47 SETI@home Scheduler request failed: Couldn't connect to server
05/01/2012 07:10:49 Internet access OK - project servers may be temporarily down.
Yet everything seems to be ok so what is ging on?

---

Today I am getting 05/01/2012 07:10:47 SETI@home Scheduler request failed: Couldn't connect to server
05/01/2012 07:10:49 Internet access OK - project servers may be temporarily down.
Yet everything seems to be ok so what is ging on?

Looking at the log on my machine that keeps asking for work ever 5ish minutes I see several of those messages the past few hours.

---

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

Still problems with the Scheduler- either "Project has no tasks avaiable" message or "Scheduler request failed- Couldn't connect to server" error.

---

Grant
Darwin NT

I am getting "no tasks available" so we must look for more squid and fish. Here fishy here fishy.

---

Still problems with the Scheduler- either "Project has no tasks avaiable" message or "Scheduler request failed- Couldn't connect to server" error.

Plus "HTTP internal server error" is one I'm getting a lot, both via proxy and direct.

T.A.

I'm sorry to tell you guys but as usual my 3 are still bouncing off the limits. Now and again I am getting the internal http error or no work available but when I do get work they download very quickly (50-120KBps) plus I havn't needed to use a proxy since the last outage.

Cheers.

---

I'm sorry to tell you guys but as usual my 3 are still bouncing off the limits. Now and again I am getting the internal http error or no work available but when I do get work they download very quickly (50-120KBps) plus I havn't needed to use a proxy since the last outage.

Cheers.

Gloating again ?? ;-)

I will agree that when you get a unit the download speed is impressive, the trouble I'm only getting one every 10 tries on 5 machines. Things are as bad via proxy as they are direct. It's just that via proxy I get "no tasks sent" or "no tasks available", direct I get HTTP or server errors......

T.A.