208.68.243.254 - Whois Information

OrgName:    SETIATHOME 
OrgID:      SETIA
Address:    7 Gauss Way
Address:    Room 325A
City:       Berkeley
StateProv:  CA
PostalCode: 94720
Country:    US

NetRange:   208.68.240.0 - 208.68.243.255 
CIDR:       208.68.240.0/22 
NetName:    SETIATHOME
NetHandle:  NET-208-68-240-0-1
Parent:     NET-208-0-0-0-0
NetType:    Direct Assignment
NameServer: ADNS1.BERKELEY.EDU
NameServer: ADNS2.BERKELEY.EDU
Comment:    
RegDate:    2006-07-19
Updated:    2006-11-14

Ping has started…

PING 208.68.240.16 (208.68.240.16): 56 data bytes
64 bytes from 208.68.240.16: icmp_seq=0 ttl=49 time=57.414 ms
64 bytes from 208.68.240.16: icmp_seq=1 ttl=49 time=48.683 ms
64 bytes from 208.68.240.16: icmp_seq=2 ttl=49 time=56.586 ms
64 bytes from 208.68.240.16: icmp_seq=3 ttl=49 time=58.014 ms
64 bytes from 208.68.240.16: icmp_seq=4 ttl=49 time=65.436 ms
64 bytes from 208.68.240.16: icmp_seq=5 ttl=49 time=51.773 ms
64 bytes from 208.68.240.16: icmp_seq=6 ttl=49 time=53.666 ms
64 bytes from 208.68.240.16: icmp_seq=7 ttl=49 time=58.524 ms
64 bytes from 208.68.240.16: icmp_seq=8 ttl=49 time=53.451 ms
64 bytes from 208.68.240.16: icmp_seq=9 ttl=49 time=55.335 ms

--- 208.68.240.16 ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 48.683/55.888/65.436/4.307 ms

traceroute to 208.68.240.16 (208.68.240.16), 64 hops max, 52 byte packets
 1  192.168.1.1 (192.168.1.1)  7.215 ms  4.343 ms  1.556 ms
 2  10.247.0.1 (10.247.0.1)  10.844 ms  7.933 ms  8.702 ms
 3  24-156-52-17.unassigned.npgco.com (24.156.52.17)  8.953 ms  22.674 ms  9.227 ms
 4  24-156-52-1.unassigned.npgco.com (24.156.52.1)  17.261 ms  11.749 ms  13.370 ms
 5  24.121.60.4 (24.121.60.4)  26.934 ms  26.141 ms  28.010 ms
 6  24.121.123.13 (24.121.123.13)  43.326 ms  38.144 ms  38.889 ms
 7  70.96.35.245 (70.96.35.245)  35.876 ms  43.601 ms  47.450 ms
 8  tg9-1.cr02.phnzaz87.integra.net (209.63.113.97)  65.158 ms  57.173 ms  40.556 ms
 9  tg13-1.cr02.lsancarc.integra.net (209.63.114.33)  44.428 ms  37.632 ms  41.421 ms
10  tg4-1.br01.lsancarc.integra.net (209.63.113.30)  37.671 ms  63.694 ms  41.011 ms
11  he.net.coresite.com (206.223.143.122)  44.517 ms  35.491 ms  47.587 ms
12  10gigabitethernet2-1.core1.lax1.he.net (72.52.92.121)  50.478 ms  44.214 ms  41.888 ms
13  10gigabitethernet1-3.core1.pao1.he.net (72.52.92.21)  54.094 ms  49.056 ms  49.135 ms
14  64.71.140.42 (64.71.140.42)  47.875 ms  52.300 ms  72.056 ms
15  208.68.243.254 (208.68.243.254)  60.072 ms  71.909 ms  76.468 ms
16  * * *
17  * * *
18  * *

It cannot get any further than that particular router and just spins it's wheels.

---

