After switching back to SETI classic for eight months-I have downloaded the most recent version of Boinc and I have been running it actively.

However the Boinc system sent me a 11.50M file to compute. It is now 100% complete but it will not upload to the server. (I imagine because of its size and my slow modem speed)

I get messages like "backing off for 2 hours 33 minutes" ect. Well I'm not going to be on the internet forever (it ties up my phone line) and when I press retry now I forever get the same message about the system backing off.

If the system can't upload large files from a 56K modem- it shouldn't issue large files to a 56K modem in the first place. Now I am stuck with this completed workunit forever and it will never upload completely!!!

Any advise? (other than high speed internet -which I can't afford?)

Thanks!

---

What project(s) did you attach too?
Seti still only has 360kB (or so) Work Units to process & the results are generally around 13kB in size (smallest i've seen is 10kB & the largest around 22kB).

---

Grant
Darwin NT

The WUs aren't that big. What you probably downloaded was the new version of the SETI application itself.

You were probably getting the backoff message because the database was being backed up, it's now back online.

Post all the messages you got for a better answer.

---

Help and BOINC documentation is available here.

The WUs aren't that big. What you probably downloaded was the new version of the SETI application itself.

You were probably getting the backoff message because the database was being backed up, it's now back online.

Post all the messages you got for a better answer.

---

The WUs aren't that big. What you probably downloaded was the new version of the SETI application itself.

You were probably getting the backoff message because the database was being backed up, it's now back online.

Post all the messages you got for a better answer.

06/07/2005 4:45:07 PM||Resuming round-robin CPU scheduling.
06/07/2005 4:45:08 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
06/07/2005 4:45:08 PM|SETI@home|Requesting 0 seconds of work, returning 0 results
06/07/2005 4:45:13 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
06/07/2005 4:46:18 PM|SETI@home|Started upload of 30ja04aa.13768.3905.648582.244_0_0
06/07/2005 4:46:39 PM|SETI@home|Temporarily failed upload of 30ja04aa.13768.3905.648582.244_0_0: -106
06/07/2005 4:46:39 PM|SETI@home|Backing off 1 hours, 59 minutes, and 2 seconds on upload of file 30ja04aa.13768.3905.648582.244_0_0
06/07/2005 4:49:43 PM||request_reschedule_cpus: project op
06/07/2005 4:49:43 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
06/07/2005 4:49:43 PM|SETI@home|Requesting 0 seconds of work, returning 0 results
06/07/2005 4:49:47 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
06/07/2005 4:52:39 PM|SETI@home|Started upload of 30ja04aa.13768.3905.648582.244_0_0
06/07/2005 4:53:01 PM|SETI@home|Temporarily failed upload of 30ja04aa.13768.3905.648582.244_0_0: -106
06/07/2005 4:53:01 PM|SETI@home|Backing off 2 hours, 46 minutes, and 51 seconds on upload of file 30ja04aa.13768.3905.648582.244_0_0
06/07/2005 5:05:31 PM|SETI@home|Started upload of 30ja04aa.13768.3905.648582.244_0_0
06/07/2005 5:05:53 PM|SETI@home|Temporarily failed upload of 30ja04aa.13768.3905.648582.244_0_0: -106
06/07/2005 5:05:53 PM|SETI@home|Backing off 3 hours, 19 minutes, and 48 seconds on upload of file 30ja04aa.13768.3905.648582.244_0_0
06/07/2005 5:29:35 PM|SETI@home|Started upload of 30ja04aa.13768.3905.648582.244_0_0
06/07/2005 5:29:56 PM|SETI@home|Temporarily failed upload of 30ja04aa.13768.3905.648582.244_0_0: -106
06/07/2005 5:29:56 PM|SETI@home|Backing off 58 minutes and 32 seconds on upload of file 30ja04aa.13768.3905.648582.244_0_0

---

The Wiki has this to say about error code -106.

Error Code
-106 ERR_IO, a failure to read/write from the Disk Drive, or in the case of network transmissions, a failure to send and receive data.

A failure to send and receive data to and from a Project Server generally means that during the transmission to or from the Project Server, or a router along the way has reset the TCP connection between the BOINC Client Software and the Project Server. This can happen for a number of different reasons, such as the Project Server being overloaded, or packets being lost in route.

And I have to mention that the upload files are much smaller than the download files. (which as has already been stated, aren't even a single MB)

I'm confused because the web site says you have WU 15au03aa.6585.31554.261062.30_0 and only that WU, but the messages you post show WU 30ja04aa.13768.3905.648582.244_0_0. Do you see WU 15au03aa.6585.31554.261062.30_0 in BOINC's "Work" tab? Is BOINC currently crunching that WU?

Did you merge computers or detach and re-attach to SETI?

Try a re-boot if you haven't already. Shut everything down, including the modem.

Did you had a previous version of BOINC installed and running 8 months ago before you went back to classic? Did you un-install your previous BOINC version before you installed BOINC 4.45? Could WU 30ja04aa.13768.3905.648582.244_0_0 be left over from 8 months ago? If it is a left-over WU from 8 months ago you may just have to abort it.

---

Help and BOINC documentation is available here.

I'm confused because the web site says you have WU 15au03aa.6585.31554.261062.30_0 and only that WU, but the messages you post show WU 30ja04aa.13768.3905.648582.244_0_0. Do you see WU 15au03aa.6585.31554.261062.30_0 in BOINC's "Work" tab? Is BOINC currently crunching that WU?

Did you merge computers or detach and re-attach to SETI?

Try a re-boot if you haven't already. Shut everything down, including the modem.

Did you had a previous version of BOINC installed and running 8 months ago before you went back to classic? Did you un-install your previous BOINC version before you installed BOINC 4.45? Could WU 30ja04aa.13768.3905.648582.244_0_0 be left over from 8 months ago? If it is a left-over WU from 8 months ago you may just have to abort it.

***I was one of the first users of classic seti to switch over to Boinc when it started up. The 30ja04aa.13768.3905.648582.244_0_0 was from that orginal Boinc version. It recently disappeared. I don't know if this means it aborted or whether or not it was successful at uploading to the server?? I couldn't get any more work from seti at home so I signed up to climatepredictor to get some work in the meanwhile. This baffles me as well- it download 53MB of work from their server but only 1 11MB work unit is showing under the work tab?? I think I'll reinstall seti classic till they can fix these bugs in Boinc and stay with seti classic till the classic project finally ends.****

---

I couldn't get any more work from seti at home so I signed up to climatepredictor to get some work in the meanwhile. This baffles me as well- it download 53MB of work from their server but only 1 11MB work unit is showing under the work tab?? I think I'll reinstall seti classic till they can fix these bugs in Boinc and stay with seti classic till the classic project finally ends.****

The size of the executable and associated files from CPDN have absolutely nothing to do with BOINC! If you have a problem with CPDN, how about posting it over on their forum. That way you have a much better chance of someone who can actually do anything about it seeing your message.