I've experienced my first upload failure as well, Maybe it's the entire 14mr04aa.17223 group of WU's? did you notice that Peder's WU failure and mine match sort of?

SETI@home - 2004-10-12 05:25:30 - Started upload of 14mr04aa.17223.10530.711070.123_0_0
SETI@home - 2004-10-12 05:25:37 - Error on file upload: file_upload_handler: no filename; nbytes 12177.000000
SETI@home - 2004-10-12 05:25:37 - Permanently failed upload of 14mr04aa.17223.10530.711070.123_0_0
SETI@home - 2004-10-12 05:25:37 - Giving up on upload of 14mr04aa.17223.10530.711070.123_0_0: server rejected file


After rereading this whole post,I notice the same 14mr04aa.17223 is the most common upload failure WU group

---

This is my second failed upload. I have 4 more WUs in Cache w/ the same date. After the first failed upload I did a reset of the project.

SETI@home - 2004-10-12 11:32:09 - Started upload of 01mr04aa.18860.514.117328.94_1_0
SETI@home - 2004-10-12 11:32:16 - Error on file upload: file_upload_handler: no filename; nbytes 9501.000000
SETI@home - 2004-10-12 11:32:16 - Permanently failed upload of 01mr04aa.18860.514.117328.94_1_0
SETI@home - 2004-10-12 11:32:16 - Giving up on upload of 01mr04aa.18860.514.117328.94_1_0: server rejected file

---

<img src=\"http://boinc.mundayweb.com/seti2/stats.php?userID=1180&trans=off\">

Heres a thought... if the servers @ UCB have been up and down doing hard reboots and disk re-syncs, is it possible that some of the data has become corrupt and therefore lost.