Boinc won't ask for work from a project, if the the number of uploads for that project exceeds twice the number of CPU cores,
so until you're down to a handfull of uploads, you'll get no downloads from Seti,
But you can still get work from other projects.

Claggy

If you’re looking for an interesting task to sick your GPU’s on, check out Collatz Conjecture at http://boinc.thesonntags.com/collatz/ They’re called Wondrous Numbers (really).

For the CPU, there are projects to help improve the human condition at World Community Grid. http://www.worldcommunitygrid.org/

This is a unique event. Everyone is, surely, doing everything they have done before. Either this project has suddenly become too popular for its own good, or some external or internal force has dampened its progress. What has happened to jam this up for so long?
I am a proponent of seeking other projects for free resources. I have done so. I wonder what is going on here?

HMM... Funny, everything but the transgers or updates goes through. (Right me a script for that)

Simple failure - immediate backoff/retry:


(Direct link)

More complicated failure: connected, upload progress bar to 100%, then retry.


(Direct link)

Yesterday most of my failures were the partial upload ones- sometimes 16%, somtimes 60%, often 100%- all usually after about a minute or so. There were a few that died within a second or so.
Today almost all of the failures occur straight away; Scarecrow's graphs & the network traffic would indicate it's this way for most people. Even less work is getting back than a couple of days ago.

---

Grant
Darwin NT

People.
I have been having problems for about 4 days now on 4 PCs and some ran out of work (prefs set for 3 days of work). Yesterday, WUs are downloading, but not uploading. So at least work is being done. That's an improvement. Patience.
They. Will. Fix. It.

---

Looks like some of you can at least download. I can not download or upload. I get a message the the inet connection is good, but the servers no workie.
TTFN

HMM... Funny, everything but the transgers or updates goes through. (write me a script for that)

Comms and ISPs are good.

Two individual servers - Anakin and Bruno - are sick and require attention.

This is a unique event. Everyone is, surely, doing everything they have done before. Either this project has suddenly become too popular for its own good, or some external or internal force has dampened its progress. What has happened to jam this up for so long?
I am a proponent of seeking other projects for free resources. I have done so. I wonder what is going on here?

Actually, it's not that unique.

The basic idea behind BOINC is that projects that would have required an expensive investment in computing can be run using relatively simple hardware, BOINC, and a stack of computers "in the wild" whose excess time is donated.

The problem is that most BOINC projects are not well funded. There is a lot less redundancy and a lot less excess capacity, and sometimes, things break.

Some of those who have been around longer remember some pretty huge outages.

They're unfortunate. If you believe the work should be done, but you can't find the money to fund it very well, this is the result. The outage problem is offset by caching in the BOINC client on your machine.

It's also offset by the fact that everyone can assign 90% of their resources to SETI and 10% to Einstein, or any one of several dozen worthy projects.

---

If things are working, and I guess we are using our government's deff of the word working, then what is the menaing of these messages I keep getting?

