Hi Folks,

13/02/2015 03:56:04 | Asteroids@home | Scheduler request completed: got 1 new tasks
13/02/2015 03:56:06 | Asteroids@home | Started download of input_42867_17
13/02/2015 03:56:07 | Asteroids@home | Finished download of input_42867_17
13/02/2015 03:56:07 | Asteroids@home | [error] File input_42867_17 has wrong size: expected 39095, got 39096
13/02/2015 03:56:07 | Asteroids@home | [error] Checksum or signature error for input_42867_17

Haven't seen this error before, anyone got a cure?

I have the same problem . . .

Same Here

Hi Folks,
I've found a way to get some tasks, when a d/l fails I abort it, wait for the end of the project timeout and do a user update.

So far out of three attempts I've managed to get 2 more tasks, but it can take more than 1 attempt per file.

This isn't a 'fix' for the problem, just a temp work around. Its gonna need sorting out server side to get it fixed.

Cheers,
Cliff

A temporary solution is to modify your cc_config.xml file, which is located in the BOINC data directory. Look for this line of code:

<dont_check_file_sizes>0|1</dont_check_file_sizes>

Change the number to 1, and BOINC will ignore "wrong size" errors.

"Checksum or signature error," "MD5 check failed," and "permanent HTTP error" will have to be fixed on the server side.

---

I cannot find this config file on the version of boinc I am running.

I have 10's and 10's of download failures.

Lots of wasted processor time over the last few days, I am surprised this has not yet been addressed, across all users this project will have lost loads of work.

This is the 3rd project I have dedicated my computer time to. It always surprises me that these issues are allowed to carry on so long on these projects.

---

Hi Daz,

When you consider the limited funding that most DC projects get, lack of resources, including human ones is understandable.

Now given that A@H has had to move location, the project lead has a new job and has to cope with both, plus hardware problems. Then the delay is more understandable.

Simply abort the failed downloads, and update boinc. I manage to replace the failed files ok doing that.

Since my resources are also somewhat limited I only run during cheap rate for electricity, here that's from 00:30 hrs to 07:30 hrs so its nightowl stuff:-)

Regards,
Cliff

Hi,

The problem with that is that not everyone is using cc_config.xml or indeed a full cc_config.xml.

Mine just contains options to use all gpu's, I don't usually need all the flags stuff.

Also since the d/l failures are in the main either failed sig/checksum or permanent http errors, setting ignore file size in cc_config.xml wont deal with the failures.

Regards,
Cliff

Hi,
I've just PM'd the boss:-) I know he must be pretty busy what with a new job and house move etc, and might not have had time to scan this forum.

Regards,
Cliff

Lots of wasted processor time over the last few days.

Not necessarily. If you have a download error, BOINC doesn't run the task, meaning that you only process tasks that download correctly.

This is the 3rd project I have dedicated my computer time to.

Then why are download errors from this one so problematic for you? Unless you have limited bandwidth, it doesn't really matter. There are tons of BOINC projects out there, and each one has a good intent and needs computing power.

---

You are right, they are all worthy causes.

I have plenty of bandwidth (150 Mbps). The download errors end up putting my pc's out of action for hours or days.

Users like me cannot contribute any specialist knowledge or money to science as I simply do not have any. All I can contribute is processor time.

It appears a huge waste when processors are left unused for hours and hours.

You are right, they are all worthy causes.

I have plenty of bandwidth (150 Mbps). The download errors end up putting my pc's out of action for hours or days.

Users like me cannot contribute any specialist knowledge or money to science as I simply do not have any. All I can contribute is processor time.

It appears a huge waste when processors are left unused for hours and hours.

Try this, on the webpage go to Your Account, Computing Preferences and at the very bottom you should see this:

Skip image file verification?
Check this ONLY if your Internet provider modifies image files (UMTS does this, for example). Skipping verification reduces the security of BOINC.
no

As you can see mine is set to NO, change yours to YES, be sure to save the changes, and see if it makes any difference. If the file really is bad you will just end up getting and keeping a bunch of bad files, which then won't run. But if the file is good, as most people suspect, then you should be able to crunch them just fine.

<message>
WU download error: couldn't get input files:
<file_xfer_error>
<file_name>input_4528_32</file_name>
<error_code>-224 (permanent HTTP error)</error_code>
<error_message>permanent HTTP error</error_message>
</file_xfer_error>

tons of those, wingmen are affected too so it's a problem on server side.

Your issue is the same issue I wrote about in http://asteroidsathome.net/boinc/forum_thread.php?id=418 that I opened because I realized my issue was a different issue than the original poster's issue. Our issue is that our BOINC clients were directed to download files that do not exist on the server. The issue the original poster wrote about is that the BOINC client is detecting signs of file corruption because the downloaded files are different sizes than their declared files, and therefore declaring download errors.

You're right, it's like that one.

I am starting to think that the Asteroids@home server's file system might be corrupted, or its hard drive might be failing. See http://asteroidsathome.net/boinc/workunit.php?wuid=26733314 Results 0 and 1 failed due to being sent to Android Lollipop devices that can't handle this project's pre-Lollipop-only Android application. Result 2 managed to get all of the required files and completed it successfully. All subsequent results are unable to get one of the required files due to permanent HTTP errors. This makes me suspect either a corrupted file system or a failing hard drive because one of the required files was successfully downloaded and now cannot be downloaded anymore.