Ready-to-send = 0 so that's it till at least opening time.
Only resends till then.

---

Grant
Darwin NT

*Prepare for a crash landing Mr. Worf."

"Saucer separated"

*Prepare for a crash landing Mr. Worf."

. . It must be nearly time for the maintenance outage, the system is in limbo ...

. . Lately every week just before the maintenance period there is a problem getting work ...

Stephen

:(

I just sent the word out about the splitters, but of course it's only 5:27AM in Berkeley.
Meow.

---

"Time is simply the mechanism that keeps everything from happening all at once."

it is after 7am in California now.

On the bright side the db purge numbers are nice and low, and there are over 600K resends ready for assimilation.

it is after 7am in California now.

On the bright side the db purge numbers are nice and low, and there are over 600K resends ready for assimilation.

I don't think these 600K are resends. Validators still seem to be working and resends are taking place (received 4 of them a little while ago ...).

Tom

I don't think these 600K are resends. Validators still seem to be working and resends are taking place (received 4 of them a little while ago ...).

Tom

interesting. My guess had been that AP resends were still happening but that s@h resends were not. The files being split hadn't moved (assuming we are seeing current info), and the "Results returned and awaiting validation" had increased (and I can see that my completed WUs are being validated just fine), so I assumed that resends were getting stuck in the assimilation phase and that Vader or Georgem had decided to take a vacation.

The other option is that splitting has been happening at a VERY slow rate and getting stuck at assimilation.

Thanks for the extra info. It gives me something to ponder while I wait...

edit to add more thoughts. Since some WUs are making it to the RTS . I'm going to guess Georgem crapped out and Vader can manage a small amount of assimilation to give us some WUs, but not enough to keep the system running well.

Strapping in and getting ready to crash now, wondering if some "Scotty" will come in to work and save us at last minute.

Eric looked into things, and thinks he has things working again.
We shall see.
Meowmeowmeow!

---

"Time is simply the mechanism that keeps everything from happening all at once."

SSP says not yet

---

SSP says not yet

Now it does.
Meow!

---

"Time is simply the mechanism that keeps everything from happening all at once."

Yep

---

Just got 74 new task on one computer.

---

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours

would this explain why i have one computer that has run dry? i rebooted it, but it is not downloading anything new :(

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

The system was just in Maintenance mode for a few minutes, but it is back now.
Check your retry times, and try a manual update.

All my hosts must have hit the servers while they were in Maintenance mode. They got forced into a 50 minute backoff. Now they are reporting the work they have finished but unfortunately getting nothing in return.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

I'm having some weirdness in my personal "remaining time".

usually the blc22 are estimated to take 3:08:53

but I got 10 that are blc22_2bit_guppi_58340_48827_HIP4845_.... that have an estimated time of 20:28:09

seems a bit ridiculous as not even APs take that long. anyone else notice this??
fills up my cache level, so I can't get anymore WUs.

edit - nevermind - I aborted all but one of them so I wasn't short on WUs before tomorrow's outage. Not sure why they gave such a bad estimate.

2nd edit - looks like mac got a new version of s@h today.

edit - nevermind - I aborted all but one of them so I wasn't short on WUs before tomorrow's outage. Not sure why they gave such a bad estimate.

2nd edit - looks like mac got a new version of s@h today.

And that was why they had a high estimate for the compute time- The new application needs to run to completion several WUs for the estimates to become more accurate, then as it processes more WUs it will refine the estimate further till it's pretty close to accurate.
Aborting them won't have helped that along.

Best bet when something like that occurs in the future- let the WUs run, and see how quickly the estimated time reduces.

---

Grant
Darwin NT

edit - nevermind - I aborted all but one of them so I wasn't short on WUs before tomorrow's outage. Not sure why they gave such a bad estimate.

2nd edit - looks like mac got a new version of s@h today.

And that was why they had a high estimate for the compute time- The new application needs to run to completion several WUs for the estimates to become more accurate, then as it processes more WUs it will refine the estimate further till it's pretty close to accurate.
Aborting them won't have helped that along.

Best bet when something like that occurs in the future- let the WUs run, and see how quickly the estimated time reduces.

After I aborted most of them, I got new WUs with reasonable times (around 4 hours and not 20 hours), so all is ok. I kept one of the WUs since I was the 4th person, and I wanted to make sure it got a good result without passing it to a 5th person.

Grant was right. I was wrong. I didn't know that over time that the times would change. Thanks for all those who continue to respond to my silly posts and teach me how seti works.

anyone else noticing that db purge doesn't seem to be working?? I have a longer than usual list of valid tasks that goes back longer than the usual 24ish hours. I think we are in for an outRage as the system has had hiccups this week.