On the plus side, since we turned off the classic data server, we freed up one of our precious few Cogent IP addresses. So we are working toward moving the scheduler onto our private Cogent link, which will keep the bandwidth off the lab routers and therefore protected from those problems.

An idle thought hit me when I read that paragraph. Wonder what's going to happen when they try to use that IP address and all those Seti@home queue programs still out there trying to call home hit it. Hopefully there are not still any DSN caches out there still resolving the old Seti@home URL to that IP address.

There well could be, but one can at least hope that as some people continue to not get work for classic, that they "get the point". If they have a firewall in place, and classic uses a different port for BOINC, they could possibly block that port at their firewall also, so the traffic doesn't hit the server. Still wouldn' recover used BW over the pipe itself though, if peeps still keep trying to use classic and hit the IP.

Another positive that has crossed my mind, is server resources. Wasn't classic being run off the same server box as some of the BOINC processes? Doubt the info would still be on the server page, so can't check there anymore... Without classic, there might well be more server resources there as well...

---

I am having trouble receiving new units on one of my computers for 24 hours now. Is anyone else having this problem? Otherwise the units are running fine, but keep getting no new work.

Thanks,

Nick

I was also earlier today/late last night, but it passed...

:)

* Nothing like the "infamous outage" we had a week back or so, & that wasn't ALL that bad!

(LOL, gave the ALU & FPU in my CPU a break, not smashing fpops constantly doing SETI!)

APK

---

http://torry.net/authorsmore.php?id=1781

"The object's hull is made of SOLID neutronium: A single StarShip cannot combat it!" quote Mr. Spock, Star Trek original series, episode title: "The Doomsday Machine"

On the plus side, since we turned off the classic data server, we freed up one of our precious few Cogent IP addresses. So we are working toward moving the scheduler onto our private Cogent link, which will keep the bandwidth off the lab routers and therefore protected from those problems.

An idle thought hit me when I read that paragraph. Wonder what's going to happen when they try to use that IP address and all those Seti@home queue programs still out there trying to call home hit it. Hopefully there are not still any DSN caches out there still resolving the old Seti@home URL to that IP address.

new information in tech news.

---

Berkeley Lab??? Campus??? LOCAL TIME STAMP Belgium =19h:36 = UTC +1

A little before 18:00 UTC someone in the Lab must have shut something down as downloads stopped. Seems to be coming back up now.

What ever it was that they did, it looks like they now have un-did it. Uploads and downloads a flying in.

---

I recieved 3 of 8 units, other 5 waiting to try again, the other system has 2 waiting to upload.
Can wait till the system is running better, have 4 and 3 on the two machines. Plunty of work for other projects on both also. While LHC has work that can use the time should I run out of SETI. (LHC is already getting most of my Rosetta time)

Ray

---

Pizza@Home Rays Place Rays place Forums

i just checked BOINC manager and i saw that one workunit had just downloaded while two workunits are still waiting to download.

---

PROUD TO BE TFFE!

Berkeley Lab??? Campus??? LOCAL TIME STAMP Belgium =19h:36 = UTC +1

A little before 18:00 UTC someone in the Lab must have shut something down as downloads stopped. Seems to be coming back up now.

The connection to the server is succedding here, however I'm getting "temporarily failed on upload" everytime BOINC tries to connect. I guess it took longer then expected for this problem they announced yesterday to get sorted out.

Home page says their provider's SSL trunk is hosing up.

I think they need to kick their providers butts up between their ears so they can THINK right! :)

---

Same situation overhere (Belgium). Problematic UL on all boxes, DL stalled...
Internet connection ok (cable). Wireless connections ok. Sattelite conections ok. Cogent??? Berkeley Lab??? Campus??? LOCAL TIME STAMP Belgium =19h:36 = UTC +1

Greetz, ;-))
HP

---

I'm seeying 'Network error : couldn't connect to server' and 'Network error : server returned nothing (no headers, no data)' as of approx 17:00 UTC.
Internet access on that machine is ok so it's not my network at fault.
A lot of downloads and some uploads waiting.
Any idees ?

