Don't worry about it. With a little luck they will get it cleared tomorrow. You will not lose credit, it's just a little delayed.

---

A lot of people are frustrated that completed work is not moving. Personally, I only had 3 Seti and 1 Beta WU when the problems stated appearing, I simply temporarily cranked up the resource share on some of my other projects. So far I still have 2 Seti WU that haven't even started to crunch. The Beta project was taken down completely to free up resources for Seti main so that is still waiting to report. I only carry a one day queue but my Seti work isn't due till April so there's no rush. When the logjam breaks, I'll give Seti back it's usual share of my CPUs.

The Seti project has always said that we should have other projects to cover down times. My system stays busy 24/7. It just devoting its crunch time to other projects right now.

---

Boinc V7.2.42
Win7 i5 3.33G 4GB, GTX470

On the last hop I see a 12% loss.
In an other test I see 25% loss in 208.68.234.254

Bye,
Franz

---

At last count, I have 38 WUs waiting to UL. Some time, within the next 4 days, I will run out of WUs to crunch for SETI.

I may have to re-set MilkyWay@home to get more WUs to keep the WinXP box doing something "constructive".

In the meantime, I thought I would throw in some more collected data to help in resolving the current problem, that is when I can gain a connection to SETI again. Seems that their Internet connection is down, 100%, for the moment.

And we're back... :)

---------------------------------------

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\WINDOWS\system32\pathping 208.68.240.16 boinc2.ssl.berkeley.edu

Tracing route to boinc2.ssl.berkeley.edu [208.68.240.13]
over a maximum of 30 hops:
  0  siran-winxp-pro [192.168.1.3]
  1  WGT624 [192.168.XXX.XXX]
  2  DI-604 [192.168.YYY.YYY]
  3  10.22.214.1
  4  172.30.1.101
  5  fed1oobl50.rd.sd.cox.cci [172.30.1.53]
  6  12-215-4-26.client.mchsi.com [12.215.4.26]
  7  cr84.cgcil.ip.att.net [12.122.132.146]
  8  cr2.cgcil.ip.att.net [12.123.7.250]
  9  ggr3.cgcil.ip.att.net [12.122.132.17]
 10  192.205.34.198
 11  sjo-bb1-link.telia.net [213.248.80.25]
 12  hurricane-113209-sjo-bb1.c.telia.net [213.248.86.54]
 13  64.71.140.42
 14  208.68.243.254
 15  boinc2.ssl.berkeley.edu [208.68.240.13]

Computing statistics for 375 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           siran-winxp-pro [192.168.1.3]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.XXX.XXX
                                0/ 100 =  0%   |
  2    1ms     0/ 100 =  0%     0/ 100 =  0%  192.168.YYY.YYY
                                0/ 100 =  0%   |
  3    6ms     0/ 100 =  0%     0/ 100 =  0%  10.22.214.1
                                0/ 100 =  0%   |
  4    7ms     0/ 100 =  0%     0/ 100 =  0%  172.30.1.101
                                0/ 100 =  0%   |
  5    7ms     0/ 100 =  0%     0/ 100 =  0%  fed1oobl50.rd.sd.cox.cci [172.30.1.53]
                                0/ 100 =  0%   |
  6   14ms     0/ 100 =  0%     0/ 100 =  0%  12-215-4-26.client.mchsi.com [12.215.4.26]
                                0/ 100 =  0%   |
  7  ---     100/ 100 =100%   100/ 100 =100%  cr84.cgcil.ip.att.net [12.122.132.146]
                                0/ 100 =  0%   |
  8  ---     100/ 100 =100%   100/ 100 =100%  cr2.cgcil.ip.att.net [12.123.7.250]
                                0/ 100 =  0%   |
  9  ---     100/ 100 =100%   100/ 100 =100%  ggr3.cgcil.ip.att.net [12.122.132.17]
                                0/ 100 =  0%   |
 10   16ms     0/ 100 =  0%     0/ 100 =  0%  192.205.34.198
                                0/ 100 =  0%   |
 11   65ms     0/ 100 =  0%     0/ 100 =  0%  sjo-bb1-link.telia.net [213.248.80.25]
                                0/ 100 =  0%   |
 12   65ms     0/ 100 =  0%     0/ 100 =  0%  hurricane-113209-sjo-bb1.c.telia.net [213.248.86.54]
                                0/ 100 =  0%   |
 13   72ms     0/ 100 =  0%     0/ 100 =  0%  64.71.140.42
                                7/ 100 =  7%   |
 14   70ms     7/ 100 =  7%     0/ 100 =  0%  208.68.243.254
                                0/ 100 =  0%   |
 15   70ms     7/ 100 =  7%     0/ 100 =  0%  boinc2.ssl.berkeley.edu [208.68.240.13]

