I'm amazed that so much persons are having upload/download problems. I'm connected via cable/broadband (permanent) and do have no transmission problems.
BOINC/Seti permanent Network Access.
Credits are rolling in, but at very intermittent intervals and in very fluctuating amounts. Sometimes a couple of fivehundreds to a couple of thousends then again very low amounts. I guess this is still caused by the backlog going down and up again and then again going down, sort of hickups when the drives have problems to follow up the demand???

Greetings ;-))
(Next week five machines extra - yippie...)

> I'm amazed that so much persons are having upload/download problems. I'm
> connected via cable/broadband (permanent) and do have no transmission
> problems.


Not unexpected if my theory of a bad WU batch is accurate. The default BOINC setting for contacting the server is 2 days, and I suspect many users haven't changed that setting. On average, these people would have anywhere from a few hours to two day of WU, and if Seti pumped out bad WU's for a day, they would have a pretty good chance of downloading a pile of bad WU's....


<a>

>
> Not unexpected if my theory of a bad WU batch is accurate. The default BOINC
> setting for contacting the server is 2 days, and I suspect many users haven't
> changed that setting. On average, these people would have anywhere from a few
> hours to two day of WU, and if Seti pumped out bad WU's for a day, they would
> have a pretty good chance of downloading a pile of bad WU's....
>
>
> <a>
>

Yes, I think you're right. Perhaps I'm not confronted with this problem because I work in the same context as you, cache for all set to 7 days and already filled up, so we don't have noticed this hickup but...are these WU' coming back??? if so we could get our share of "the plague".

Greetz from Belgium ;-))

Work units are like a box of chocolates, you never know what you're going to get! LOL!





Application has reported a 'Not My Fault' in module KRNL.EXE in line 0200:103F

> Work units are like a box of chocolates, you never know what you're going to
> get! LOL!

We do have very good chocolates over here - I like them, more than credits -,
What do you think of the following :

For every 10 bad WU's Berkeley sends one? tranquilizer to sedate overuse of Seti... LoL

Greetz, ;-))

> Work units are like a box of chocolates, you never know what you're going to
> get! LOL!
>
>
>
>
>
> Application has reported a 'Not My Fault' in module KRNL.EXE in line 0200:103F
>

Same problem yesterday....

SETI@home - 2004-10-07 20:42:15 - Started upload of 01mr04ab.2990.16914.342308.119_3_0
SETI@home - 2004-10-07 20:42:21 - Error on file upload: file_upload_handler: no filename; nbytes 9724.000000
SETI@home - 2004-10-07 20:42:21 - Permanently failed upload of 01mr04ab.2990.16914.342308.119_3_0
SETI@home - 2004-10-07 20:42:21 - Giving up on upload of 01mr04ab.2990.16914.342308.119_3_0: server rejected file

> > I'm amazed that so much persons are having upload/download problems. I'm
> > connected via cable/broadband (permanent) and do have no transmission
> > problems.
>
>
> Not unexpected if my theory of a bad WU batch is accurate. The default BOINC
> setting for contacting the server is 2 days, and I suspect many users haven't
> changed that setting. On average, these people would have anywhere from a few
> hours to two day of WU, and if Seti pumped out bad WU's for a day, they would
> have a pretty good chance of downloading a pile of bad WU's....

Well, I'm on dialup and contact daily. I haven't had any upload problems since they fired things back up. Maybe I'm just lucky and have missed the "bad" WUs?

A recent WU.
SETI@home - 2004-10-08 06:37:22 - Started upload of 14mr04aa.17223.7186.915908.243_0_0
SETI@home - 2004-10-08 06:37:29 - Finished upload of 14mr04aa.17223.7186.915908.243_0_0
SETI@home - 2004-10-08 06:37:29 - Throughput 4734 bytes/sec

> Well, I'm on dialup and contact daily. I haven't had any upload problems since
> they fired things back up. Maybe I'm just lucky and have missed the "bad"
> WUs?
>
> A recent WU.
> SETI@home - 2004-10-08 06:37:22 - Started upload of
> 14mr04aa.17223.7186.915908.243_0_0
> SETI@home - 2004-10-08 06:37:29 - Finished upload of
> 14mr04aa.17223.7186.915908.243_0_0
> SETI@home - 2004-10-08 06:37:29 - Throughput 4734 bytes/sec
>

When were these WUs downloaded?

