Hello!

I\'m new to the project (running Boinc 5.8.11 on Win XP Prof) and unfortunately I\'ve now tried for 3 days to download simulation data, but the download fails with error messages saying there are checksum mismatches. This is not to every file, but to about 70-80% of the downloaded files.

Does anyone know what could be the reason for this and how I could fix it?

Thanks a lot in advance!

Here is some of the log:

19.03.2007 21:00:18||Starting BOINC client version 5.8.11 for windows_intelx86
19.03.2007 21:00:18||log flags: task, file_xfer, sched_ops
19.03.2007 21:00:18||Libraries: libcurl/7.16.0 OpenSSL/0.9.8a zlib/1.2.3
19.03.2007 21:00:18||Data directory: C:\\Programme\\BOINC
19.03.2007 21:00:19||Processor: 1 GenuineIntel Intel(R) Pentium(R) M processor 1500MHz [x86 Family 6 Model 9 Stepping 5] [fpu tsc sse sse2 mmx]
19.03.2007 21:00:19||Memory: 1.25 GB physical, 2.98 GB virtual
19.03.2007 21:00:19||Disk: 23.61 GB total, 10.56 GB free
19.03.2007 21:00:20|climateprediction.net|URL: http://climateprediction.net/; Computer ID: *CENSORED*; location: (none); project prefs: default
19.03.2007 21:00:20||No general preferences found - using BOINC defaults
19.03.2007 21:00:20||Reading preferences override file
19.03.2007 21:00:21|climateprediction.net|Sending scheduler request: To fetch work
19.03.2007 21:00:21|climateprediction.net|Requesting 8640 seconds of new work
19.03.2007 21:00:38||Project communication failed: attempting access to reference site
19.03.2007 21:00:38|climateprediction.net|Scheduler request failed: couldn\'t resolve host name
19.03.2007 21:00:38|climateprediction.net|Deferring communication for 2 min 12 sec
19.03.2007 21:00:38|climateprediction.net|Reason: scheduler request failed
19.03.2007 21:00:56||Access to reference site failed - check network connection or proxy configuration.
19.03.2007 21:02:51|climateprediction.net|Sending scheduler request: To fetch work
19.03.2007 21:02:51|climateprediction.net|Requesting 8640 seconds of new work
19.03.2007 21:02:56|climateprediction.net|Scheduler RPC succeeded [server version 509]
19.03.2007 21:02:58|climateprediction.net|[file_xfer] Started download of file hadcm3ohe_1jn7_05720453.zip
19.03.2007 21:02:58|climateprediction.net|[file_xfer] Started download of file SULPC_OXIDANTS_19_A2_1990.mod.gz
19.03.2007 21:03:01|climateprediction.net|[file_xfer] Finished download of file hadcm3ohe_1jn7_05720453.zip
19.03.2007 21:03:01|climateprediction.net|[file_xfer] Throughput 19525 bytes/sec
19.03.2007 21:03:01|climateprediction.net|[file_xfer] Started download of file DMSNH3SO2A1B_19182082N.mod.gz
19.03.2007 21:03:08|climateprediction.net|[file_xfer] Finished download of file SULPC_OXIDANTS_19_A2_1990.mod.gz
19.03.2007 21:03:08|climateprediction.net|[file_xfer] Throughput 135286 bytes/sec
19.03.2007 21:03:08|climateprediction.net|[file_xfer] Finished download of file DMSNH3SO2A1B_19182082N.mod.gz
19.03.2007 21:03:08|climateprediction.net|[file_xfer] Throughput 55921 bytes/sec
19.03.2007 21:03:08|climateprediction.net|[file_xfer] Started download of file spec3a_lw_3_asol2c_hadcm3.gz
19.03.2007 21:03:08|climateprediction.net|[file_xfer] Started download of file spec3a_sw_3_asol2b_hadcm3.gz
19.03.2007 21:03:08|climateprediction.net|[error] MD5 check failed for SULPC_OXIDANTS_19_A2_1990.mod.gz
19.03.2007 21:03:08|climateprediction.net|[error] expected af32b3d36a4db4ca08c899c355fcb857, got 6915bc21bc3008ed3bf4ee520e6f5464
19.03.2007 21:03:08|climateprediction.net|[error] Checksum or signature error for SULPC_OXIDANTS_19_A2_1990.mod.gz
19.03.2007 21:03:08|climateprediction.net|[error] MD5 check failed for DMSNH3SO2A1B_19182082N.mod.gz
19.03.2007 21:03:08|climateprediction.net|[error] expected c3aa86f35348736c2630dafce6294a33, got a69d0cff98edf453daa95f6d1e9f915a
19.03.2007 21:03:08|climateprediction.net|[error] Checksum or signature error for DMSNH3SO2A1B_19182082N.mod.gz

[snip]
[a lot more errors like the above]
[snip}

19.03.2007 21:04:11|climateprediction.net|Sending scheduler request: To fetch work
19.03.2007 21:04:11|climateprediction.net|Requesting 8640 seconds of new work, and reporting 1 completed tasks
19.03.2007 21:04:16|climateprediction.net|Scheduler RPC succeeded [server version 509]
19.03.2007 21:04:16|climateprediction.net|Message from server: No work sent
19.03.2007 21:04:16|climateprediction.net|Message from server: (reached daily quota of 1 results)
19.03.2007 21:04:16|climateprediction.net|Deferring communication for 4 hr 39 min 36 sec
19.03.2007 21:04:16|climateprediction.net|Reason: requested by project
19.03.2007 21:34:54||No general preferences found - using BOINC defaults
19.03.2007 21:34:54||Reading preferences override file

---

First, there\'s no point in \"censoring\" your computer ID. This only applies to this project, and is need to provide help in some cases.

Second, the answer to part of your problem is in the messages:

Sending scheduler request: To fetch work
.....
Project communication failed: attempting access to reference site
Scheduler request failed: couldn\'t resolve host name
......
Access to reference site failed - check network connection or proxy configuration.

When BOINC can\'t contact the project\'s servers, it attempts to \'ping\' a reference site that is known to be available most of the time; this site is Google.

If the reference site is contactable, then the project is most likely \'down\'.
When it can\'t be, then it\'s most likely that the computer can\'t contact the outside world on one of the several ports used by BOINC.
One is port 80, but you\'re already using this to post here.
Another is 31416.

And it\'s usually a firewall or proxy server problem.
Proxys are mostly used by business computers, so that leaves your firewall blocking a needed port as the most likely reason you\'re not getting anywhere.

*************

As for the checksum errors, it could be your ISP. AOL users are limited in the size of files that they are allowed to download, and some used here are bigger than this limit.

---

Backups: Here

Hello!

Thanks for the hints; I think the first unsuccessful connection attempt was due to the startup of my computer, which hadn\'t established a network connection at that point.

As for the checksum errors, it could be your ISP. AOL users are limited in the size of files that they are allowed to download, and some used here are bigger than this limit.

Today I tried it using another Internet connection, which worked.
So my ISP seems to be the problem.

However, now the simulation is running.

Thanks again,

Thorsten

---

When it can\'t be, then it\'s most likely that the computer can\'t contact the outside world on one of the several ports used by BOINC.
One is port 80, but you\'re already using this to post here.
Another is 31416.

Sorry Les, but only TCP ports 80 and 443 are used by BOINC to make contact with the outside world. Normally port 80. Port 443 is used by projects using HTTPS.

Port 31416 is only used by BOINC for communication between Boinc.exe, Boingmgr.exe and Boinc.scr, or the client, the graphical user interface and the screen saver. It isn\'t used for communications onto the internet.

---

Jord.

OK, thanks for that.