I wouldnt worry too much, the setup at their end is very technical and as with most things hiccups occur, enjoy yourself and if you run out crunch a little somewhere else for a while :)

---

http://timmygadget.blogspot.com/
http://www.mikesbawx.org/~timmygadget/

The Froxen Penny has about 120 or so it would like to report...............

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

115 uploads waiting across two fairly ordinary machines here.

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

115 uploads waiting across two fairly ordinary machines here.

And another 100 plus WU's, waiting to UPLoad, on 3 host's, here is a piece off BOINC's logfile, from the QX9650 @3350MHz

zo 10 aug 2008 15:55:55 CEST|SETI@home|Started upload of 18jn08aa.14017.2526.9.8.64_1_0
zo 10 aug 2008 15:55:55 CEST|SETI@home|Started upload of 19jn08aa.905.16023.8.8.131_1_0
zo 10 aug 2008 15:55:55 CEST|SETI@home|Restarting task ap_04jl08ab_B0_P0_00160_20080807_29767.wu_1 using astropulse version 435
zo 10 aug 2008 15:55:55 CEST|SETI@home|Restarting task ap_04jl08ab_B0_P0_00243_20080807_29767.wu_1 using astropulse version 435
zo 10 aug 2008 15:55:55 CEST|SETI@home|Restarting task 19jn08ac.2890.2117.8.8.222_0 using setiathome_enhanced version 527
zo 10 aug 2008 15:55:55 CEST|SETI@home|Restarting task 19jn08aa.6949.16432.12.8.70_1 using setiathome_enhanced version 527
zo 10 aug 2008 15:55:57 CEST|SETI@home|Temporarily failed upload of 18jn08aa.14017.2526.9.8.64_1_0: can't resolve hostname
zo 10 aug 2008 15:55:57 CEST|SETI@home|Backing off 3 hr 57 min 39 sec on upload of 18jn08aa.14017.2526.9.8.64_1_0
zo 10 aug 2008 15:55:57 CEST|SETI@home|Temporarily failed upload of 19jn08aa.905.16023.8.8.131_1_0: can't resolve hostname
zo 10 aug 2008 15:55:57 CEST|SETI@home|Backing off 44 min 26 sec on upload of 19jn08aa.905.16023.8.8.131_1_0
zo 10 aug 2008 15:55:57 CEST|SETI@home|Started upload of 17jn08ad.32708.16843.10.8.195_2_0
zo 10 aug 2008 15:56:03 CEST|SETI@home|Temporarily failed upload of 17jn08ad.32708.16843.10.8.195_2_0: system connect
zo 10 aug 2008 15:56:03 CEST|SETI@home|Backing off 2 hr 38 min 18 sec on upload of 17jn08ad.32708.16843.10.8.195_2_0
zo 10 aug 2008 15:58:47 CEST|SETI@home|Started upload of 19jn08aa.905.18886.8.8.170_1_0
zo 10 aug 2008 15:58:49 CEST||Project communication failed: attempting access to reference site
zo 10 aug 2008 15:58:49 CEST|SETI@home|Temporarily failed upload of 19jn08aa.905.18886.8.8.170_1_0: system connect
zo 10 aug 2008 15:58:49 CEST|SETI@home|Backing off 1 hr 43 min 1 sec on upload of 19jn08aa.905.18886.8.8.170_1_0
zo 10 aug 2008 15:58:51 CEST||Access to reference site succeeded - project servers may be temporarily down.
zo 10 aug 2008 15:59:09 CEST|SETI@home|Started upload of 19jn08aa.9137.890.9.8.91_0_0
zo 10 aug 2008 15:59:12 CEST||Project communication failed: attempting access to reference site
zo 10 aug 2008 15:59:12 CEST|SETI@home|Temporarily failed upload of 19jn08aa.9137.890.9.8.91_0_0: system connect
zo 10 aug 2008 15:59:12 CEST|SETI@home|Backing off 3 hr 12 min 20 sec on upload of 19jn08aa.9137.890.9.8.91_0_0
zo 10 aug 2008 15:59:18 CEST||Access to reference site succeeded - project servers may be temporarily down.

---

It sounds like there will be a considerable backlog by the time the servers get going again. They could even run out of work units as well because there will be a high demand. Anyone short of work should try to select another project as a reserve. There are plenty of worthy causes to choose from, apart from LHC which seems to be out of work at the moment. If you set the new project to a low share of your computer time, Seti will kick in as soon as it is available because of its higher share plus backlog time. Let the other WU finish, though, otherwise the crunching time will be wasted.

