ATLASLocalRootBase Diagnostic Tools

Diagnostic tools are available when you do this:

(login)
setupATLAS
diagnostics

The tools are described in more detail in the following sections. Please login from a fresh terminal session to run the diagnostics tools.

If you are requested to run them, please send the complete output to user support, not what you think is useful !

checkOS

  • Purpose: check user's environment for missing software and other OS related settings.
  • When to run: anytime you see errors that cannot be reproduced on lxplus.
  • Limitations: RHEL 6, 7 based OS and MacOS will be checked.
  • Usage: eg. checkOS

db-fnget

  • Purpose: checks that the various combinations of squids and frontier launchpads work for the user. At least one must work.
  • When to run: anytime you see database errors.
  • Requirements:
    • if the environment FRONTIER_SERVER is not set, you need to first setup an athena release so that it is set.
  • Note: At least one combination must pass and sites should fix the FRONTIER_SERVER environment setting to add or remove inaccessible launchpads or bad squids to attain 100% success. Look at how many failures and successes there are in the test summary at the end.
  • Usage: eg.
    • db-fnget
    • or if FRONTIER_SERVER env is missing, asetup 19.0.3; db-fnget. (Any release is ok to use as the aim is to test Frontier access)

db-readReal

  • Purpose: checks that a job will successfully access the Frontier launchpads.
  • When to run: anytime you see database errors.
  • Requirements:
    • if the environment FRONTIER_SERVER is not set, you need to first setup an athena release so that it is set.
  • Usage: eg.
    • db-readReal
    • or if FRONTIER_SERVER env is missing, asetup 19.0.3; db-readReal. (Any release is ok to use as the aim is to test Frontier access)

gridCert

  • Purpose: this tool will check that a user's grid credentials will allow access to the many aspects of ATLAS distributed computing infrastructure.
  • When to run: anytime there is a grid access issue or connections failing that involve grid credentials.
  • Requirements:
    • valid grid credential files in $HOME/.globus.
  • Usage: eg. gridCert

rseCheck

  • Purpose: to help understand any DDM related issue reported by users. This also checks for site downtimes.
  • When to run: anytime there is a file failing to download or upload from / to a rse.
  • Requirements:
    • valid grid credential files in $HOME/.globus.
  • Note: If a rucio rse is specificd, and for which the user has write access (e.g. SCRATCHDISK, LOCALGROUPDISK), an upload and delete test will be also done.
  • Usage: specify either a rucio rse or a rucio data identifier or both. If it is ambiguous, you will be asked for details. eg.
    • rseCheck INFN-GENOVA_SCRATCHDISK
    • rseCheck data15_13TeV:AOD.07709524._000052.pool.root.1
    • seCheck data15_13TeV:AOD.07709524._000052.pool.root.1 -r WEIZMANN-LCG2_DATADISK

runKV

  • Purpose: run Kit Validation of an Athena release to ensure that a site is ATLAS ready for that release.
  • When to run: when you need to check that an Athena release is good at your site.
  • Note: This is not something normally done or required by users.
  • Requirements: You need to first setup a release; e.g..
setupATLAS
asetup 19.0.3,here
diagnostics
runKV

setMeUpData

  • Purpose: This is not strictly a diagnostics tool. It is used to download and setup the area needed for tutorials described here.
  • When to run: when you want to run tutorials at your site instead of lxplus.
  • Requirements:
    • valid grid credential files in $HOME/.globus
    • a directory to download data.
  • Usage: find the tutorial you want and enter the place-date as the first argument; e.g.. setMeUpData chicago-mar2016 $HOME/myTutorialData

setMeUp

  • Purpose: check user environment and readiness for tutorials described here.
  • When to run: when you want to be sure that your environment is ready for the tutorials. (Outside of tutorials, can also be run to verify that you are ATLAS ready).
  • Requirements:
    • valid grid credential files in $HOME/.globus
    • data needed for tutorial
      • already available on lxplus so no configurations needed
      • or download outside CERN using the setMeUpData tool referred to earlier in this page and define the environment variable ALRB_TutorialData to the local directory containing the tutorial datafiles.
  • Usage: eg. specify the place-date of the tutorial setMeUp chicago-mar2016

supportInfo

  • Purpose: generates a dump file which should be sent to user support.
  • When to run: Anytime you have an issue that cannot be reproduced on lxplus.
  • Note: what to look for is listed in the output but most times an expert eye is needed.
  • Usage: eg. supportInfo

toolTest

  • Purpose: test a tool, or validate a container/VM, or test new versions of tools for deployment
  • When to run:
    • (option -m user) users: if they have a problem with a particular tool
    • (option -m validate) container producers: to validate that the container is ready for ATLAS users. Note that this will not run the other diagnostics tools (eg checkOS) which you should run on your own
    • (option -m test) tool deployment: can check if a testing version is good or problematic
  • Note: toolTest <tool> -v verbose option will show details of tests done.
  • Note: toolTest <tool> -h will show the additional options / env to override the settings used by default
  • Note: -m test will use the testing version for all tools
  • Usage: eg toolTest -m user all to test all tools as a user
  • Examples:
    • toolTest -m user rucio
    • toolTest -m validate all
    • toolTest -m test rucio
Edit | Attach | Watch | Print version | History: r6 < r5 < r4 < r3 < r2 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r6 - 2019-02-26 - AsokaDeSilva
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback