SAM CMS Software Installation Test

Full name: org.cms.WN-swinst

Maintainer: Christoph Wissing


Verifies that the CMSSW versions required by CMS are installed on the site, available through scramv1 and published in BDII


This script checks:
  • Stop that the CMS software directory ($VO_CMS_SW_DIR for gLite/ARC and $OSG_APP/cmssoft/cms for OSG) is defined, exists and is readable
  • ALERT! that the CMS software directory is writable by lcgadmin (only on gLite/ARC, except CERN and sites CVMFS mount /cvmfs/
  • Stop that the CMS software initialisation script ( exists and can be sourced without errors for at least one defined architecture
  • Stop CMS_PATH is defined and points to an existing directory
  • Stop that scramv1 is found
  • ALERT! that installation is OK for a selected list of releases (so called required CMSSW releases) , by creating a project area with scramv1 project CMSSW CMSSW_X_Y_Z and setting up runtime environment in the project area with eval `scramv1 runtime -sh`
    • the list of required CMSSW release is maintained here in CVS and updated as needed
  • ALERT! that if a production release is installed, the corresponding VO-cms tag is published in BDII
  • Stop that if a production release is published in BDII, it is also installed
    • list of production release is from Tag Collector
    • list of tags published in BDII is in this page (updated every hour by a crontab)
  • Stop that architecture tags (like e.g. VO-cms-slc5_amd64_gcc434 and VO-cms-slc5_amd64_gcc462) are published in the BDII
  • ALERT! that all production releases are installed

  • Stop: failure of this check generates an ERROR
  • ALERT!: failure of this check generates a WARNING
  • Note: failure of this check generates a NOTE

Source code


The CMSSW releases are usually maintained centrally by for most of the sites. In case of questions and problems site admins are always welcome to submit a Savannah ticket and assign it to the cmscompinfrasup-cmsswdeploy squad.

WARNING: Some production release is not installed
Cause: The release has not yet been installed.

Note: The deployment cycle of release might need several hours.

Solution: In most cases it is sufficient just to wait until the deployment team has rolled out the missing release.

WARNING: Some CMS VO Tags are missing
Cause: List typical cases when it can occur.

Note: After a new release was announced and installed, it takes some time until information system is up to date.

Solution: The missing tags should be published, or the corresponding CMSSW releases uninstalled. The first option is highly preferred.

WARNING: Cannot write to CMSSW installation area
Cause: the lcgadmin role does not have write permissions on the software area. Software installation via grid jobs is impossible.

Solution: grant write permission in $VO_CMS_SW_DIR (for gLite/ARC) or $OSG_APP/cmssoft/cms (for OSG) to the local user to which the lcgadmin role is mapped.

Symbol Legend

-- ChristophWissing - 21-Jun-2012

Edit | Attach | Watch | Print version | History: r15 < r14 < r13 < r12 < r11 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r12 - 2012-07-03 - AndreaSciaba
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    CMSPublic All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback