Panic Mode On (77) Server Problems?

Mark, I noticed something last night that I think you're talking about. I reported one completed AP and the website showed it as reported, but BOINC didn't get the memo and instead.. "timeout was reached." The next report cleared it up, but every time you talk to the scheduler, your client_state has to be sent. I imagine for the faster rigs, it is probably in the >1MB range, so I agree.. wasted bandwidth for scheduler time-outs.

Kind of like cramming 16MB of data through the pipe only to have it be 100% blanked.
____________

Linux laptop uptime: 1484d 22h 42m
Ended due to UPS failure, found 14 hours after the fact

Now I have over 3000 phantom wu's up from about 2k last night. This is about 5x my normal caches size. Should I set NNT? Or just let it do its thing?

I have been monitoring my rig and have no issues.
Except Mark is partnered with me on of my inconclusives. I sure it is stuck in the upload problem.

(...) but every time you talk to the scheduler, your client_state has to be sent. I imagine for the faster rigs, it is probably in the >1MB range, so I agree.. wasted bandwidth for scheduler time-outs.

Mark, I suspect, however, that the kitties are not purring right now. ;)

By the way, I did do one thing to help alleviate the obviously gigantic mess developing between the SETI host and its clients. I suspended network activity on all my machines.

I always keep my caches maxed out to handle these emergencies, so I'm good-to-go for at least a week. It'll be awhile before any of my units time out. When the dust settles and traffic is back to normal, I'll just let my rigs report their stored results one machine at a time. :)

Maybe the last 20 hours or something no well scheduler contact. Always:

Scheduler request failed: Timeout was reached

*new tasks* was enabled.

I set *no new tasks* - and then 178 uploaded tasks were accepted from the scheduler server in a bunch (successful report).

That also worked for me, my last successful scheduler request was on the 30th, I just set 'no new tasks,' clicked 'update' and the request/report went through straight away.

I hope they can sort this Scheduler out soon. With all the shorties in the system, and the inabilty to get work on more than 1 attempt in 20, i'm going to run out of work very quickly when almost everything that does get downloaded will be done in minutes.
____________
Grant
Darwin NT.

I hope they can sort this Scheduler out soon. With all the shorties in the system, and the inabilty to get work on more than 1 attempt in 20, i'm going to run out of work very quickly when almost everything that does get downloaded will be done in minutes.

Scheduler cannot do nothing without bandwidth to send and receive.
This needs to be addressed before you folks complain about much more.

Over and out.

Scheduler cannot do nothing without bandwidth to send and receive.
This needs to be addressed before you folks complain about much more.

One wonders if the incredible volume
of incoming data (as shown by cricket graph)
is not a manifestation of the
infamous 'buffer bloat'. Rather than
really a need for more bandwidth.

Something is strange. I have zero issue with SetiBeta right now, but I can't report on main. As it is on the same communications link it isn't a link issue. It has to be an issue in the lab. Perhaps failed disk in an array?

Have had 0 tasks since Thurs morning .. haven't been able to report completions or get new work on mach xxxx033 .. have had this response for almost two days now :(

11/2/2012 4:17:19 PM | SETI@home | Reporting 410 completed tasks, requesting new tasks for CPU and ATI
11/2/2012 4:23:01 PM | SETI@home | Scheduler request failed: Timeout was reached
11/2/2012 4:23:05 PM | | Project communication failed: attempting access to reference site
11/2/2012 4:23:06 PM | | Internet access OK - project servers may be temporarily down.
11/2/2012 4:27:33 PM | SETI@home | update requested by user
11/2/2012 4:27:37 PM | SETI@home | Sending scheduler request: Requested by user.
11/2/2012 4:27:37 PM | SETI@home | Reporting 410 completed tasks, requesting new tasks for CPU and ATI
11/2/2012 4:32:57 PM | SETI@home | Scheduler request failed: Timeout was reached
11/2/2012 4:33:00 PM | | Project communication failed: attempting access to reference site
11/2/2012 4:33:01 PM | | Internet access OK - project servers may be temporarily down.

____________