It is interesting to note that during the 7 hours since the outage, when the validators went off, 5,943 units have joined tha validator queue. Not a lot, but some.

I did notice that seven of my units were received May 16 so a few of the results are getting through. But my caches are full of results, some with deadlines of tomorrow. I sure hope that deadlines will be adjusted appropriately!!!

---

Deadlines don't matter as long as the validators are down. This is probably why they shut them off in the first place and most likely they won't turn them back on until the current torrent of hosts trying reach the project drops back down to a more or less normal level.

The corollary to that is don't be expecting any credit to get granted and your number of results shown as pending will most likely swell considerably as well. In addition, they may or may not appear on the Pending Credit page, most will probably be stuck at 'Checked, but no consesus' Validate State.

Alinator

Deadlines don't matter as long as the validators are down.

I'm holding back on commenting directly for about 17 hours. This is a placeholder ;-)

I'm holding back on commenting directly for about 17 hours. This is a placeholder ;-)

The only qualifier is if the WU had a quorum formed before the validators were turned off you are hosed. However the assimilators being off gives the project the chance to 'manually' fix that, since the WU's won't transition through to the purge state and go poof.

Alinator

I'm holding back on commenting directly for about 17 hours. This is a placeholder ;-)

The only qualifier is if the WU had a quorum formed before the validators were turned off you are hosed. However the assimilators being off gives the project the chance to 'manually' fix that, since the WU's won't transition through to the purge state and go poof.

Alinator

I'm not disagreeing with any of that... Like I said, 17 hours... Dontcha love the suspense? :-)

I'm holding back on commenting directly for about 17 hours. This is a placeholder ;-)

The only qualifier is if the WU had a quorum formed before the validators were turned off you are hosed. However the assimilators being off gives the project the chance to 'manually' fix that, since the WU's won't transition through to the purge state and go poof.

Alinator

Now they just don't seem to be accepting completed WU's...Most of my uploads now say 100% yet are in retry mode. Seems they fix that and a lot of the backlog would be gone.

---

Official Abuser of Boinc Buttons...
And no good credit hound!

I'm not disagreeing with any of that... Like I said, 17 hours... Dontcha love the suspense? :-)

LOL...

Sounds like the plot for 'SAH/BOINC, the Movie (or How I learned to stop worrying about RAC and love the outage)'! :-D

Alinator

I'm not disagreeing with any of that... Like I said, 17 hours... Dontcha love the suspense? :-)

LOL...

Sounds like the plot for 'SAH/BOINC, the Movie (or How I learned to stop worrying about RAC and love the outage)'! :-D

Alinator

Thanks...I needed that, ROFL!

---

Official Abuser of Boinc Buttons...
And no good credit hound!

Yep, ever since the spike-up in network traffic, I was able to upload about 80 WUs over the course of about 4 hours. I still have about 10 trying, but the upload/download server was off like recently. Now if I could only download some work...

---

Dublin, California
Team: SETI.USA

Thanks...I needed that, ROFL!

Then it served its purpose! :-)

BTW, when the upload goes to 100%, it just means that the host was able to send the whole file OK, but the connection got dropped before the UL server could send the ACK for it back to the host. That's why you may see some uploads refused the next time around, they got there so the refusal should be treated by BOINC as the ACK, and the CC should transition the WU to 'Ready to Report'.

Alinator

Thanks...I needed that, ROFL!

Then it served its purpose! :-)

BTW, when the upload goes to 100%, it just means that the host was able to send the whole file OK, but the connection got dropped before the UL server could send the ACK for it back to the host. That's why you may see some uploads refused the next time around, they got there so the refusal should be treated by BOINC as the ACK, and the CC should transition the WU to 'Ready to Report'.

Alinator

I've gotten 4 of those 100%, But nothing but plenty of Retries so far. :( But I'll keep watching as I think It's slowly being fixed. :)

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

Thanks...I needed that, ROFL!

Then it served its purpose! :-)

