The scheduler is timing out unless you are reporting around 25 at a time and have No New Tasks set.

Even reporting a couple of WUs & NNT the Scheduler still frequently times out.
It appears to timeout more often when requesting work, but that's like saying it only times out 95 times out of 100 instead of 99 times out of 100 if you set it to NNT.
It's pretty screwed at the moment.Grant
Darwin NT

Besides the slow up- and downloads, my three Linux pc's report just fine and they get new work as well.
My Windows 7 pc's will only report when I set NNT. Any attempt to get new work on the Windows pc's results in a server timeout message.

It would appear that this problem might be difficult for the SETI staff to notice quickly at their end, especially since the traffic appears to the monitoring software to be moving beautifully at the moment and the staff is often too busy to follow the threads too closely.

Since I have not seen anyone mention it yet (of course, I can't follow everything), I was wondering if anyone has had an opportunity to notify the staff of this seriously escalating problem?

I simply set "no new tasks" and it reported no mater how many tasks I had ready to report. Of course I'm not getting any new tasks and Ghost Detector is reporting 40 that I hopefully get when the storm is over and I get allow new tasks again.

Let me elaborate as to what I'm seeing.

Uploading is fine. No new tasks since early Nov 1st, 9-10z and those were resent "lost" units.

When I'm allowing new tasks, the log says it's timing out and the units listed as ready to report still appear on my tasks tab, however when I check my tasks online, they are listed as reported and validated. However since the reporting process has "timed out" from the client's point of view, it is retried after backoff.

When I disallow new tasks, the log reports success and the "ready to report" tasks listed in my tasks tab are removed.

I would like to stress that I'm seeing that my uploaded tasks are being reported and processed and it's just the acknowledgement that is not being sent to the client. That and no downloads in over 24 hours when new tasks are allowed."Life is just nature's way of keeping meat fresh." - The Doctor

All of my six machines are in trouble. No work and not able to report work completed units. I do not understand why these type problems continue to occur. It seems to always happen going into a weekend and takes till the next Wednesday to straighten out.

I have moved my buffers to 5 days to try and ride out these glitches. I have already worked through that data and I am now down. When we finally get some units I guess I will move my Buffers even higher.

I looked at the tasks from all of your active computers Dannis and you have been reporting and they are processed up on the server, it's just that the server acknowledging that isn't being sent back down to the client so the client still shows them as ready to report and will retry reporting them. They will be acknowledged as report right now only if you select "No New Tasks" on the projects tab.

Of course we aren't getting any new tasks either way but if you want to see all those "ready to report" tasks listed on the tasks tab of your client to vanish and eliminate all the retries, "No New Tasks" is the way to do it. It's not like either of us has seen any new tasks downloaded in the last 24+ hours (again gleaned from looking at your computer's tasks)."Life is just nature's way of keeping meat fresh." - The Doctor