what exactly means the tittle?
if appears in my proyect menu page communication deferred, and stay there for the last 2 days.
what suppose i must to do?

looking forward to yours answers.
regards
glormoon

---

Basically, it means BOINC is going to wait for a period of time (the remaining time is shown after the word deferred) before trying to contact the project again. I assume you are now without any tasks to crunch. To understand why, look at the messages shown in the messages tab. If you are unclear what they mean, please report them here (and, if needed, your best translation of the messages to English would be very helpful).

Are you running multiple BOINC projects?
Have you recently changed your resource shares between projectS? Or added additional projects?

I am guessing that your messages will confirm when you contact Rosetta that you are not requesting new work. This occurs when BOINC allocates time to work on your other projects. It is normal and will probably request more Rosetta work within another day or two.

---

Add this signature to your EMail:
Running Microsoft's "System Idle Process" will never help cure cancer, AIDS nor Alzheimer's. But running Rosetta@home just might!
https://boinc.bakerlab.org/rosetta/

I actually have the same problem, every time it connects, the connection is defered for 3 minutes, but sometimes 1 hour and 50 minutes, so i have no idea what's wrong, there is nothing in the message that will explain the cause.

---

Yin, looking at your RAC, I can pretty well guess that you are running several other projects on your computer. It is normal for there to be periods of time with no work from any given project, while your machine crunches for the others. BOINC will manage the work. The messages will tell you if it is actually requesting work from Rosetta and not getting it, or if it is just reporting in to the project periodically.

The deferred communication times is also normal. BOINC randomizes the amount of time that you wait before you contact the project again. And after failed contacts, it makes you wait a bit longer each time. This helps the project servers avoid situations where ALL of the clients are hitting them at the same time. Especially after a project server outage of some kind. As you probably know, everyone hitting the server at the same time will bog everything down and it's harder to get work done.

---

Add this signature to your EMail:
Running Microsoft's "System Idle Process" will never help cure cancer, AIDS nor Alzheimer's. But running Rosetta@home just might!
https://boinc.bakerlab.org/rosetta/

Yin, looking at your RAC, I can pretty well guess that you are running several other projects on your computer. It is normal for there to be periods of time with no work from any given project, while your machine crunches for the others. BOINC will manage the work. The messages will tell you if it is actually requesting work from Rosetta and not getting it, or if it is just reporting in to the project periodically.

The deferred communication times is also normal. BOINC randomizes the amount of time that you wait before you contact the project again. And after failed contacts, it makes you wait a bit longer each time. This helps the project servers avoid situations where ALL of the clients are hitting them at the same time. Especially after a project server outage of some kind. As you probably know, everyone hitting the server at the same time will bog everything down and it's harder to get work done.

Thanks, but it doesn't seem to do that anymore, actually, i only run rosetta, at the time of the writing, i was only on the first couple of days, so my rac had rise slowly, since i didn't run boinc for months.

---

If the time frame is ridiculously long go to the projects tab and highlight the waiting project, then click "Update Now". That should initiate a connection and reset the timer. Sometimes, if the project is down a while, BOINC can up the communication delay to a ridiculous value, like a week or more. It's actually a bug that should be fixed in an upcoming version.

---

If the time frame is ridiculously long go to the projects tab and highlight the waiting project, then click "Update Now". That should initiate a connection and reset the timer. Sometimes, if the project is down a while, BOINC can up the communication delay to a ridiculous value, like a week or more. It's actually a bug that should be fixed in an upcoming version.

It is fixed in latest alpha version. We're testing the crap out of it right now trying to get it ready for release.