2/20/2010 4:27:55 PM SETI@home update requested by user
2/20/2010 4:27:57 PM SETI@home Sending scheduler request: Requested by user.
2/20/2010 4:27:57 PM SETI@home Requesting new tasks for GPU
2/20/2010 4:27:58 PM Project communication failed: attempting access to reference site
2/20/2010 4:27:59 PM Internet access OK - project servers may be temporarily down.
2/20/2010 4:28:02 PM SETI@home Scheduler request failed: Server returned nothing (no headers, no data)
2/20/2010 4:29:03 PM SETI@home Fetching scheduler list
2/20/2010 4:29:08 PM SETI@home Master file download succeeded
2/20/2010 4:29:13 PM SETI@home Sending scheduler request: To fetch work.
2/20/2010 4:29:13 PM SETI@home Requesting new tasks for GPU
2/20/2010 4:29:14 PM Project communication failed: attempting access to reference site
2/20/2010 4:29:15 PM Internet access OK - project servers may be temporarily down.
2/20/2010 4:29:18 PM SETI@home Scheduler request failed: Server returned nothing (no headers, no data)
2/20/2010 4:30:19 PM SETI@home Sending scheduler request: To fetch work.
2/20/2010 4:30:19 PM SETI@home Requesting new tasks for GPU
2/20/2010 4:30:21 PM Project communication failed: attempting access to reference site
2/20/2010 4:30:22 PM Internet access OK - project servers may be temporarily down.
2/20/2010 4:30:24 PM SETI@home Scheduler request failed: Failure when receiving data from the peer
2/20/2010 4:31:25 PM SETI@home Sending scheduler request: To fetch work.
2/20/2010 4:31:25 PM SETI@home Requesting new tasks for GPU
2/20/2010 4:31:26 PM Project communication failed: attempting access to reference site
2/20/2010 4:31:27 PM Internet access OK - project servers may be temporarily down.
2/20/2010 4:31:30 PM SETI@home Scheduler request failed: Server returned nothing (no headers, no data)
2/20/2010 4:32:31 PM SETI@home Sending scheduler request: To fetch work.
2/20/2010 4:32:31 PM SETI@home Requesting new tasks for GPU
2/20/2010 4:32:32 PM Project communication failed: attempting access to reference site
2/20/2010 4:32:33 PM Internet access OK - project servers may be temporarily down.
2/20/2010 4:32:36 PM SETI@home Scheduler request failed: Server returned nothing (no headers, no data)

It's kinda working...I got 17,119 through yesterday but not all...

Didn't know about PathPing, it's pretty sweet. Found this convenient gadget: http://whitepapers.zdnet.com/abstract.aspx?docid=1164559

Tracing route to setiboincdata.ssl.berkeley.edu [208.68.240.16]
over a maximum of 30 hops:
0 WOPR-III [192.168.101.245]
1 192.168.101.1
2 10.50.96.1
3 ge3-2-njmnyhubp-rtr1.nj.rr.com [24.168.128.146]
4 cpe-24-29-150-94.nyc.res.rr.com [24.29.150.94]
5 tenge-0-1-0-nwrknjmd-rtr.nyc.rr.com [24.29.119.150]
6 ae-4-0.cr0.nyc30.tbone.rr.com [66.109.6.78]
7 ae-0-0.cr0.nyc20.tbone.rr.com [66.109.6.27]
8 66.109.6.10
9 ae-1-0.pr0.sjc10.tbone.rr.com [66.109.6.137]
10 gige-g5-6.core1.sjc2.he.net [216.218.135.225]
11 10gigabitethernet3-2.core1.pao1.he.net [72.52.92.69]
12 64.71.140.42
13 208.68.243.254
14 setiboincdata.ssl.berkeley.edu [208.68.240.16]

Computing statistics for 350 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 WOPR-III [192.168.101.245]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.101.1
0/ 100 = 0% |
2 --- 100/ 100 =100% 100/ 100 =100% 10.50.96.1
0/ 100 = 0% |
3 12ms 0/ 100 = 0% 0/ 100 = 0% ge3-2-njmnyhubp-rtr1.nj.rr.com [24.168.128.146]
0/ 100 = 0% |
4 14ms 0/ 100 = 0% 0/ 100 = 0% cpe-24-29-150-94.nyc.res.rr.com [24.29.150.94]
0/ 100 = 0% |
5 17ms 0/ 100 = 0% 0/ 100 = 0% tenge-0-1-0-nwrknjmd-rtr.nyc.rr.com [24.29.119.150]
0/ 100 = 0% |
6 19ms 0/ 100 = 0% 0/ 100 = 0% ae-4-0.cr0.nyc30.tbone.rr.com [66.109.6.78]
0/ 100 = 0% |
7 19ms 0/ 100 = 0% 0/ 100 = 0% ae-0-0.cr0.nyc20.tbone.rr.com [66.109.6.27]
0/ 100 = 0% |
8 95ms 0/ 100 = 0% 0/ 100 = 0% 66.109.6.10
0/ 100 = 0% |
9 98ms 0/ 100 = 0% 0/ 100 = 0% ae-1-0.pr0.sjc10.tbone.rr.com [66.109.6.137]
0/ 100 = 0% |
10 108ms 0/ 100 = 0% 0/ 100 = 0% gige-g5-6.core1.sjc2.he.net [216.218.135.225]
0/ 100 = 0% |
11 108ms 0/ 100 = 0% 0/ 100 = 0% 10gigabitethernet3-2.core1.pao1.he.net [72.52.92.69]
0/ 100 = 0% |
12 108ms 0/ 100 = 0% 0/ 100 = 0% 64.71.140.42
10/ 100 = 10% |
13 111ms 10/ 100 = 10% 0/ 100 = 0% 208.68.243.254
3/ 100 = 3% |
14 110ms 13/ 100 = 13% 0/ 100 = 0% setiboincdata.ssl.berkeley.edu [208.68.240.16]

