Are you using a BOINC account manager?

---

What's listed on the Projects and Tasks tabs of the Boinc manager screens under Status?

---

Well, I repaired it...I think. I decided to "detach," which I did not want to do in case I would lose data. However, once I detached and then re-attached (or whatever it's called), everything went back to normal...for now. I think that I am attached to my old account, but the stats look bad in my graph. I'll wait to see if everything evens out.

Thanks for the prompt help attempts. I will definitely return if something else goes wrong.

John

---

My question is similar to one below.

Sometimes my laptop tries to communicate with R@H and if I am not connected to the net, it keeps trying until it fails four times. Then comes the kicker: it ceases communications for an entire week!! I lost 12+ hours of crunching yesterday when it decided not to communicate, even after finishing all of the current tasks. What do I do to get BOINC to keep trying for a day or so until I get back online to update the tasks? A couple of times when this happened I was only offline for a couple of crunching hours. I do have BAM! for my manager.

---

(Click for detailed stats)

My question is similar to one below.

Sometimes my laptop tries to communicate with R@H and if I am not connected to the net, it keeps trying until it fails four times. Then comes the kicker: it ceases communications for an entire week!! I lost 12+ hours of crunching yesterday when it decided not to communicate, even after finishing all of the current tasks. What do I do to get BOINC to keep trying for a day or so until I get back online to update the tasks? A couple of times when this happened I was only offline for a couple of crunching hours. I do have BAM! for my manager.

It shouldn't back off that much.. :eek:

But you can use the 'Advanced -> Retry communications' will kick communication into action again.

---

Team mauisun.org

It shouldn't back off that much.. :eek:

But you can use the 'Advanced -> Retry communications' will kick communication into action again.

I was just thinking that perhaps there is a setting that is different from the norm that might be the cause. I looked, and reset the activity tab to => Run based on preferences, rather than => Run always. Don't know if that will help, but that's the only thing I can see that is different that I've changed for that computer.

---

(Click for detailed stats)

It shouldn't back off that much.. :eek:

But you can use the 'Advanced -> Retry communications' will kick communication into action again.

I was just thinking that perhaps there is a setting that is different from the norm that might be the cause. I looked, and reset the activity tab to => Run based on preferences, rather than => Run always. Don't know if that will help, but that's the only thing I can see that is different that I've changed for that computer.

The run always just makes the computer ignore specified timings to run and the only run when not in use.

The network one may make a difference, not sure if it really does though (again I think that just makes it ignore the netwrok restrictions)

Though this should really be in a new thread by itself ;)

---

Team mauisun.org