> Berkeley has reseted on the 8th.From what I understand is it takes they
> equipment around 12 hours to syncronize it self. I reseted on the 9th.I'm not
> an expert so all I can suggest is resetting again .It couldn't hurt.
>

I resetted yesterday and it worked for about 15 hours and then errors again.I reset again and will see what happens when a wu completes.

---

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

Well, yesterday I reset the project when I started getting bad uploads and the first few WU's crunched and uploaded okay. But when I got up this morning and attached to the network to upload, all three failed.

SETI@home - 2004-10-10 17:36:26 - Resuming computation for result 27ap04aa.19773.6833.236066.126_6 using setiathome version 4.05
--- - 2004-10-10 17:36:37 - Suspending network activity - user request
SETI@home - 2004-10-10 21:34:28 - Computation for result 27ap04aa.19773.6833.236066.126 finished
SETI@home - 2004-10-10 21:34:28 - Starting result 14mr04aa.17223.29234.642322.71_0 using setiathome version 4.05
SETI@home - 2004-10-11 01:46:28 - Computation for result 14mr04aa.17223.29234.642322.71 finished
SETI@home - 2004-10-11 01:46:28 - Starting result 14mr04aa.17223.29234.642322.61_1 using setiathome version 4.05
SETI@home - 2004-10-11 05:58:25 - Computation for result 14mr04aa.17223.29234.642322.61 finished
SETI@home - 2004-10-11 05:58:25 - Starting result 14mr04aa.17223.29234.642322.56_2 using setiathome version 4.05
--- - 2004-10-11 08:34:44 - Resuming network activity
--- - 2004-10-11 08:34:44 - May run out of work in 7.00 days; requesting more
SETI@home - 2004-10-11 08:34:44 - Requesting 498012 seconds of work
SETI@home - 2004-10-11 08:34:44 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-10-11 08:34:44 - Started upload of 27ap04aa.19773.6833.236066.126_6_0
SETI@home - 2004-10-11 08:34:44 - Started upload of 14mr04aa.17223.29234.642322.71_0_0
SETI@home - 2004-10-11 08:34:49 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - 2004-10-11 08:34:49 - Project prefs: no separate prefs for home; using your defaults
SETI@home - 2004-10-11 08:34:50 - Error on file upload: file_upload_handler: no filename; nbytes 9495.000000
SETI@home - 2004-10-11 08:34:50 - Permanently failed upload of 14mr04aa.17223.29234.642322.71_0_0
SETI@home - 2004-10-11 08:34:50 - Giving up on upload of 14mr04aa.17223.29234.642322.71_0_0: server rejected file
SETI@home - 2004-10-11 08:34:50 - Started upload of 14mr04aa.17223.29234.642322.61_1_0
SETI@home - 2004-10-11 08:34:52 - Error on file upload: file_upload_handler: no filename; nbytes 19556.000000
SETI@home - 2004-10-11 08:34:52 - Permanently failed upload of 27ap04aa.19773.6833.236066.126_6_0
SETI@home - 2004-10-11 08:34:52 - Giving up on upload of 27ap04aa.19773.6833.236066.126_6_0: server rejected file
SETI@home - 2004-10-11 08:34:52 - Started download of 01mr04aa.18860.2096.647150.27
SETI@home - 2004-10-11 08:35:17 - Error on file upload: file_upload_handler: no filename; nbytes 8373.000000
SETI@home - 2004-10-11 08:35:17 - Permanently failed upload of 14mr04aa.17223.29234.642322.61_1_0
SETI@home - 2004-10-11 08:35:17 - Giving up on upload of 14mr04aa.17223.29234.642322.61_1_0: server rejected file
SETI@home - 2004-10-11 08:35:17 - Started download of 01mr04aa.18860.2096.647150.17
--- - 2004-10-11 08:36:05 - Suspending network activity - user request

At this point I disabled network access seeing no reason to download a bunch of files that would probably fail anyway.

Guess it's Seti Classic until they get the problem fixed (my other two PC's have yet to fail uploads for some reason).

If I get errors again I am going to run classic too until this is fixed.

---

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

It's back to classic for me, reluctantly, until there is a fix to the "Permanently failed upload" problem. It would be nice to hear a projected date for the fix. And a reason that the server status page still shows 0400 UTC October 10.

---

For the moment uploads and downloads are functioning as before.
Don't know if any changes have been made, since no info.
But a lot of these pages/forums show on scrolling down an odd/ incorrect format.
For heavens sake WHEN are they going to get something right the first time when something reasonably simple is changed, instead of these trial and error methods...

No offence, I won't leave but, ...
Greetz ;-))

---

Put your money where it will do the most good!!!
Team Members (not very many)
Team members photos (Two years old)

---

Semper Eadem
So long Paul, it has been a hell of a ride.

Park your ego's, fire up the computers, Science YES, Credits No.

Switching to a different project for the time being. ALL of my WU's are being refused atm..

