Still having WU files refused.

Message boards : Number crunching : Still having WU files refused.
Message board moderation

To post messages, you must log in.

Previous · 1 · 2 · 3 · 4 · 5 . . . 7 · Next

AuthorMessage
Dusty33
Volunteer tester
Avatar

Send message
Joined: 16 Jul 01
Posts: 24
Credit: 3,368,100
RAC: 0
United States
Message 34409 - Posted: 9 Oct 2004, 9:22:46 UTC
Last modified: 9 Oct 2004, 9:27:26 UTC

Well.... It looks like I can now join the party with U/L issues.

I looked into the client_state.xml file just for fun and seen this:
{result}
{name}05my04ab.172.10658.579834.189_4{/name}
{final_cpu_time}6207.856459{/final_cpu_time}
{exit_status}0{/exit_status}
{state}5{/state}
{stderr_out}
{stderr_txt}
SETI@Home Informational message -9 result_overflow
NOTE: The number of results detected exceeds the storage space allocated.

{/stderr_txt}
{/stderr_out}
{ready_to_report/}
{wu_name}05my04ab.172.10658.579834.189{/wu_name}
{report_deadline}1097809711{/report_deadline}
{file_ref}
{file_name}05my04ab.172.10658.579834.189_4_0{/file_name}
{open_name}result.sah{/open_name}
{/file_ref}
{/result}



Hmmmm... The number of results detected exceed the storage space allocated? Which side is this on, my box or the server?



Dusty
ID: 34409 · Report as offensive
Profile Siran d'Vel'nahr
Volunteer tester
Avatar

Send message
Joined: 23 May 99
Posts: 7110
Credit: 28,704,019
RAC: 116,052
United States
Message 34548 - Posted: 9 Oct 2004, 19:19:37 UTC - in response to Message 34409.  

> Well.... It looks like I can now join the party with U/L issues.
>
> I looked into the client_state.xml file just for fun and seen this:
> {result}
> {name}05my04ab.172.10658.579834.189_4{/name}
> {final_cpu_time}6207.856459{/final_cpu_time}
> {exit_status}0{/exit_status}
> {state}5{/state}
> {stderr_out}
> {stderr_txt}
> SETI@Home Informational message -9 result_overflow
> NOTE: The number of results detected exceeds the storage space allocated.
>
> {/stderr_txt}
> {/stderr_out}
> {ready_to_report/}
> {wu_name}05my04ab.172.10658.579834.189{/wu_name}
> {report_deadline}1097809711{/report_deadline}
> {file_ref}
> {file_name}05my04ab.172.10658.579834.189_4_0{/file_name}
> {open_name}result.sah{/open_name}
> {/file_ref}
> {/result}
>
>
>
> Hmmmm... The number of results detected exceed the storage space allocated?
> Which side is this on, my box or the server?
>
>

HMMMMMMM.... I just had a thought.... Remember when we used to get WUs that would only take a few minutes to process? I wonder if these messages are because of those WUs.

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....
ID: 34548 · Report as offensive
Profile Siran d'Vel'nahr
Volunteer tester
Avatar

Send message
Joined: 23 May 99
Posts: 7110
Credit: 28,704,019
RAC: 116,052
United States
Message 34553 - Posted: 9 Oct 2004, 19:23:55 UTC - in response to Message 34405.  

> Running WindowsXP, BOINC ver.4.09, setiathome ver.4.05 on a:
> System: AMD 3200+ 2.25 Ghz, L1 128kb, L2 512kb
> RAM: 512meg DDR400
> Graphics: ATI 9600 Pro 256mb
> HD: Western Digital 80gb 7200rpm 8mb cache
>
> Even though WU processing time has increased, from approx. 2.1hrs to 3.6hrs,
> this doesn't bother me. It would be nice if "THEY" would or could give us a
> nice short explanation why?
>
> But this upload problem, on every WU processed with ver.4.05, with no info
> addressing it will just make me stop processing WU's until it is addressed and
> solved. I'll just return to SETI classic until then. The "silence" from the
> SETI development team is deafening. Its like they took Public Relations
> lessons from the Division of Motor Vehicles, ie: contempt for those that keep
> them in business.
>
>
> SETI@home 2004-10-09 00:06:08 Started
> upload of 14mr04aa.17223.13314.211098.41_1_0
> SETI@home 2004-10-09 00:06:14 Error on
> file upload: file_upload_handler: no filename; nbytes 9722.000000
> SETI@home 2004-10-09 00:06:14
> Permanently failed upload of 14mr04aa.17223.13314.211098.41_1_0
> SETI@home 2004-10-09 00:06:14 Giving up
> on upload of 14mr04aa.17223.13314.211098.41_1_0: server rejected file
>
>