Hey guys from the firedepartment in Berkeley,...
Please spray some dry ice on them overheated drives...

Yes, overhere its starting too, uploads don't go through on several machines,

SETI@home - 2004-10-08 19:23:21 - Backing off 1 minutes and 21 seconds on transfer of file 04mr04aa.22434.9314.773582.16_2_0
SETI@home - 2004-10-08 19:24:42 - Started upload of 04mr04aa.22434.9314.773582.16_2_0
SETI@home - 2004-10-08 19:25:59 - Temporarily failed upload of 04mr04aa.22434.9314.773582.16_2_0
SETI@home - 2004-10-08 19:25:59 - Backing off 11 minutes and 6 seconds on transfer of file 04mr04aa.22434.9314.773582.16_2_0
SETI@home - 2004-10-08 19:37:05 - Started upload of 04mr04aa.22434.9314.773582.16_2_0
SETI@home - 2004-10-08 19:38:22 - Temporarily failed upload of 04mr04aa.22434.9314.773582.16_2_0
SETI@home - 2004-10-08 19:38:22 - Backing off 44 minutes and 18 seconds on transfer of file 04mr04aa.22434.9314.773582.16_2_0
SETI@home - 2004-10-08 20:22:40 - Started upload of 04mr04aa.22434.9314.773582.16_2_0
SETI@home - 2004-10-08 20:23:56 - Temporarily failed upload of 04mr04aa.22434.9314.773582.16_2_0
SETI@home - 2004-10-08 20:23:56 - Backing off 1 hours, 44 minutes, and 28 seconds on transfer of file 04mr04aa.22434.9314.773582.16_2_0
SETI@home - 2004-10-08 20:46:04 - Started upload of 04mr04aa.22434.9314.773582.16_2_0
SETI@home - 2004-10-08 20:47:21 - Temporarily failed upload of 04mr04aa.22434.9314.773582.16_2_0
SETI@home - 2004-10-08 20:47:21 - Backing off 8 minutes and 55 seconds on transfer of file 04mr04aa.22434.9314.773582.16_2_0

This is a sample on one machine, on other machines all of the same family-code,

Greetings, don't worry be happy, ... ;-))

I have 5 machines crunching, 4 local and 1 remote. I have not been able to check the remote box, but none of the 4 local ones have had any upload errors. I have had tons of download errors, and some temporary upload failure(all were eventually successful), but no permanent upload errors. All of my crunchers are running and connected 24/7, even during the outages. All of them have the cache set to 5 days. This whole situation seems strange indeed.

Addendum : see two messages back, after several retries on some machines finally success but nevertheless uploads often problematic ...

SETI@home - 2004-10-08 20:47:21 - Backing off 8 minutes and 55 seconds on transfer of file 04mr04aa.22434.9314.773582.16_2_0
SETI@home - 2004-10-08 20:56:16 - Started upload of 04mr04aa.22434.9314.773582.16_2_0
SETI@home - 2004-10-08 20:58:34 - Finished upload of 04mr04aa.22434.9314.773582.16_2_0
SETI@home - 2004-10-08 20:58:35 - Throughput 6713 bytes/sec
SETI@home - 2004-10-08 20:59:43 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-10-08 21:00:03 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
SETI@home - 2004-10-08 21:00:03 - No schedulers responded

So be it, happy crunching folk, don't worry, be happy ;-))

Greetz.

> When were these WUs downloaded?

Last night.

Just had another one go.

SETI@home - 2004-10-08 13:26:30 - Started upload of 14mr04aa.17223.752.572166.15_4_0
SETI@home - 2004-10-08 13:26:37 - Finished upload of 14mr04aa.17223.752.572166.15_4_0
SETI@home - 2004-10-08 13:26:37 - Throughput 5958 bytes/sec

I got the same problem on one of my workunits so far.. failed to upload.
Error on file upload: file_upload_handler: no filename; nbytes 8336.000000
permanently failed upload of (workunit name)
Giving up on upload of (workunit name) server rejected file

My client tried to upload once, I right clicked the "retry now" and it tried once more, and then proceeded to remove the workunit.

"Error on file upload: file_upload_handler: no filename; nbytes 16575.000000
Permanently failed upload of 01mr04ab.2990.15904.28390.225_3_0
Giving up on upload of 01mr04ab.2990.15904.28390.225_3_0: server rejected file"

And it keeps on going and going,
should we hold the uploads?????

