Seems as though the Connections have dropped in the past few minutes....Bad time for cogent to foul up, lol

Anybody get anything Since 1 UTC?

http://fragment1.berkeley.edu/~cricket/inr-668-interfaces.html

---

Still none for me, but bandwidth usage can be seen here -> http://fragment1.berkeley.edu/~cricket/inr-668-interfaces.html

There is a strange downturn on the graph now as well. Maybe something upstream can't handle the heat?
Or perhaps somethings been turned off that doesn't show up on the status page.

Whatever it is, my uploads started to go, but about half way through the first one it died. Tried resending several times in the last half hour, to no avail :(

---

Even the WFV Dropped....I guess we blew sumthin'up
From 24,000 to 14,000

---

Even the WFV Dropped....I guess we blew sumthin'up
From 24,000 to 14,000

wow the WFV is now at 0, if that number is correct then wow those validators did a kick ass job

-matt

---

"They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety."
- Benjamin Franklin,
Historical Review of Pennsylvania, 1759.

Even the WFV Dropped....I guess we blew sumthin'up
From 24,000 to 14,000

wow the WFV is now at 0, if that number is correct then wow those validators did a kick ass job

-matt

Or the system went FUBAR.. There should be a backlog after a 1 week outage - as there are THOUSANDS of results waiting to be sent back - and the WFV never seems to have gove above 25,000. Heck.. I've not been able to send a single result back, and about 1/2 of the work I'm trying to download has been "stuck" for a couple hours.

WFV=0 could mean that things are really hosed at this point! (it might be the SSL ISP, but data isn't flowing!)

---

So I suppose that someone is able to upload something somewhere. I can't seem to do it.

---

but also notice that it seems the bandwidth in and out has been decreased. So all the people trying to download and upload are giving the validators a chance to get them as they come in now. Also notice that when the project first came back up the validators showed 8000+ waiting. Then the network bandwidth slowed considerably and limited the number of incoming results. Maybe also the validators were tweaked...

-matt

---

"They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety."
- Benjamin Franklin,
Historical Review of Pennsylvania, 1759.

See this Thread
http://setiweb.ssl.berkeley.edu/forum_thread.php?id=19359

---

So I suppose that someone is able to upload something somewhere. I can't seem to do it.

The UCB sysadmins will be back in about 12 hours, and I'm sure they'll sort out things! (after a coffee)

In the mean time, WFV is at zero. (Rah, Rah UCB! You fixed the problem! Ya... Right)

---

Just got back from a trip to the Berkshires (Mass. USA). System creshed and took my CPDN units out with it, was 139 Hours (17 Trickle out of 72) into the model. Still got 909.96 credits for what I did. Sure wish that I could get that one back to work from that point.

SETI

Like a lot of others I uploaded the 10 units that I had, no downloads, server to busy. No problem here, will finish up the LHC units that I have and get more of them along with a new Climet Model. Oh yea I turned tha network connection off so you can get through to the SETI server.

Cheers
Ray

---

Pizza@Home Rays Place Rays place Forums

So I suppose that someone is able to upload something somewhere. I can't seem to do it.

Remember that everyone is trying to upload right now. Most of them just aren't getting through because of everyone else trying to get thru.

---

So I suppose that someone is able to upload something somewhere. I can't seem to do it.

Remember that everyone is trying to upload right now. Most of them just aren't getting through because of everyone else trying to get thru.

Do you have pom-poms tatooed on your body?

Things are not happening like in a "normal" long term outage it seems.

---

So I suppose that someone is able to upload something somewhere. I can't seem to do it.

Remember that everyone is trying to upload right now. Most of them just aren't getting through because of everyone else trying to get thru.

Do you have pom-poms tatooed on your body?

Things are not happening like in a "normal" long term outage it seems.

If I respond in any substantive way to your post, you'll just respond with something irrelevant.

No, they aren't tattooed on. Tattooed pom-poms don't keep the dust off of my keyboard the way the real ones do.

---

This cricket graph seems to show that Cogent is still up, but something is preventing connection to the SETI/BOINC servers.

This cricket graph seems to show that Cogent is still up, but something is preventing connection to the SETI/BOINC servers.

I don't know what kind of routers Cogent uses (or for that matter, Berkeley).

My current upstream uses a mix of Junipers (which are very cool) and Shasta BSNs (which are mostly cool).

The Shasta routers are "flow based." A flow is a sort of "circuit" -- a table entry that pre-routes every circuit.

Flow based routers are really good up to a point. At some point, the router runs out of "flows" and spends most of its time trying to add and remove flows and none of its time routing.

When the SQL Slammer worm came out, our bandwidth went to zero. Our upstream reported that the router was trying to manage significantly more flows than it was able to do.

A few weeks after that, they moved our circuit to a Juniper because it isn't flow based.

... but even if the router isn't flow based, at some point it just plain has to drop packets.

---

This cricket graph seems to show that Cogent is still up, but something is preventing connection to the SETI/BOINC servers.

I don't know what kind of routers Cogent uses (or for that matter, Berkeley).

My current upstream uses a mix of Junipers (which are very cool) and Shasta BSNs (which are mostly cool).

The Shasta routers are "flow based." A flow is a sort of "circuit" -- a table entry that pre-routes every circuit.

Flow based routers are really good up to a point. At some point, the router runs out of "flows" and spends most of its time trying to add and remove flows and none of its time routing.

When the SQL Slammer worm came out, our bandwidth went to zero. Our upstream reported that the router was trying to manage significantly more flows than it was able to do.

A few weeks after that, they moved our circuit to a Juniper because it isn't flow based.

... but even if the router isn't flow based, at some point it just plain has to drop packets.

Damn.. You're nothing more than a poorly trained "trade shool trained" Network type. This is clear in this post!

"flow based" routers! What a joke! ""flow based." A flow is a sort of "circuit" -- a table entry that pre-routes every circuit."

Damn! with folks like Ned doing networking, it's no wonder that hackers are gaining our personal info!

(just a clue Ned.. There are no circuits.. They are called "routes")...

---

Oh, Cool! The Cricket graph just leapt way up to nearly 80! Maybe WU traffic will really flow, now.

Whit

This cricket graph seems to show that Cogent is still up, but something is preventing connection to the SETI/BOINC servers.

I don't know what kind of routers Cogent uses (or for that matter, Berkeley).

My current upstream uses a mix of Junipers (which are very cool) and Shasta BSNs (which are mostly cool).

The Shasta routers are "flow based." A flow is a sort of "circuit" -- a table entry that pre-routes every circuit.

Flow based routers are really good up to a point. At some point, the router runs out of "flows" and spends most of its time trying to add and remove flows and none of its time routing.

When the SQL Slammer worm came out, our bandwidth went to zero. Our upstream reported that the router was trying to manage significantly more flows than it was able to do.

A few weeks after that, they moved our circuit to a Juniper because it isn't flow based.

... but even if the router isn't flow based, at some point it just plain has to drop packets.

Damn.. You're nothing more than a poorly trained "trade shool trained" Network type. This is clear in this post!

"flow based" routers! What a joke! ""flow based." A flow is a sort of "circuit" -- a table entry that pre-routes every circuit."

Damn! with folks like Ned doing networking, it's no wonder that hackers are gaining our personal info!

(just a clue Ned.. There are no circuits.. They are called "routes")...

Actually, Woody, on a router like a Shasta BSN, they are called "flows" -- a flow encapsulates all of the routing for a pair of IP addresses.

A flow is generally created when a TCP syn comes through the router, and either times out or is discarded when the TCP rst comes through. The idea is to trade the time needed to build "flows" in exchange for faster routing.

I'm not sure I agree with the theory, but I don't work for Shasta either.

You can probably find the relevant pages from the Shasta BSN documentation on-line.

Some providers like flow-based routers because it is really easy to add enhanced services like firewalls to a flow-based router. QoS is easy to implement because you can prioritize the flows.

They don't handle high connection rates well. Probably why Ciscos and Junipers do not do flows. I'd rather not be connected to a Shasta.

But that isn't really the point.

If you call someone an idiot enough times, a few people may start to believe you.

Mostly, the insults just get old. Why does it always have to get personal?

---

[font='courier,courier new']Internal combustion engine : SETI/BOINC :: Intake, compression, power, exhaust : Download, crunch, upload, accreditation

Let's go![/font]

---

I got 9 WUs, the last 20 minutes ago.

---

mcbeth