Climate Prediction (CPDN) is a good reserve because, although the WUs are a lot bigger, the results trickle up as they go and all count even if not finished and you have about a year to finish anyway.

Mike

I have two finished WU, for the past few hours, I cant seems to be able to upload them, I get this:
Sun 10 Aug 2008 06:54:59 PM IDT|SETI@home|Started upload of 19jn08aa.18915.4980.10.8.50_0_0
Sun 10 Aug 2008 06:55:01 PM IDT||Project communication failed: attempting access to reference site
Sun 10 Aug 2008 06:55:01 PM IDT|SETI@home|Temporarily failed upload of 19jn08aa.18915.4980.10.8.50_0_0: connect() failed
Sun 10 Aug 2008 06:55:01 PM IDT|SETI@home|Backing off 3 hr 3 min 12 sec on upload of 19jn08aa.18915.4980.10.8.50_0_0
Sun 10 Aug 2008 06:55:03 PM IDT||Internet access OK - project servers may be temporarily down.

are the servers down or something? another strange this is that I got the connect() failed.

I'm using an self compiled 6.2.16 on linux 64 bit

---

With all the problems i'm quite glad that I don't crunch that much anymore.

---

please point me to an other crunch job who has more stable servers (up-download)

possible it´s better to run true idletime..ie, waist cycles..Seti@ is fkdup

I'm sure you meant "waste" -- or you might be talking about an exercise bike?

SETI is only problematic if we apply the wrong standards. This isn't like Amazon.com where servers down means lost dollars.

For a BOINC project, server problems are an inconvenience. It leads to congestion when they're back up, and that is an inconvenience.

All of the waiting uploads, downloads and reports will be done when the servers are back.

There are two answers:

1) Crunch several projects. Find the ones that interest you and spread the wealth.

2) Run a larger cache of work: set "connect every 'x' days" to 1, and set "extra days" to 10.

I don't run a large cache, and I'm still 40 hours from running out of work.

I only crunch SETI and SETI Beta -- and if one is sick, the other tends to be as well.

No worries, they'll get well.

---

I started with S@H back in 1999 and have stayed through various computers till now I am running a Quad and 3 Duels, 2 of the duels are simply crunchers. My intrest is in SETI, I have no desire to crunch for another project. I also do not want Astroplulse WU's, this is supposed to be a "spare CPU cyles" project, but a WU that can last 50+ hours is no way a "spare CPU cyles" project. I don't run 24/7 just evenings and weekends possibly 50-60 hors per week, see the problem. To be 100% sure of not missing targets these Astropulse WU will need minimum 3 weeks otherwise I WILL miss some. My Quad has 2 MB WU's currently sitting in it's upload queue that have a date for Tuesday so they will fail.

I feel like several others here that the changes made to accomadate Astropulse have helped cause the current problems.

Please can we have a stable platform for at least a week so I can finally clear my 100+ WU's and consider my future with S@H, if it has to include Astropulse count me out.

---

just evenings and weekends possibly 50-60 hors per week, see the

Busy boy! You must be on some sort of stimulant to do that! ;-}

Me too, me too!!!!

8/10/2008 5:17:37 PM|SETI@home|Started upload of 31mr08ab.10835.13160.4.8.123_2_0
8/10/2008 5:17:59 PM|SETI@home|Temporarily failed upload of 31mr08ab.10835.13160.4.8.123_2_0: system connect
8/10/2008 5:17:59 PM|SETI@home|Backing off 1 hr 10 min 49 sec on upload of 31mr08ab.10835.13160.4.8.123_2_0


Vista sp1, 5.10.45

All other projects seem to be working.

I started with S@H back in 1999 and have stayed through various computers till now I am running a Quad and 3 Duels, 2 of the duels are simply crunchers. My intrest is in SETI, I have no desire to crunch for another project. I also do not want Astroplulse WU's, this is supposed to be a "spare CPU cyles" project, but a WU that can last 50+ hours is no way a "spare CPU cyles" project.

Don't tell that to CPDN. Yet many people run it on "spare".

I feel like several others here that the changes made to accomadate Astropulse have helped cause the current problems.

Please can we have a stable platform for at least a week so I can finally clear my 100+ WU's and consider my future with S@H, if it has to include Astropulse count me out.

How are they to iron out the issues if they never find the problems only apparent when released full scale?

