I have BOINC set-up to work on 3 different projects:

SETI
LHC
ROSETTA

On two different computers. None of the installations work anymore, i.e. they do not send or fetch new work. I have tried to look and change the connection parameters, but to no avail.

I keep getting the same kind of messages as below:

02/01/2006 08:23:13||Starting BOINC client version 5.2.13 for windows_intelx86
02/01/2006 08:23:13||libcurl/7.14.0 OpenSSL/0.9.8 zlib/1.2.3
02/01/2006 08:23:13||Data directory: C:\\Program Files\\BOINC
02/01/2006 08:23:13||Processor: 1 GenuineIntel Intel(R) Pentium(R) M processor 1400MHz
02/01/2006 08:23:13||Memory: 511.36 MB physical, 1.22 GB virtual
02/01/2006 08:23:13||Disk: 20.01 GB total, 13.62 GB free
02/01/2006 08:23:13|rosetta@home|Computer ID: 89336; location: home; project prefs: default
02/01/2006 08:23:13|LHC@home|Computer ID: 78092; location: ; project prefs: default
02/01/2006 08:23:13|SETI@home|Computer ID: 1815320; location: home; project prefs: default
02/01/2006 08:23:13||General prefs: from SETI@home (last modified 2005-11-28 22:14:32)
02/01/2006 08:23:13||General prefs: no separate prefs for home; using your defaults
02/01/2006 08:23:14||Remote control not allowed; using loopback address
02/01/2006 08:23:17||Running CPU benchmarks
02/01/2006 08:24:16||Benchmark results:
02/01/2006 08:24:16|| Number of CPUs: 1
02/01/2006 08:24:16|| 1110 double precision MIPS (Whetstone) per CPU
02/01/2006 08:24:16|| 2321 integer MIPS (Dhrystone) per CPU
02/01/2006 08:24:16||Finished CPU benchmarks
02/01/2006 08:24:17||Resuming computation and network activity
02/01/2006 08:24:17||request_reschedule_cpus: Resuming activities
02/01/2006 08:24:17|LHC@home|Fetching master file
02/01/2006 08:24:22|LHC@home|Master file parse failed
02/01/2006 08:24:22|LHC@home|Too many backoffs - fetching master file
02/01/2006 08:24:27|SETI@home|Fetching master file
02/01/2006 08:24:33|SETI@home|Master file parse failed
02/01/2006 08:24:33|SETI@home|Too many backoffs - fetching master file
02/01/2006 09:42:29||request_reschedule_cpus: project op
02/01/2006 09:42:32|SETI@home|Fetching master file
02/01/2006 09:42:38|SETI@home|Master file parse failed
02/01/2006 09:42:38|SETI@home|Too many backoffs - fetching master file
02/01/2006 09:42:47||request_reschedule_cpus: project op
02/01/2006 09:42:48|LHC@home|Fetching master file
02/01/2006 09:42:53|LHC@home|Master file parse failed
02/01/2006 09:42:53|LHC@home|Too many backoffs - fetching master file
02/01/2006 09:47:06||Fetching config info from http://einstein.phys.uwm.edu/get_project_config.php
02/01/2006 09:48:43||request_reschedule_cpus: project op
02/01/2006 09:48:45|LHC@home|Fetching master file
02/01/2006 09:48:51|LHC@home|Master file parse failed
02/01/2006 09:48:51|LHC@home|Too many backoffs - fetching master file
02/01/2006 09:49:04||request_reschedule_cpus: project op
02/01/2006 09:49:06|SETI@home|Fetching master file
02/01/2006 09:49:11|SETI@home|Master file parse failed
02/01/2006 09:49:11|SETI@home|Too many backoffs - fetching master file
02/01/2006 09:49:33||Fetching config info from http://einstein.phys.uwm.edu/get_project_config.php
02/01/2006 09:49:54||Fetching config info from http://einstein.phys.uwm.edu/get_project_config.php
02/01/2006 09:52:43||request_reschedule_cpus: project op
02/01/2006 09:52:46|rosetta@home|Fetching master file
02/01/2006 09:52:51|rosetta@home|Master file fetch failed
02/01/2006 09:52:51|rosetta@home|Too many backoffs - fetching master file
02/01/2006 09:55:28|SETI@home|Resetting project
02/01/2006 09:55:28||request_reschedule_cpus: exit_tasks
02/01/2006 09:55:28||request_reschedule_cpus: project op
02/01/2006 10:05:10||request_reschedule_cpus: project op
02/01/2006 10:05:10|rosetta@home|Fetching master file
02/01/2006 10:05:12||Couldn't connect to hostname [boinc.bakerlab.org]
02/01/2006 10:05:15|rosetta@home|Master file fetch failed
02/01/2006 10:05:15|rosetta@home|Too many backoffs - fetching master file
02/01/2006 10:05:29||request_reschedule_cpus: project op
02/01/2006 10:05:30|rosetta@home|Fetching master file
02/01/2006 10:05:35|rosetta@home|Master file fetch failed
02/01/2006 10:05:35|rosetta@home|Too many backoffs - fetching master file
02/01/2006 12:07:58||request_reschedule_cpus: project op
02/01/2006 12:07:59|rosetta@home|Fetching master file
02/01/2006 12:08:04|rosetta@home|Master file fetch failed
02/01/2006 12:08:04|rosetta@home|Too many backoffs - fetching master file
02/01/2006 17:10:25||request_reschedule_cpus: project op
02/01/2006 17:10:26|rosetta@home|Fetching master file
02/01/2006 17:10:27||request_reschedule_cpus: project op
02/01/2006 17:10:28||request_reschedule_cpus: project op
02/01/2006 17:10:31|rosetta@home|Master file fetch failed
02/01/2006 17:10:31|rosetta@home|Too many backoffs - fetching master file
02/01/2006 17:10:36|LHC@home|Fetching master file
02/01/2006 17:10:41|LHC@home|Master file parse failed
02/01/2006 17:10:41|LHC@home|Too many backoffs - fetching master file
02/01/2006 17:10:46|SETI@home|Fetching master file
02/01/2006 17:10:51|SETI@home|Master file parse failed
02/01/2006 17:10:51|SETI@home|Too many backoffs - fetching master file

