SAM CMS Squid test
Full name:
org.cms.WN-squid
Maintainer:
Barry Blumenfeld
Overview
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.
Checks
The test checks that:
-
the CMS software directory ($VO_CMS_SW_DIR
for EGEE and $OSG_APP/cmssoft/cms
for OSG) is defined
-
that the CMS software initialisation script (cmsset_default.sh
) can be sourced without errors
-
that the CMS_PATH variable is set
-
that the $CMS_PATH/SITECONF/local/JobConfig/site-local-config.xml
file exists
-
that site-local-config.xml
has a proxy
or a proxyconfig
tag
-
that for at least one of the Squid servers defined the query SELECT 1 FROM DUAL
to http://cmsfrontier.cern.ch:8080/FrontierProd/Frontier
via Squid returns a not-empty and valid answer without error messages
-
that the above is true for all the Squid servers defined. Squids from proxyconfig
are not currently tested.
Legend
-
: failure of this check generates an ERROR
-
: failure of this check generates a WARNING
Source code
More information
Troubleshooting
FailingSquid
--
StefanoBelforte - 22 Feb 2007