Did your AMD replace the PC pictured in your avatar? If it did, was the avatar an Intel machine? Did running SETI cause the avatar PC to look like that after some time? That PC looks very well used! ;-)

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....
ID: 34553 · Report as offensive
Profile Kirsten
Volunteer tester
Avatar

Send message
Joined: 7 Jul 00
Posts: 190
Credit: 566,047
RAC: 0
Denmark
Message 34573 - Posted: 9 Oct 2004, 21:07:22 UTC
Last modified: 9 Oct 2004, 21:08:45 UTC

Some more examples of wu's being rejected as of today (October 9th). I would appreciate some reaction from someone, preferably developers.

SETI@home - 2004-10-09 09:46:56 - Permanently failed upload of 27ap04aa.24346.19216.78404.26_1_0
SETI@home - 2004-10-09 09:46:56 - Giving up on upload of 27ap04aa.24346.19216.78404.26_1_0: server rejected file
SETI@home - 2004-10-09 09:46:56 - Error on file upload: file_upload_handler: no filename; nbytes 15553.000000

SETI@home - 2004-10-09 10:52:38 - Permanently failed upload of 14mr04aa.17223.16178.217334.233_1_0
SETI@home - 2004-10-09 10:52:38 - Giving up on upload of 14mr04aa.17223.16178.217334.233_1_0: server rejected file
SETI@home - 2004-10-09 10:52:38 - Giving up on upload of 14mr04aa.17223.16178.217334.233_1_0: server rejected file


Greetings from Kirsten, Copenhagen, DK
ID: 34573 · Report as offensive
Profile The worm that turned
Volunteer tester
Avatar

Send message
Joined: 15 May 99
Posts: 100
Credit: 4,872,533
RAC: 0
Australia
Message 34577 - Posted: 9 Oct 2004, 21:46:48 UTC
Last modified: 11 Oct 2004, 8:19:06 UTC

some of the stuff I'm getting this morning (Australian eastern time ).

SETI@home - 2004-10-09 21:46:07 - Unrecoverable error for result 14mr04aa.17223.19057.123566.85_1 ( - exit code -5 (0xfffffffb))
SETI@home - 2004-10-09 21:46:07 - Deferring communication with project for 1 minutes and 0 seconds
SETI@home - 2004-10-09 21:46:07 - Computation for result 14mr04aa.17223.19057.123566.85 finished
SETI@home - 2004-10-09 21:46:07 - Starting result 14mr04aa.17223.19009.454834.102_0 using setiathome version 4.05
SETI@home - 2004-10-09 21:46:12 - Error on file upload: file_upload_handler: no filename; nbytes 9930.000000
SETI@home - 2004-10-09 21:46:12 - Permanently failed upload of 14mr04aa.17223.19009.454834.101_0_0
SETI@home - 2004-10-09 21:46:12 - Giving up on upload of 14mr04aa.17223.19009.454834.101_0_0: server rejected file
SETI@home - 2004-10-09 21:46:29 - Computation for result 14mr04aa.17223.19009.454834.97 finished
SETI@home - 2004-10-09 21:46:29 - Starting result 14mr04aa.17223.19009.454834.104_0 using setiathome version 4.05
SETI@home - 2004-10-09 21:46:29 - Started upload of 14mr04aa.17223.19009.454834.97_1_0
SETI@home - 2004-10-09 21:46:52 - Error on file upload: file_upload_handler: no filename; nbytes 11713.000000
SETI@home - 2004-10-09 21:46:52 - Permanently failed upload of 14mr04aa.17223.19009.454834.97_1_0
SETI@home - 2004-10-09 21:46:52 - Giving up on upload of 14mr04aa.17223.19009.454834.97_1_0: server rejected file
SETI@home - 2004-10-09 22:00:50 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-10-09 22:00:54 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - 2004-10-10 00:39:08 - Computation for result 14mr04aa.17223.19009.454834.102 finished
SETI@home - 2004-10-10 00:39:08 - Starting result 14mr04aa.17223.19009.454834.93_2 using setiathome version 4.05
SETI@home - 2004-10-10 00:39:08 - Started upload of 14mr04aa.17223.19009.454834.102_0_0
SETI@home - 2004-10-10 00:39:19 - Error on file upload: file_upload_handler: no
ID: 34577 · Report as offensive
Craig Dickinson

