My Windows 98 system logged an error I hadn’t seen before after “successfully� crunching h1_0256.60_S5R2__95_S5R2c in about 65 hours of CPU-time:
[pre]2007-06-05 18:05:01.2600 [debug]: DEBUG: read_fstat_toplist_from_fp() returned 552826
2007-06-05 18:05:01.2600 [CRITICAL]: ERROR: checksum error in toplist 30767351 / 27543408
2007-06-05 18:05:01.2600 [debug]: Total skypoints = 16202. Progress: 14032, 14033, 14034, 14035, 14036, 14037, 14038, 14039,
14040, 14041, 14042, 14043, 14044, 14045, 14046, 14047, 14048, 14049, 14050
2007-06-05 18:09:13.4200 [CRITICAL]: Failed to write toplist item to file: 9: Bad file descriptor
2007-06-05 18:09:13.4200 [CRITICAL]: Windows system call returned: 5
2007-06-05 18:09:13.4200 [debug]: ERROR: bytecount mismatch: returned: 52, bytes: 565270, file: 557109[/pre]followed by numerous similar lines to the last: “bytecount mismatch�. The result was invalid. Two other hosts had “compute errors� after many hours of crunching.
Copyright © 2024 Einstein@Home. All rights reserved.
Checksum error in toplist
)
Call it the doomed workunit ...
To me the other client errors look unrelated: disk space problems, error parsing command line (never saw ´that one before!), checksum in toplist.
CU
BRM