Here's the new thread, May yer problems be brief ones.

Or preferably, none at all...
(But I look at the world with big kitty eyes........).

---

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

Hopefully not have to use it very often .... :)

---

Logan.

BOINC FAQ Service (Ahora, también disponible en Español/Now available in Spanish)

Hosed again!


(suggested new title) :-)

Hosed again!


(suggested new title) :-)

How so hosed?

---

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

Hosed again!


(suggested new title) :-)

How so hosed?

Maybe rubber in a back room? ;)

Hosed again!


(suggested new title) :-)

How so hosed?

http://www.urbandictionary.com/define.php?term=hosed :-)

Says it all... I hope we can have an uninteruppted service one day...

Have you seen the level of demand on the Cricket graphs is still very high. This shows the system still settling down, and drawing 92+Mbps bandwidth.

Can this demand go on, or will the servers collapse under the strain?

---

It's good to be back amongst friends and colleagues

Offhand, I'd say this looks solid so far. The recent trend has been somewhat less than half the outage time at 90+ bandwidth before starting to tail off.

My recommendation; Panic Off for now. :-)

Alinator

Have you seen the level of demand on the Cricket graphs is still very high. This shows the system still settling down, and drawing 92+Mbps bandwidth.

Can this demand go on, or will the servers collapse under the strain?

If it lasted this long, then there's no reason to think that it'll fail because of overload... other factors seem to be the cause.

It's interesting, that the area of the peak above average should be roughly the same as the area of the gap in the chart...

Looking at the graph the servers have coped remarkably well catching up with the backlog and only now is the throughout starting to reduce indicating the worst of it is over for them.

---

Wow........but that was an extended bit of bandwidth.....
Cricket Gone Wild......

---

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

Wow........but that was an extended bit of bandwidth.....
Cricket Gone Wild......

With two instances of about 100, One at or near and one slightly above 100, wow.

Interesting, even though we've dropped down quite a bit, we're still running above normal and increasing over the past week. We started at about 35MB after the recovery from an outage on 25 Mar, and are currently running 60-65MB (as of this post).

This link displays activity a little clearer.

Wow........but that was an extended bit of bandwidth.....
Cricket Gone Wild......

With two instances of about 100, One at or near and one slightly above 100, wow.

Interesting, even though we've dropped down quite a bit, we're still running above normal and increasing over the past week. We started at about 35MB after the recovery from an outage on 25 Mar, and are currently running 60-65MB (as of this post).

This link displays activity a little clearer.

Actually, I would say that the current level is closer to 'normal'.

Coincident with the installation of the new router, Matt found a stash of tapes which split to provide almost exclusively long-running WUs. Now the shorties are back in the mix. We get through them quicker, so more have to be sent out to keep our shivering cores warm, so the bandwidth goes up - to about the level the old router maxxed out. Now, we have a bit of spare overhead for recovery too.

Things look better at my computers. Fewer "Ready To Reports" and a fuller cache than yesterday.

---

Minor problem- looking at Scarecrow's graphs only the Result's recieved in the last hour, Result turn around time & Result creation rate graphs are updating. Just had a look at the Server Status page & it's been 37 hours since the other stats were updated.

---

Grant
Darwin NT

08/04/2008 16:27:45|SETI@home|Sending scheduler request: To fetch work. Requesting 624 seconds of work, reporting 0 completed tasks
08/04/2008 16:27:50|SETI@home|Scheduler request succeeded: got 0 new tasks
08/04/2008 16:27:50|SETI@home|[sched_ops_debug] Server version 601
08/04/2008 16:27:50|SETI@home|Project requested delay of 11.000000 seconds
08/04/2008 16:27:50|SETI@home|[sched_op_debug] Deferring communication for 4 min 5 sec
08/04/2008 16:27:50|SETI@home|[sched_op_debug] Reason: no work from project

---

Sir Arthur C Clarke 1917-2008

Minor problem- looking at Scarecrow's graphs only the Result's recieved in the last hour, Result turn around time & Result creation rate graphs are updating. Just had a look at the Server Status page & it's been 37 hours since the other stats were updated.

I reverse my stand on this issue... I liked it it better when the RTS was flat but at half a million. I hereby request you break it again. (just no pleasing some people, is there?) :)

Yeah I'm seeing the stats both local to Seti and not so local not updating, I think something is broken again. :(

See Latest Tech News. Matt has explained the reason for the longer than usual outage yesterday, and there may be another one today. He also explained the reason that the validators are currently offline.

Stuff always seem to happen when I get close to a milestone, hoping to reach 50,000 SETI credits this month.

---

Sir Arthur C Clarke 1917-2008

The cricket graphs indicate the servers are not communicating again.

Daily Graph

The cricket graphs indicate the servers are not communicating again.

Daily Graph

Yeah, looks like we will have to wait until we hear from the staff about whats happened. Probably something simple I hope, but since I have a heap of WU's queued, probably no big deal here... For about 36 more hrs that is ;)

---