Send message
Joined: 15 Jun 99
Posts: 1
Credit: 1,067,059
RAC: 0
United Kingdom
Message 34583 - Posted: 9 Oct 2004, 22:01:07 UTC

I'va also had 3 failed work units in the last two days. The final message is always SERVER REJECTED FILE. Is this possibly linked to the fact that the SAH_Validate Server is offline.
ID: 34583 · Report as offensive
Profile Marcin Radzikowski

Send message
Joined: 15 May 99
Posts: 17
Credit: 10,988,180
RAC: 147
Canada
Message 34593 - Posted: 9 Oct 2004, 22:43:13 UTC

I've had 4 or 5 of my last COMPLETED work units rejected by the server. I have no problem if there is no work or something minor wrong with the project. However, having my computer cruch the data, complete it and then have it REJECTED by the server is not right. I've detached from the project and won't be wasting my CPU time on this until it is fixed. Climateprediction.net doesn't have such issues and neither did Predictor.


---

ID: 34593 · Report as offensive
geoff

Send message
Joined: 25 Apr 00
Posts: 123
Credit: 33,507,708
RAC: 0
United Kingdom
Message 34597 - Posted: 9 Oct 2004, 22:53:44 UTC

Is anybody at SSL reading this thread?? My PCs are crunching like mad and NO credits appearing, it seems to me a waste of my CPU time. The SNAP hardware seems to be unreliable and if my PC was like it I would put it on the scrap heap. I will detach from project soon if things dont get better.
A reply from SSL PLEEEEEASE.
ID: 34597 · Report as offensive
Profile Siran d'Vel'nahr
Volunteer tester
Avatar

Send message
Joined: 23 May 99
Posts: 7110
Credit: 28,704,019
RAC: 116,052
United States
Message 34686 - Posted: 10 Oct 2004, 2:29:12 UTC
Last modified: 10 Oct 2004, 2:33:58 UTC

Ok, the dev team has finally noticed (figured out) that there is an upload problem.

Please note:

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.


Here we go again, another unpteenth upgrade to the SETI Client.

EDIT: Please excuse my fat fingers.... The Core Client will be the upgrade, not the SETI Client, I hope.

EDIT AGAIN: Uhhh. v4.09 CC was working just fine using the v4.03 SETI Client. These problems didn't appear until the upgrade to v4.05 SETI Client. So why work on the Core Client?

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....
ID: 34686 · Report as offensive
EclipseHA

Send message
Joined: 28 Jul 99
Posts: 1018
Credit: 528,523
RAC: 0
United States
Message 34697 - Posted: 10 Oct 2004, 2:42:07 UTC - in response to Message 34686.  


> EDIT AGAIN: Uhhh. v4.09 CC was working just fine using the v4.03 SETI
> Client. These problems didn't appear until the upgrade to v4.05 SETI Client.
> So why work on the Core Client?

And the CC works fine on other projects...

It's the server code.... (under UCB's control for seti, but not the other projects!)

Seti will distribute a new CC which works with their server code, but break LHC and CPD - I can just see it now!
ID: 34697 · Report as offensive
Profile Siran d'Vel'nahr
Volunteer tester
Avatar

Send message
Joined: 23 May 99
Posts: 7110
Credit: 28,704,019
RAC: 116,052
United States
Message 34698 - Posted: 10 Oct 2004, 2:46:25 UTC - in response to Message 34697.  

