Is it just me or is there a problem with the file.
I just reset the project and deleted all files in the einstein folder after finishing all wu's with computation errors.
But i always get the same message
2008-06-21 22:11:36 [Einstein@Home] [error] MD5 check failed for l1_1191.30_S5R3
2008-06-21 22:11:36 [Einstein@Home] [error] expected 964857026afb3a3c20d94e19917e78d5, got 8b06b05a0ff26875118df5819140a28f
2008-06-21 22:11:36 [Einstein@Home] [error] Checksum or signature error for l1_1191.30_S5R3
2008-06-21 22:11:36 [Einstein@Home] Deferring communication for 1 min 0 sec
2008-06-21 22:11:36 [Einstein@Home] Reason: Unrecoverable error for result h1_1190.90_S5R3__813_S5R3b_0 (WU download error: couldn't get input files:
l1_1191.30_S5R3
-119
MD5 check failed
)
Thank you for any help. Seti is working without problems.
Just reached the daily quota, have to wait until tomorrow for any tests.
Copyright © 2024 Einstein@Home. All rights reserved.
Download problems, computation errors
)
Hmmmm....
I haven't noticed any problems with the communications to and from the project lately.
I did notice when looking over the series of failures for your host that they seemed to start off with a CRC sanity check failure when restarting from checkpoints. The rest have been MD5 hash failures on the input files.
This might indicate a RAM, Hard Drive, or other hardware related problem on your host.
Might not be a bad idea to give it a general maintenance and diagnostic run.
HTH,
Alinator
Thank you Alinator, I just
)
Thank you Alinator,
I just realized that my system is crunching again after downloding an other inputfile during the night.
I realy don't know what was wrong yesterday, no changes are made on the system.
Now I wait until the new wu's are validated.
Glad to here your host is
)
Glad to here your host is back in the game.
Thinking about it some more and reviewing my logs, I remembered that one of my hosts which runs EAH primarily drew a couple of tasks from Leiden around the middle of last week.
When I checked the BOINC logs at the time, I noticed there there were a couple of brief periods where the EAH scheduler and UL/DL servers weren't available.
In my case it didn't cause any compute errors or other anomalies on my host, but that might have had something to do with your event.
Alinator