BTW, when the upload goes to 100%, it just means that the host was able to send the whole file OK, but the connection got dropped before the UL server could send the ACK for it back to the host. That's why you may see some uploads refused the next time around, they got there so the refusal should be treated by BOINC as the ACK, and the CC should transition the WU to 'Ready to Report'.

Alinator

I've gotten 4 of those 100%, But nothing but plenty of Retries so far. :( But I'll keep watching as I think It's slowly being fixed. :)

I've got some gloss paint, on doors etc, you could watch. If you need a life. LOL

Andy

P.S. Therefore kitchen is out of bounds, so you'll have to bring your own beer.

Thanks...I needed that, ROFL!

Then it served its purpose! :-)

BTW, when the upload goes to 100%, it just means that the host was able to send the whole file OK, but the connection got dropped before the UL server could send the ACK for it back to the host. That's why you may see some uploads refused the next time around, they got there so the refusal should be treated by BOINC as the ACK, and the CC should transition the WU to 'Ready to Report'.

Alinator

I've gotten 4 of those 100%, But nothing but plenty of Retries so far. :( But I'll keep watching as I think It's slowly being fixed. :)

I've got some gloss paint, on doors etc, you could watch. If you need a life. LOL

Andy

P.S. Therefore kitchen is out of bounds, so you'll have to bring your own beer.

Life? What's that? ;)
I'd just as much watch the traffic go by on the Freeway outside.

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

I've uploaded 5 WU's in the past 3 days....

---

In the past few minutes i've uploaded 3 wu's, slowly but it works. But i can not find them on my results ??? Is this good or not...i do not know...just wait and see. But it look that things getting better, i hope.

Hi everybody,

I also have problems with UpLoad, like veryone.
Only at me it are now more than 1,200 WU waiting for UL !!!
Some are already out the deadline !!!

Can someone from the team answer us or post a message about what shall happen
on the outdated reports ???

It is stupid to dowload WU if there are not validated !!!
The only result will be a surcharge of UL tentative.

Please, Matt, make a break and explain us. When we will know, we also can
have and take the correct attitude to help all the servers.

I am sure you and tyhe team do the best, but INFORM US !!!!

---

In the last hour all mine have uploaded, but request for work and reporting, has internal server error.

Andy

P.S. Paint brushes now cleaned.

so long the validators are of you can stil report late results
i myself just got all my results uploaded so i am out of the loop

Hi everybody,

I also have problems with UpLoad, like veryone.
Only at me it are now more than 1,200 WU waiting for UL !!!
Some are already out the deadline !!!

Can someone from the team answer us or post a message about what shall happen
on the outdated reports ???

It is stupid to dowload WU if there are not validated !!!
The only result will be a surcharge of UL tentative.

Please, Matt, make a break and explain us. When we will know, we also can
have and take the correct attitude to help all the servers.

I am sure you and tyhe team do the best, but INFORM US !!!!

---

In the last hour all mine have uploaded, but request for work and reporting, has internal server error.

Same here, or "no work"

Wed May 16 13:00:33 2007|SETI@home|Requesting 4147200 seconds of new work, and reporting 11 completed tasks
Wed May 16 13:01:23 2007|SETI@home|Scheduler RPC succeeded [server version 509]
Wed May 16 13:01:23 2007|SETI@home|Deferring communication for 11 sec
Wed May 16 13:01:23 2007|SETI@home|Reason: requested by project
Wed May 16 13:01:23 2007|SETI@home|Deferring communication for 1 min 0 sec
Wed May 16 13:01:23 2007|SETI@home|Reason: no work from project
Wed May 16 13:02:23 2007|SETI@home|Sending scheduler request: To fetch work
Wed May 16 13:02:23 2007|SETI@home|Requesting 4147200 seconds of new work
Wed May 16 13:04:23 2007|SETI@home|Scheduler request failed: HTTP internal server error
Wed May 16 13:04:23 2007|SETI@home|Deferring communication for 1 min 0 sec
Wed May 16 13:04:23 2007|SETI@home|Reason: scheduler request failed

---

Dublin, California
Team: SETI.USA