I have a Run Unit waiting for Upload.

in the message section I found a lot of

20.03.2007 22:16:19|SETI@home|[file_xfer] Started upload of file 30no04ab.9158.29361.698572.3.156_0_0
20.03.2007 22:18:05|SETI@home|[error] Error on file upload: socket read incomplete: asked for 10195, got 7940: No such file or directory
20.03.2007 22:18:05|SETI@home|[file_xfer] Temporarily failed upload of 30no04ab.9158.29361.698572.3.156_0_0: transient upload error

No problems with other run units (by now).

What do I have to do? Abort Transfer?

Bye,
Franz

---

This is a rare class of error I've been trying to get the BOINC developers to take an interest in - see Error on file upload: Socket Read incomplete on the BOINC Dev boards.

First, and most importantly, what version of BOINC are you running on the machine with the problem? The devs claim the problem is fixed in BOINC v5.8.11, but two people have proved them wrong. So far, I've seen no reports on v5.8.15, so I'd be interested in further information if you're running v5.8.15: if you're running an earlier version, it probably isn't worth taking it much further. Nobody seems to have found a way to recover from this, so just abort the transfer and let the WU report in the normal way.

If it's BOINC v5.8.15, could you tell us which machine has the problem (in particular, is it a dual- or multi-core?), and could you post a section of the message log covering the end of the crunch run and the first of the upload errors? [No need for all the repetitions - once it's gone wrong once, the rest don't tell us anything new].

Thanks.

I don't know what time zone Francesco is in, but one of my hosts had a batch of three validate errors. From looking the WU details I have, it looks to have run from around 1520 to 2200 UTC. This looks to me like Kryten was having another psychotic episode at that time, although I suppose it could have been just a rough restart after the outage.

Alinator

Subject to further information, and assuming it's similar to earlier episodes, I'm pretty sure Francesco's error is client-side, not server-side: in other words, his PC is offering duff data to Berkeley, rather than any problem at the project end regarding readiness to receive it. But we'll wait and see.

This is a rare class of error I've been trying to get the BOINC developers to take an interest in - see Error on file upload: Socket Read incomplete on the BOINC Dev boards.

First, and most importantly, what version of BOINC are you running on the machine with the problem? The devs claim the problem is fixed in BOINC v5.8.11, but two people have proved them wrong. So far, I've seen no reports on v5.8.15, so I'd be interested in further information if you're running v5.8.15: if you're running an earlier version, it probably isn't worth taking it much further. Nobody seems to have found a way to recover from this, so just abort the transfer and let the WU report in the normal way.

If it's BOINC v5.8.15, could you tell us which machine has the problem (in particular, is it a dual- or multi-core?), and could you post a section of the message log covering the end of the crunch run and the first of the upload errors? [No need for all the repetitions - once it's gone wrong once, the rest don't tell us anything new].

Thanks.

I've had them happen on 5.8.15 not to long ago, Beyond that It happened on PC1. As to when I don't remember that much. sorry.

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

First, and most importantly, what version of BOINC are you running on the machine with the problem? The devs claim the problem is fixed in BOINC v5.8.11, but two people have proved them wrong. So far, I've seen no reports on v5.8.15, so I'd be interested in further information if you're running v5.8.15: if you're running an earlier version, it probably isn't worth taking it much further. Nobody seems to have found a way to recover from this, so just abort the transfer and let the WU report in the normal way.

If it's BOINC v5.8.15, could you tell us which machine has the problem (in particular, is it a dual- or multi-core?), and could you post a section of the message log covering the end of the crunch run and the first of the upload errors? [No need for all the repetitions - once it's gone wrong once, the rest don't tell us anything new].

Thanks.

Ok, here I am ....sorry but I was sleeping :-)

1) here is my host coordinates
http://setiathome.berkeley.edu/show_host_detail.php?hostid=2855752
2) I'm running 5.8.8 and the Optimized apps by Simon Zadra R-2.2B
(for CPUID: Intel Core 2 Duo 'Conroe')
3) No log about the crunch run, because I have exited the application to restart BOINC yesterday evening.