---

Downloading but not uploading on one machine and no up or down on the other.

---

AMD Athlon 64 X2 4400+
AMD Athlon 64 3800+
AMD AthlonXP 3200+

Spiffy new format for the Perf graphs, and now the data generators are shut off more than they're on lately! ;-)

heh... yeah, all dressed up and nowhere to go. Well, at least it verifies that the GIGO module is working. :)

Ahh yes, the Cricket graphs indicate the SSL firewall's arteries have received their stent (if that was the problem as Matt hypothesized earlier). :-)

My money's still on Ex-lax.

LOL

Yes, I can see your viewpoint Scarecrow!

Spiffy new format for the Perf graphs, and now the data generators are shut off more than they're on lately! ;-)

Alinator

Ahh yes, the Cricket graphs indicate the SSL firewall's arteries have received their stent (if that was the problem as Matt hypothesized earlier). :-)

My money's still on Ex-lax.

Looks like the DAM broke and WU's are starting to flow as of around 14:53 UTC or about 35 minutes ago. Seti downloads have spiked up to about 73Mbps. I was within twenty minutes of running out of work on one machine, but it is happy now. The others have a backlog to download that built up the past 24 hours. But they still have days of work.

Looks like someone came in at Berkeley before 7am and reset something. Most likely in their campus network that was bocking Scheduler requests from getting through or responding. So in effect, we are now in a "recovery".

Ahh yes, the Cricket graphs indicate the SSL firewall's arteries have received their stent (if that was the problem as Matt hypothesized earlier). :-)

Alinator

Looks like the DAM broke and WU's are starting to flow as of around 14:53 UTC or about 35 minutes ago. Seti downloads have spiked up to about 73Mbps. I was within twenty minutes of running out of work on one machine, but it is happy now. The others have a backlog to download that built up the past 24 hours. But they still have days of work.

Looks like someone came in at Berkeley before 7am and reset something. Most likely in their campus network that was bocking Scheduler requests from getting through or responding. So in effect, we are now in a "recovery".

Likewise, starting to get a few work units here too. Machine is humming a happier tune now!

Nick

---

Looks like the DAM broke and WU's are starting to flow as of around 14:53 UTC or about 35 minutes ago. Seti downloads have spiked up to about 73Mbps. I was within twenty minutes of running out of work on one machine, but it is happy now. The others have a backlog to download that built up the past 24 hours. But they still have days of work.

Looks like someone came in at Berkeley before 7am and reset something. Most likely in their campus network that was bocking Scheduler requests from getting through or responding. So in effect, we are now in a "recovery".

got a few down.

17/01/2006 8:13:52 AM|SETI@home|Temporarily failed download of 05oc03ab.24335.22720.853396.1.239: system I/O
17/01/2006 8:13:52 AM|SETI@home|Backing off 1 minutes and 0 seconds on download of file 05oc03ab.24335.22720.853396.1.239
17/01/2006 8:13:52 AM|SETI@home|Temporarily failed download of 27fe05aa.13854.5232.847134.1.61: system I/O
17/01/2006 8:13:52 AM|SETI@home|Backing off 1 minutes and 0 seconds on download of file 27fe05aa.13854.5232.847134.1.61
17/01/2006 8:14:53 AM|SETI@home|Started download of 05oc03ab.24335.22720.853396.1.239
17/01/2006 8:14:53 AM|SETI@home|Started download of 27fe05aa.13854.5232.847134.1.61
17/01/2006 8:15:24 AM|SETI@home|Finished download of 05oc03ab.24335.22720.853396.1.239
17/01/2006 8:15:24 AM|SETI@home|Throughput 12434 bytes/sec
17/01/2006 8:15:24 AM|SETI@home|Finished download of 27fe05aa.13854.5232.847134.1.61
17/01/2006 8:15:24 AM|SETI@home|Throughput 12341 bytes/sec
17/01/2006 8:15:25 AM||request_reschedule_cpus: files downloaded
17/01/2006 8:15:25 AM||request_reschedule_cpus: files downloaded

---