Hi
you may want to post this as a sticky. This works for the Boinc version of Seti@home and Einstein@home and I assume anything else running under Boinc.

One of the problems for the Linux version is difficulty in forcing upload or download of workunits if the computer is not constantly connected to the internet, as in a dial-up setting. The -update_prefs command has not worked for me.

I'll use Seti@home as an example

In order to force an upload and/or download, if you see in the terminal that unsuccessful attempts have been made, close your running Boinc terminal, open your client_state.xml file with a text editor such as gedit. This is divided into sections for each project, so scroll down to your desired project by finding

-project-
-project_name-Seti@home-/project_name-
then scroll down until you find an entry similar to
min_rpc_time-1109454153-/min_rpc_time
change the number 1109454153 to 0

then, if upload attempts have been made, continue to scroll down to the first section under the project until you find
file_info...
num_retries-8 (just an example number)-/num_retries
first_request_time-1109456868-/first_request_time
next_request_time-1109460454-/next_request_time

whatever the number is in next_request_time change it so that it is 1 greater than the number in first_request_time.

in other words, 1109460454 would become 1109456869

if multiple workunits have attempted, continue to scroll down to the next entry with the showing up and repeat this process.

now, save and close client_state.xml

connect to the internet first, then start Boinc and it will now upload/download the pending workunits. This process is needed each time an upload/download is missed, they are not permanent changes, but once you get used to doing it, it is quick and easy.

if you happen to get some occasional error messages such as "restarting result ..." with
"if this happens again you may need to restart.."
then exit Boinc, log out of your x-window or gnome, etc, log back in and restart Boinc. I'm not sure if that error is related to this process but this fixes it.

I hope this helps everyone.

Tom

---

Wow, it works for me.
I was glad that i'm not the only one with this problem.

Thanks !

---

Uh, but i got one Problem with this solution:
The Client uploaded the Result, but i got no Credits for it.
Here on the Page the WU is still not uploaded after one day.
Anybody any clue?

---

I'm not sure about the workunit credit issue, I haven't noticed that it has been a problem for me, as this method should not affect anything other than forcing the unit to be uploaded or downloaded.

The one thing you may observe, however, is that if you run more than one project, let's say Seti and Einstein, Boinc will sometime stall on just one project instead of switching every hour or whatever interval you have set up. I noticed it did this even without using the forced upload/download technique. You can solve this problem like this: anytime you upload or download units, forced or not, close boinc, log out of your gui, then log back in and restart Boinc. It seems to stop the stalling problem. Do this everytime you upload/download.

good luck to all.

Tom

---

I let my BOINC run for a while and during the Serverproblems in early March some WUs started to crowd my harddisk (well, there's enough space left). Then I had to re-install the whole system. I backup'd the complete /BOINC and after system installation I just wrote the complete directory back to the new system. I started boinc and it worked ok. It downloads WUs, it crunches the numbers and it uploads the finished WUs - but not the finished WUs which were finished before the system change.

They are still on my harddisk and they are listed as unfinished in my statistics.

I looked at client_state.xml and the units are all there but no sign of an error or a failed upload attempt. min_rpc_time is on '0'. There are all the units listed, some with 'status 1' and some with 'status 0'

I have a continuos uplink so there is always a connection to SETI/BOINC.

wobo

---

Hi Wobo
I don't have enough knowledge about boinc to figure this one out, but obviously it has to do with the re-install. If you haven't done so, try closing boinc, restart your computer, and examine the client_state.xml again and see if it is now configurable for those work units. If not, you may want to try to post that problem as a new message on the forum.

Tom


> I let my BOINC run for a while and during the Serverproblems in early March
> some WUs started to crowd my harddisk (well, there's enough space left). Then
> I had to re-install the whole system. I backup'd the complete /BOINC and after
> system installation I just wrote the complete directory back to the new
> system. I started boinc and it worked ok. It downloads WUs, it crunches the
> numbers and it uploads the finished WUs - but not the finished WUs which were
> finished before the system change.
>
> They are still on my harddisk and they are listed as unfinished in my
> statistics.
>
> I looked at client_state.xml and the units are all there but no sign of an
> error or a failed upload attempt. min_rpc_time is on '0'. There are all the
> units listed, some with 'status 1' and some with 'status 0'
>
> I have a continuos uplink so there is always a connection to SETI/BOINC.
>
> wobo
>

---