Can I install 5.8.15 or do you have any other questions about my system as it's now?

Bye,
Franz

---

more info.

Effectively the file size is 7940 bytes.
I have aborted the upload and now the RU is reported as:
http://setiathome.berkeley.edu/result.php?resultid=500956212

I have saved a copy of the file on my Host, for future use if you need it.

Bye,
Franz

---

1) here is my host coordinates
http://setiathome.berkeley.edu/show_host_detail.php?hostid=2855752
2) I'm running 5.8.8 and the Optimized apps by Simon Zadra R-2.2B
(for CPUID: Intel Core 2 Duo 'Conroe')

No surprise there - I think this is a problem limited to multi-core machines.

3) No log about the crunch run, because I have exited the application to restart BOINC yesterday evening.

You could find the old log details in 'stdoutdae.txt' if you're interested, but I doubt the devs will take any notice as it isn't the current version of BOINC.

Effectively the file size is 7940 bytes.
I have aborted the upload and now the RU is reported as:
http://setiathome.berkeley.edu/result.php?resultid=500956212

Yes, that's typical. Note that your machine only ran for 134 seconds, whereas the other quorum members did a full run. I expect yours did do the full run, but then started all over again before the upload: what you have will be the shorter 'work in progress' result file, rather than a full one with the result summary at the end. The full file, from the end of the first run, would have been 10195 bytes in length: that's what BOINC told Berkeley to expect when it first offered the upload, and that's what got the servers confused - hence the error.

Can I install 5.8.15 or do you have any other questions about my system as it's now?

v5.8.15 seems to be working well for me - some people have reported problems, but it seems to be the best of the 5.8.x range so far. So yes, I would suggest you install it - there's nothing extra we need to learn about v5.8.8

v5.8.15 seems to be working well for me - some people have reported problems, but it seems to be the best of the 5.8.x range so far. So yes, I would suggest you install it - there's nothing extra we need to learn about v5.8.8

Ok, now I do it.

Bye and thanks for collaboration!

Franz

---

Got one, Running on a Quad core cpu in Windows XP x64 sp2, And this is with Boinc 5.8.15.

3/21/2007 10:47:25 AM|SETI@home|[file_xfer] Started upload of file 13mr04aa.25128.15362.679814.3.41_3_0
3/21/2007 10:47:28 AM|SETI@home|Error on file upload: socket read incomplete: asked for 13832, got 7422: No such file or directory
3/21/2007 10:47:28 AM|SETI@home|[file_xfer] Temporarily failed upload of 13mr04aa.25128.15362.679814.3.41_3_0: transient upload error
3/21/2007 10:47:28 AM|SETI@home|Backing off 3 hr 50 min 12 sec on upload of file 13mr04aa.25128.15362.679814.3.41_3_0
3/21/2007 10:47:34 AM|SETI@home|[file_xfer] Started upload of file 13mr04aa.25128.15362.679814.3.41_3_0
3/21/2007 10:47:37 AM|SETI@home|Error on file upload: socket read incomplete: asked for 13832, got 7422: No such file or directory
3/21/2007 10:47:37 AM|SETI@home|[file_xfer] Temporarily failed upload of 13mr04aa.25128.15362.679814.3.41_3_0: transient upload error
3/21/2007 10:47:37 AM|SETI@home|Backing off 1 hr 50 min 23 sec on upload of file 13mr04aa.25128.15362.679814.3.41_3_0

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

This is a rare class of error I've been trying to get the BOINC developers to take an interest in - see Error on file upload: Socket Read incomplete on the BOINC Dev boards.

First, and most importantly, what version of BOINC are you running on the machine with the problem? The devs claim the problem is fixed in BOINC v5.8.11, but two people have proved them wrong. So far, I've seen no reports on v5.8.15, so I'd be interested in further information if you're running v5.8.15: if you're running an earlier version, it probably isn't worth taking it much further. Nobody seems to have found a way to recover from this, so just abort the transfer and let the WU report in the normal way.

If it's BOINC v5.8.15, could you tell us which machine has the problem (in particular, is it a dual- or multi-core?), and could you post a section of the message log covering the end of the crunch run and the first of the upload errors? [No need for all the repetitions - once it's gone wrong once, the rest don't tell us anything new].

