Frontier Squid Caching Proxy Installation Guide

1 About This Document

This document is intended for System Administrators who are installing frontier-squid, the OSG distribution of the Frontier Squid software.

2 Applicable Versions

The applicable software versions for this document are OSG Version >= 3.4.0. The version of frontier-squid installed should be >= 3.5.24-3.1. When using an OSG Version < 3.4.0 and a frontier-squid version in the 2.7STABLE9 series, refer to the old upstream install documentation instead of the current links included below. There are some incompatibilities between the two versions, so if you are upgrading from a 2.7STABLE9 version to a 3.5 version, see the upstream documentation on upgrading.

3 About Frontier Squid

Frontier Squid is a distribution of the well-known squid HTTP caching proxy software that is optimized for use with applications on the Worldwide LHC Computing Grid (WLCG). It has many advantages over regular squid for common grid applications, especially Frontier and CVMFS.

The OSG distribution of frontier-squid is a straight rebuild of the upstream frontier-squid package for the convenience of OSG users.

4 Frontier Squid is Recommended

OSG recommends that all sites run a caching proxy for HTTP and HTTPS to help reduce bandwidth and improve throughput. To that end, Compute Element (CE) installations include Frontier Squid automatically. We encourage all sites to configure and use this service, as described below.

For large sites that expect heavy load on the proxy, it may be best to run the proxy on its own host. In that case, the Frontier Squid software still will be installed on the CE, but it need not be enabled. Instead, install your proxy service on the separate host and then configure the CE host to refer to the proxy on that host.

The osg-configure configuration tool (version 1.0.45 and later) warns users who have not added the proxy location to their CE configuration. In the future, a proxy will be required and osg-configure will fail if the proxy location is not set.

5 Engineering Considerations

If you will be supporting the Frontier application at your site, review the upstream documentation Hardware considerations section to determine how to size your equipment.

6 Requirements

6.1 Host and OS

  • OS is Red Hat Enterprise Linux 6, 7, and variants (see details...).
  • Root access

6.2 Users

The frontier-squid installation will create one user account unless it already exists.

User Comment
squid Reduced privilege user that the squid process runs under. Set the default gid of the "squid" user to be a group that is also called "squid".

The package can instead use another user name of your choice if you create a configuration file before installation. Details are in the upstream documentation Preparation section.

6.3 Networking

For more details on overall Firewall configuration, please see our Firewall documentation.

Service Name Protocol Port Number Inbound Outbound Comment
Squid tcp 3128 Y Y Also limited in squid ACLs. Both in and outbound must not be wide open to internet simultaneously
Squid monitor udp 3401 Y   Also limited in squid ACLs. Should be limited to monitoring server addresses

The addresses of the WLCG monitoring servers for use in firewalls are listed in the upstream documentation Enabling monitoring section.

7 Install Instructions

7.1 Installing Frontier Squid

After meeting the requirements in the previous section, install frontier-squid with this command:

[root@client ~]$ yum install frontier-squid 

Then enable it to start at boot time with this command:

[root@client ~]$ chkconfig frontier-squid on

8 Configuring Frontier Squid

8.1 Configuring the Frontier Squid Service

To configure the Frontier Squid service itself:

  1. Follow the upstream Frontier Squid documentation, in the Configuration section

    Note: An important difference between the standard Squid software and the Frontier Squid variant is that Frontier Squid changes are in /etc/squid/ instead of /etc/squid/squid.conf.

  2. Enable, start, and test the service (as described below)
  3. Enable WLCG monitoring as described in the upstream documentation on enabling monitoring and register the squid in OIM.

8.2 Configuring the OSG CE

To configure the OSG Compute Element (CE) to know about your Frontier Squid service:

  1. On your CE host, edit /etc/osg/config.d/01-squid.ini
    • Make sure that enabled is set to True
    • Set location to the hostname and port of your Frontier Squid service (e.g.,
    • Leave the other settings at DEFAULT unless you have specific reasons to change them
  2. Run osg-configure to propagate the changes on your CE

    Note: You may want to finish other CE configuration tasks before running osg-configure. Just be sure to run it once before starting CE services.

9 Starting and Stopping the Frontier Squid Service

Starting frontier-squid:

[root@client ~]$ service frontier-squid start

Stopping frontier-squid:

[root@client ~]$ service frontier-squid stop

10 Testing Frontier Squid

As any user on another computer, do the following (where yoursquid.your.domain is the fully qualified domain name of your squid server):

[user@client ~]$ export http_proxy=http://yoursquid.your.domain:3128
[user@client ~]$ wget -qdO/dev/null 2>&1|grep X-Cache
X-Cache: MISS from yoursquid.your.domain
[user@client ~]$ wget -qdO/dev/null 2>&1|grep X-Cache
X-Cache: HIT from yoursquid.your.domain

If the grep doesn't print anything, try removing it from the pipeline to see if errors are obvious. If the second try says MISS again, something is probably wrong with the squid cache writes. Look at the squid access.log file to try to see what's wrong.

If your squid will be supporting the Frontier application, it is also good to do the test in the upstream documentation Testing the installation section.

11 Frontier Squid Log Files

Log file contents are explained in the upstream documentation Log file contents section.

12 Getting Help

To get assistance please use Help Procedure.


Topic revision: r33 - 13 Jun 2017 - 15:18:32 - DaveDykstra
Hello, TWikiGuest!


TWiki | Report Bugs | Privacy Policy

This site is powered by the TWiki collaboration platformCopyright by the contributing authors. All material on this collaboration platform is the property of the contributing authors..