New batch of wuwus and it is the same, this wuwu was trying to upload for about 2 hrs and then

SETI@home - 2004-10-08 13:18:58 - Started upload of 14mr04aa.17223.11105.897148.32_2_0
SETI@home - 2004-10-08 13:19:00 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
SETI@home - 2004-10-08 13:19:00 - No schedulers responded
SETI@home - 2004-10-08 13:19:00 - Deferring communication with project for 1 hours, 14 minutes, and 20 seconds
SETI@home - 2004-10-08 13:19:03 - Error on file upload: file_upload_handler: no filename; nbytes 16098.000000
SETI@home - 2004-10-08 13:19:03 - Permanently failed upload of 14mr04aa.17223.11105.897148.32_2_0
SETI@home - 2004-10-08 13:19:03 - Giving up on upload of 14mr04aa.17223.11105.897148.32_2_0: server rejected file


this is after about 2 hrs of trying, this is new to me.............
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...

Posted: 7 Oct 2004 21:08:30 UTC
in response to Message ID 33703.

>
>
> 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.


ID: 33807 / Rating: 0


http://setiweb.ssl.berkeley.edu/forum_thread.php?id=5196
http://setiweb.ssl.berkeley.edu/forum_thread.php?id=5258
http://setiweb.ssl.berkeley.edu/forum_thread.php?id=5273
http://setiweb.ssl.berkeley.edu/sah/forum_thread.php?id=5281

There seems to be at least 4 threads all saying the same thing. I think there must have been some bad WU's released on the 5th or the 6th. I had 2 machines that were having problems. I reset both of them and I haven't had any more problems. Of course I don't really know if that was the case because none of the Admin's have said anything about this problem even though there are 4 threads saying they have problems.

October 8, 2004
This morning a hardware failure caused one of our storage arrays to require resetting. Downloads will be temporarily halted until the drives have completed re-synchronizing. This should be complete in the early evening hours (Pacific Time).

only for Info

Greetings from Germany NRW
Ulli S@h Berkeley's Staff Friends Club m7 ©

Been lucky until today with this problem.

Just got round to checking messages and found this.

SETI@home - 2004-10-08 18:29:18 - Started upload of 04my04aa.14406.24752.90902.110_7_0
SETI@home - 2004-10-08 18:29:41 - Temporarily failed upload of 04my04aa.14406.24752.90902.110_7_0
SETI@home - 2004-10-08 18:29:41 - Backing off 1 minutes and 0 seconds on transfer of file 04my04aa.14406.24752.90902.110_7_0
SETI@home - 2004-10-08 18:30:41 - Started upload of 04my04aa.14406.24752.90902.110_7_0
SETI@home - 2004-10-08 18:31:04 - Temporarily failed upload of 04my04aa.14406.24752.90902.110_7_0
SETI@home - 2004-10-08 18:31:04 - Backing off 1 minutes and 0 seconds on transfer of file 04my04aa.14406.24752.90902.110_7_0
SETI@home - 2004-10-08 18:32:04 - Started upload of 04my04aa.14406.24752.90902.110_7_0
SETI@home - 2004-10-08 18:32:27 - Temporarily failed upload of 04my04aa.14406.24752.90902.110_7_0
SETI@home - 2004-10-08 18:32:27 - Backing off 1 minutes and 0 seconds on transfer of file 04my04aa.14406.24752.90902.110_7_0
SETI@home - 2004-10-08 18:33:27 - Started upload of 04my04aa.14406.24752.90902.110_7_0
SETI@home - 2004-10-08 18:33:50 - Temporarily failed upload of 04my04aa.14406.24752.90902.110_7_0
SETI@home - 2004-10-08 18:33:50 - Backing off 2 minutes and 16 seconds on transfer of file 04my04aa.14406.24752.90902.110_7_0
SETI@home - 2004-10-08 18:36:06 - Started upload of 04my04aa.14406.24752.90902.110_7_0
SETI@home - 2004-10-08 18:36:29 - Temporarily failed upload of 04my04aa.14406.24752.90902.110_7_0
SETI@home - 2004-10-08 18:36:29 - Backing off 5 minutes and 41 seconds on transfer of file 04my04aa.14406.24752.90902.110_7_0
SETI@home - 2004-10-08 18:42:10 - Started upload of 04my04aa.14406.24752.90902.110_7_0
SETI@home - 2004-10-08 18:42:33 - Temporarily failed upload of 04my04aa.14406.24752.90902.110_7_0
SETI@home - 2004-10-08 18:42:33 - Backing off 2 minutes and 14 seconds on transfer of file 04my04aa.14406.24752.90902.110_7_0
SETI@home - 2004-10-08 18:44:47 - Started upload of 04my04aa.14406.24752.90902.110_7_0
SETI@home - 2004-10-08 18:45:10 - Temporarily failed upload of 04my04aa.14406.24752.90902.110_7_0
SETI@home - 2004-10-08 18:45:10 - Backing off 1 minutes and 25 seconds on transfer of file 04my04aa.14406.24752.90902.110_7_0
SETI@home - 2004-10-08 18:46:35 - Started upload of 04my04aa.14406.24752.90902.110_7_0
SETI@home - 2004-10-08 18:56:37 - Temporarily failed upload of 04my04aa.14406.24752.90902.110_7_0
SETI@home - 2004-10-08 18:56:37 - Backing off 1 hours, 25 minutes, and 36 seconds on transfer of file 04my04aa.14406.24752.90902.110_7_0
SETI@home - 2004-10-08 20:14:00 - Started upload of 04my04aa.14406.24752.90902.110_7_0
SETI@home - 2004-10-08 20:14:51 - Error on file upload: file_upload_handler: no filename; nbytes 18096.000000
SETI@home - 2004-10-08 20:14:51 - Permanently failed upload of 04my04aa.14406.24752.90902.110_7_0
SETI@home - 2004-10-08 20:14:51 - Giving up on upload of 04my04aa.14406.24752.90902.110_7_0: server rejected file

