I did reset then fully detached then re-attached when the Certificate was updated, and also need to wait for the release of more WU's, so it is still a case of have-patience for Asteroids because of the specific situation here. Over on Skynet-Pogs, that is also a wait-game as they are changing things around also, so once their current WU situation clears out (similar to here) then they'll generate new WUs from what I gather.

I am really sorry, the script with adding new workunits has failed and I was unable to check it during the weekend. I am going to check it now.

Thanks.. all 8 machines are now doing Asteroids again :)

---

Thanks Kyong,

All working here again :)

My office heater now working properly.

Cheers

Kerry

There doesn't seem to be an end to the number of wu downloading. My preferences are set to get 5 days worth but it just goes on and on and on downloading more and more work units. It this intended behavior?

Nick

Hi Nick,

Some WU are easy and fast to process, others take longer and slower.

It may be that you have downloaded a bunch of fast short WU, easy to process.

Just keep on with them.

Cheers

Kerry

Kerry

No, they're all about an hour and a half and I had already downloaded 10x what I usually get when I had to turn off the "allow new tasks" tab.

Something's not right.

Kerry

No, they're all about an hour and a half and I had already downloaded 10x what I usually get when I had to turn off the "allow new tasks" tab.

Something's not right.

That's not unusual, I've had this in the past. Most of those will eventually be cancelled by the server as they time out or are processed by others. Your cache of WUs will settle down to the amount you expect in the next couple of days.

18.03.2015 11:42:39 | Asteroids@home | Finished download of input_1803_4
18.03.2015 11:42:39 | Asteroids@home | Finished download of input_1755_47
18.03.2015 11:42:39 | Asteroids@home | Finished download of input_1872_18
18.03.2015 11:42:39 | Asteroids@home | [error] File input_1633_17 has wrong size: expected 46567, got 0
18.03.2015 11:42:39 | Asteroids@home | [error] Checksum or signature error for input_1633_17
18.03.2015 11:42:39 | Asteroids@home | [error] File input_1872_7 has wrong size: expected 20156, got 0
18.03.2015 11:42:39 | Asteroids@home | [error] Checksum or signature error for input_1872_7
18.03.2015 11:42:39 | Asteroids@home | [error] File input_1722_51 has wrong size: expected 40702, got 0
18.03.2015 11:42:39 | Asteroids@home | [error] Checksum or signature error for input_1722_51
18.03.2015 11:42:39 | Asteroids@home | [error] File input_1418_27 has wrong size: expected 38331, got 0
18.03.2015 11:42:39 | Asteroids@home | [error] Checksum or signature error for input_1418_27
18.03.2015 11:42:39 | Asteroids@home | [error] File input_1412_37 has wrong size: expected 40340, got 0
18.03.2015 11:42:39 | Asteroids@home | [error] Checksum or signature error for input_1412_37


Still getting tons of this erros. This lead to a delay when my client asks again und my queue runs dry.

Please fix.

These are the old workunits. Just cancel them and they will be canceled by server. The new workunits should be fine.

Thanks for sending new tasks. I'm cranking again. However, there are many download failures among the new workunits. The old ones are gone.

Haven't been able to process any work units in several days...
Have seen quite a few errors lately. As I'm fairly new to BOINC, I'm not sure if this is normal...
Can anyone help?
Thanks
Steve




Sent Time reported
or deadline
explain Status Run time
(sec) CPU time
(sec) Credit Application
69262107 28029074 146527 19 Mar 2015, 4:14:32 UTC 29 Mar 2015, 16:14:32 UTC In progress --- --- --- Period Search Application v102.10 (sse2)
66672819 28041723 146527 19 Mar 2015, 4:14:32 UTC 29 Mar 2015, 16:14:32 UTC In progress --- --- --- Period Search Application v102.10 (sse2)
69262070 28035441 146527 19 Mar 2015, 4:14:32 UTC 29 Mar 2015, 16:14:32 UTC In progress --- --- --- Period Search Application v102.10 (sse2)
69262162 27985982 146527 19 Mar 2015, 4:13:59 UTC 29 Mar 2015, 16:13:59 UTC In progress --- --- --- Period Search Application v102.10 (sse2)
69262184 28037133 146527 19 Mar 2015, 4:13:59 UTC 29 Mar 2015, 16:13:59 UTC In progress --- --- --- Period Search Application v102.10 (sse2)
69260609 28034095 146527 19 Mar 2015, 4:02:30 UTC 19 Mar 2015, 4:13:59 UTC Error while downloading 0.00 0.00 --- Period Search Application v102.10 (sse2)
66671730 28041300 146527 19 Mar 2015, 4:02:30 UTC 19 Mar 2015, 4:13:59 UTC Error while downloading 0.00 0.00 --- Period Search Application v102.10 (sse2)
66667747 28039308 146527 19 Mar 2015, 2:57:36 UTC 19 Mar 2015, 4:02:30 UTC Error 0.00 0.00 --- Period Search Application v102.10 (sse2)
66663315 28037084 146527 19 Mar 2015, 1:57:06 UTC 29 Mar 2015, 13:57:06 UTC In progress --- --- --- Period Search Application v102.10 (sse2)
66663328 28037090 146527 19 Mar 2015, 1:57:06 UTC 19 Mar 2015, 2:57:36 UTC Error while downloading 0.00 0.00 --- Period Search Application v102.10 (sse2)
69236011 28032565 146527 19 Mar 2015, 0:56:11 UTC 19 Mar 2015, 1:57:05 UTC Error while downloading 0.00 0.00 --- Period Search Application v102.10 (sse2)
66659057 28034952 146527 19 Mar 2015, 0:56:11 UTC 19 Mar 2015, 1:57:05 UTC Error while downloading 0.00 0.00 --- Period Search Application v102.10 (sse2)
69227666 28032446 146527 18 Mar 2015, 23:55:20 UTC 19 Mar 2015, 0:56:11 UTC Error while downloading 0.00 0.00 --- Period Search Application v102.10 (sse2)
66645992 28028345 146527 18 Mar 2015, 21:44:34 UTC 29 Mar 2015, 9:44:34 UTC In progress --- --- --- Period Search Application v102.10 (sse2)
66645996 28028347 146527 18 Mar 2015, 21:44:34 UTC 29 Mar 2015, 9:44:34 UTC In progress --- --- --- Period Search Application v102.10 (sse2)
69209099 28021733 146527 18 Mar 2015, 21:21:16 UTC 18 Mar 2015, 21:44:33 UTC Error while downloading 0.00 0.00 --- Period Search Application v102.10 (sse2)
69209130 28022585 146527 18 Mar 2015, 21:21:16 UTC 18 Mar 2015, 21:44:33 UTC Error while downloading 0.00 0.00 --- Period Search Application v102.10 (sse2)
69201484 28008478 146527 18 Mar 2015, 20:20:54 UTC 18 Mar 2015, 21:21:16 UTC Error while downloading 0.00 0.00 --- Period Search Application v102.10 (sse2)
69201485 28008802 146527 18 Mar 2015, 20:20:54 UTC 18 Mar 2015, 21:21:16 UTC Error while downloading 0.00 0.00 --- Period Search Application v102.10