I started with S@H back in 1999 and have stayed through various computers till now I am running a Quad and 3 Duels, 2 of the duels are simply crunchers. My intrest is in SETI, I have no desire to crunch for another project. I also do not want Astroplulse WU's, this is supposed to be a "spare CPU cyles" project, but a WU that can last 50+ hours is no way a "spare CPU cyles" project.

Don't tell that to CPDN. Yet many people run it on "spare".

AFAIK CPDN used additional mechanisms to handle long WU runtimes.
AP needs 2 such mechanisms:
1) ability to report partially done WU (w/o it any "out of memory" failure (for example) will lead to waste few days of hard work - not very nice situation.
2) ability to grant credit gradually (although I personally consider this issue far less meaningful as first one, there are many participants who will be angry not getting their earned credits for a weeks or even ~month).

None of those were implemented before release.

I started with S@H back in 1999 and have stayed through various computers till now I am running a Quad and 3 Duels, 2 of the duels are simply crunchers. My intrest is in SETI, I have no desire to crunch for another project. I also do not want Astroplulse WU's, this is supposed to be a "spare CPU cyles" project, but a WU that can last 50+ hours is no way a "spare CPU cyles" project.

Don't tell that to CPDN. Yet many people run it on "spare".

AFAIK CPDN used additional mechanisms to handle long WU runtimes.
AP needs 2 such mechanisms:
1) ability to report partially done WU (w/o it any "out of memory" failure (for example) will lead to waste few days of hard work - not very nice situation.
2) ability to grant credit gradually (although I personally consider this issue far less meaningful as first one, there are many participants who will be angry not getting their earned credits for a weeks or even ~month).

None of those were implemented before release.

Those points are moot. Fact is, CPDN has long WU run times and it runs under BOINC whose goal is to harness all the "spare" CPU cycles of all volunteers.

I started with S@H back in 1999 and have stayed through various computers till now I am running a Quad and 3 Duels, 2 of the duels are simply crunchers. My intrest is in SETI, I have no desire to crunch for another project. I also do not want Astroplulse WU's, this is supposed to be a "spare CPU cyles" project, but a WU that can last 50+ hours is no way a "spare CPU cyles" project.

Don't tell that to CPDN. Yet many people run it on "spare".

AFAIK CPDN used additional mechanisms to handle long WU runtimes.
AP needs 2 such mechanisms:
1) ability to report partially done WU (w/o it any "out of memory" failure (for example) will lead to waste few days of hard work - not very nice situation.
2) ability to grant credit gradually (although I personally consider this issue far less meaningful as first one, there are many participants who will be angry not getting their earned credits for a weeks or even ~month).

None of those were implemented before release.

I think there is a difference between AP (at 6 or 7 days of crunching on my slow machine) and CPDN which runs months or years.

---

I'm getting a different message on my uploads...

11/08/2008 6:02:33 p.m.|SETI@home|Started upload of 11jn08ab.29238.259163.10.8.57_0_0
11/08/2008 6:03:57 p.m.|SETI@home|Temporarily failed upload of 11jn08ab.29238.259163.10.8.63_0_0: http error
11/08/2008 6:03:57 p.m.|SETI@home|Backing off 2 hr 54 min 49 sec on upload of 11jn08ab.29238.259163.10.8.63_0_0

Mine appears to be different by the http error at the end...

EDIT : And their deadline is on the 16th! Hope it gets fixed before then...

---

- Luke.

Always the same story.

Technical problems imediatly lead to complaints and angry posts about quality of service.
Solution purposed is running a large cache.

When evrything is working the discussion about large workcache is restarted.

If in the future some one again questions why i run a 10 day cache Read his post first please.

---

Always the same story.

Technical problems imediatly lead to complaints and angry posts about quality of service.
Solution purposed is running a large cache.

When evrything is working the discussion about large workcache is restarted.

If in the future some one again questions why i run a 10 day cache Read his post first please.

Same here. I have always (selfishly?) carried a large cache, but then I don't sweat when there is a problem like now. My machines are merrily chomping away on work and will be able to do so for a few days yet.

---

Same here. I have always (selfishly?) carried a large cache, but then I don't sweat when there is a problem like now. My machines are merrily chomping away on work and will be able to do so for a few days yet.

Most of my machines have 10 days work cache. The one I am using at the moment was set to 7 before this issue arose (changed it to 10 now). According to that, it should still have 3 more days of work, but I guess it had some gastronomical problem and has already finished most of the work. It will run dry in another 10 hours or so...

Hmm... I am confused, should I compliment this system or reprimand it :-)

---