Every once in a while when it\'s time for my boinc cpdn work unit to trickle up a result, I get a connection refused, try again type of message above my system tray (XP Pro).

I don\'t have a problem with cpdn not being reachable, but I do find it irrating that boinc drops all of the various project workunits. After I restart the boinc manager, the workunits are processed as they should be. After a little bit (< 15 minutes), boinc is trying to trickle up again and gives me the same kind of networking error and temporarily loses all project work units until I restart the boinc manager.

My question is, is there a setting somewhere that I can set that states \"networking issue..., ignore the current project and process a different work unit\" instead of just dropping the workunits and seating idle?

The 2 sulpher units I have successfully trickled up 88 and 25 times.



TIA,
William

---

Every once in a while when it\'s time for my boinc cpdn work unit to trickle up a result, I get a connection refused, try again type of message above my system tray (XP Pro).

I don\'t have a problem with cpdn not being reachable, but I do find it irrating that boinc drops all of the various project workunits. After I restart the boinc manager, the workunits are processed as they should be. After a little bit - less than 15 minutes, boinc is trying to trickle up again and gives me the same kind of networking error and temporarily loses all project work units until I restart the boinc manager.

My question is, is there a setting somewhere that I can set that states \"networking issue..., ignore the current project and process a different work unit\" instead of just dropping the workunits and seating idle?

The 2 sulpher units I have successfully trickled up 88 and 25 times.



TIA,
William[/quote]

---

I\'m sorry but I am a little confused by what you mean by \"boinc drops all of the various project workunits\"

What should happen is the connection fails so the trickle is stored until the nect successful communication. During this period crunching should continue as normal.

You seem to be saying your computer sits idle. This shouldn\'t happen. Can you explain a little more about what makes you think the system is idle?

There may be solutions such as setting network activity disabled and just allowing communication every so often. However, I want to ensure I understand the problem before recommending anything like that.

---

Visit BOINC WIKI for help

And join BOINC Synergy for all the news in one place.

I\'m sorry but I am a little confused by what you mean by \"boinc drops all of the various project workunits\"

What should happen is the connection fails so the trickle is stored until the nect successful communication. During this period crunching should continue as normal.

You seem to be saying your computer sits idle. This shouldn\'t happen. Can you explain a little more about what makes you think the system is idle?

There may be solutions such as setting network activity disabled and just allowing communication every so often. However, I want to ensure I understand the problem before recommending anything like that.

---

That\'s correct. I\'ve seen some messages in the past where it couldn\'t trickle up and it kept processing.

After I see the message, I check out task manager and I see \"System Idle Process\" at 99%.

I have 3 other projects running on that machine - P4 w HT so disabling or throttle the communications isn\'t an option.

Since I lost about 60 true hours, I went and suspended the 2 cpdn work units.

I\'ll restart it when I get to work and if it happens, I\'ll get the exact text of the error message.



Thanks,
William

---

Once I got to work and resumed it, it was able to trickle up. When it happens again, I\'ll post to this message.



Thanks,
William

---