Trace complete.

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Hey, Wait a minute! Nobody ever said that the packet loss we all see is THE problem, it might not even be a problem. For all I know, the packet loss may have been there before any of the current issues started.

I was glad to see folks with Internet tools and experience join in the hunt.

Hopefully, the issue/s will be resolved before everyone runs out of work! The recovery is already going to be quite a stress test for the servers, I think.

Martin

Hey, Wait a minute! Nobody ever said that the packet loss we all see is THE problem, it might not even be a problem. For all I know, the packet loss may have been there before any of the current issues started.

Correct.
packet loss and slow traffic is what we see.
Just like a diagnostic in hospital, we see problems and we do more investigations.
I hope that somewhere we have ... Dr. House able to start a differential analysis.
We can only suggest more ideas ad do some test.

Bye,
Franz

---

Has everyone here seen the Saturday Night Live where William Shatner tells all the Trekkies to Get a Life, kiss a girl, etc. ???

Relax! Take a deep breath. Turn off BOINC and focus on something else.

I sincerely hope that this is not the most important thing in any of your lives (as some of you are making it sound to me). After all, none of these projects are about the data that is going back and forth between server and client. They are BIG PROJECTS that hopefully will benefit all humans some day (not today or next week). Don't act like SETI@Home is going to collapse if you leave. It will be fine, don't worry.

Now... Think positive for a moment.

When our computers run out of work, they will get a well deserved break!

BOINC projects will benefit from this in the future because it is times like this that lead to improvement (even if YOU don't ever see/feel it).

---

Not sure whatcha all are crying about. I just reported 37 results and downloaded 110 more tasks. Seems like everything is working fine...

---

IBA# 11465
http://imagesdesavions.com

No thank you, i already donate at least $6,ooo.oo a year in cpu time. they need to find appropriate funding, or just fold (pun intended). either i'm fine with, put just don't continue the way they are.

You must have terrible utility rates. I have double the number of computers running BOINC as you show, some at home and some at the office, and my combined utility expense, which includes non-BOINC things such as lights, TV, pool pump and refridgerator, barely tops $6,000 a year.

Holy ____, Batman! Where do you guys live? Are you talking US dollars?!?

I send less than $2000 to PECO (Philadelphia, PA) each year, and that includes heat, hot water, long showers/baths, etc.

What would you save if you didn't do any extra computing?

---

Ralf,
I was getting that message (only in english :-) ) on my machine too. I think you have to run the command prompt in administrater to get pathping to work in Vista or Windows 7.

You were right, thanks for your hint. I'll post the result in a moment.

Greetings

Ralf

Relax! Take a deep breath. Turn off BOINC and focus on something else.

Nope. I just let BOINC work on some other project for a while. It would take a large number of projects being down before I notice much.

---

BOINC WIKI

Nope. I just let BOINC work on some other project for a while. It would take a large number of projects being down before I notice much.

Time to take notice again, the floodgates have opened.

---

PROUD MEMBER OF Team Starfire World BOINC

Upload still does not work.

So here are my results from Aachen in Germany:

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. Alle Rechte vorbehalten.

C:\Windows\system32>pathping 208.68.240.16 boinc2.ssl.berkeley.edu

Routenverfolgung zu boinc2.ssl.berkeley.edu [208.68.240.13]
über maximal 30 Abschnitte:
  0  Ralf-PC [192.168.1.33]
  1  192.168.1.1
  2     *     rdsl-koln-de03.nw.mediaways.net [213.20.58.132]
  3  xmwc-koln-de01-chan-18.nw.mediaways.net [195.71.204.82]
  4  rmwc-koln-de02-gigaet-0-0-0.nw.mediaways.net [62.53.198.66]
  5  rmwc-dsdf-de02-ge-4-0-0-0.nw.mediaways.net [195.71.254.53]
  6  rmwc-dsdf-de01-chan-0-0.nw.mediaways.net [195.71.243.33]
  7  rmwc-frnk-de01-chan-3-0.nw.mediaways.net [195.71.254.145]
  8  xmws-frnk-de07-chan-2.nw.mediaways.net [213.20.249.202]
  9  de-cix.he.net [80.81.192.172]
 10  10gigabitethernet1-2.core1.par1.he.net [72.52.92.89]
 11  10gigabitethernet1-3.core1.lon1.he.net [72.52.92.33]
 12  10gigabitethernet4-4.core1.nyc4.he.net [72.52.92.241]
 13  10gigabitethernet1-2.core1.chi1.he.net [72.52.92.102]
 14  10gigabitethernet3-2.core1.sjc2.he.net [72.52.92.73]
 15  10gigabitethernet3-2.core1.pao1.he.net [72.52.92.69]
 16  64.71.140.42
 17  208.68.243.254
 18  boinc2.ssl.berkeley.edu [208.68.240.13]