:(

Garindan

---

Bas van Zuilen

Finally... Got the first sucessful WU from the 64 up sometime today (can't remember exactly when) maybe it's fixed, maybe I just got lucky.. We'll have to wait and see.

---

I just think it's some wacky WU's. I've been getting several upload rejections on the 9th and first part of the 10th, then they all started uploading fine and I didn't change anything. I just let BOINC keep doing its thing.

Mark H.

---

I don't know what's going on... I had the same problems yesterday but for the last 19 hours everythings been running smoothly with no error messages at all... I haven't changed a thing.

Robert

---

Well... That's the second WU successfully sent from the 64 box. Unfortunately It'll be another 3hrs or so before I can verify that the 1900+ can get a WU up there successfully.

---

I'm not sure how much water this will hold but check the due dates as well.
BOINC WUs are perishable and might get rejected if to old.It's possible that the timeing got all haywire.

---

I Refuse to hold myself responsible for any of my actions.

si hoc legere scis nimium eruditionis habes

> More speculation, but here goes ...
>
> We are running along and are submitting work and everything looks fine ...
>
> A bug is found in the code on the server side. That bug is fixed ...
>
> Now work is rejected by the server because the client code was written
> to work with the server software with the bug, and is now failing because the
> server code was changed to the now known correct version.
>
> True story ...
>
> I worked on a computerized tester used on F-14, S3A, E-2C and A7 aircraft. I
> worked on S-3 avionics and we had problems with the tester not being able to
> certify a particular black box (called a Weapons Replaceable
> A</B>ssembly, or WRA). For some reason the A2 module was always singled
> out as a defective component. The Lockheed engineer did a lot of travel and
> he would come to the site and prove that the A2 was defective because the
> program certified the box with his "personal" and "gloden" A2 card ...
>
> This lasted right up to the point where his A2 card had to be repaired for a
> different casualty. Guess what, right after it was repaired it no longer
> would allow the WRA to be certified. The program was written to accomodate a
> defective component.
>
> So, we may be seeing an instance where a fix on one side of the system causes
> the other side to fail requiring an additional fix ...
>

Paul, you make a very logical point. [b]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.

L8R....

---

---

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

Well, I'm getting failed uploads again after my reset yesterday. All my WUs, downloaded after reset, were 14mr04aa. The first one did upload just fine, but now.... I'm not resetting right now because I got some new WUs with the date 01mr04aa. I will wait and see what happens with them.

L8R....

---

---

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

> Well, I'm getting failed uploads again after my reset yesterday. All my WUs,
> downloaded after reset, were 14mr04aa. The first one did upload just fine,
> but now.... I'm not resetting right now because I got some new WUs with the
> date 01mr04aa. I will wait and see what happens with them.
>
> L8R....
>
Hello
I got errors too.Downloaded new wu's of 01mr04aa and they have completed faster and 4 so far have sent back fine.Time will tell.

---

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

I did a reset, and things were happy for a while, then a few minutes ago...bam! back to the same problem. I'll suspend till things get worked out.

Well I am getting the same errors

SETI@home - 2004-10-10 21:26:21 - Started upload of 06my04ab.9911.27760.190906.3_3_0
SETI@home - 2004-10-10 21:26:30 - Error on file upload: file_upload_handler: no filename; nbytes 17898.000000
SETI@home - 2004-10-10 21:26:30 - Permanently failed upload of 06my04ab.9911.27760.190906.3_3_0
SETI@home - 2004-10-10 21:26:30 - Giving up on upload of 06my04ab.9911.27760.190906.3_3_0: server rejected file
--- - 2004-10-10 21:27:54 - Suspending network activity - user request
--- - 2004-10-11 01:11:33 - Resuming network activity
SETI@home - 2004-10-11 01:11:41 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-10-11 01:11:45 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - 2004-10-11 12:59:29 - Computation for result 06my04ab.9911.27760.190906.24 finished
SETI@home - 2004-10-11 12:59:29 - Starting result 06my04ab.9911.27760.190906.55_4 using setiathome version 4.05
SETI@home - 2004-10-11 12:59:29 - Started upload of 06my04ab.9911.27760.190906.24_3_0
SETI@home - 2004-10-11 12:59:38 - Error on file upload: file_upload_handler: no filename; nbytes 19160.000000
SETI@home - 2004-10-11 12:59:38 - Permanently failed upload of 06my04ab.9911.27760.190906.24_3_0
SETI@home - 2004-10-11 12:59:38 - Giving up on upload of 06my04ab.9911.27760.190906.24_3_0: server rejected file

But i have also noticed that my WU's are taking longer to be processed, i used to avarge the 9hrs but now they are taking 14hrs on avarge.

Is this a problem with the setiathome_4.05_windows_intelx86.exe???

---

Cheers Quail

I've had about 8-10 of the now infamous 14mr04aa batch fail upload
And I expect another 17 of those not uploading properly..

---

// Just because you\'re not paranoid, doesn\'t mean they\'re not after you

There is a lot of info. on another thread on upload/validator problems with replies from Matt.
See number crunching - Validator / File Uploads / etc.

---

Now for the first time I have problems as well...

SETI@home - 2004-10-12 15:36:34 - Computation for result 14mr04aa.17223.31153.897174.204 finished

SETI@home - 2004-10-12 15:36:34 - Starting result 14mr04aa.17223.31153.897174.230_0 using setiathome version 4.05

SETI@home - 2004-10-12 15:36:34 - Started upload of 14mr04aa.17223.31153.897174.204_2_0

SETI@home - 2004-10-12 15:36:41 - Error on file upload: file_upload_handler: no filename; nbytes 11488.000000

SETI@home - 2004-10-12 15:36:41 - Permanently failed upload of 14mr04aa.17223.31153.897174.204_2_0

---

Happy crunching