Think about it. We downloaded WU's from server. We process the WU's and return them to the servers... but if the servers no longer have a record of these files (WU's) then the server would reject all files it can not validate.

Looking back on the error messages people have posted there does seem to be many WU's from "mr" (march) that wont return to servers correctly.

--Long Live the Nova--

Hadn't thought of that NovaPaul. Sounds believable to me... In fact it sounds highly probable.

Anyhow, overnight the 1900+ successfully sent that long awaited WU back with no errors.

---

> Hadn't thought of that NovaPaul. Sounds believable to me... In fact it sounds
> highly probable.
>
> Anyhow, overnight the 1900+ successfully sent that long awaited WU back with
> no errors.
>
>
>

I am still uploading here ok.Reset yesterdayand got loads of 01mr04aa wu's.I think the 14mr wu's are the one's which are mostly getting errors.I notice that 01mr04aa wu's are completing in one and and a half faster too.I am still using 4.09 and hope it carries on working ok.Been ok now for about 20 hours.Doing 2 wu's(ht) in about 4 hours and 50 mins.It was taking 6 and a half hours with 4.09 with other wu's.

---

......In Space No One Can Hear You Scream......

Hi!

This is my 29 failed upload ....

SETI@home - 2004-10-12 08:11:28 - Giving up on upload of 01mr04aa.18860.7249.454810.98_1 : server rejected file

:(

---

---

> I've experienced my first upload failure as well, Maybe it's the entire
> 14mr04aa.17223 group of WU's? did you notice that Peder's WU failure and mine
> match sort of?
>
> SETI@home - 2004-10-12 05:25:30 - Started upload of
> 14mr04aa.17223.10530.711070.123_0_0
> SETI@home - 2004-10-12 05:25:37 - Error on file upload: file_upload_handler:
> no filename; nbytes 12177.000000
> SETI@home - 2004-10-12 05:25:37 - Permanently failed upload of
> 14mr04aa.17223.10530.711070.123_0_0
> SETI@home - 2004-10-12 05:25:37 - Giving up on upload of
> 14mr04aa.17223.10530.711070.123_0_0: server rejected file
>

Hm, and here I have one that did upload correctly - even thought it came from the same day!


SETI@home - 2004-10-12 13:07:26 - Computation for result 04mr04aa.22434.9362.436050.139 finished

SETI@home - 2004-10-12 13:07:26 - Starting result 04mr04aa.22434.9362.436050.132_1
SETI@home - 2004-10-12 13:07:26 - Started upload of 04mr04aa.22434.9362.436050.139_1_0
SETI@home - 2004-10-12 13:07:34 - Finished upload of 04mr04aa.22434.9362.436050.139_1_0

I look at one of my other computers and it seems to upload properly even though it is 04mr04aa's.

---

Happy crunching

> I am still uploading here ok.Reset yesterdayand got loads of 01mr04aa wu's.I
> think the 14mr wu's are the one's which are mostly getting errors.I notice
> that 01mr04aa wu's are completing in one and and a half faster too.I am still
> using 4.09 and hope it carries on working ok.Been ok now for about 20
> hours.Doing 2 wu's(ht) in about 4 hours and 50 mins.It was taking 6 and a half
> hours with 4.09 with other wu's.
>

Rachel,

I just had one of those 01mr04aa wu's that shows a failed upload, so I guess that blows that possiblility. :-(

Hi Everyone.

I had losts of 14mr WU's and so i reset my project thus deleting all work. Now i have fresh new workunits from 01mr with only one WU from 14mr.

So far one of the 01mr has uploaded sucessfully. im waiting for the 14mr to complete. I will keep you all posted. Im 90% sure that it is a set of Wu's that the server had lost or that theyre damaged on the server side, therefore as you upload them the server has no recollection of it.

Lets hope our Devs see this and stop sendings us the 14 mr units soon.

Failed on upload of WU from 14mr and success on WUs from 01mr.

---

Lots of "Temporarily failed upload" at my end right now. Both LHC and SAH. Earlier today I had an permanent giving up on an LHC wu.

It might just as well be a BOINC backend bug, as a client one.

---

The Alpha test of BOINC that can be downloaded here ( http://setiboincdata.ssl.berkeley.edu/boinc_alpha/download.php ) fixed all my problems. And it is crunching away fine on both SETI and LHC

---

Ups. But be aware that there might be a problem on P4 HT machines. Sorry

---

> Paul, you make a very logical point. Very good! Uhh, in you "true
> story", you referenced an A7 aircraft. Was that a "missprint" in that you
> were talking about an A2 module? Or did you forget to reference the A2
> aircraft? I really do not know a lot about aviation, even though I work in
> GA. We have an avionics hangar but obviously do not work on WRAs.

My first squadren was an A7B outfit ... when we forward deployed to Japan (USS Midway) my squadron had to turn in the A7B's we had and take over A7A's that we were issued. If I recall correctly we were forced into the change because someone decided that the A7A was a more reliable plane.

The A7E had a few components that were testable with automated test equipment.

Modules in equipment were called SRA (Shop Replaceable Addembly), circuit cards and a few other names we won't go into here ... :)

The modules in a particular WRA (Weapon{s} Replaceable Assembly) were numbered from A1 to A-whatever. Some modules were composed of two sub assemblies, which gave us the lunacy of A1-A and A1-B and other names which escape me now ... heck it has been over 25 years ... :)

So, that explains the confusion ... The "A" stands for attack aircraft and for a module slot ...

---

>
> So, that explains the confusion ... The "A" stands for attack aircraft and for
> a module slot ...
>


...and what has all this to do with "Still having WU files refused"?!?!

---

Happy crunching

> ...and what has all this to do with "Still having WU files refused"?!?!

Well, as Tom Lerher said: "Base 8 is like base ten really .... if you are missing two fingers ..."

"Well, if you ask a silly question, you get a silly answer ..."

:)

---

> Ups. But be aware that there might be a problem on P4 HT machines. Sorry
>
I'm running BOINC 4.12 on a P4 H/T machine, Win XP SP2, and everything OK so far. Successful upload on a 14Mar WU.

---

Yes, here too once in a while some WU's rejected.
But only intermittently.

Greetings ;-))

---

Hi... Had another one fail on the Athlon 64 earlier on. I happened to be watching the "Work" tab in the BOINC window at the time. I'm not sure whether it always exhibits this behaviour, but calculations seemed to still be being performed AFTER the entry for the WU in the "Work" tab had said the WU had completed. You could still see the cruncher working when you viewed graphics too.

Don't know whether this helps at all.

---