Thanks.

Well since I'm not a Beta participant or a dev, I can't post there, I've posted about the error just befor this post and read the linked thread there, So they think they fixed It in 5.8.11, Well You and I both know their wrong. It exists in 5.8.15 still to this day.

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

This is a rare class of error I've been trying to get the BOINC developers to take an interest in - see Error on file upload: Socket Read incomplete on the BOINC Dev boards.

First, and most importantly, what version of BOINC are you running on the machine with the problem? The devs claim the problem is fixed in BOINC v5.8.11, but two people have proved them wrong. So far, I've seen no reports on v5.8.15, so I'd be interested in further information if you're running v5.8.15: if you're running an earlier version, it probably isn't worth taking it much further. Nobody seems to have found a way to recover from this, so just abort the transfer and let the WU report in the normal way.

If it's BOINC v5.8.15, could you tell us which machine has the problem (in particular, is it a dual- or multi-core?), and could you post a section of the message log covering the end of the crunch run and the first of the upload errors? [No need for all the repetitions - once it's gone wrong once, the rest don't tell us anything new].

Thanks.

Well since I'm not a Beta participant or a dev, I can't post there, I've posted about the error just befor this post and read the linked thread there, So they think they fixed It in 5.8.11, Well You and I both know their wrong. It exists in 5.8.15 still to this day.

To save me looking, could you list one of the WU / Result / Computer IDs, please?

And more importantly, could you dig out the message log covering the period when the WU finished, possibly restarted, and first attempted to upload? It would be a good idea to include any log entries for a minute or two either side of that lot, so we see it in context. Either post it here, or email to initial [dot] surname [at] btinternet [dot] com - I can mark it up and upload it to the dev board for you. Thanks.

[PS - if it's scrolled off the top of your messages list, you can get the older entries from 'stdoutdae.txt' (BOINC directory) - or if that fails, zip that whole file and email it to me]

Well since I'm not a Beta participant or a dev, I can't post there, I've posted about the error just befor this post and read the linked thread there, So they think they fixed It in 5.8.11, Well You and I both know their wrong. It exists in 5.8.15 still to this day.

The BOINC message boards are open for anyone to join.

http://boinc.berkeley.edu/dev/forum_thread.php?id=1575

You will find a few familiar names there too :-)

Keith.

This is a rare class of error I've been trying to get the BOINC developers to take an interest in - see Error on file upload: Socket Read incomplete on the BOINC Dev boards.

First, and most importantly, what version of BOINC are you running on the machine with the problem? The devs claim the problem is fixed in BOINC v5.8.11, but two people have proved them wrong. So far, I've seen no reports on v5.8.15, so I'd be interested in further information if you're running v5.8.15: if you're running an earlier version, it probably isn't worth taking it much further. Nobody seems to have found a way to recover from this, so just abort the transfer and let the WU report in the normal way.

If it's BOINC v5.8.15, could you tell us which machine has the problem (in particular, is it a dual- or multi-core?), and could you post a section of the message log covering the end of the crunch run and the first of the upload errors? [No need for all the repetitions - once it's gone wrong once, the rest don't tell us anything new].

Thanks.

Well since I'm not a Beta participant or a dev, I can't post there, I've posted about the error just befor this post and read the linked thread there, So they think they fixed It in 5.8.11, Well You and I both know their wrong. It exists in 5.8.15 still to this day.

To save me looking, could you list one of the WU / Result / Computer IDs, please?

And more importantly, could you dig out the message log covering the period when the WU finished, possibly restarted, and first attempted to upload? It would be a good idea to include any log entries for a minute or two either side of that lot, so we see it in context. Either post it here, or email to initial [dot] surname [at] btinternet [dot] com - I can mark it up and upload it to the dev board for you. Thanks.

