Ok, so if the uploading is fixed what is going on here then?...

SETI@home - 2004-10-07 22:15:34 - Computation for result 04my04aa.25870.22689.811074.219 finished
SETI@home - 2004-10-07 22:15:34 - Starting result 05my04aa.9306.6000.497156.83_7 using setiathome version 4.05
SETI@home - 2004-10-07 22:15:34 - Started upload of 04my04aa.25870.22689.811074.219_7_0
SETI@home - 2004-10-07 22:15:42 - Error on file upload: file_upload_handler: no filename; nbytes 21046.000000
SETI@home - 2004-10-07 22:15:42 - Permanently failed upload of 04my04aa.25870.22689.811074.219_7_0
SETI@home - 2004-10-07 22:15:42 - Giving up on upload of 04my04aa.25870.22689.811074.219_7_0: server rejected file


JT

Have you tried exiting the client and re-installing Boinc on top of itself?

I had some upload problems, and this fixed it for me.

Dunc

Nope, didn't work...

SETI@home - 2004-10-07 22:42:11 - Computation for result 26ap04ab.3369.16657.423578.101 finished
SETI@home - 2004-10-07 22:42:11 - Starting result 04mr04aa.22434.4993.386062.243_4 using setiathome version 4.05
SETI@home - 2004-10-07 22:42:11 - Started upload of 26ap04ab.3369.16657.423578.101_3_0
SETI@home - 2004-10-07 22:42:19 - Error on file upload: file_upload_handler: no filename; nbytes 17378.000000
SETI@home - 2004-10-07 22:42:19 - Permanently failed upload of 26ap04ab.3369.16657.423578.101_3_0
SETI@home - 2004-10-07 22:42:19 - Giving up on upload of 26ap04ab.3369.16657.423578.101_3_0: server rejected file

The upload problem may be bad parameters in the workunit. The 'no filename' error message tends to imply this. If that is the case then there will be some bad units still floating around and they will hang around for weeks or months until they all fail enough to be deleted from the server side queue. On the bright side they should be more and more rare.

John Keck -- BOINCing since 2002/12/08 --

Getting that same message.......
My name is Pascal and this message has no meaning, but still has my approval...

It is 10 oclock, do you know what your WUWUs are doing tonight...

Also getting the same message! In fact all wu's processed over the last 48 hours have been rejected??????????

just got a couple myself

SETI@home - 2004-10-07 18:27:37 - Started upload of 26ap04ab.3369.18832.1015912.180_4_0
SETI@home - 2004-10-07 18:27:51 - Error on file upload: file_upload_handler: no filename; nbytes 13699.000000
SETI@home - 2004-10-07 18:27:51 - Permanently failed upload of 26ap04ab.3369.18832.1015912.180_4_0
SETI@home - 2004-10-07 18:27:51 - Giving up on upload of 26ap04ab.3369.18832.1015912.180_4_0: server rejected file
SETI@home - 2004-10-07 18:33:30 - Started upload of 26ap04aa.4387.9569.73576.38_5_0
SETI@home - 2004-10-07 18:33:39 - Error on file upload: file_upload_handler: no filename; nbytes 21154.000000
SETI@home - 2004-10-07 18:33:39 - Permanently failed upload of 26ap04aa.4387.9569.73576.38_5_0
SETI@home - 2004-10-07 18:33:39 - Giving up on upload of 26ap04aa.4387.9569.73576.38_5_0: server rejected file


regards
Z

Mine have all gone through. Sorry if y'all are having problems. But things seem to be running as smoothly as possible right now.
Yours,
Tatheg

> just got a couple myself
>
> SETI@home - 2004-10-07 18:27:37 - Started upload of
> 26ap04ab.3369.18832.1015912.180_4_0
> SETI@home - 2004-10-07 18:27:51 - Error on file upload: file_upload_handler:
> no filename; nbytes 13699.000000
> SETI@home - 2004-10-07 18:27:51 - Permanently failed upload of
> 26ap04ab.3369.18832.1015912.180_4_0
>.....................
> regards
> Z
>
>

