Panic Mode On (78) Server Problems?

My client_state is 2.4MB in size, my sched_request_setiathome.berkeley.edu is 450kB in size. I suspect yours are a lot smaller. You're in the US, i'm a few thousand kms away.
End result- you may be able to get work, i'm lucky if i can even report work- even after 30min of endless Update clicking with No New Tasks set.

By the way ..

My machine can report uploaded results, but only if no work request simultaneously (*no new tasks* set).
Work request (also alone) don't work (Scheduler request failed: Timeout was reached).

I use BOINC V7.0.28.


* Best regards! :-) * Sutaru Tsureku, team seti.international founder. * Optimize your PC for higher RAC. * SETI@home needs your help. *
____________


>Das Deutsche Cafe. The German Cafe.<

My computer has finished and reported all tasks and I get "project has no tasks available". But according to the website there are still a number of tasks that were sent yesterday that have not been reported. I would have expected a "resent lost task" message. Has "resent lost tasks" been disabled or is just another symptom of server side problems ?

Tom

____________

By the way ..

My machine can report uploaded results, but only if no work request simultaneously (*no new tasks* set).
Work request (also alone) don't work (Scheduler request failed: Timeout was reached).

I use BOINC V7.0.28.


* Best regards! :-) * Sutaru Tsureku, team seti.international founder. * Optimize your PC for higher RAC. * SETI@home needs your help. *

Because of the way the distribution system works it is quite possible to get a "no tasks available" message when there are a lots (300,000) of tasks ready for distribution.
The distribution system works something like this - One hundred tasks are loaded into the output cache, the tasks are allocated to the next few users to request task, the tasks are now move to the delivery servers, a bit of internal house keeping is done, and the next one hundred tasks are loaded. The whole cycle takes about a second to complete, so if your request arrives just after the tasks have been allocated you have to make another attempt in a short while (and it can take a few attempts to arrive just at the right fraction of a second...)
____________
Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Don´t want to enter in some type of controversy but...

I have few relatively hungry hosts, and i was able to feed all of them at >150kpbs and don´t need to use NNT. In some of them report more than 1000 WU with the use of a proxie.

And all simultaneusly (7 hosts DL at the same time from 3 diferent ISP). Before the proxie nothing works.

So the question remains, if bandwith is the problem, why everything works fine with a proxie, for any chance the proxie uses a diferent bandwith...

It certainly looks as if there is a problem - nothing in the "ready to send" queue, plenty of tapes available to split, splitters chugging at idle.
Something in the server closet needs the delicate attention of they tyre kicker in chief. But its the wee small hours of Sunday morning in CA, so it will be a few hours before he arises from his well earned slumbers and can administer the required potion.....
____________
Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

When I connect on a work request, I'm now getting "no tasks avaiilable" on most, even though I had 150 lost tasks out there. Just got the first batch of 20, but it also included the "no tasks available" message. (

11/4/2012 4:14:48 AM Scheduler request completed: got 20 new tasks
11/4/2012 4:14:48 AM Resent lost task 09se12ac.20763.9065.140733193388045.10.10_0
(19 more of those, then:)
11/4/2012 4:14:48 AM Project has no tasks available
11/4/2012 4:14:48 AM Project requested delay of 303 seconds
etc.

I have not seen that combination of responses before. Usually doesn't try to assign new work when resending ghosts.

Like others, I can report on NNT with a limit of 50.

Rob wrote:

The distribution system works something like this - One hundred tasks are loaded into the output cache, the tasks are allocated to the next few users to request task, the tasks are now move to the delivery servers, a bit of internal house keeping is done, and the next one hundred tasks are loaded.

Scheduler seems to be assigning new work while handling lost tasks, and I have not seen that before. Earlier in the thread I said I was working on 150 lost tasks and had received the first 20. Have had more timeouts since then and just received the 2nd 20. But the total difference between the website totals and BOINCTasks counts has grown to 371, suggesting more tasks were assigned on those requests that timed out.

Must be happening to fscheel as well because the lost task count (592) exceeds the feeder amount, and mine also exceeds it.

BOINC will keep asking for work until it actually gets it, so I could easily get more than my cache setting stuck in the lost category. If I reduce my cache settings, can't get any of the lost tasks. Not sure what to do.

Edit: My lost task count contimues to cl8imb, and I just received 1 new task (not a lost task resend).
____________
Another Fred
Support SETI@home when you search the Web or shop online with GoodSearch and GoodShop

Results ready to send is now 0 and 0, and scheduler contacts to Main and Beta are going through without problem,

Claggy

Results ready to send is now 0 and 0, and scheduler contacts to Main and Beta are going through without problem,

Claggy

I have been able to report tasks using the NNT trick. That responds pretty quickly, and the tasks disappear from my local computer, and show up on the web in a few seconds.

It seems that GETTING new tasks is the issue right now. The web page claims I should have 160 some tasks, but the local computer shows 28. Occasionally, I actually get something, most of the successful ones seem to be the resending 20 tasks variety.
____________