[PS - if it's scrolled off the top of your messages list, you can get the older entries from 'stdoutdae.txt' (BOINC directory) - or if that fails, zip that whole file and email it to me]

Computer ID is: 2933190
WU: 13mr04aa.25128.15362.679814.3.41_3_0

from 'Boinc 5.8.15'
3/21/2007 10:47:25 AM|SETI@home|[file_xfer] Started upload of file 13mr04aa.25128.15362.679814.3.41_3_0
3/21/2007 10:47:28 AM|SETI@home|Error on file upload: socket read incomplete: asked for 13832, got 7422: No such file or directory

from 'stdoutdae.txt'
2007-03-21 03:16:03 [SETI@home] Scheduler RPC succeeded [server version 509]
2007-03-21 03:16:03 [SETI@home] Deferring communication 11 sec, because requested by project
2007-03-21 03:29:19 [SETI@home] Computation for task 13mr04aa.25128.15362.679814.3.17_0 finished
2007-03-21 03:29:19 [SETI@home] Resuming task 04se04aa.14192.30096.934640.3.134_2 using setiathome_enhanced version 515
2007-03-21 03:29:22 [SETI@home] [file_xfer] Started upload of file 13mr04aa.25128.15362.679814.3.17_0_0
2007-03-21 03:29:26 [SETI@home] [file_xfer] Finished upload of file 13mr04aa.25128.15362.679814.3.17_0_0
2007-03-21 03:29:26 [SETI@home] [file_xfer] Throughput 12730 bytes/sec
2007-03-21 03:29:28 [SETI@home] Sending scheduler request: To report completed tasks
2007-03-21 03:29:28 [SETI@home] Reporting 1 tasks
2007-03-21 03:29:38 [SETI@home] Scheduler RPC succeeded [server version 509]
2007-03-21 03:29:38 [SETI@home] Deferring communication 11 sec, because requested by project
2007-03-21 03:29:45 [SETI@home] Computation for task 13mr04aa.25128.15362.679814.3.64_0 finished
2007-03-21 03:29:45 [SETI@home] Resuming task 04se04aa.14192.30049.211072.3.148_2 using setiathome_enhanced version 515
2007-03-21 03:29:46 [SETI@home] Computation for task 13mr04aa.25128.15362.679814.3.41_3 finished
2007-03-21 03:29:47 [SETI@home] [file_xfer] Started upload of file 13mr04aa.25128.15362.679814.3.64_0_0
2007-03-21 03:29:47 [---] Starting 13mr04aa.25128.15362.679814.3.41_3
2007-03-21 03:29:47 [SETI@home] Starting task 13mr04aa.25128.15362.679814.3.41_3 using setiathome_enhanced version 515
2007-03-21 03:29:49 [SETI@home] [file_xfer] Started upload of file 13mr04aa.25128.15362.679814.3.41_3_0
2007-03-21 03:29:51 [SETI@home] [file_xfer] Finished upload of file 13mr04aa.25128.15362.679814.3.64_0_0
2007-03-21 03:29:51 [SETI@home] [file_xfer] Throughput 10210 bytes/sec
2007-03-21 03:29:52 [SETI@home] Error on file upload: socket read incomplete: asked for 13832, got 7422: No such file or directory
2007-03-21 03:29:52 [SETI@home] [file_xfer] Temporarily failed upload of 13mr04aa.25128.15362.679814.3.41_3_0: transient upload error
2007-03-21 03:29:52 [SETI@home] Backing off 1 min 0 sec on upload of file 13mr04aa.25128.15362.679814.3.41_3_0
2007-03-21 03:29:52 [SETI@home] Computation for task 04se04aa.14192.30049.211072.3.148_2 finished
2007-03-21 03:29:52 [SETI@home] Resuming task 04se04aa.14192.30049.211072.3.178_0 using setiathome_enhanced version 515
2007-03-21 03:29:52 [SETI@home] Resuming task 04se04aa.14192.30290.636084.3.138_2 using setiathome_enhanced version 515
2007-03-21 03:29:55 [SETI@home] Sending scheduler request: To report completed tasks
2007-03-21 03:29:55 [SETI@home] Reporting 1 tasks
2007-03-21 03:29:55 [SETI@home] [file_xfer] Started upload of file 04se04aa.14192.30049.211072.3.148_2_0
2007-03-21 03:30:03 [SETI@home] [file_xfer] Finished upload of file 04se04aa.14192.30049.211072.3.148_2_0
2007-03-21 03:30:03 [SETI@home] [file_xfer] Throughput 4072 bytes/sec
2007-03-21 03:30:05 [SETI@home] Scheduler RPC succeeded [server version 509]
2007-03-21 03:30:05 [SETI@home] Deferring communication 11 sec, because requested by project
2007-03-21 03:30:11 [SETI@home] Computation for task 04se04aa.14192.30049.211072.3.178_0 finished
2007-03-21 03:30:11 [SETI@home] Restarting task 25ja04aa.20240.13504.990916.3.39_1 using setiathome_enhanced version 515
2007-03-21 03:30:13 [SETI@home] [file_xfer] Started upload of file 04se04aa.14192.30049.211072.3.178_0_0
2007-03-21 03:30:16 [SETI@home] Sending scheduler request: To report completed tasks
2007-03-21 03:30:16 [SETI@home] Reporting 1 tasks
2007-03-21 03:30:20 [SETI@home] [file_xfer] Finished upload of file 04se04aa.14192.30049.211072.3.178_0_0
2007-03-21 03:30:20 [SETI@home] [file_xfer] Throughput 8789 bytes/sec
2007-03-21 03:30:27 [SETI@home] Scheduler RPC succeeded [server version 509]

Hopefully this will do, As to result, That is either the text output or I'm stumped.

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

Computer ID is: 2933190
WU: 13mr04aa.25128.15362.679814.3.41_3_0

from 'Boinc 5.8.15'
3/21/2007 10:47:25 AM|SETI@home|[file_xfer] Started upload of file 13mr04aa.25128.15362.679814.3.41_3_0
3/21/2007 10:47:28 AM|SETI@home|Error on file upload: socket read incomplete: asked for 13832, got 7422: No such file or directory

from 'stdoutdae.txt'....<snipped>

Thanks - the message log is exactly what I was looking for, and confirms the previous pattern.

The only slight fly in the ointment is that result 501592013 - I think that's the right one - reports as being BOINC v5.9.0: presumably a 64-bit one, to match your XP Pro x64 on that machine? Can you let us know whose compilation you used, and how sure you are that is was made from the stable v5.8.15 codebase, otherwise the devs may not accept that the problem lies in the Berkeley code.

> see Matt's NEW Post - Switcheroo (Mar 21 2007)

Computer ID is: 2933190
WU: 13mr04aa.25128.15362.679814.3.41_3_0

from 'Boinc 5.8.15'
3/21/2007 10:47:25 AM|SETI@home|[file_xfer] Started upload of file 13mr04aa.25128.15362.679814.3.41_3_0
3/21/2007 10:47:28 AM|SETI@home|Error on file upload: socket read incomplete: asked for 13832, got 7422: No such file or directory

from 'stdoutdae.txt'....<snipped>

Thanks - the message log is exactly what I was looking for, and confirms the previous pattern.

The only slight fly in the ointment is that result 501592013 - I think that's the right one - reports as being BOINC v5.9.0: presumably a 64-bit one, to match your XP Pro x64 on that machine? Can you let us know whose compilation you used, and how sure you are that is was made from the stable v5.8.15 codebase, otherwise the devs may not accept that the problem lies in the Berkeley code.

I have 5.9.0.32 of Crunch3r's Boinc files copied into the Boinc 5.8.15 folder and the whole folder/directory is filled with 32bit files and the Seti app is only the Chickens 2.2B which is also 32bit, Only the OS is 64bit of course(XP x64), Otherwise It's a normal Boinc install.

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

Computer ID is: 2933190
WU: 13mr04aa.25128.15362.679814.3.41_3_0

from 'Boinc 5.8.15'
3/21/2007 10:47:25 AM|SETI@home|[file_xfer] Started upload of file 13mr04aa.25128.15362.679814.3.41_3_0
3/21/2007 10:47:28 AM|SETI@home|Error on file upload: socket read incomplete: asked for 13832, got 7422: No such file or directory

from 'stdoutdae.txt'....<snipped>

Thanks - the message log is exactly what I was looking for, and confirms the previous pattern.

The only slight fly in the ointment is that result 501592013 - I think that's the right one - reports as being BOINC v5.9.0: presumably a 64-bit one, to match your XP Pro x64 on that machine? Can you let us know whose compilation you used, and how sure you are that is was made from the stable v5.8.15 codebase, otherwise the devs may not accept that the problem lies in the Berkeley code.

I have 5.9.0.32 of Crunch3r's Boinc files copied into the Boinc 5.8.15 folder and the whole folder/directory is filled with 32bit files and the Seti app is only the Chickens 2.2B which is also 32bit, Only the OS is 64bit of course(XP x64), Otherwise It's a normal Boinc install.

It almost says to Me that the Devs want to see problems but will dismiss problems If they see anything from a setup Like I have, In other words It seems like they want users to use 5.8.15 only and no user created(read: better) code, If that's the case Why bother allowing better code from the likes of the Chicken(and Co.) and/or Crunch3r to be used at all? I mean what's next are they going to say Boinc should not be allowed to run on an Overclocked PC and have Boinc only run on DELL type PCs??

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

This just tripped my trigger!

Eric does actually support ways to make thing happen more quickly esp with MultiBeam coming online... Joe who is one of the creators of the current "Chicken" Optimized Seti Application is also a "Seti developer"... IF YOU OVERCLOCK ANYTHING IT IS YOUR RESPONIBILITY! IF YOU YOU USE AN OPTIMIZED BOINC CORE OR AN OPTIMIZED APPLICATION IT IS YOUR RESPONSIBILITY! IF YOU IGNORE IT THEN YOU ARE WRONG! RESONSIBLE REPORTING OF ERRORS TO THE "SOURCE" IS IMPORTANT AND YOUR RESPONSIBILITY! Otherwise some of those people are working on things that fix problems! They do not have time to read Everything!

So everyone has to figure out what is Important! Science or Credit! It has been proven that those that run "Optimized Anything and/or Seti Applications" tend to set it and forget it... They do not watch and upgrade as they should... Then they cause problems, that causes even More Problems than many know... The Forums are littered with them... Some of those can been seen in NC Forum saying my RAC Dropped! Then not understand all of the reasons why...

Edit:

This does not mention some of the Validate issues concern "optimized applications." Or Old Optimized Seti Applications!

Computer ID is: 2933190
WU: 13mr04aa.25128.15362.679814.3.41_3_0

from 'Boinc 5.8.15'
3/21/2007 10:47:25 AM|SETI@home|[file_xfer] Started upload of file 13mr04aa.25128.15362.679814.3.41_3_0
3/21/2007 10:47:28 AM|SETI@home|Error on file upload: socket read incomplete: asked for 13832, got 7422: No such file or directory

from 'stdoutdae.txt'....<snipped>

Thanks - the message log is exactly what I was looking for, and confirms the previous pattern.

The only slight fly in the ointment is that result 501592013 - I think that's the right one - reports as being BOINC v5.9.0: presumably a 64-bit one, to match your XP Pro x64 on that machine? Can you let us know whose compilation you used, and how sure you are that is was made from the stable v5.8.15 codebase, otherwise the devs may not accept that the problem lies in the Berkeley code.

I have 5.9.0.32 of Crunch3r's Boinc files copied into the Boinc 5.8.15 folder and the whole folder/directory is filled with 32bit files and the Seti app is only the Chickens 2.2B which is also 32bit, Only the OS is 64bit of course(XP x64), Otherwise It's a normal Boinc install.

It almost say that the Devs want to see problems but will dismiss problems If they see anything from a setup Like I have, In other words It seems like they want users to use 5.8.15 only and no user created(read better), If that's the case Why bother allowing better code from the likes of the Chicken(and Co.) and/or Crunch3r to be used at all? I mean what's next are they going to say Boinc should not be allowed to run on an Overclocked PC and have Boinc only run on DELL type PCs??

---

Please consider a Donation to the Seti Project.

Everyone loves you....as long as you're buying.