>
> > EDIT AGAIN: Uhhh. v4.09 CC was working just fine using the v4.03
> SETI
> > Client. These problems didn't appear until the upgrade to v4.05 SETI
> Client.
> > So why work on the Core Client?
>
> And the CC works fine on other projects...
>
> It's the server code.... (under UCB's control for seti, but not the other
> projects!)
>
> Seti will distribute a new CC which works with their server code, but break
> LHC and CPD - I can just see it now!
>
>

Oh drats.... That means I'll have problems with LHC and CPDN and SETI. 3 up 3 down....

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....
ID: 34698 · Report as offensive
Profile Brian Uitti
Volunteer tester
Avatar

Send message
Joined: 14 Sep 99
Posts: 39
Credit: 547,983
RAC: 0
United States
Message 34699 - Posted: 10 Oct 2004, 2:52:31 UTC

I've got some of this bad news too..

One machine: BOINC Client 4.09/SETI Version 4.05
SETI@home - 2004-10-09 19:07:21 - Started upload of
06my04ab.9911.22514.1028410.108_4_0
SETI@home - 2004-10-09 19:07:26 - Error on file upload:
file_upload_handler: no filename; nbytes 17046.000000
SETI@home - 2004-10-09 19:07:26 - Permanently failed upload of
06my04ab.9911.22514.1028410.108_4_0
SETI@home - 2004-10-09 19:07:26 - Giving up on upload of
06my04ab.9911.22514.1028410.108_4_0: server rejected file

Another machine..
Bad News:
SETI@home - 2004-10-09 09:32:13 - Started upload of
14mr04aa.17223.3682.117328.9_1_0
SETI@home - 2004-10-09 09:32:40 - Error on file upload:
file_upload_handler: no filename; nbytes 12698.000000
SETI@home - 2004-10-09 09:32:40 - Permanently failed upload of
14mr04aa.17223.3682.117328.9_1_0
SETI@home - 2004-10-09 09:32:40 - Giving up on upload of
14mr04aa.17223.3682.117328.9_1_0: server rejected file

More Bad News:
SETI@home - 2004-10-09 16:15:00 - Started upload of
14mr04aa.17223.11058.186078.228_1_0
SETI@home - 2004-10-09 16:15:06 - Error on file upload:
file_upload_handler: no filename; nbytes 8871.000000
SETI@home - 2004-10-09 16:15:06 - Permanently failed upload of
14mr04aa.17223.11058.186078.228_1_0
SETI@home - 2004-10-09 16:15:06 - Giving up on upload of
14mr04aa.17223.11058.186078.228_1_0: server rejected file

Good News:
SETI@home - 2004-10-09 17:15:00 - Starting result
14mr04aa.17223.14065.223570.238_1 using setiathome version 4.05
SETI@home - 2004-10-09 17:19:12 - Computation for result
14mr04aa.17223.14065.223570.238 finished
SETI@home - 2004-10-09 17:19:12 - Starting result
14mr04aa.17223.22162.567312.117_0 using setiathome version 4.05
SETI@home - 2004-10-09 17:19:12 - Started upload of
14mr04aa.17223.14065.223570.238_1_0
SETI@home - 2004-10-09 17:19:18 - Finished upload of
14mr04aa.17223.14065.223570.238_1_0
SETI@home - 2004-10-09 17:19:18 - Throughput 10492 bytes/sec

So, it's not all bad!

// Brian
ID: 34699 · Report as offensive
Profile abject
Avatar

Send message
Joined: 3 Apr 99
Posts: 65
Credit: 857,951
RAC: 0
United States
Message 34859 - Posted: 10 Oct 2004, 15:22:17 UTC

(Cross-post from the Linux help desk thread about this problem)

The front-page news says:

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.
ID: 34859 · Report as offensive
Profile Rachel
Avatar

Send message
Joined: 13 Apr 02
Posts: 978
Credit: 449,704
RAC: 0
United Kingdom
Message 35058 - Posted: 11 Oct 2004, 6:59:17 UTC - in response to Message 34859.  

> (Cross-post from the Linux help desk thread about this problem)
>
> The front-page news says:
>
> 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.
>

Reset the project and my wu's are uploading fine now for the last 15 hours.I think it was a bad batch of wu's myself not the system because if it was the system no wu's would upload surely?A person said I should of not reset as other people will have to wait weeks to get credit but I replied saying my wu results were not being sent back anyway as they were being deleted after failed uploads.So the only thing to do was reset and it seems the batch of wu's I am now running are fine.
......In Space No One Can Hear You Scream......