Hi,
There seems to be a repeat of the checksum download errors:-/
And its almost non stop with every d/l erroring out.

Even aborting the d/l and trying again just results in the same error for the next d/l.

Anyone got a way to get new work and avoid this d/l problem?

Regards,
Cliff

Android 4.0.3 I have on a Acer A200 tablet,the problem is the projects are attaching but taking 2 seconds to complete so what may be the problem?I know my tablet can't be this fast or are the new work units that small?

Some crazy reason mines aren't downloading errors mines are downloading &completing in 2 or 3 seconds...something is wrong

Hi, thank you and Mr. Vančo for all your hard work.

I did an update of A@H today and got some work units but lots said they failed to download. Using the BOINC manager GUI, there were only two things I could do to these, either wait to see if they ever succeeded in re-downloading or using the abort. I decided on the latter.
I stopped A@H from accepting new WUs, so I wouldn't get any more failed downloads then aborted the failed WUs, then did another update. What I was hoping was that this would immediately free up those units as work for some other user.

Was I wrong?

---

I'm also unsure why Downloads fail.

I now had many "Failed Downloads" so selected them and "Aborted" them

On Updating Asteroids, I got Downloads again, they all failed.

I can't see any easy way to post the list here, without laboriously typing it out by hand.

AThe Deadline for each of the "Failed Downloads" is 30/03/2015 11:52:-- pm

Helpful advice would be useful

Cheers from a Faraway Land[/img]

---

Anyone got a way to get new work and avoid this d/l problem?

No way to "avoid this d/l problem" - files either do not exist on the server, have a wrong filename, are empty or are in the wrong directory.

Or the database entries which translate from Workunit name to filename to Download are wrong, e.g. (one of the failed WUs, one of the tasks is yours):
Workunit name period_search_32306_1426496976.196767_81059
<file_name>input_2498_39</file_name>
http://asteroidsathome.net/boinc/workunit.php?wuid=28042119

Or the files are somehow locked (on the server) (permissions?)

Any of this have to be checked and corrected on the server.

---

- ALF - "Find out what you don't do well ..... then don't do it!" :)

 
OK, I used the method described here:
http://home.ssl.berkeley.edu/forum_thread.php?id=56536&postid=953939#953939

... and think that input_2498_39 have to be in:
http://asteroidsathome.net/boinc/download/4b/

... but it is not there.


Method:
The name/string:
period_search_32306_1426496976.196767_81059
... have MD5 Hash:
9c30204b4718e37e624092ac37bf1f14

You skip the first 9c302 and come to 04b which translates to directory 4b


* But maybe this method do not work here as I can't find one of my "waiting for validation" (+ "In progress" on another computer) WUs:
http://asteroidsathome.net/boinc/workunit.php?wuid=27984808

period_search_32306_1426496976.196767_23748 -> 1592dcc3a7861a8673d79b647cfdd78d -> cc3 -> c3
http://asteroidsathome.net/boinc/download/c3/

Searching for period_search_32306_1426496976.196767_23748 in my stdoutdae.txt and stdoutdae.old I found:
18-Mar-2015 05:11:59 [Asteroids@home] Finished download of input_1469_7
18-Mar-2015 05:11:59 [Asteroids@home] Starting period_search_32306_1426496976.196767_23748_0

... but input_1469_7 is not in "c3" directory

 

---

- ALF - "Find out what you don't do well ..... then don't do it!" :)

No way to "avoid this d/l problem" - files either do not exist on the server, have a wrong filename, are empty or are in the wrong directory.

Any of this have to be checked and corrected on the server.

Then perhaps its time Radim considered taking a@h offline until he has time to sort out these problems?

Then no one would have to footle about endlessly trying to get WU and failing while the problem got sorted out.

Regards,
Cliff