What to do if CMS SAM test for Squid fails
- the obvious thing is to look at server logs and run a local test as indicated in squid installation instructions
- some not-so-obvious problems that have been reported are
- farm was reconfigured, with new subnet, and the list of allowed subnets in squid was not updated
- squid cache was corrupted. This should be reported in squid's cache.log file, a 'squid -z' command will be needed, see installation instructions. Note that the version of the installation tarball 2.0rc3 and later (see https://twiki.cern.ch/twiki/bin/view/CMS/SquidForCMS ) should detect the corruption and automatically recover from it
- any new squid problem should be reported to http://savannah.cern.ch/bugs/?func=additem&group=frontier
- the contact for help on the CMS Frontier tools and Squid is mailto:cms-frontier-support@cernNOSPAMPLEASE.ch
This topic: CMSPublic > ComputingCommissioning > SAMForCMS > FailingSquid
Topic revision: r8 - 2008-09-16 - BarryBlumenfeld
Copyright &© 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