Sometimes when I leave rosetta unattended for a long time my client just disconnects from localhost... and it's usually a few hours before I'm back to restart the client to start work again. Any idea why it disconnects from the very computer it's running on or what can be done?
For this reason I cannot leave rosetta overnight or when I'm not home coz it's just pointless to leave it if it's not processing WUs.
I don't know about other projects coz I'm running only rosetta.
Also, the message list get cleared so I cannot even see what went wrong. All I (sometimes) get is "Boinc cannot connect to localhost" or sth like that (can't remember exactly).

I have the same problem and started a forum item to discuss it here.

I can only explain that this is BOINC problem (or perhaps Windows), not Rosetta. And suggest that from my experience with the problem, it always seems to occur during internet communications. So, if you can minimize the number of internet connections made, that will bring you less frequent disconnected state. In fact, if you downloaded several days of work, and then suspend the network activity, I'm sure you could crunch without incident for those days. You suspend network activity from the Activity pulldown menu in BOINC Manager.

You can get several days of work either by changing your general preference for "connect to network about every .... days", or you can suspend WUs and update to the project (wait until the delay time shown in the projects tab passes, usually about 3 min., in between updates).

---

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/