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.

Seems to always happen on a weekend! I'm lucky that some of my slower machines are still trying to crank out AP units, but my newer units are about to run on empty, and my LHC@home has had no work for a while, but that is expected so not upsetting. A year ago when this was far more frequesnt, I set my default to 8 days as protection, but set it back after long periods of up-time.

I don't care as much about sending in the completes as I do in filling my pipe.
Maybe I'll get lucky and receive something within the 4:22:02 I have left on this machine.

At least some communication today would have been nice.

---

That's then a bug in 6.4.5 ... and already fixed in 6.6.x ;-)

---

It's just that it managed to get all the way through but did not receive an acknowledgement from the server. It will go when the retry time is up

---

PROUD MEMBER OF Team Starfire World BOINC

I do read the woods but i havent seen any thing from the man since he posted it. I would like to see the mods here or a few tetsters get the straight scoop from the man so They can tell us whats up. As far as the server page goes that thing is useless.

---

[/quote]

Old James

OK it's 18:00+ in the UK, 10am in seti land, is anything being done to resolve this. On the "Technical" board any chance of a thread with a sensible title? And one that syas some thing of use would be nice, I know they are voulentees and all that but without us crunchers they are pointless.

---

After reading 2 hours on numerous posts related to this. I agree ... It's sad to see such a large and important project, with so many dedicated Crunchers tell people: Look around at other posts, you will find your answer. The appearance of late seems to be, SETI is acting like it is to big for it's britches, users will not tolerate donating crunching time to a project that does not show appreciation, for what we are doing or our concerns enough to post on the main www page the problems/resolutions. To Bad ...this was a good, reliable project over the years. This seems to be a downhill slide here. I guess they figure that when we stop crunching for them new users will join and take over where we left off. FWTW

/obnoxious rant

---

Well it was updating yesterday getting to 100% on the upload then quitting the upload and retrying later. I assume this has to do with the server failing to confirm the upload with the client.

---

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

Yeah but they will have the CUDA card sand tricked out opt apps! not like us unwashed stock users;

---

[/quote]

Old James

Well it was updating yesterday getting to 100% on the upload then quitting the upload and retrying later. I assume this has to do with the server failing to confirm the upload with the client.

