1) Questions and Answers : Wish list : Server statistics page should accurately reflect workunits waiting validation (Message 39812)
Posted 3 Sep 2019 by 2BbwZPYG2XaMQQaG8qsvsz4QDGuL
Post:
The https://lhcathome.cern.ch/lhcathome/server_status.php page does not correctly reflect the workunits waiting on validation.

Currently (3th of September 2019 15:25 GMT) the server status page reflects 6 workunits waiting on validation, however, My statistics show that I have 11 jobs waiting on validation. Clearly the server status page does not correctly reflect the amount of workunits that are actually waiting on validation.

I suspect this is due to other contributors not having finished their copy of the task that was also sent to me (as I suspect the server validates by comparing results from multiple contributors having performed the same task).

Maybe the server status page could distinguish between workunits that can not be queued for validation and once that are actually awaiting to be validated.
2) Message boards : ATLAS application : ATLAS native_mt error while computing after 600 seconds (Message 37998)
Posted 12 Feb 2019 by 2BbwZPYG2XaMQQaG8qsvsz4QDGuL
Post:
ATLAS VBox is just ATLAS native running in a VBox. If they fail as native tasks then they'll fail inside the VBox as well.


Sorry this is not going to hold and is simply completely not true. The operating system being virtualized in the virtualbox environment can be substantially different to an extend were it has significant impact on the ability to run computing tasks.

For example the kernel can be different, the bios that is virtualized and it's corresponding smbios are almost certainly different. Inside an virtualized environment it is possible to run completely different operating systems such as Linux on Windows or Windows on Linux.

What is important in this case is that running the computing tasks in a vm allows to have cvmfs preinstalled which is a dependency required for the tasks to correctly function. One reason one might prefer to run a computing tasks natively instead of inside a virtual machine is because virtualization imposes a performance hit.
3) Message boards : ATLAS application : ATLAS native_mt error while computing after 600 seconds (Message 37976)
Posted 11 Feb 2019 by 2BbwZPYG2XaMQQaG8qsvsz4QDGuL
Post:
If that's the case than I really feel like it should be an option to exclude native_mt but still participate in regular vbox64_mt_mcore_atlas as it is very wasteful of resources to just push tasks that will fail after 600 seconds.

Unchecking test applications is a possible solution but will also opt out of other test applications which I would like to continue to run.
4) Message boards : ATLAS application : ATLAS native_mt error while computing after 600 seconds (Message 37974)
Posted 11 Feb 2019 by 2BbwZPYG2XaMQQaG8qsvsz4QDGuL
Post:
Recently I have been getting errors on the ATLAS native_mt job always precisely after 600 seconds.

https://imgur.com/a/ilyLMW8

Does anyone know how to resolve this? or disable native_mt as vbox_64_mt seems to work flawlessly.

All the best,
Corne



©2024 CERN