SAM CMS Squid test

Full name: org.cms.WN-squid

Maintainer: Barry Blumenfeld


Verify that the Squid server at the site
  • is defined in the site local configuration file
  • is up and running
  • can access the FroNtier launchpad at CERN
it does this making an SQL call that reflects on Oracle server at CERN, testing the full chain.


The test checks that:
  • Stop the CMS software directory ($VO_CMS_SW_DIR for EGEE and $OSG_APP/cmssoft/cms for OSG) is defined
  • Stop that the CMS software initialisation script ( can be sourced without errors
  • Stop that the CMS_PATH variable is set
  • Stop that the $CMS_PATH/SITECONF/local/JobConfig/site-local-config.xml file exists
  • Stop that site-local-config.xml has a proxy or a proxyconfig tag
  • Stop that for at least one of the Squid servers defined the query SELECT 1 FROM DUAL to via Squid returns a not-empty and valid answer without error messages
  • ALERT! that the above is true for all the Squid servers defined. Squids from proxyconfig are not currently tested.

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

Source code

More information



-- StefanoBelforte - 22 Feb 2007

This topic: CMSPublic > ComputingCommissioning > SAMForCMS > SamSquid
Topic revision: r15 - 2020-01-08 - DaveDykstra
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2023 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