Trace complete.

This is a unique event. Everyone is, surely, doing everything they have done before. Either this project has suddenly become too popular for its own good, or some external or internal force has dampened its progress. What has happened to jam this up for so long?
I am a proponent of seeking other projects for free resources. I have done so. I wonder what is going on here?

Actually, it's not that unique.

The basic idea behind BOINC is that projects that would have required an expensive investment in computing can be run using relatively simple hardware, BOINC, and a stack of computers "in the wild" whose excess time is donated.

The problem is that most BOINC projects are not well funded. There is a lot less redundancy and a lot less excess capacity, and sometimes, things break.

Some of those who have been around longer remember some pretty huge outages.

They're unfortunate. If you believe the work should be done, but you can't find the money to fund it very well, this is the result. The outage problem is offset by caching in the BOINC client on your machine.

It's also offset by the fact that everyone can assign 90% of their resources to SETI and 10% to Einstein, or any one of several dozen worthy projects.

If you are saying that this project is too popular I agree. Distributed computing should be distributed. I have always agreed. People should find their red buttons and compute on them. Health, , numbers, forms of matter, where that matter is, where it might go, how the earth evolves, what stars do, where they are (I think everything but safety[and hopefully that somehow]): these are other projects that can use your idle CPU and GPU time.

Certainly there will always be network and hardware issues, caused by both political and financial drives. The crunching must go on: one way or another!

This is a unique event. Everyone is, surely, doing everything they have done before. Either this project has suddenly become too popular for its own good, or some external or internal force has dampened its progress. What has happened to jam this up for so long?
I am a proponent of seeking other projects for free resources. I have done so. I wonder what is going on here?

Actually, it's not that unique.

The basic idea behind BOINC is that projects that would have required an expensive investment in computing can be run using relatively simple hardware, BOINC, and a stack of computers "in the wild" whose excess time is donated.

The problem is that most BOINC projects are not well funded. There is a lot less redundancy and a lot less excess capacity, and sometimes, things break.

Some of those who have been around longer remember some pretty huge outages.

They're unfortunate. If you believe the work should be done, but you can't find the money to fund it very well, this is the result. The outage problem is offset by caching in the BOINC client on your machine.

It's also offset by the fact that everyone can assign 90% of their resources to SETI and 10% to Einstein, or any one of several dozen worthy projects.

If you are saying that this project is too popular I agree. Distributed computing should be distributed. I have always agreed. People should find their red buttons and compute on them. Health, , numbers, forms of matter, where that matter is, where it might go, how the earth evolves, what stars do, where they are (I think everything but safety[and hopefully that somehow]): these are other projects that can use your idle CPU and GPU time.

Certainly there will always be network and hardware issues, caused by both political and financial drives. The crunching must go on: one way or another!

Too true, I jumped on GPUGRID today for lack of SETI CUDA jobs. I'm still crunching SETI on CPU, GPUs are cooking some molecules now... :)

If you are saying that this project is too popular I agree.

