SETI @ Home - Berkeley down?

[IsOs]

I wasn't able to find any official word on this outage. Any idea how long will this last?

 

[Assimilator1]

Nope ,its still down btw ,looking at the graph though there is something getting in

 

[Eponymous]

I think we can safely say that the current rate of 0.92bits/sec can be attributed to statistical error.

1 bit/sec is even slower than I can type! :Q

Boy a 300Baud modem would seem fast now...

 

[htmlmasterdave]

Stats are down for me too, but I think I am still able to upload and download

 

[AkumaBao]

The one night I decided to leave all three of my system on all night, and the SETI server is down. Still down after 26 hours. Guess I'm going to continue to leave them on.

 

[Confused]

If anyone needs WUs send a result to my queue teamanandtech.d2g.com port 80 and i'll move some WUs into a queue for you

ConfusedBW

 

[Rattledagger]

Some info on alt.sci.seti...
1st by George Kaplan:


<< "SSL is some distance away from campus; in fact, they didn't lose power
on 7 March, although their network connectivity was cut off due to the
problem on campus.

So what's the current problem? Well it isn't an electrical outage, or
at least not a widespread one. The SSL router (inr-60) is located at
SSL, and it's fine, so SSL has electrical power. But all of the SSL
subnets (not just S@H) are currently unreachable.

We don't know much more right now, since my group (Communications and
Network Services) doesn't manage the network within SSL. (SSL is what
we call a "private net"; we manage the backbone up to their router
interface; they handle everything else within their buildings). At
this point all I can say for sure is that there's an equipment failure
of some sort at SSL." >>



2nd, by Michael Sinatra:


<< "As my colleague George Kaplan has mentioned, we (from campus) can't reach
anything beyond inr-60, which is phyically located at SSL. inr-60 is
reachable, and all of its interfaces are functioning properly, but the
next hop beyond it (which is not the seti server, by the way, it's a
firewall) is not responding. Because of that, traceroute keeps bumping
the TTL and trying the next hop, which of course doesn't reply, and so on,
until traceroute gives up after some arbitrary number of hops (often 30 or
60).

There's not much we can do about the current problem, other than try to
get in touch with the SSL system admins (by phone, of course; email is
somewhat problematic here), which we have been trying to do." >>



In other words, the url posted by Assimilator1 is the link between SSL and Campus, and shows some traffic due to all trying to trace to seti. It's good to know this link is up, since we then know there's no new diggers out like last year...

 

[conjur]

Thanks for catching that info, rattledagger...preshadit

 

[Assimilator1]

Thanks for the info Rattledagger ,btw I think it was Logix who posted the link

 

[Logix]

Actually, what I posted was for the Residence Hall network. I was just showing how much bandwidth all the students' music and divx pirating is eating up! :Q

The graph for inr-60, the SSL router, is the one you posted, Assimilator1, which currently has next to nil data flowing. Here's that link again.

 

[Assimilator1]

Ah ok ,I got confused!

The graph still shows no outgoing

 

[Fornoth]

Well, people at SSL should be getting to work shortly - and hopefully this will be resolved!