Alpha 5.7.5 - upload error

Message boards : BOINC client : Alpha 5.7.5 - upload error
Message board moderation

To post messages, you must log in.

AuthorMessage
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 5082
United Kingdom
Message 6682 - Posted: 28 Nov 2006, 14:02:54 UTC

(Yes I know it's alpha, but the alpha boards don't seem to be an active location for bug reports!)

Installed 5.7.5 as a service under Win XP SP2 on a brand-new dual Xeon workstation - 8 cores.

Attached to SETI (only) for the time being. First two WUs finished almost at the same time, and I got:

28/11/2006 12:48:47|SETI@home|Started upload of file 07jn03aa.5768.25602.767320.3.93_3_0
28/11/2006 12:48:47||Starting 07jn03aa.5768.25602.767320.3.92_0
28/11/2006 12:48:47|SETI@home|Starting task 07jn03aa.5768.25602.767320.3.92_0 using setiathome_enhanced version 517
28/11/2006 12:48:48|SETI@home|Started upload of file 07jn03aa.5768.25602.767320.3.92_0_0
28/11/2006 12:48:52|SETI@home|Error on file upload: socket read incomplete: asked for 11649, got 7425: No such file or directory
28/11/2006 12:48:52|SETI@home|Finished upload of file 07jn03aa.5768.25602.767320.3.93_3_0
28/11/2006 12:48:52|SETI@home|Throughput 9801 bytes/sec
28/11/2006 12:48:52|SETI@home|Temporarily failed upload of 07jn03aa.5768.25602.767320.3.92_0_0: transient upload error

in the message log.

It's a badly-written error message - from other checking, I think it means the uploaded file was shorter than expected (7425 bytes instead of 11649)

I also got some very odd information in the 'Tasks' tab of BOINC Manager:

BOINC Manager - (localhost)
CPU time: 00:01:25
Progress: 1.897%
To completion: ---
Report deadline: 02/12/2006 19:14:43
Status: Uploading

After a BOINC restart, I got:

28/11/2006 13:21:30|SETI@home|State file error: result 07jn03aa.5768.25602.767320.3.92_0 is in wrong state

and

CPU time: 01:43:28
Progress: 100.000%
To completion: ---
Report deadline: 02/12/2006 19:14:43
Status: Uploading

- but the upload kept on failing at about 75%, with the same error message in the log. In the end, I aborted it, and reverted down to BOINC 5.6.5 for the time being. I have fuller notes, and I'm willing to do more testing, if it would help.

ID: 6682 · Report as offensive
Profile KSMarksPsych
Avatar

Send message
Joined: 30 Oct 05
Posts: 1239
United States
Message 6683 - Posted: 28 Nov 2006, 16:43:35 UTC

Alpha email list is here.


Have you checked the Seti boards to see if anyone else is running into this?
Kathryn :o)
ID: 6683 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 5082
United Kingdom
Message 6684 - Posted: 28 Nov 2006, 16:53:30 UTC - in response to Message 6683.  
Last modified: 28 Nov 2006, 16:54:23 UTC

Alpha email list is here.

Have you checked the Seti boards to see if anyone else is running into this?

Thanks for the link, but I think I'll keep in on the boards for now. I hope I may be able to contribute more to testing now I've got more cores, but I'll let it settle down a bit first.

I'm going to post it on SETI later, and possibly on lunatics.at (since it was one of Simon's apps that went belly-up). But I do read those (SETI) boards quite closely, and I haven't seen any similar report that I can recall. The unusual thing about the event was two results finishing within a second of each other, and I wondered if BOINC (or SETI, or Windows) got the two result files muddled up.

But that c**p error message is certainly all down to BOINC!
ID: 6684 · Report as offensive

Message boards : BOINC client : Alpha 5.7.5 - upload error

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.