3/22/2009 7:47:11 PM|SETI@home|Message from server: Completed result 03ja09ad.1633.481.16.8.219_0 refused: result already reported as success


Not seen that message before when reporting

---

3/22/2009 7:47:11 PM|SETI@home|Message from server: Completed result 03ja09ad.1633.481.16.8.219_0 refused: result already reported as success


Not seen that message before when reporting

That's nothing, really. During heavy network loads, your client reports a finished task to the server, and then the acknowledgment (ACK) from the server back to you doesn't make it through the network, because of the load, so your client tries to report it again.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

Thought it might be something simple.

Thanks for the response.

---

I'm getting this on downloads right now.

3/22/2009 9:20:28 PM SETI@home [error] File 11ja09aa.17799.14387.11.8.156 has wrong size: expected 375339, got 0
3/22/2009 9:20:28 PM SETI@home Started download of 11ja09aa.17799.14387.11.8.156
update: Something cleared, So that isn't an issue for Me now.

---

Savoir-Faire is everywhere!
The T1 Trust, T1 Class 4-4-4-4 #5550, America's First HST

The downloads are fine, but noticed that none of the four MB validators are running. My pending credits just shot up by 10k since yesterday.
______________

Indeed -- the validators all went offline sometime on Sunday and are still offline as of 11AM PDT today.

The downloads are fine, but noticed that none of the four MB validators are running. My pending credits just shot up by 10k since yesterday.

---

They're back online right now and crediting goes well again.

Ops.. unplanned outage after the weekly outage?

---

Might want to read THIS.

---

Woohoo.. the train is on a straight track? ;-D




BTW.
Someone know when we could get new WUs?

---

I get some WU but can't upload? I see the cricket graph and see abnormal traffic :( . What happend?

---

I get some WU but can't upload? I see the cricket graph and see abnormal traffic :( . What happend?

The flood gates opened. Matt turned all the MB splitters on yesterday, so there is much more work available to download, and thousands of clients world-wide ended up draining their cache, and are trying to refill it.

Once the bandwidth is no longer maxed out (as shown by the cricket graph, or that picture above..which is static), uploads should flow just fine.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

No, the graph I posted isn't static.. it's 'real time, live' or what ever.. ;-)

---

No, the graph I posted isn't static.. it's 'real time, live' or what ever.. ;-)

Alright. I'm used to static pictures being posted. Packets/sec is a strange way of looking at it though. I have octets (bytes)/sec bookmarked (link here).

Oh, and my official submission for panic at the moment is.. I have 10 WUs that won't upload! One of them has an hour and a half of upload time on it. I know there's the backoff mechanism that they run through, but every 20-30 minutes I'll pick one and tell it to retry now, and that just doesn't work.

Oh well, I tried.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

Alright, [/panic]. They all uploaded at the same time (select all, retry now). It's too early to tell, but it looks like the bytes/sec rate has come down from the ceiling of ~93mbit to ~90mbit. That 3mbit drop in the project outbound has correlated to a 3mbit rise for inbound.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

Well, it appears (at 2155utc) that the database issues must be done. All four MB validators have been turned on, and I think the "waiting for assimilation" queue is getting smaller. There are several hundred thousand results/wus in the "waiting for deletion" queue.

And it must be doing something, because the splitters are creating at ~25/sec and there is a RTS queue. Of course the server status page isn't a "real time" picture, nor very accurate, but it's a general picture at least.

Yay!

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

Something has gone wrong. The graph has bottemed out and web pages are slow to load. Also I cannot get any mb jobs.

---

It's the weekend...

---

--
Classic 82353 WU / 400979 h

Good cache, nice cache.......

---

Looks like the assimilators are crunching away. "waiting for assimilation" is down under 1M, and the "waiting for db purge" queue is into the 7-digit range. Now just waiting for those purge queues to be processed and that should free up a TON of storage space and allow the splitters to provide a stable amount of work.

Looks like the storm is over. :D

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)