Isn't that what I said? Oh, and I may be wrong about it going on the retry. Looks like it's stalled again. :(

---

PROUD MEMBER OF Team Starfire World BOINC

I was told on another therd I should pay up if I want to crunch, to be more accurate I was told: If I can afford to build a cruncher I can afford to pay. "B**l*ks" (vowels removed) I was about to donate, but not now, that comment from a beta tested with a low rac and total and less than a year's crunching typifies this projects current outlook. I'm not going to get to my 10 years in June at this rate.

It does not take much to consider your customers, because thats what we are, do some thing simple like not pressing the release button last thing on friday! Schoolboy error number one; if you can't support it don't release it.

---

Oh, and I may be wrong about it going on the retry. Looks like it's stalled again. :(

My 2 results finally just went thru.

Just made a stock checking on my home rigs, 893 WUs waiting upload. No idea how many are waiting in my office systems to which I have no access presently. My estimate is around 200. So all in all around 1000+ or so. CUDA rig and laptop are dry, two more running on fumes.

This has gone too long this time...
______________

---

May 16 I will have ten years. Depending on what happens every weekend .I might leave it to the Ober crunchers with the big bucks.

---

[/quote]

Old James

I guess they figure that when we stop crunching for them new users will join and take over where we left off.

Corporate thinking!!!!!!!!

---

It does not take much to consider your customers, because thats what we are, do some thing simple like not pressing the release button last thing on friday! Schoolboy error number one; if you can't support it don't release it.

i totally agree with you.

how about this? as much users as possible shall just stop any work for seti, just to show them that they should just take their job seriously.
I mean some kind of boykott against this project and unless they do whatever it takes to fix their infrastructure.
if just 10% of the active users (the top 10%) or more would just drop the work, it is a significant drop of workunits beeing processed for them.

may we can raise up some pressure that way.

---

NOT that it make sense, but UPped my cache to 7 days and gonna make that 10 days :), NO WORK and NO UPload, bummer :(
No, just annoying and kidding, but IT IS a BIG out(r)age!?
Maybe tommorow, maintenance day, then, I hope, they'll fixe 'it'.
Last BOINC (6.4.5.) logfile:
21-2-2009 20:19:10||Internet access OK - project servers may be temporarily down.
21-2-2009 20:20:06||Project communication failed: attempting access to reference site
21-2-2009 20:20:06|SETI@home|Temporarily failed upload of 15ja09aa.22215.1708.5.8.160_0_0: HTTP error
21-2-2009 20:20:06|SETI@home|Backing off 20 min 10 sec on upload of 15ja09aa.22215.1708.5.8.160_0_0
22-2-2009 0:31:20|SETI@home|Backing off 1 min 0 sec on upload of 16ja09aa.21944.27772.5.8.251_0_0
22-2-2009 0:31:21||Internet access OK - project servers may be temporarily down.
22-2-2009 0:31:21|SETI@home|Started upload of 16ja09aa.21944.27772.5.8.233_0_0
22-2-2009 0:32:36||Project communication failed: attempting access to reference site
22-2-2009 0:32:36|SETI@home|Temporarily failed upload of 16ja09aa.21944.27772.5.8.245_0_0: HTTP error
22-2-2009 0:32:36|SETI@home|Backing off 1 min 0 sec on upload of 16ja09aa.21944.27772.5.8.245_0_0
22-2-2009 16:40:44|SETI@home|Started upload of 16ja09ab.13627.24612.8.8.117_0_0
22-2-2009 16:40:45||Internet access OK - project servers may be temporarily down.
22-2-2009 16:41:05||Project communication failed: attempting access to reference site
22-2-2009 16:41:05|SETI@home|Temporarily failed upload of 16ja09ab.13627.24612.8.8.117_0_0: connect() failed
22-2-2009 16:41:05|SETI@home|Backing off 30 min 51 sec on upload of 16ja09ab.13627.24612.8.8.117_0_0
22-2-2009 21:41:49|Einstein@Home|Started download of einstein_S5R5_3.01_windows_intelx86.exe
22-2-2009 21:41:49|Einstein@Home|Started download of einstein_S5R5_3.01_windows_intelx86_0.exe
22-2-2009 21:41:50||Project communication failed: attempting access to reference site
22-2-2009 21:41:50|SETI@home|Temporarily failed upload of 16ja09ab.2474.10297.5.8.147_1_0: connect() failed
22-2-2009 21:41:50|SETI@home|Backing off 3 hr 46 min 31 sec on upload of 16ja09ab.2474.10297.5.8.147_1_0
22-2-2009 21:41:50|SETI@home|Started upload of 16ja09ab.2474.10297.5.8.133_0_0
22-2-2009 21:42:46|SETI@home|Started upload of 16ja09ab.2474.10297.5.8.120_0_0

23-2-2009 12:58:35||Project communication failed: attempting access to reference site
23-2-2009 12:58:35|SETI@home|Temporarily failed upload of 15ja09aa.3377.9888.9.8.149_0_0: HTTP error
23-2-2009 14:23:08|SETI@home|Temporarily failed upload of 16ja09aa.24128.7843.10.8.14_0_0: connect() failed
23-2-2009 14:23:08|SETI@home|Backing off 1 hr 50 min 33 sec on upload of 16ja09aa.24128.7843.10.8.14_0_0
23-2-2009 14:23:09||Internet access OK - project servers may be temporarily down.
23-2-2009 17:21:23||Project communication failed: attempting access to reference site
23-2-2009 17:21:23|SETI@home|Temporarily failed upload of 16ja09ab.13627.20113.8.8.177_0_0: connect() failed
23-2-2009 19:26:35||Internet access OK - project servers may be temporarily[ADDED]/PERMANENTLY down.
All hosts are now crunching EINSTEIN@home's WU's, NO SETI WU's otherwise, I would have turned the PC's off and take a few days of myself, which is tempting ;), I must admit.
Why DOES ''IT', take that long, to see and arrange (a temporary) solution?
Could be easier said then done, hope you can fix this, otherwise it would be wednesday afternoon/evening.
Otherwise, more 'traffic', would be generated, through forum pages.
But, keep on crunching, anyway . . .

---

Well i think i might have to suspend seti on friday and turn it back on on wednesday. let milkyway@home get some time in. seems thats how its working anyway.

---

[/quote]

Old James

Possible Corporate thinking, From a non profit edu. Great …that is just what we need more of. NOT!
I would implore SETI admins to look at other projects (like that will happen).The Spinhenge@home main server has been continuously up for 105 days 10 hours 35 minutes and has 233,090 Results ready to send, with a server status page that works. FWTW

---

I was told on another therd I should pay up if I want to crunch, to be more accurate I was told: If I can afford to build a cruncher I can afford to pay. ....

Yeah, I couldn't believe what I was reading, then I looked around a bit and realized that seems to be the attitude. 10 years crunching off and on and that's what you get, SETI turned into IBM somewhere along the way.