No, I wasn't saying that at all.

What I said was that the normal way of doing an internet based "x" (whatever it is) involves buying rack space in three or four large data centers, chosen to be relatively near a major exchange point.

You put together a package that will handle 2 to 3 times the anticipated load (database servers, switches and routers, etc.) and you put a complete set in each of the four data centers.

... and you write big checks every single month.

Either that, or buy time on a supercomputer cluster somewhere, and not have to deal with all of the messy volunteer issues.

To do large computing when you don't have that kind of budget, you have to scale something back.

So SETI runs on what they can afford. They don't have spares in depth, or excess capacity. There are lots of places where just one failure can take the server component down, or cause it to run badly, for an extended period.

It has happened before, and it will happen again.

As a 40-year veteran of the computer industry (more than 20 in datacomm and networking) SETI@Home (and BOINC) isn't a study in reliability, it is a study in fault tolerance and resiliency.

... and if we can stop worrying about the moment-to-moment performance, it does an amazingly good job.

If you ask me, the problem isn't that SETI@Home is too popular, it is that the average computer user is comparing it to eBay or Amazon.com. If they went down it'd make the nightly news -- but if SETI@Home is down, the clients keep crunching and work gets reported when things come back.

---

Yeah, I agree Ned, If Seti@Home itself went down, Except for the users, The media would probably not even notice or care. :(

---

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

Yeah, I agree Ned, If Seti@Home itself went down, Except for the users, The media would probably not even notice or care. :(

What I meant was that Amazon.com being down would be a notable event, that would have repercussions beyond the inability to see a web site.

It would lower revenue at Amazon, and certainly orders would be up at BN.com.

A lot of money would not go to Amazon (and their merchant processor) but Barnes&Noble (and their bankers) would be happy. Some customers would switch.

It would be newsworthy.

In contrast, if SETI@Home is down, computers that are turned on anyway are sending a few hundred bytes of data toward servers that are not up, and if it stays down, those same computers will retry until they come back up.

... a few people at Berkeley would work very hard, and a few of the volunteers would waste a whole lot of angst over something they cannot control. [Edit: and a lot of processing would still get done during the outage]

That is not newsworthy.

---

That is not newsworthy.

Translated - Nobody ever lost a dime because SETI wasn't available.

---

That is not newsworthy.

Translated - Nobody ever lost a dime because SETI wasn't available.

Translate this...........
Got it?

It is newsworthy to ME.

---

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

That is not newsworthy.

Translated - Nobody ever lost a dime because SETI wasn't available.

I'm saying that the BOINC client expects outages.

It is the people who are fickle, and thin-skinned, and apparently, see the impending destruction of civilization in the most trivial hiccups.

With Amazon, those fickle consumers are an integral part of the process.

With BOINC, it will run fine without the slightest bit of supervision.

When the project servers are down, work continues.

---

That is not newsworthy.

Translated - Nobody ever lost a dime because SETI wasn't available.

Translate this...........
Got it?

It is newsworthy to ME.

Yes, and if you could gain just a little bit of perspective, you'd be much happier.

"The first sign of a nervous breakdown is when you start thinking your work is terribly important." -- Milo Bloom

---

That is not newsworthy.

Translated - Nobody ever lost a dime because SETI wasn't available.

Please don't translate unless you actually understand what I'm saying.

I'm saying that the BOINC client expects outages.

It is the people who are fickle, and thick-skinned, and apparently, see the impending destruction of civilization in the most trivial hiccups.

With Amazon, those fickle consumers are an integral part of the process.

With BOINC, it will run fine without the slightest bit of supervision.

Ned....
May I cry now?

8 rigs chugging along...one has not been able to phone home since the 16th.
No reporting, no new work.

Please don't belittle one who cares so much about a simple science project.
I have donated hours of my life and countless dollars to it.

And it hurts me that things have gone bad.

Not a life-changing thing, but it does affect me more than some realize.

Hope you can understand that.

---

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