Just had Minirosetta_2.14_windows_intel386.exe try to phone home: 207.46.209.243 What is that IP address? Moreover, why is an app trying to phone anywhere?

The only thing that has ever phone'd home is BOINC.exe and that to very specific and identifiable IP's relevant, pertainant and germane to either BOINC, or the project itself. The default destination IPs for BOINC.exe is defined by the project host names as seen in the message log when BOINC starts. The projects that require additional IP addresses for results are specifically SETI, Einstein, Lattice & Rosetta. The Rosetta specific IP's that have been resolved are: 140.142.20.107/140.142.20.125

The only exception to this is when BOINC.exe attempts to ascertain internet connection by attempting to contact IP's in the 1e100 domain. However, never have I seen projects attempt connection to any IP whatsoever.

Furthermore, in this particular instance - never having occured before - no results are being transmitted as the IP connection attempt occurs shortly after Rosetta launches and begins processing WU.

---

You are correct that a BOINC application such as rosettamini should not generally use the internet. The internet access occurs via the boinc.exe. The exception to this is as transient described when an exception is raised, things clearly are not going well and successfully interacting back to BOINC to report details of the problem will not necessarily be possible. So the debug portion takes over and references Microsoft with the symbol tables. If this should fail, usually due to a firewall, which is probably how you noticed it in the first place... it just means less detail about the problem is captured and returned. But there shouldn't be any need to do anything on your end to recover. And once the opportunity to report the information is gone, you can't get it back. No big deal, if there is a persistent problem, others will get the details reported.

---

Rosetta Moderator: Mod.Sense

Interesting. Yes, I noticed that that IP address is in my MSECN.net port 80 zone. That's one of the things I wondered about: why is Rosetta hitting MS' edge caching net?

Both times Rosetta phoned home it coughed up a bit-ball:

9/10/2010 5:41:02 PM rosetta@home Restarting task lr5_jorj_combined_torsion_it05_run01_A_rlbd_1t2i_SAVE_ALL_OUT_IGNORE_THE_REST_DECOY_21164_1655_0 using minirosetta version 214
9/10/2010 5:46:36 PM rosetta@home Computation for task lr5_jorj_combined_torsion_it05_run01_A_rlbd_1t2i_SAVE_ALL_OUT_IGNORE_THE_REST_DECOY_21164_1655_0 finished
9/10/2010 5:46:36 PM rosetta@home Output file lr5_jorj_combined_torsion_it05_run01_A_rlbd_1t2i_SAVE_ALL_OUT_IGNORE_THE_REST_DECOY_21164_1655_0_0 for task lr5_jorj_combined_torsion_it05_run01_A_rlbd_1t2i_SAVE_ALL_OUT_IGNORE_THE_REST_DECOY_21164_1655_0 absent

Rosetta phoned home at 5:46:13 PM After the final death throe tremor, he began downloading 'nother WU. It too horked a bit-ball:

9/10/2010 6:02:53 PM rosetta@home Starting Dengue9Sept2010_3c5x_1gis_ProteinInterfaceDesign_9Sep2010_21855_28_0
9/10/2010 6:02:54 PM rosetta@home Starting task Dengue9Sept2010_3c5x_1gis_ProteinInterfaceDesign_9Sep2010_21855_28_0 using minirosetta version 214
9/10/2010 6:12:05 PM rosetta@home Computation for task Dengue9Sept2010_3c5x_1gis_ProteinInterfaceDesign_9Sep2010_21855_28_0 finished
9/10/2010 6:12:05 PM rosetta@home Output file Dengue9Sept2010_3c5x_1gis_ProteinInterfaceDesign_9Sep2010_21855_28_0_0 for task Dengue9Sept2010_3c5x_1gis_ProteinInterfaceDesign_9Sep2010_21855_28_0 absent