primarily in red, i.e. not a good sign. What do I do wrong?

Thanks for your replies

Frank

---

Until someone with more knowledge co=mes along I will say this, It is probably because the servers are down or the project has no WUs or they are being hammered and are busy; Seti is down and LHC has no WUs.

From the WIKI

The most common causes of this error is when your Internet connection has failed or the Project's Web Server is off-line.

Another cause is when the site is under heavy load (I just experienced this one with LHC@Home = {050223} when they restarted the Project).

---

BOINC Wiki

As you're seeing the failure (total failure to connect) on three separate projects, the error pretty well has to be on your end, in the network connection. Extremely likely that a firewall has been turned on that is blocking BOINC from having access. It needs ports 80 and 443 for "external", and 1043 and 31416 for "internal" connections.

---

As you're seeing the failure (total failure to connect) on three separate projects, the error pretty well has to be on your end, in the network connection. Extremely likely that a firewall has been turned on that is blocking BOINC from having access. It needs ports 80 and 443 for "external", and 1043 and 31416 for "internal" connections.

Bill you sure about that 443????

Rom walton says Boinc needs the following:
BOINC Manager needs to be able to open outbound connections to either 1043 or 31416.
BOINC Screensaver needs to be able to open outbound connections to either 1043 or 31416.
BOINC needs to open an inbound connection to either 1043 or 31416, and an outbound connection to port 80 for downloads and uploads of workunits, results, and science packages.

---

BOINC Wiki

Port 443 isn't in use yet. If it's going to be used, it'll be for secure attaching to only, as far as I know.

---

Port 443 isn't in use yet. If it's going to be used, it'll be for secure attaching to only, as far as I know.

I haven't looked at the code, but are you sure? My understanding was that it was already in there for the "account manager" stuff, would send all passwords via HTTPS. I don't know if that means "only" to AMS, or if it means to "attach project" for V5 servers as well.

---

The code to use port 443 was adding with any of the 5.x.x versions. I do not believe any project is currently using it though. I advise allowing access to that port just in case.

---

BOINC WIKI

BOINCing since 2002/12/8

TY, good to this stuff.....

---

BOINC Wiki