I was just checking the same thing. Across 7 machines, the server thinks I've got more than 1500 tasks in progress. But I've actually got 91 - and almost all of those are because two machines have started getting lost tasks resent within the last hour.

I have one computer that has just over 400 tasks on it while the server thinks it has just short of 5,200........
It can not connect to the server and should I get that many tasks I will have to abort most of them because they will never finish in time. I do keep trying to connect but am unable to.
I guess there is nothing I can do about this right now.
SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours

Shortly the server will break from the ghost storm it is creating. It will run out of result storage space. Perhaps then Eric and or Jeff will take action. With Matt out I hope they have notes on the last time this happened.

The tasks in progress is now showing 592 with only 1 completed completed task on the machine. Is there something I need to do? Or do I just sit back and wait for it to correct itself? this machine has only received 2 tasks in the last 18 hours.

Wow..within minutes of posting this the machine actually got 20 "resent lost tasks" Hoping this is a sign of things to come,

After getting the 20 resent task crunched and reported have not got anything else. since it appears the lost tasks are all for my GPU I set it to only use the gpu. however, instead of getting lost tasks resent it appears to try to send new tasks and the number of lost tasks is up to 701.

What if some of us just suspend network contact with the seti server for maybe 12hours?

It could help, since the server is hamerred with 1300queries/second.

Most of witch are the same computers trying again an again to report or receive new tasks desesperately?

I've gone NNT and will stay there for a day or two - have 2.75 days of CPU work and 5 days of gpu work, so I will wait it out. After my last post, I again received a new task rather than a lost task resend, so that's when I went NNT.

If you suspend network operations, you can't report completions, and some folks crunch a second project (or more).Another Fred
Support SETI@home when you search the Web with GoodSearch or shop online with GoodShop.

I was just checking the same thing. Across 7 machines, the server thinks I've got more than 1500 tasks in progress. But I've actually got 91 - and almost all of those are because two machines have started getting lost tasks resent within the last hour.

My notional list of "work in progress" has gone up from 1,500 to 2,100 in the last two hours.

Everything is getting set to NNT and staying there, until I see zero tasks ready to send AND the splitters disabled.

Anybody got any idea whether we're being haunted by Astropulse ghosts, to the same degree?

I think it's getting to the point that I need to put out an urgent APB, reluctant though I am to do so on a Sunday - just to get a lid put on the situation, until they can look at it tomorrow or Tuesday.

The question is - is stopping the MB splitters enough, or should I ask them to stop AP as well?

With splitters stopped, and no new work entering the system, we could allow work fetch and fish for resends of the work we've already supposedly got.

Anybody got any idea whether we're being haunted by Astropulse ghosts, to the same degree?

I think it's getting to the point that I need to put out an urgent APB, reluctant though I am to do so on a Sunday - just to get a lid put on the situation, until they can look at it tomorrow or Tuesday.

The question is - is stopping the MB splitters enough, or should I ask them to stop AP as well?

With splitters stopped, and no new work entering the system, we could allow work fetch and fish for resends of the work we've already supposedly got.

My vote would be to stop both. If most systems are like mine upwards of 900 tasks assigned but not received so there is plenty of work to run if we can get it.