Rosetta phoned home at 6:09:25 PM and then went belly up. The WU immediately downloaded thereafter - gunn_fragments_SAVE_ALL_bla_bla_bla - hasn't started yet. If this is a 'computer security policy' permission issue, I haven't a clue; BOINC apps are co-equal master's of their own domain and god's of their little individual fiefdoms in accordance to 'computer security permissions' established for the 'BOINC_Projects file group. The 'BOINC_Projects' file group is defined as:

%BOINC_data_HD%BOINC_Dataprojects*
%BOINC_data_HD%BOINC_Dataslots*

That file group has 'installer or updater' computer security policy permissions; they're essentially masters of their domain (kings of their castle), etc and can trash or obliterate each other's projects / slots to their hearts content. Moreover, %BOINC_Prog_HD%BOINC.exe has access rights to run as executable ANYTHING in the 'BOINC_Projects' file-group; long time ago I threw in the towel trying to define what's runnable in there.

Furthermore, %BOINC_Prog_HD%BOINCmgr.exe has access rights to run as executable:

%BOINC_Prog_HD%BOINC.exe
%PROGRAMFILES%Internet Exploreriexplore.exe
%BOINC_data_HD%projects*
%SystemRoot%boinc.scr
%BOINC_Prog_HD%boincscr.exe

Why can't Rosetta use %BOINC_Data_HD%symbols? If Rosetta can't use that for what putatively is posited as being the cause to phone home, what the F do I need to waste 10% of a bloody GB?

---

Succinctly put:

What permissions should I establish for BOINC 'projects' as a global rule to phone home in event of tiny nuclear accident where a little bit radiation was let out? I need to know PRECISELY who should be notified by whom?

This circumstance is bizarro world. I've NEVER seen this since Apr 2010 (and my machine is a BOINC goose for WU's). I aint givin' no BOINC project carte blanche inter-web access. Aint happeninin'. Aint NO way.

---

Succinctly put:

What permissions should I establish for BOINC 'projects' as a global rule to phone home in event of tiny nuclear accident where a little bit radiation was let out? I need to know PRECISELY who should be notified by whom?

This circumstance is bizarro world. I've NEVER seen this since Apr 2010 (and my machine is a BOINC goose for WU's). I aint givin' no BOINC project carte blanche inter-web access. Aint happeninin'. Aint NO way.

Roger that. RESTRICTION
!

---

Succinctly put:

What permissions should I establish for BOINC 'projects' as a global rule to phone home in event of tiny nuclear accident where a little bit radiation was let out? I need to know PRECISELY who should be notified by whom?

This circumstance is bizarro world. I've NEVER seen this since Apr 2010 (and my machine is a BOINC goose for WU's). I aint givin' no BOINC project carte blanche inter-web access. Aint happeninin'. Aint NO way.

Roger that. RESTRICTION! NO new tasks

Talk to me, we'll discuss unrestricting the project.

---

In fact I've detached from the project.

---

I had exactly the same problem once and only once during my whole time crunching Rosetta. I have made no changes to my firewall as I don't like the idea of Rosetta firing information off at random, so only the normal BOINC communication channels are open.

Other than that one work unit in 4 years I have never seen this error again and everything else is working fine.

If I do get a repeat of the same problem the error message will be blocked and everything will then go back to normal.

Detaching from the project to prevent Rosetta sending messages that you can get your firewall to block anyway seems a little drastic, but it is your choice.

---

Why can't Rosetta use %BOINC_Data_HD%symbols?

What are you seeing that would indicate there was any problem using the symbols? Were you running BOINC as a Windows service?

As I said, you don't need to give any "carte". BOINC will report the task back to the project as normal. The only hic-cup I can think of is the darn pop-up indicating the failed internet connection, but that may not occur if you run as a service.

In general, you just signon to Windows as the restricted user you wish it to run under and install BOINC while signed on as that user and everything it needs access to it will have access to. No tinkering required.

If your patience threshold is all of 3.5 minutes, I would suggest you might better enjoy other pursuits. There's no online chat with a dedicated customer service rep here. But then there's no 50% markup on merchandise either.

---

Rosetta Moderator: Mod.Sense