Odd errors in BOINC

[Mictlan]

From my log report :

SETI@home - 2004-10-08 09:56:44 - Computation for result 06my04ab.9911.25697.903410.213 finished
SETI@home - 2004-10-08 09:56:44 - Starting result 06my04ab.9911.25697.903410.188_4 using setiathome version 4.05
SETI@home - 2004-10-08 09:56:44 - Started upload of 06my04ab.9911.25697.903410.213_3_0
SETI@home - 2004-10-08 09:56:49 - Error on file upload: file_upload_handler: no filename; nbytes 15560.000000
SETI@home - 2004-10-08 09:56:49 - Permanently failed upload of 06my04ab.9911.25697.903410.213_3_0
SETI@home - 2004-10-08 09:56:49 - Giving up on upload of 06my04ab.9911.25697.903410.213_3_0: server rejected file

Have anyone seen this in the last days?

Also yesterday I was trying to get BOINC to run in laptop and it kept returning the WU in 3-5 minutes saying that it were crunched completly. Odd don't you think?

Both machines are running at stock speed, no funky settings.

[eaglescouter]

I had that a week or two ago, had to reset the project, then it went merrily on it's way again.

[Hamm3r]

Yesterday I had to reset the project because of this, uploaded 2 work units after that and it worked, and now im getting same error back :(, until this gets fixed im on Classic

[Mictlan]

I ressted the project and still keeeps doing the same......Funny thing doing exactly the same in my laptop

[Dk Jedi Allianc]

Hi Juan.


There is a tread regarding this in SAH forum:

LINK (http://setiweb.ssl.berkeley.edu/sah/forum_thread.php?id=5281)


Now get it fixed and get that rig crunching - so we can beat Katelin :burn: :p

[Lancelot]

Yes I've seen this happening on my rig twice during the past week, even ran dual Prime95's overnight to be sure my OC was still stable. All was fine. It seems to be a Berkeley-side problem though...

[texasfit]

I have not personally had this problem but they seem to have a fix based on the front page news.
-

October 9, 2004
A problem with file uploads has existed for the last few days. This problem causes file uploads to fail. We now understand the problem and are working on a fix - it will probably require upgrading your BOINC client. Please stay tuned.

[Mictlan]

The problem seams widespread. To fix it we need to wait for a BOINC/Client upgrade.....sigh

[eaglescouter]

I got it again last night, I selected reset project and this morning all was better.

[texasfit]

I have not personally had this problem but they seem to have a fix based on the front page news.

Oooops!!

I take it back. I just had my first Permanently Failed Upload.
This one had a 'Report Deadline' of 10/18, so it would have been downloaded
on 10/4. There have been 7 others with the same date that uploads were
completed without error. I still have 9 more wu's with that date. Think that I will 'Disable Network Access'
and see if they put out a version update in the next day or two.

SETI@home - 2004-10-11 09:23:14 - Computation for result 01mr04ab.2990.15954.736090.9 finished
SETI@home - 2004-10-11 09:23:14 - Started upload of 01mr04ab.2990.15954.736090.9_4_0
SETI@home - 2004-10-11 09:25:05 - Error on file upload: file_upload_handler: no filename; nbytes 13388.000000
SETI@home - 2004-10-11 09:25:05 - Permanently failed upload of 01mr04ab.2990.15954.736090.9_4_0
SETI@home - 2004-10-11 09:25:05 - Giving up on upload of 01mr04ab.2990.15954.736090.9_4_0: server rejected file

[katelin]

it kept returning the WU in 3-5 minutes saying that it were crunched completly. Odd don't you think?



I hope you aren't getting credits for those, this may explain why you guys all of a sudden jumped 2000 points. Hehe just kidding :D

[katelin]

Now get it fixed and get that rig crunching - so we can beat Katelin :burn: :p

No, don't fix it yet. Let me catch up first :D

[eaglescouter]

Texasfit, when I receive that error, I just click projects, right click on seti, update. That appears to transmit the unit correctly.

[Dk Jedi Allianc]

Texasfit, when I receive that error, I just click projects, right click on seti, update. That appears to transmit the unit correctly.


Did the same thing with 2 WU´s just now. Looked rigth to me??

[texasfit]

Texasfit, when I receive that error, I just click projects, right click on seti, update. That appears to transmit the unit correctly.
When you do that type of 'Update' that will connect with the scheduler which would send any 'Ready to Report' wu's but would not have anything to do with the upload/download directory. (Two different servers) The one unit that I have that shows the 'Giving up on upload" failure still shows 'Ready to Report' and also shows having 34.22 credits in BonicView pending.

The question would be:
"if a unit gets the 'Giving up on upload' error which would indicate that the unit was not sent back at all, would the credit still be granted from the validator when that wu is reported"? I don't think so but there is no way of knowing this with the pending credit feature disabled.

[JigPu]

I just started getting this error too... Hopefully it won't be too long before a bugfix is released, since I'm getting ansy not moving anywhere in this race! :D

JigPu

[Lancelot]

off topic; but JigPu; is that your 256bit WEP-key in your signature or what? lol!

[JigPu]

Not really :D If you check out the last 6 charachters (and then Google them) you'll see that it's a 512-bit SHA hash. $20 to the first person who can reverse the hash into the source file ;)

JigPu