I have previously had WU's from O4my04 with no problem.

Now comes the crunch I have had three power failures today. Two because thye coffee make blew (quite a bang as well and I had not got my caffeine). That was around 10:00 UTC. Then sometime between 14 and 17:00 UTC there was a local sub failure. None of the logs show an unexpected shutdown. Now the question is was it the power failure or a file failure? If it was the power failure then why didn't the client pickup from an earlier checkpoint. (I am sure I read somewhere that is what should happen but I may be wrong.) I know outages can do some weird things and no I do not have an UPS (can't afford it!) but the supply is well filtered. Not over worried, just curious!

Thanks

David

Saturday: Lost four more overnight!

[b][i]...only a fool never makes a mistake![b][i]

I too have been having this problem, been going on for 2 days now, on 3 different PC's:
(time is -7 UTC)
SETI@home - 2004-10-09 06:43:29 - Computation for result 06my04ab.9911.25313.429840.122 finished
SETI@home - 2004-10-09 06:43:29 - Starting result 14mr04aa.17223.18914.73576.237_2 using setiathome version 4.05
SETI@home - 2004-10-09 06:43:29 - Started upload of 06my04ab.9911.25313.429840.122_4_0
SETI@home - 2004-10-09 06:43:35 - Error on file upload: file_upload_handler: no filename; nbytes 14982.000000
SETI@home - 2004-10-09 06:43:35 - Permanently failed upload of 06my04ab.9911.25313.429840.122_4_0
SETI@home - 2004-10-09 06:43:35 - Giving up on upload of 06my04ab.9911.25313.429840.122_4_0: server rejected file

I think I had only 1 WU go thru yesterday, message is gone since I shut the PC down overnight, I don't keep a large cache of WU's, only one sitting ready to go when the other completes.

SETI@home - 2004-10-09 11:45:44 - Computation for result 14mr04aa.17223.13713.573572.159 finished
SETI@home - 2004-10-09 11:45:44 - Starting result 14mr04aa.17223.13713.573572.161_0 using setiathome version 4.05
SETI@home - 2004-10-09 11:45:45 - Started upload of 14mr04aa.17223.13713.573572.159_0_0
SETI@home - 2004-10-09 11:45:51 - Error on file upload: file_upload_handler: no filename; nbytes 9599.000000
SETI@home - 2004-10-09 11:45:51 - Permanently failed upload of 14mr04aa.17223.13713.573572.159_0_0
SETI@home - 2004-10-09 11:45:51 - Giving up on upload of 14mr04aa.17223.13713.573572.159_0_0: server rejected file

That's another 11 hours of crunching down the drain...



SetiUK - The Offical UK Seti Site - Team Lookers
The Space Directory
Visit Seti.org.uk
SETI News Mailing List


S@h Berkeley's Staff Friends Club ©
[/url]