1) Message boards : Number crunching : checksum errors (Message 5671)
Posted 20 Feb 2005 by ttocs
Post:
A similar thing happened on one of my machines as well. Not checksum errors, but the app wouldn't run giving a "text busy" error or something like that. Doing a reset on the project resolved the problem, but still, it is a sign of something wrong.
2) Message boards : Number crunching : stderr out text not visible on the host computer? (Message 5659)
Posted 19 Feb 2005 by ttocs
Post:
I can see my stderr.out from my 4.61, 4.20 and 4.22 clients (linux).
3) Message boards : Number crunching : Validator Problem (Message 5650)
Posted 17 Feb 2005 by ttocs
Post:
I've had this issue with the regular alpha core client, not just self compiled ones. I don't know if it occurs with the released client, though. I have seen the CPU and credit misreported on Predictor WUs, though the issue seems more pronounced with LHC.

Since the alpha core client (4.19, 4.61, 4.62, 4.20, 4.21) switches among projects more, the conjecture of a checkpointing issue makes some amount of sense. If the CPU info is forgotten between switches, this could be an explanation.

4) Message boards : Number crunching : Validator Problem (Message 5647)
Posted 16 Feb 2005 by ttocs
Post:
Note that http://lxfsrk4101.cern.ch/results.php?hostid=20798 has a lot of 0 credit WUs (as do several of mine). This is a 2.8 GHZ Pentium 4 running Linux. Another odd thing is that for the nonzero WUs, the CPU times are still pretty low. For example on, http://lxfsrk4101.cern.ch/workunit.php?wuid=245 this machine reported
2,023.23 CPU seconds, but a faster machine running win XP ( http://lxfsrk4101.cern.ch/show_host_detail.php?hostid=20790 ) claims more than 20 times the amount of CPU time. Something is way off.

-ttocs



©2023 CERN