I've always been fascinated by the resurgence of complainers every time Seti has a hiccup. Usually we go 3 to 4 months between bad weekend. BIG DEAL s**t happens.

I have 15 projects in my Boinc Manager....

You aren't a member of Orbit?

Turned loose a bunch of workunits in June last year. Took many times longer than estimated, and ate up hundreds of megabytes of disk space (and often didn't validate). Prime (sole?) developer hasn't posted anything of significance for 247 days. Independent "front page" website has only had one (derivative) update since 6 October 2008.

Prime (sole?) developer hasn't posted anything of significance for 247 days.

Did you miss Pasquale's post then? It happened on the 29 Jan 2009, which as far as I know isn't 247 days ago. Not even when you're counting in those 42 hour days. ;-)

---

Prime (sole?) developer hasn't posted anything of significance for 247 days.

Did you miss Pasquale's post then? It happened on the 29 Jan 2009, which as far as I know isn't 247 days ago. Not even when you're counting in those 42 hour days. ;-)

You mean "The server will be down for power interruptions for the next few days...", "...in the last few months we have been busy analyzing the results...", "We don't anticipate yet a date for the initial public testing.".

In the context of this debate, that counts as hot air and waffle. It doesn't come under my definition of "significance".

[I wish I didn't have to say that. Orbit is one of only seven projects I've ever joined - five projects, if you don't count Beta projects separately from their parents. I want to crunch for it, because I think it's equally important for the future development of the human race as SETI. But all they've run so far are simulations]

---

It seems that some SETI BOINC advocates take umbrage at SETI being categorized as a high maintenance BOINC project -- they may have a point. I'd say it is a 'more maintenance' project compared to low maintenance projects like Climate, Einstein and a number of others. What SETI does have going for it are a number of dedicated support folks. It also has the highest volume of BOINC processing by far and that alone tends to make for somewhat more frequent 'interesting times' as well as longer recovery cycles. I am assuming that BOINC SETI advocates would acknowledge that.

SETI is probably running on the biggest collection of "scrounged" hardware anywhere in the known BOINC universe.

That doesn't help when times are tough.

I'd definitely call myself a BOINC SETI advocate. I think there are things that the BOINC client should do that would mitigate the problems somewhat, and Matt's post today in technical news is about one of those spots where BOINC should back down, and doesn't.

If they could slow BOINC down to keep a sustained 90% bandwidth use, things could charge along stunningly well. It's when you try to get to 105% that things get really yucky.

All of that said, I'm impressed with how well things do work.

---

For that, check the progress column in the Transfers tab. :-)

:-) That's where I am:

Project: SETI@home
File: 16ja09ab...
Progress: 100.00%
Size: 28.17/28.17 KB
Elapsed Time: 13:20
Speed: 0.00 KBps
Status: Retry in 03:12:46 (and counting)

2 of my uploads are like this.

I currently have 11 like that! Show totally transfered but for some reason still want to retry?!

---

My last upload finally made the trip home. I'm now crunching away on new WUs.

---

PROUD MEMBER OF Team Starfire World BOINC

For the whingers............

http://setiathome.berkeley.edu/tech_news.php

I wish they could fix the system so it would accept the ones that make it to 100% upload and not set the upload time to start over.
I currently have 6 units at 100% of the 9 work units trying to upload.
Timer is counting down to re-upload the those 6.
If I have more than half of mine are at 100% I wonder how many other users are out there that are in the same boat.....
If they could fix this problem it would go a long way fixing the traffic problem.

I'm no tekkie but I think the response time to acknowledge a data transmission Is Not readily programmable, I get LOTS of 100% stuff that gets re-sent because the server was too busy to acknowledge in the time my system expected it. It's like trying to drain lake Superior into the colorado river through a fire hose in one day. To fix the problem you ask them to reprogram every internet connection - NICE TRICK IF IT COULD BE DONE. The ultimate solution is to consider that the MAIN goal is to FIND ALIENS, and this may take your lifetime AND MINE ( pushing 70 ) and if their system hiccups - at least you never get left in the cold- eventually it all winds up making muffins.

The problem could be in Boinc software. Maybe they could give the server more time to reply before setting the count down timer for another try....

---

Here's what I get:

2/23/2009 9:48:06 PM|SETI@home|Temporarily failed upload of 14ja09aa.29048.1295.15.8.146_0_0: HTTP error
2/23/2009 9:48:06 PM|SETI@home|Backing off 40 min 51 sec on upload of 14ja09aa.29048.1295.15.8.146_0_0
2/23/2009 9:48:06 PM|SETI@home|Started upload of 16ja09aa.24128.2526.10.8.87_0_0
2/23/2009 9:48:07 PM||Internet access OK - project servers may be temporarily down.


Anyone else having problems uploading Finished WUs?

Thanks!

---

350+ GHZ of power for the PC Perspective Seti Team We Are The Uncle B's

Hi, just to let you know, everybody is having trouble uploading and downloading. If you look at the message boards, this thread has been repeated multiple times. Matt provides a form of explanation here:-

Matt's Post

regards, Gizbar.

---

A proud GPU User Server Donor!

Yep, there has been massive gridlock getting to the project since the beginning of last weekend.

Things were just starting to free up yesterday. Probably will take until later in the week for everything to clear and get back to more or less normal.

Alinator

I am going through the same dilema, cant upload completed work, are the servers down or is this a generated message as its been going onfor days now?

---

But it IS the *biggest* collection of hardware <smile>. A lot of hardware, with a LOT of duct tape.

One thing I'd like to see in a future iteration of the client, is for users to have the ability to *at the project level* to choose 'no network traffic'.

---

Wow! The cricket graph isn't maxed out anymore! I just checked at 1300utc and it was down to 87mbit. Still pretty high up there, but not maxed out, which means any connections should go through the first try. Pretty impressive.. the recovery happened a little faster than Matt expected. He was thinking it would begin to settle down toward the end of the day PST, but the sun hasn't even risen there yet.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

LOL...

Yep, and they just set a new record for the longest period of sustained max bandwidth since the switch to Hurricane! :-)

Of course, it's a much better user experience with things working more or less correctly again. My hosts didn't seem to care too much either way though. ;-)

Alinator

Does anyone know why the neither AP_validate is running? They both say "Not Running" Expanation is "Program failed or ran out of work". I don't think they ran out of work.

Also do they pertain to both AP 5.00 and 5.03?

---

Don't know why but it seems that Berkeley takes down the AP validators at the first sign of problems.

And since I prefere to crunch AP it really hurts.

---

Boinc....Boinc....Boinc....Boinc....

looks like the credits aren't getting moved along. I see that I have 26000 more credits on my page yet the stats are still sitting back from a couple days ago.

---

In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope

Had about 6-10 wu's to report, waited for 4 complete days, it reported succesfully. Now my reports are going perfect, up- and downloads are going well now...Good job to the SETI team...bravo!

Mark

---

To boldly go where no human has gone before!

Does anyone know why the neither AP_validate is running? They both say "Not Running" Expanation is "Program failed or ran out of work". I don't think they ran out of work.

They're both back online now ;-)