md5 check failed

Many thanks for the report, I forwarded this to the E@H team.

CU
Bikeman

Kudoes for spotting this problem!

We found a corrupted file on the E@H server. The wrong md5 sum was being shipped out. I have just fixed this in the workunits (replace incorrect md5 sum with the correct one):

mysql> update workunit set xml_doc=REPLACE(xml_doc,"c2c67b1cf86121f7b79d8184069e9926","0b35efca8e47808f6b751a8045e7113c") where xml_doc like '%l1_0873.00_S5R4%' limit 200;
Query OK, 115 rows affected (14.41 sec)
Rows matched: 126  Changed: 115  Warnings: 0

mysql> select count(id) from workunit where xml_doc like '%l1_0873.00_S5R4%' and xml_doc like '%c2c67b1cf86121f7b79d8184069e9926%' ;
+-----------+
| count(id) |
+-----------+
| 0 |
+-----------+
1 row in set (10.90 sec)

mysql> select count(id) from workunit where xml_doc like '%l1_0873.00_S5R4%' and xml_doc like '%0b35efca8e47808f6b751a8045e7113c%' ;
+-----------+
| count(id) |
+-----------+
| 126 |
+-----------+
1 row in set (10.67 sec)

This means that approximate 250 'results in progress' are going to fail because they have the wrong md5 sum. We'll then generate new results for these workunits that should succeed. I'm keeping my fingers crossed that this is a 'one time' corruption problem on the download server and not something that will occurr a lot!

Cheers,
Bruce