ID: 35058 · Report as offensive
Profile The worm that turned
Volunteer tester
Avatar

Send message
Joined: 15 May 99
Posts: 100
Credit: 4,872,533
RAC: 0
Australia
Message 35063 - Posted: 11 Oct 2004, 7:26:33 UTC

I have different work units on different machines failing .
So it's not just a batch of faulty work units
Or if it is then more than one date is involved.
All we can do is wait for more information from admin
In the meantime i've disabled network access to boinc.


visit boinc@Australia

ID: 35063 · Report as offensive
Profile Paul D. Buck
Volunteer tester

Send message
Joined: 19 Jul 00
Posts: 3898
Credit: 1,158,042
RAC: 0
United States
Message 35112 - Posted: 11 Oct 2004, 13:22:33 UTC

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 [b]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 ...
ID: 35112 · Report as offensive
Gareth Lock

Send message
Joined: 14 Aug 02
Posts: 358
Credit: 952,720
RAC: 134
United Kingdom
Message 35127 - Posted: 11 Oct 2004, 14:08:58 UTC

I've had another look through my logs and it does seem to be that 90% of my failures have been on WUs starting with 14mr as their ID. Maybe it is a batch of dud WUs... I'm not sure.

I can confirm however, that it is not to do with 4.05 because it was happening with these "mr" WUs BEFORE I reset the project, it was only resetting the project that gave me SETI v4.05.

I have two machines. One is a Athlon64 FX53, the other is the one I started this project on, an Athlon XP 1900+. Both are running CCv4.09 with SAHv4.05. Both are exhibiting similar upload problems. They share a wireless gateway/router on a DSL connection.



ID: 35127 · Report as offensive
Profile Scallywag
Avatar

Send message
Joined: 23 May 04
Posts: 162
Credit: 100,318
RAC: 0
Canada
Message 35130 - Posted: 11 Oct 2004, 14:29:04 UTC

Did you reset your project.
This is damn peculiar because I'm still running 4.05 Uploads and down loads are working fine.Just got a new set over night.
I Refuse to hold myself responsible for any of my actions.

si hoc legere scis nimium eruditionis habes
ID: 35130 · Report as offensive
Gareth Lock

Send message
Joined: 14 Aug 02
Posts: 358
Credit: 952,720
RAC: 134
United Kingdom
Message 35137 - Posted: 11 Oct 2004, 15:03:24 UTC
Last modified: 11 Oct 2004, 15:05:23 UTC

As I mentioned earlier in this thread, I reset the project on both machines within a day of each other. Another look at the logs and the last cough reported this...

SETI@home - 2004-10-11 15:54:22 - Started upload of 14mr04aa.17223.23506.654818.169_1_0
SETI@home - 2004-10-11 15:54:30 - Error on file upload: file_upload_handler: no filename; nbytes 12608.000000
SETI@home - 2004-10-11 15:54:30 - Permanently failed upload of 14mr04aa.17223.23506.654818.169_1_0
SETI@home - 2004-10-11 15:54:30 - Giving up on upload of 14mr04aa.17223.23506.654818.169_1_0: server rejected file

This was the last "completed" workunit. As you can see, this was completed a moment ago. I reset about a week and a half ago, hoping this would solve it. It was only when I started this thread a couple of days later I got a reliable enough internet connection to post it. It's still somewhat flakey now.

Anyone who looks at my stats will notice that my Athlon64 has apparently done nothing. It goes through a WU in about 3 hrs. Every one I've uploaded to date has been rejected.





ID: 35137 · Report as offensive
Profile Scallywag
Avatar

Send message
Joined: 23 May 04
Posts: 162
Credit: 100,318
RAC: 0
Canada
Message 35141 - Posted: 11 Oct 2004, 15:33:52 UTC
Last modified: 11 Oct 2004, 15:34:28 UTC

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 Refuse to hold myself responsible for any of my actions.

si hoc legere scis nimium eruditionis habes
ID: 35141 · Report as offensive
Previous · 1 · 2 · 3 · 4 · 5 . . . 7 · Next

Message boards : Number crunching : Still having WU files refused.


 
©2019 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.