Berechnung der Statistiken dauert ca. 450 Sekunden...
            Quelle zum Abs.  Knoten/Verbindung
Abs. Zeit   Verl./Ges.=   %  Verl./Ges.=   %  Adresse
  0                                           Ralf-PC [192.168.1.33]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.1.1
                                0/ 100 =  0%   |
  2  ---     100/ 100 =100%   100/ 100 =100%  rdsl-koln-de03.nw.mediaways.net [2
13.20.58.132]
                                0/ 100 =  0%   |
  3   21ms     0/ 100 =  0%     0/ 100 =  0%  xmwc-koln-de01-chan-18.nw.mediaway
s.net [195.71.204.82]
                                0/ 100 =  0%   |
  4   21ms     0/ 100 =  0%     0/ 100 =  0%  rmwc-koln-de02-gigaet-0-0-0.nw.med
iaways.net [62.53.198.66]
                                0/ 100 =  0%   |
  5   23ms     0/ 100 =  0%     0/ 100 =  0%  rmwc-dsdf-de02-ge-4-0-0-0.nw.media
ways.net [195.71.254.53]
                                0/ 100 =  0%   |
  6   26ms     0/ 100 =  0%     0/ 100 =  0%  rmwc-dsdf-de01-chan-0-0.nw.mediawa
ys.net [195.71.243.33]
                                0/ 100 =  0%   |
  7   25ms     0/ 100 =  0%     0/ 100 =  0%  rmwc-frnk-de01-chan-3-0.nw.mediawa
ys.net [195.71.254.145]
                                0/ 100 =  0%   |
  8   30ms     0/ 100 =  0%     0/ 100 =  0%  xmws-frnk-de07-chan-2.nw.mediaways
.net [213.20.249.202]
                                0/ 100 =  0%   |
  9   31ms     0/ 100 =  0%     0/ 100 =  0%  de-cix.he.net [80.81.192.172]
                                0/ 100 =  0%   |
 10   42ms     0/ 100 =  0%     0/ 100 =  0%  10gigabitethernet1-2.core1.par1.he
.net [72.52.92.89]
                                0/ 100 =  0%   |
 11   44ms     0/ 100 =  0%     0/ 100 =  0%  10gigabitethernet1-3.core1.lon1.he
.net [72.52.92.33]
                                0/ 100 =  0%   |
 12  112ms     0/ 100 =  0%     0/ 100 =  0%  10gigabitethernet4-4.core1.nyc4.he
.net [72.52.92.241]
                                0/ 100 =  0%   |
 13  133ms     0/ 100 =  0%     0/ 100 =  0%  10gigabitethernet1-2.core1.chi1.he
.net [72.52.92.102]
                                0/ 100 =  0%   |
 14  189ms     0/ 100 =  0%     0/ 100 =  0%  10gigabitethernet3-2.core1.sjc2.he
.net [72.52.92.73]
                                0/ 100 =  0%   |
 15  190ms     0/ 100 =  0%     0/ 100 =  0%  10gigabitethernet3-2.core1.pao1.he
.net [72.52.92.69]
                                0/ 100 =  0%   |
 16  195ms     0/ 100 =  0%     0/ 100 =  0%  64.71.140.42
                               13/ 100 = 13%   |
 17  254ms    18/ 100 = 18%     5/ 100 =  5%  208.68.243.254
                                0/ 100 =  0%   |
 18  261ms    13/ 100 = 13%     0/ 100 =  0%  boinc2.ssl.berkeley.edu [208.68.24
0.13]

Ablaufverfolgung beendet.

C:\Windows\system32>

All of my uploads came through now!

Thanks for your good work, SETI guys! I'm sure you shed some blood, sweat and tears!

Regards from Germany

Ralf

I just got 38 cuda tasks that all failed in 3 seconds. I hope this isn't something that is going to go on from all the downtime.

---

Results are trickling through guys, excellent timing I had 3 WU's left on my Quad core!

Excellent work, you deserve a break now!

D

---

Cheers
D

I just got 38 cuda tasks that all failed in 3 seconds. I hope this isn't something that is going to go on from all the downtime.

Just checked your hosts. Three of them have batches of ....

.... VLAR tasks.

You run the VLAR-killer application. You get VLAR. It kills them. That's what it does.

You beat me to it Richard, just checked the same thing.

---

PROUD MEMBER OF Team Starfire World BOINC

I am not killing off any tasks on this system. I finally seem to have gotten GPU tasks that are working correctly.

---

Brkovip,

You are running the optimized Apps, if you installed with the handy-dandy installer it probably gave you the VLAR-killer. When you see your work units giving a -6 error that is your VLAR-killer in action.

---

PROUD MEMBER OF Team Starfire World BOINC