October 6, 2004
There's been a problem with file uploading for the last few days. We think it is fixed now. Our apologies if you lost work because of this.


My last log of an upload that may have failed, though BOINC indicated it was ready to report it.


--- - 2004-10-07 12:23:35 - Resuming network activity
SETI@home - 2004-10-07 12:23:37 - Started upload of 26ap04aa.7733.23474.872154.20_4_0
SETI@home - 2004-10-07 12:23:58 - Temporarily failed upload of 26ap04aa.7733.23474.872154.20_4_0
SETI@home - 2004-10-07 12:23:58 - Backing off 1 minutes and 0 seconds on transfer of file 26ap04aa.7733.23474.872154.20_4_0
SETI@home - 2004-10-07 12:24:14 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-10-07 12:24:58 - Started upload of 26ap04aa.7733.23474.872154.20_4_0
SETI@home - 2004-10-07 12:25:00 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - 2004-10-07 12:27:02 - Error on file upload: file_upload_handler: no filename; nbytes %f
SETI@home - 2004-10-07 12:27:02 - Permanently failed upload of 26ap04aa.7733.23474.872154.20_4_0
SETI@home - 2004-10-07 12:27:02 - Giving up on upload of 26ap04aa.7733.23474.872154.20_4_0: server rejected file
SETI@home - 2004-10-07 12:27:45 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-10-07 12:28:06 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
SETI@home - 2004-10-07 12:28:06 - No schedulers responded
SETI@home - 2004-10-07 12:28:06 - Deferring communication with project for 1 minutes and 0 seconds
SETI@home - 2004-10-07 12:29:06 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-10-07 12:29:13 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded


Apparently the problem still exists, or is a new one.

I am experiencing the same problem, cant send any updates and they seem to give up permanently after a few attempts, hwta happens to the credit for results that get rejected by the server during this problem.
Its not having what you want its wanting what you have

Once again those geniuses at Berkeley have screwed up. This is another problem that they're blowing off, ignoring the simple fact that if the uploads aren't working, THERE'S NO BLOODY PURPOSE FOR THIS PROJECT IN THE FIRST PLACE!!!!!! ....Ahem.....I feel better now. Seriously, Berkeley, get on the ball here.

I got something similar here:

SETI@home - 2004-10-07 22:09:52 - Started upload of 26ap04aa.7733.26657.761084.86_3_0
SETI@home - 2004-10-07 22:10:12 - Error on file upload: file_upload_handler: no filename; nbytes 20389.000000
SETI@home - 2004-10-07 22:10:12 - Permanently failed upload of 26ap04aa.7733.26657.761084.86_3_0
SETI@home - 2004-10-07 22:10:12 - Giving up on upload of 26ap04aa.7733.26657.761084.86_3_0: server rejected file

I think I`ll donate my time do another project until its fixed.

I'm experiencing the same problem; have been losing work units all day. Is there anything I can do at my end, or should I just switch to another project until it's fixed?

>
>
> October 6, 2004
> There's been a problem with file uploading for the last few days. We think it
> is fixed now. Our apologies if you lost work because of this.
>
>
> My last log of an upload that may have failed, though BOINC indicated it was
> ready to report it.
>
>
>
> SETI@home - 2004-10-07 12:24:14 - Sending request to scheduler:
> http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
> SETI@home - 2004-10-07 12:24:58 - Started upload of
> 26ap04aa.7733.23474.872154.20_4_0
> SETI@home - 2004-10-07 12:25:00 - Scheduler RPC to
> http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
> SETI@home - 2004-10-07 12:27:02 - Error on file upload: file_upload_handler:
> no filename; nbytes %f
> SETI@home - 2004-10-07 12:27:02 - Permanently failed upload of
> 26ap04aa.7733.23474.872154.20_4_0
> SETI@home - 2004-10-07 12:27:02 - Giving up on upload of
> 26ap04aa.7733.23474.872154.20_4_0: server rejected file

> Apparently the problem still exists, or is a new one.
>
I'm getting the same thing
SETI@home - 2004-10-07 14:01:51 - Computation for result 27ap04aa.19773.2225.823572.38 finished
SETI@home - 2004-10-07 14:01:52 - Starting result 14mr04aa.17223.4561.298580.74_2 using setiathome version 4.05
SETI@home - 2004-10-07 14:01:52 - Started upload of 27ap04aa.19773.2225.823572.38_3_0
SETI@home - 2004-10-07 14:01:57 - Error on file upload: file_upload_handler: no filename; nbytes 15223.000000
SETI@home - 2004-10-07 14:01:57 - Permanently failed upload of 27ap04aa.19773.2225.823572.38_3_0
SETI@home - 2004-10-07 14:01:57 - Giving up on upload of 27ap04aa.19773.2225.823572.38_3_0: server rejected file
This is what I'm getting on all of my machines today. I guess we are just not going to get any credit for any of the WU's our machines finish and try to upload today. Guess it's time to reattach to CPDN and come back to Seti some other time.