Every so often I reboot my system and have several programs set to start such as BOINC, Anti Virus, Spybot, etc..
I have a Cable connection and am always online, but when BOINC starts it always gives me an: unable to connect to localhost, message in the bottom corner. So I have to close BOINC and restart it. Then I often have to go to Projects or Transfers and have it Update or Retry.

I assume its just attempting to connect before my computer is finished doing whatever it does before connecting.

So is there anyway to slow down BOINCS connection?

Every so often I reboot my system and have several programs set to start such as BOINC, Anti Virus, Spybot, etc..
I have a Cable connection and am always online, but when BOINC starts it always gives me an: unable to connect to localhost, message in the bottom corner. So I have to close BOINC and restart it. Then I often have to go to Projects or Transfers and have it Update or Retry.

I assume its just attempting to connect before my computer is finished doing whatever it does before connecting.

So is there anyway to slow down BOINCS connection?

localhost is THAT machine. By the time applications (BOINC) starts networking is already available. This has nothing to do with cable.
It's possible that other startup programs are using so much cpu that BOINC is timeing out with itself.
Are you running with 5.10.x? Are you running as a service or on login?

localhost is THAT machine. By the time applications (BOINC) starts networking is already available. This has nothing to do with cable.
It's possible that other startup programs are using so much cpu that BOINC is timeing out with itself.
Are you running with 5.10.x? Are you running as a service or on login?

Running BOINC Manager version 5.2.8, just running a service, SETI to be exact.

Heres the message log from this morning.

9/2/2007 10:55:56 AM||Memory: 511.48 MB physical, 1.97 GB virtual
9/2/2007 10:55:56 AM||Disk: 24.40 GB total, 5.77 GB free
9/2/2007 10:55:56 AM|SETI@home|Computer ID: XXXXXXX; location: home; project prefs: default
9/2/2007 10:55:56 AM||General prefs: from SETI@home (last modified 2007-08-17 23:04:49)
9/2/2007 10:55:56 AM||General prefs: no separate prefs for home; using your defaults
9/2/2007 10:55:56 AM||Remote control not allowed; using loopback address
9/2/2007 10:59:22 AM|SETI@home|Started download of 11mr07ae.20964.184988.6.5.33
9/2/2007 10:59:44 AM||Couldn't connect to hostname [boinc2.ssl.berkeley.edu]
9/2/2007 10:59:44 AM|SETI@home|Temporarily failed download of 11mr07ae.20964.184988.6.5.33: system I/O
9/2/2007 10:59:44 AM|SETI@home|Backing off 2 hours, 59 minutes, and 16 seconds on download of file 11mr07ae.20964.184988.6.5.33


Maybe this a seperate thing, and I was just assuming theey were related to the : unable to connect to localhost, on the lower right corner of my BOINC manager.

Basically Im wondering if there is a way to have either BOINC start a few minutes or so after everything else boots so they arent competing for resources, or have it wait a few minutes before attempting to connect to boinc2 or seti, or just not 'Backing off 2 hours, 59 minutes, and 16 seconds'?

Thanks

Mike

I also had one host that was starting the boinc service too fast and did the following to slow it down.

If you don't mind editing the registry, you can try this:

under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BOINC find DependOnService in the right pane. Right click and choose Modify. Leave the RpcSs entry on the first line, and add Netman on the second line and click OK.

Netman starts later among the services and making boinc depend on it will start the boinc service later than it was before.

[Running BOINC Manager version 5.2.8, just running a service, SETI to be exact.

BOINC 5.2 still uses TCP port 1043 for its connection between the daemon (BOINC client) and the GUI (BOINC Manager). Other programs in Windows use this same port. To mind comes the email program delivered with Windows, Outlook Express. If that starts up first, the daemon won't be able to connect to the GUI (and v.v.) when you start BOINC Manager.

That is when you get the message that BOINC Manager cannot connect to localhost. Localhost lives on IP address 127.0.0.1, which is YOUR computer. The message has nothing to do with whether or not BOINC can connect to the internet.

Now, please upgrade to BOINC 5.10.13, which uses TCP port 31416 for its internal communications. That way you can get rid of the localhost not connecting error that is plaguing you.

The other message you see in your Messages log:

9/2/2007 10:59:44 AM|SETI@home|Temporarily failed download of 11mr07ae.20964.184988.6.5.33: system I/O
9/2/2007 10:59:44 AM|SETI@home|Backing off 2 hours, 59 minutes, and 16 seconds on download of file 11mr07ae.20964.184988.6.5.33

This means that BOINC can't connect to Seti, most probably because Seti is down or has other problems. Best check that on the Seti forums. http://setiathome.berkeley.edu will get you there. Read the news, read the forums.

BOINC as a service starts at the same time as all the other services, before Windows login.

---