I too have had one box doing this for last 36 hours and another two boxes have just started doing it. Resetting project didn't fix for me either.

Ned

Sorry guys, 30 PC's and not one upload error today.....perhaps there was a bad batch of WU's at some point....


<a>

I just noticed the same thing as JTHM did. 6:51:54 total time spent processing and for NOTHING! My v4.05 SC WUs are processing about 3 hours longer than with v4.03 SC. I think they broke the SETI Client.

I WISH they would leave BOINC alone, after fixing it of course, and consentrate on their servers! To fix the SETI Client, they should revert back to the code for v4.03 and call it v4.07.

I don't care about the status bar showing 50% after a few minutes and taking a little over 3 hours to finish. I don't sit here and watch the status bar increment as work is being done.

@dev team: Fix the SETI Client and leave it alone.

L8R....

---




Rick A. - BOINCing right along now.... It can only get better!

"There is no fate except that which we create for ourselves."

Live Long and Prosper....

> I just noticed the same thing as JTHM did. 6:51:54 total time spent
> processing and for NOTHING! My v4.05 SC WUs are processing about 3
> hours longer than with v4.03 SC. I think they broke the SETI Client.
>
> I WISH they would leave BOINC alone, after fixing it of course, and
> consentrate on their servers! To fix the SETI Client, they should revert back
> to the code for v4.03 and call it v4.07.
>
> I don't care about the status bar showing 50% after a few minutes and taking a
> little over 3 hours to finish. I don't sit here and watch the status bar
> increment as work is being done.
>
> @dev team: Fix the SETI Client and leave it alone.
>
> L8R....
>

I don't think it's necessarily the client. My linux boxes are all doing it and they were fine a few days ago. A windows box with a large cache is also still OK atm. It's only WUs downloaded in the last two days or so that are borked

I tried resetting 3 of my machines (windows and linux) which empties the project folder, downloads a fresh copy of the seti client and a fresh batch of units, and all 3 machines haven't returned a unit since. The one machine that's still OK is still trundling through older work units and has about 2-3 days worth left before getting on to the newer batch.

I'm sure it's the current batch of units being given out that are causing the problem. Because people are either dumping them by resetting the project or they're failing to upload, the same units are just going out over and over again.

Ned

Just had a rejected upload also. 11 hours wasted on a machine that used to take 7 hours before the 4.05 client. I downloaded that WU yesterday after doing a reformat and fresh install. Going to dump the WU's downloaded yesterday and hope it doesn't happen again. Here is the message from the server:

SETI@home - 2004-10-07 22:43:20 - Started upload of 14mr04aa.17223.1712.184644.55_2_0
SETI@home - 2004-10-07 22:43:26 - Error on file upload: file_upload_handler: no filename; nbytes 10065.000000
SETI@home - 2004-10-07 22:43:26 - Permanently failed upload of 14mr04aa.17223.1712.184644.55_2_0
SETI@home - 2004-10-07 22:43:26 - Giving up on upload of 14mr04aa.17223.1712.184644.55_2_0: server rejected file

I reset the project last thing last night....we'll see what the new work units do.

Why on earth did we have to upgrade to BOINC 4.09/SETI 4.05? BOINC 3.20/SETI 4.03 worked fine!

JT

I'm now getting this on a couple of boxes, I will try reseting the project then, of course I will need to do the workaround for the P4 HT bug as well *laugh*
[url=http://acidtrax.net/forum/index.php]
<a>

Nothing seems repaired, just check a host and it seems to be trashing work after processing for the 5 day's it's running. Last Wu trashed 10 minutes ago, have to check the other hosts, but seems like a huge waste of computer power.

I'm also having uploading issues. Just reset.

This is looking more and more like a batch of buggy WUs in which case a reset should clear it. If not, it must be a server problem as I have it sporadically under SETI client 4.02 Linux and 4.05 Windows - so client version 4.05 isn't the issue............

Yep! Me too! I've had two WU's report "permanently failed upload", "giving up on upload". Wayne.