Difference: InstallSquidTarball (1 vs. 42)

Revision 422019-08-29 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallSquid"

Installing frontier-squid from source tarball

We recommend installing the frontier-squid package from the frontier-squid rpm, but if you want to use the source tarball, which is more portable, easily relocatable and can be run under any username, the instructions are below.
Line: 13 to 13
  Unpack and configure the current version of the tarball:

Changed:
<
<
$ wget http://frontier.cern.ch/dist/frontier-squid-4.6-2.tar.gz $ tar -xvzf frontier-squid-4.6-2.tar.gz $ cd frontier-squid-4.6-2
>
>
$ wget http://frontier.cern.ch/dist/frontier-squid-4.8-2.tar.gz $ tar -xvzf frontier-squid-4.8-2.tar.gz $ cd frontier-squid-4.8-2
  $ ./configure

Revision 412019-07-17 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallSquid"

Installing frontier-squid from source tarball

We recommend installing the frontier-squid package from the frontier-squid rpm, but if you want to use the source tarball, which is more portable, easily relocatable and can be run under any username, the instructions are below.
Line: 35 to 35
  You can double check your responses to the prompts by reading Makefile.conf.inc and edit them there before running make if you wish.
Added:
>
>
On RHEL6-based Linux, a newer version of the compiler is required for squid-4. Before doing any building, do the following:
    $ sudo yum install devtoolset-2-toolchain scl-utils
    $ scl enable devtoolset-2 bash
That will put you into a shell where the new compiler is first in the PATH.
 Then do:
    $ make

Revision 402019-05-17 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallSquid"

Installing frontier-squid from source tarball

We recommend installing the frontier-squid package from the frontier-squid rpm, but if you want to use the source tarball, which is more portable, easily relocatable and can be run under any username, the instructions are below.
Line: 13 to 13
  Unpack and configure the current version of the tarball:

Changed:
<
<
$ wget http://frontier.cern.ch/dist/frontier-squid-4.6-1.tar.gz $ tar -xvzf frontier-squid-4.6-1.tar.gz $ cd frontier-squid-4.6-1
>
>
$ wget http://frontier.cern.ch/dist/frontier-squid-4.6-2.tar.gz $ tar -xvzf frontier-squid-4.6-2.tar.gz $ cd frontier-squid-4.6-2
  $ ./configure

Revision 392019-04-08 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallSquid"

Installing frontier-squid from source tarball

We recommend installing the frontier-squid package from the frontier-squid rpm, but if you want to use the source tarball, which is more portable, easily relocatable and can be run under any username, the instructions are below.
Line: 13 to 13
  Unpack and configure the current version of the tarball:

Changed:
<
<
$ wget http://frontier.cern.ch/dist/frontier-squid-4.4-1.tar.gz $ tar -xvzf frontier-squid-4.4-1.tar.gz $ cd frontier-squid-4.4-1
>
>
$ wget http://frontier.cern.ch/dist/frontier-squid-4.6-1.tar.gz $ tar -xvzf frontier-squid-4.6-1.tar.gz $ cd frontier-squid-4.6-1
  $ ./configure

Revision 382018-12-06 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallSquid"

Installing frontier-squid from source tarball

We recommend installing the frontier-squid package from the frontier-squid rpm, but if you want to use the source tarball, which is more portable, easily relocatable and can be run under any username, the instructions are below.
Line: 13 to 13
  Unpack and configure the current version of the tarball:

Changed:
<
<
$ wget http://frontier.cern.ch/dist/frontier-squid-3.5.28-3.tar.gz $ tar -xvzf frontier-squid-3.5.28-3.tar.gz $ cd frontier-squid-3.5.28-3
>
>
$ wget http://frontier.cern.ch/dist/frontier-squid-4.4-1.tar.gz $ tar -xvzf frontier-squid-4.4-1.tar.gz $ cd frontier-squid-4.4-1
  $ ./configure

Revision 372018-10-29 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallSquid"

Installing frontier-squid from source tarball

We recommend installing the frontier-squid package from the frontier-squid rpm, but if you want to use the source tarball, which is more portable, easily relocatable and can be run under any username, the instructions are below.
Line: 13 to 13
  Unpack and configure the current version of the tarball:

Changed:
<
<
$ wget http://frontier.cern.ch/dist/frontier-squid-3.5.28-1.tar.gz $ tar -xvzf frontier-squid-3.5.28-1.tar.gz $ cd frontier-squid-3.5.28-1
>
>
$ wget http://frontier.cern.ch/dist/frontier-squid-3.5.28-3.tar.gz $ tar -xvzf frontier-squid-3.5.28-3.tar.gz $ cd frontier-squid-3.5.28-3
  $ ./configure

Revision 362018-08-23 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallSquid"

Installing frontier-squid from source tarball

We recommend installing the frontier-squid package from the frontier-squid rpm, but if you want to use the source tarball, which is more portable, easily relocatable and can be run under any username, the instructions are below.
Line: 13 to 13
  Unpack and configure the current version of the tarball:

Changed:
<
<
$ wget http://frontier.cern.ch/dist/frontier-squid-3.5.27-5.tar.gz $ tar -xvzf frontier-squid-3.5.27-5.tar.gz $ cd frontier-squid-3.5.27-5
>
>
$ wget http://frontier.cern.ch/dist/frontier-squid-3.5.28-1.tar.gz $ tar -xvzf frontier-squid-3.5.28-1.tar.gz $ cd frontier-squid-3.5.28-1
  $ ./configure

Revision 352018-07-06 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallSquid"

Installing frontier-squid from source tarball

We recommend installing the frontier-squid package from the frontier-squid rpm, but if you want to use the source tarball, which is more portable, easily relocatable and can be run under any username, the instructions are below.
Line: 13 to 13
  Unpack and configure the current version of the tarball:

Changed:
<
<
$ wget http://frontier.cern.ch/dist/frontier-squid-3.5.27-4.tar.gz $ tar -xvzf frontier-squid-3.5.27-4.tar.gz $ cd frontier-squid-3.5.27-4
>
>
$ wget http://frontier.cern.ch/dist/frontier-squid-3.5.27-5.tar.gz $ tar -xvzf frontier-squid-3.5.27-5.tar.gz $ cd frontier-squid-3.5.27-5
  $ ./configure

Revision 342018-03-01 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallSquid"

Installing frontier-squid from source tarball

We recommend installing the frontier-squid package from the frontier-squid rpm, but if you want to use the source tarball, which is more portable, easily relocatable and can be run under any username, the instructions are below.
Line: 13 to 13
  Unpack and configure the current version of the tarball:

Changed:
<
<
$ wget http://frontier.cern.ch/dist/frontier-squid-3.5.27-3.tar.gz $ tar -xvzf frontier-squid-3.5.27-3.tar.gz $ cd frontier-squid-3.5.27-3
>
>
$ wget http://frontier.cern.ch/dist/frontier-squid-3.5.27-4.tar.gz $ tar -xvzf frontier-squid-3.5.27-4.tar.gz $ cd frontier-squid-3.5.27-4
  $ ./configure

Revision 332018-01-25 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallSquid"

Installing frontier-squid from source tarball

We recommend installing the frontier-squid package from the frontier-squid rpm, but if you want to use the source tarball, which is more portable, easily relocatable and can be run under any username, the instructions are below.
Line: 13 to 13
  Unpack and configure the current version of the tarball:

Changed:
<
<
$ wget http://frontier.cern.ch/dist/frontier-squid-3.5.27-2.tar.gz $ tar -xvzf frontier-squid-3.5.27-2.tar.gz $ cd frontier-squid-3.5.27-2
>
>
$ wget http://frontier.cern.ch/dist/frontier-squid-3.5.27-3.tar.gz $ tar -xvzf frontier-squid-3.5.27-3.tar.gz $ cd frontier-squid-3.5.27-3
  $ ./configure

Revision 322017-12-08 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallSquid"

Installing frontier-squid from source tarball

We recommend installing the frontier-squid package from the frontier-squid rpm, but if you want to use the source tarball, which is more portable, easily relocatable and can be run under any username, the instructions are below.
Line: 13 to 13
  Unpack and configure the current version of the tarball:

Changed:
<
<
$ wget http://frontier.cern.ch/dist/frontier-squid-3.5.27-1.tar.gz $ tar -xvzf frontier-squid-3.5.27-1.tar.gz $ cd frontier-squid-3.5.27-1
>
>
$ wget http://frontier.cern.ch/dist/frontier-squid-3.5.27-2.tar.gz $ tar -xvzf frontier-squid-3.5.27-2.tar.gz $ cd frontier-squid-3.5.27-2
  $ ./configure

Revision 312017-09-01 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallSquid"

Installing frontier-squid from source tarball

We recommend installing the frontier-squid package from the frontier-squid rpm, but if you want to use the source tarball, which is more portable, easily relocatable and can be run under any username, the instructions are below.
Line: 13 to 13
  Unpack and configure the current version of the tarball:

Changed:
<
<
$ wget http://frontier.cern.ch/dist/frontier-squid-3.5.24-3.tar.gz $ tar -xvzf frontier-squid-3.5.24-3.tar.gz $ cd frontier-squid-3.5.24-3
>
>
$ wget http://frontier.cern.ch/dist/frontier-squid-3.5.27-1.tar.gz $ tar -xvzf frontier-squid-3.5.27-1.tar.gz $ cd frontier-squid-3.5.27-1
  $ ./configure

Revision 302017-03-22 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallSquid"

Installing frontier-squid from source tarball

We recommend installing the frontier-squid package from the frontier-squid rpm, but if you want to use the source tarball, which is more portable, easily relocatable and can be run under any username, the instructions are below.
Line: 13 to 13
  Unpack and configure the current version of the tarball:

Changed:
<
<
$ wget http://frontier.cern.ch/dist/frontier-squid-3.5.24-2.tar.gz $ tar -xvzf frontier-squid-3.5.24-2.tar.gz $ cd frontier-squid-3.5.24-2
>
>
$ wget http://frontier.cern.ch/dist/frontier-squid-3.5.24-3.tar.gz $ tar -xvzf frontier-squid-3.5.24-3.tar.gz $ cd frontier-squid-3.5.24-3
  $ ./configure

Revision 292017-03-17 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallSquid"

Installing frontier-squid from source tarball

We recommend installing the frontier-squid package from the frontier-squid rpm, but if you want to use the source tarball, which is more portable, easily relocatable and can be run under any username, the instructions are below.
Line: 13 to 13
  Unpack and configure the current version of the tarball:

Changed:
<
<
$ wget http://frontier.cern.ch/dist/frontier-squid-3.5.24-1.tar.gz $ tar -xvzf frontier-squid-3.5.24-1.tar.gz $ cd frontier-squid-3.5.24-1
>
>
$ wget http://frontier.cern.ch/dist/frontier-squid-3.5.24-2.tar.gz $ tar -xvzf frontier-squid-3.5.24-2.tar.gz $ cd frontier-squid-3.5.24-2
  $ ./configure

Revision 282017-01-31 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallSquid"

Installing frontier-squid from source tarball

We recommend installing the frontier-squid package from the frontier-squid rpm, but if you want to use the source tarball, which is more portable, easily relocatable and can be run under any username, the instructions are below.
Line: 13 to 13
  Unpack and configure the current version of the tarball:

Changed:
<
<
$ wget http://frontier.cern.ch/dist/frontier-squid-3.5.23-6.tar.gz $ tar -xvzf frontier-squid-3.5.23-6.tar.gz $ cd frontier-squid-3.5.23-6
>
>
$ wget http://frontier.cern.ch/dist/frontier-squid-3.5.24-1.tar.gz $ tar -xvzf frontier-squid-3.5.24-1.tar.gz $ cd frontier-squid-3.5.24-1
  $ ./configure

Revision 272017-01-26 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallSquid"

Installing frontier-squid from source tarball

We recommend installing the frontier-squid package from the frontier-squid rpm, but if you want to use the source tarball, which is more portable, easily relocatable and can be run under any username, the instructions are below.
Line: 13 to 13
  Unpack and configure the current version of the tarball:

Changed:
<
<
$ wget http://frontier.cern.ch/dist/frontier-squid-3.5.23-5.tar.gz $ tar -xvzf frontier-squid-3.5.23-5.tar.gz $ cd frontier-squid-3.5.23-5
>
>
$ wget http://frontier.cern.ch/dist/frontier-squid-3.5.23-6.tar.gz $ tar -xvzf frontier-squid-3.5.23-6.tar.gz $ cd frontier-squid-3.5.23-6
  $ ./configure

Revision 262017-01-25 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallSquid"

Installing frontier-squid from source tarball

We recommend installing the frontier-squid package from the frontier-squid rpm, but if you want to use the source tarball, which is more portable, easily relocatable and can be run under any username, the instructions are below.
Line: 13 to 13
  Unpack and configure the current version of the tarball:

Changed:
<
<
$ wget http://frontier.cern.ch/dist/frontier-squid-3.5.23-4.tar.gz $ tar -xvzf frontier-squid-3.5.23-4.tar.gz $ cd frontier-squid-3.5.23-4
>
>
$ wget http://frontier.cern.ch/dist/frontier-squid-3.5.23-5.tar.gz $ tar -xvzf frontier-squid-3.5.23-5.tar.gz $ cd frontier-squid-3.5.23-5
  $ ./configure

Revision 252017-01-13 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallSquid"

Installing frontier-squid from source tarball

We recommend installing the frontier-squid package from the frontier-squid rpm, but if you want to use the source tarball, which is more portable, easily relocatable and can be run under any username, the instructions are below.
Line: 13 to 13
  Unpack and configure the current version of the tarball:

Changed:
<
<
$ wget http://frontier.cern.ch/dist/frontier-squid-3.5.23-3.tar.gz $ tar -xvzf frontier-squid-3.5.23-3.tar.gz $ cd frontier-squid-3.5.23-3
>
>
$ wget http://frontier.cern.ch/dist/frontier-squid-3.5.23-4.tar.gz $ tar -xvzf frontier-squid-3.5.23-4.tar.gz $ cd frontier-squid-3.5.23-4
  $ ./configure

Revision 242016-12-27 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallSquid"

Installing frontier-squid from source tarball

We recommend installing the frontier-squid package from the frontier-squid rpm, but if you want to use the source tarball, which is more portable, easily relocatable and can be run under any username, the instructions are below.
Line: 13 to 13
  Unpack and configure the current version of the tarball:

Changed:
<
<
$ wget http://frontier.cern.ch/dist/frontier-squid-3.5.23-2.tar.gz $ tar -xvzf frontier-squid-3.5.23-2.tar.gz $ cd frontier-squid-3.5.23-2
>
>
$ wget http://frontier.cern.ch/dist/frontier-squid-3.5.23-3.tar.gz $ tar -xvzf frontier-squid-3.5.23-3.tar.gz $ cd frontier-squid-3.5.23-3
  $ ./configure

Revision 232016-12-20 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallSquid"

Installing frontier-squid from source tarball

We recommend installing the frontier-squid package from the frontier-squid rpm, but if you want to use the source tarball, which is more portable, easily relocatable and can be run under any username, the instructions are below.
Line: 13 to 13
  Unpack and configure the current version of the tarball:

Changed:
<
<
$ wget http://frontier.cern.ch/dist/frontier-squid-3.5.22-2.tar.gz $ tar -xvzf frontier-squid-3.5.22-2.tar.gz $ cd frontier-squid-3.5.22-2
>
>
$ wget http://frontier.cern.ch/dist/frontier-squid-3.5.23-2.tar.gz $ tar -xvzf frontier-squid-3.5.23-2.tar.gz $ cd frontier-squid-3.5.23-2
  $ ./configure

Revision 222016-12-20 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallSquid"

Installing frontier-squid from source tarball

We recommend installing the frontier-squid package from the frontier-squid rpm, but if you want to use the source tarball, which is more portable, easily relocatable and can be run under any username, the instructions are below.
Line: 13 to 13
  Unpack and configure the current version of the tarball:

Changed:
<
<
$ wget http://frontier.cern.ch/dist/frontier-squid-3.5.23-1.tar.gz $ tar -xvzf frontier-squid-3.5.23-1.tar.gz $ cd frontier-squid-3.5.23-1
>
>
$ wget http://frontier.cern.ch/dist/frontier-squid-3.5.22-2.tar.gz $ tar -xvzf frontier-squid-3.5.22-2.tar.gz $ cd frontier-squid-3.5.22-2
  $ ./configure

Revision 212016-12-19 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallSquid"

Installing frontier-squid from source tarball

We recommend installing the frontier-squid package from the frontier-squid rpm, but if you want to use the source tarball, which is more portable, easily relocatable and can be run under any username, the instructions are below.
Line: 13 to 13
  Unpack and configure the current version of the tarball:

Changed:
<
<
$ wget http://frontier.cern.ch/dist/frontier-squid-3.5.22-2.tar.gz $ tar -xvzf frontier-squid-3.5.22-2.tar.gz $ cd frontier-squid-3.5.22-2
>
>
$ wget http://frontier.cern.ch/dist/frontier-squid-3.5.23-1.tar.gz $ tar -xvzf frontier-squid-3.5.23-1.tar.gz $ cd frontier-squid-3.5.23-1
  $ ./configure
Line: 27 to 27
  Examples: 131.154.184.0/255.255.255.0 or 131.154.0.0/255.255.0.0
Changed:
<
<
The script does allow to specify many subnets - just separate them by a blank. If you just hit enter, the standard private network addresses 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 will be allowed. NOTE: The default behavior is to allow any IP address you specify here to use the squid to cache objects coming from any destination address. If you would like a more restrictive policy or other options please see the rpm instructions for restricting the destination.
>
>
The script does allow to specify many subnets - just separate them by a blank. Include IPv6 address ranges if you plan to support IPv6 addresses. If you just hit enter, the standard private network addresses 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16, fc00::/7, and fe80::/10 will be allowed. NOTE: The default behavior is to allow any IP address you specify here to use the squid to cache objects coming from any destination address. If you would like a more restrictive policy or other options please see the rpm instructions for restricting the destination.
  On prompt enter the amount of cache memory (in MB) the squid should use. This should be at most 1/8 of your hardware memory. 128 MB should be fine, leaving a lot of memory for disk buffering by the OS, because squid performs better for large objects in disk cache buffers than in its own internal memory cache.

Revision 202016-11-08 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallSquid"

Installing frontier-squid from source tarball

We recommend installing the frontier-squid package from the frontier-squid rpm, but if you want to use the source tarball, which is more portable, easily relocatable and can be run under any username, the instructions are below.
Line: 13 to 13
  Unpack and configure the current version of the tarball:

Changed:
<
<
$ wget http://frontier.cern.ch/dist/frontier-squid-2.7.STABLE9-27.tar.gz $ tar -xvzf frontier-squid-2.7.STABLE9-27.tar.gz $ cd frontier-squid-2.7.STABLE9-27
>
>
$ wget http://frontier.cern.ch/dist/frontier-squid-3.5.22-2.tar.gz $ tar -xvzf frontier-squid-3.5.22-2.tar.gz $ cd frontier-squid-3.5.22-2
  $ ./configure
Line: 169 to 169
 

Responsible: DaveDykstra \ No newline at end of file

Added:
>
>
META TOPICMOVED by="dwd" date="1478628937" from="Frontier.InstallSquidTarball" to="Frontier.OldInstallSquidTarball"

Revision 192016-08-31 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallSquid"

Installing frontier-squid from source tarball

We recommend installing the frontier-squid package from the frontier-squid rpm, but if you want to use the source tarball, which is more portable, easily relocatable and can be run under any username, the instructions are below.
Line: 13 to 13
  Unpack and configure the current version of the tarball:

Changed:
<
<
$ wget http://frontier.cern.ch/dist/frontier-squid-2.7.STABLE9-26.tar.gz $ tar -xvzf frontier-squid-2.7.STABLE9-26.tar.gz $ cd frontier-squid-2.7.STABLE9-26
>
>
$ wget http://frontier.cern.ch/dist/frontier-squid-2.7.STABLE9-27.tar.gz $ tar -xvzf frontier-squid-2.7.STABLE9-27.tar.gz $ cd frontier-squid-2.7.STABLE9-27
  $ ./configure

Revision 182016-06-16 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallSquid"

Installing frontier-squid from source tarball

We recommend installing the frontier-squid package from the frontier-squid rpm, but if you want to use the source tarball, which is more portable, easily relocatable and can be run under any username, the instructions are below.
Line: 13 to 13
  Unpack and configure the current version of the tarball:

Changed:
<
<
$ wget http://frontier.cern.ch/dist/frontier-squid-2.7.STABLE9-25.tar.gz $ tar -xvzf frontier-squid-2.7.STABLE9-25.tar.gz $ cd frontier-squid-2.7.STABLE9-25
>
>
$ wget http://frontier.cern.ch/dist/frontier-squid-2.7.STABLE9-26.tar.gz $ tar -xvzf frontier-squid-2.7.STABLE9-26.tar.gz $ cd frontier-squid-2.7.STABLE9-26
  $ ./configure

Revision 172016-05-12 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallSquid"

Installing frontier-squid from source tarball

We recommend installing the frontier-squid package from the frontier-squid rpm, but if you want to use the source tarball, which is more portable, easily relocatable and can be run under any username, the instructions are below.
Line: 13 to 13
  Unpack and configure the current version of the tarball:

Changed:
<
<
$ wget http://frontier.cern.ch/dist/frontier-squid-2.7.STABLE9-24.tar.gz $ tar -xvzf frontier-squid-2.7.STABLE9-24.tar.gz $ cd frontier-squid-2.7.STABLE9-24
>
>
$ wget http://frontier.cern.ch/dist/frontier-squid-2.7.STABLE9-25.tar.gz $ tar -xvzf frontier-squid-2.7.STABLE9-25.tar.gz $ cd frontier-squid-2.7.STABLE9-25
  $ ./configure

Revision 162015-06-03 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallSquid"

Installing frontier-squid from source tarball

We recommend installing the frontier-squid package from the frontier-squid rpm, but if you want to use the source tarball, which is more portable, easily relocatable and can be run under any username, the instructions are below.
Line: 13 to 13
  Unpack and configure the current version of the tarball:

Changed:
<
<
$ wget http://frontier.cern.ch/dist/frontier-squid-2.7.STABLE9-23.tar.gz $ tar -xvzf frontier-squid-2.7.STABLE9-23.tar.gz $ cd frontier-squid-2.7.STABLE9-23
>
>
$ wget http://frontier.cern.ch/dist/frontier-squid-2.7.STABLE9-24.tar.gz $ tar -xvzf frontier-squid-2.7.STABLE9-24.tar.gz $ cd frontier-squid-2.7.STABLE9-24
  $ ./configure

Revision 152015-04-22 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallSquid"

Installing frontier-squid from source tarball

We recommend installing the frontier-squid package from the frontier-squid rpm, but if you want to use the source tarball, which is more portable, easily relocatable and can be run under any username, the instructions are below.
Line: 13 to 13
  Unpack and configure the current version of the tarball:

Changed:
<
<
$ wget http://frontier.cern.ch/dist/frontier-squid-2.7.STABLE9-22.tar.gz $ tar -xvzf frontier-squid-2.7.STABLE9-22.tar.gz $ cd frontier-squid-2.7.STABLE9-22
>
>
$ wget http://frontier.cern.ch/dist/frontier-squid-2.7.STABLE9-23.tar.gz $ tar -xvzf frontier-squid-2.7.STABLE9-23.tar.gz $ cd frontier-squid-2.7.STABLE9-23
  $ ./configure

Revision 142015-01-30 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallSquid"

Installing frontier-squid from source tarball

We recommend installing the frontier-squid package from the frontier-squid rpm, but if you want to use the source tarball, which is more portable, easily relocatable and can be run under any username, the instructions are below.
Line: 13 to 13
  Unpack and configure the current version of the tarball:

Changed:
<
<
$ wget http://frontier.cern.ch/dist/frontier-squid-2.7.STABLE9-21.tar.gz $ tar -xvzf frontier-squid-2.7.STABLE9-21.tar.gz $ cd frontier-squid-2.7.STABLE9-21
>
>
$ wget http://frontier.cern.ch/dist/frontier-squid-2.7.STABLE9-22.tar.gz $ tar -xvzf frontier-squid-2.7.STABLE9-22.tar.gz $ cd frontier-squid-2.7.STABLE9-22
  $ ./configure

Revision 132014-12-03 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallSquid"

Installing frontier-squid from source tarball

We recommend installing the frontier-squid package from the frontier-squid rpm, but if you want to use the source tarball, which is more portable, easily relocatable and can be run under any username, the instructions are below.
Line: 13 to 13
  Unpack and configure the current version of the tarball:

Changed:
<
<
$ wget http://frontier.cern.ch/dist/frontier-squid-2.7.STABLE9-20.tar.gz $ tar -xvzf frontier-squid-2.7.STABLE9-20.tar.gz $ cd frontier-squid-2.7.STABLE9-20
>
>
$ wget http://frontier.cern.ch/dist/frontier-squid-2.7.STABLE9-21.tar.gz $ tar -xvzf frontier-squid-2.7.STABLE9-21.tar.gz $ cd frontier-squid-2.7.STABLE9-21
  $ ./configure

Revision 122014-11-06 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallSquid"

Installing frontier-squid from source tarball

We recommend installing the frontier-squid package from the frontier-squid rpm, but if you want to use the source tarball, which is more portable, easily relocatable and can be run under any username, the instructions are below.
Line: 13 to 13
  Unpack and configure the current version of the tarball:

Changed:
<
<
$ wget http://frontier.cern.ch/dist/frontier-squid-2.7.STABLE9-19.tar.gz $ tar -xvzf frontier-squid-2.7.STABLE9-19.tar.gz $ cd frontier-squid-2.7.STABLE9-19
>
>
$ wget http://frontier.cern.ch/dist/frontier-squid-2.7.STABLE9-20.tar.gz $ tar -xvzf frontier-squid-2.7.STABLE9-20.tar.gz $ cd frontier-squid-2.7.STABLE9-20
  $ ./configure

Revision 112014-09-15 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallSquid"

Installing frontier-squid from source tarball

We recommend installing the frontier-squid package from the frontier-squid rpm, but if you want to use the source tarball, which is more portable, easily relocatable and can be run under any username, the instructions are below.
Line: 13 to 13
  Unpack and configure the current version of the tarball:

Changed:
<
<
$ wget http://frontier.cern.ch/dist/frontier-squid-2.7.STABLE9-16.tar.gz $ tar -xvzf frontier-squid-2.7.STABLE9-16.tar.gz $ cd frontier-squid-2.7.STABLE9-16
>
>
$ wget http://frontier.cern.ch/dist/frontier-squid-2.7.STABLE9-19.tar.gz $ tar -xvzf frontier-squid-2.7.STABLE9-19.tar.gz $ cd frontier-squid-2.7.STABLE9-19
  $ ./configure
Line: 78 to 78
 
    7 7 * * * /install_dir/frontier-cache/utils/cron/daily.sh </dev/null 2<&1
Changed:
<
<
8 * * * * /install_dir/frontier-cache/utils/cron/hourly.sh </dev/null 2<&1
>
>
8,23,38,53 * * * * /install_dir/frontier-cache/utils/cron/hourly.sh </dev/null 2<&1
 

You could get the above crontab by doing (with the appropriate value of install_dir)

Line: 87 to 87
  $ crontab /install_dir/frontier-cache/utils/cron/crontab.dat
Changed:
<
<
You can change the hour and minute as you like, but leave hourly.sh to be one minute after daily.sh, and avoid multiples of 5 for the minute because it can interfere with the monitoring probes which happen every 5 minutes. The hourly.sh script will rotate the logs if access.log goes over a given size, default 1GB. You can change that value by setting the environment variable LARGE_ACCESS_LOG to a different number of bytes. For example for 10GB you can use:
>
>
You can change the hour and minutes as you like, but leave the first hourly.sh to be one minute after daily.sh, and avoid multiples of 5 for the minute because it can interfere with the monitoring probes which happen every 5 minutes. The hourly.sh script will rotate the logs if access.log goes over a given size, default 5GB when compression is used (which is the default) or 1GB when compression is not used. You can change that value by setting the environment variable SQUID_MAX_ACCESS_LOG to a different number of bytes. You can also append an M for megabytes or G for gigabytes. For example for 20GB you can use:
 
Changed:
<
<
8 * * * * LARGE_ACCESS_LOG=10000000000 /install_dir/frontier-cache/utils/cron/hourly.sh </dev/null 2>&1
>
>
8,23,38,53 * * * * SQUID_MAX_ACCESS_LOG=20G /install_dir/frontier-cache/utils/cron/hourly.sh </dev/null 2>&1
 
Changed:
<
<
In order to estimate disk usage, note that up to 11 access.log files are kept at a time, and the size can go a bit above the $LARGE_ACCESS_LOG size because the cron job only checks once per hour. If disk space for the logs is a concern see the section on the Access log growth issue below.
>
>
To help with choosing the max log size, see the corresponding rpm instructions, except that if you choose to disable compression you can set SQUID_COMPRESS_LOGS=false in the cron command line. If disk space for the logs is a concern see the section on the Access log growth issue below.
 

As root, set up start at boot time

Revision 102013-05-10 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallSquid"

Installing frontier-squid from source tarball

We recommend installing the frontier-squid package from the frontier-squid rpm, but if you want to use the source tarball, which is more portable, easily relocatable and can be run under any username, the instructions are below.
Line: 13 to 13
  Unpack and configure the current version of the tarball:

Changed:
<
<
$ wget http://frontier.cern.ch/dist/frontier-squid-2.7.STABLE9-15.tar.gz $ tar -xvzf frontier-squid-2.7.STABLE9-15.tar.gz $ cd frontier-squid-2.7.STABLE9-15
>
>
$ wget http://frontier.cern.ch/dist/frontier-squid-2.7.STABLE9-16.tar.gz $ tar -xvzf frontier-squid-2.7.STABLE9-16.tar.gz $ cd frontier-squid-2.7.STABLE9-16
  $ ./configure

Revision 92013-05-08 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallSquid"

Installing frontier-squid from source tarball

We recommend installing the frontier-squid package from the frontier-squid rpm, but if you want to use the source tarball, which is more portable, easily relocatable and can be run under any username, the instructions are below.
Line: 13 to 13
  Unpack and configure the current version of the tarball:

Changed:
<
<
$ wget http://frontier.cern.ch/dist/frontier-squid-2.7.STABLE9-14.tar.gz $ tar -xvzf frontier-squid-2.7.STABLE9-14.tar.gz $ cd frontier-squid-2.7.STABLE9-14
>
>
$ wget http://frontier.cern.ch/dist/frontier-squid-2.7.STABLE9-15.tar.gz $ tar -xvzf frontier-squid-2.7.STABLE9-15.tar.gz $ cd frontier-squid-2.7.STABLE9-15
  $ ./configure

Revision 82013-03-30 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallSquid"

Installing frontier-squid from source tarball

We recommend installing the frontier-squid package from the frontier-squid rpm, but if you want to use the source tarball, which is more portable, easily relocatable and can be run under any username, the instructions are below.
Line: 13 to 13
  Unpack and configure the current version of the tarball:

Changed:
<
<
$ wget http://frontier.cern.ch/dist/frontier-squid-2.7.STABLE9-13.tar.gz $ tar -xvzf frontier-squid-2.7.STABLE9-13.tar.gz $ cd frontier-squid-2.7.STABLE9-13
>
>
$ wget http://frontier.cern.ch/dist/frontier-squid-2.7.STABLE9-14.tar.gz $ tar -xvzf frontier-squid-2.7.STABLE9-14.tar.gz $ cd frontier-squid-2.7.STABLE9-14
  $ ./configure

Revision 72013-01-28 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallSquid"

Installing frontier-squid from source tarball

We recommend installing the frontier-squid package from the frontier-squid rpm, but if you want to use the source tarball, which is more portable, easily relocatable and can be run under any username, the instructions are below.
Line: 13 to 13
  Unpack and configure the current version of the tarball:

Changed:
<
<
$ wget http://frontier.cern.ch/dist/frontier-squid-2.7.STABLE9-12.tar.gz $ tar -xvzf frontier-squid-2.7.STABLE9-12.tar.gz $ cd frontier-squid-2.7.STABLE9-12
>
>
$ wget http://frontier.cern.ch/dist/frontier-squid-2.7.STABLE9-13.tar.gz $ tar -xvzf frontier-squid-2.7.STABLE9-13.tar.gz $ cd frontier-squid-2.7.STABLE9-13
  $ ./configure

Revision 62013-01-25 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallSquid"

Installing frontier-squid from source tarball

We recommend installing the frontier-squid package from the frontier-squid rpm, but if you want to use the source tarball, which is more portable, easily relocatable and can be run under any username, the instructions are below.
Line: 13 to 13
  Unpack and configure the current version of the tarball:

Changed:
<
<
$ wget http://frontier.cern.ch/dist/frontier-squid-2.7.STABLE9-11.tar.gz $ tar -xvzf frontier-squid-2.7.STABLE9-11.tar.gz $ cd frontier-squid-2.7.STABLE9-11
>
>
$ wget http://frontier.cern.ch/dist/frontier-squid-2.7.STABLE9-12.tar.gz $ tar -xvzf frontier-squid-2.7.STABLE9-12.tar.gz $ cd frontier-squid-2.7.STABLE9-12
  $ ./configure

Revision 52013-01-11 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallSquid"

Installing frontier-squid from source tarball

We recommend installing the frontier-squid package from the frontier-squid rpm, but if you want to use the source tarball, which is more portable, easily relocatable and can be run under any username, the instructions are below.
Line: 13 to 13
  Unpack and configure the current version of the tarball:

Changed:
<
<
$ wget http://frontier.cern.ch/dist/frontier-squid-2.7.STABLE9-10.tar.gz $ tar -xvzf frontier-squid-2.7.STABLE9-10.tar.gz $ cd frontier-squid-2.7.STABLE9-10
>
>
$ wget http://frontier.cern.ch/dist/frontier-squid-2.7.STABLE9-11.tar.gz $ tar -xvzf frontier-squid-2.7.STABLE9-11.tar.gz $ cd frontier-squid-2.7.STABLE9-11
  $ ./configure

Revision 42012-12-26 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallSquid"

Installing frontier-squid from source tarball

We recommend installing the frontier-squid package from the frontier-squid rpm, but if you want to use the source tarball, which is more portable, easily relocatable and can be run under any username, the instructions are below.
Added:
>
>
See the frontier-squid tarball release notes for information on what has changed in each release.
 Here is what is on this page:

Revision 32012-12-20 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallSquid"

Installing frontier-squid from source tarball

We recommend installing the frontier-squid package from the frontier-squid rpm, but if you want to use the source tarball, which is more portable, easily relocatable and can be run under any username, the instructions are below.
Line: 12 to 12
  Unpack and configure the current version of the tarball:

Changed:
<
<
$ wget http://frontier.cern.ch/dist/frontier-squid-2.7.STABLE9-9.tar.gz $ tar -xvzf frontier-squid-2.7.STABLE9-9.tar.gz $ cd frontier-squid-2.7.STABLE9-9
>
>
$ wget http://frontier.cern.ch/dist/frontier-squid-2.7.STABLE9-10.tar.gz $ tar -xvzf frontier-squid-2.7.STABLE9-10.tar.gz $ cd frontier-squid-2.7.STABLE9-10
  $ ./configure

Revision 22012-11-01 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallSquid"
Deleted:
<
<
THIS PAGE IS UNDER CONSTRUCTION
 

Installing frontier-squid from source tarball

Changed:
<
<
We recommend to installing the frontier-squid package from the frontier-squid rpm, but if you want to use the source tarball, which is easily relocatable and can be run under any user id, the instructions are below.

Download and Install Software

The second step is to create an account with username dbfrontier on your hardware. (If for some reason, you can't use the username dbfrontier, any username will work.) Then as user dbfrontier (NOT root) download a tarball into this account. The current version is:

http://frontier.cern.ch/dist/frontier-squid-2.7.STABLE9-9.tar.gz

>
>
We recommend installing the frontier-squid package from the frontier-squid rpm, but if you want to use the source tarball, which is more portable, easily relocatable and can be run under any username, the instructions are below.
 
Changed:
<
<
Unpack the tarball:
>
>
Here is what is on this page:
 
Changed:
<
<
tar -xvzf frontier-squid-2.7.STABLE9-9.tar.gz
>
>

Download and install software

 
Changed:
<
<
cd frontier-squid-2.7.STABLE9-9
>
>
First, create an account with username dbfrontier on your machine. (If for some reason, you can't use the username dbfrontier, any username will work.) Then as user dbfrontier (NOT root) download a tarball into this account.
 
Changed:
<
<
./configure
>
>
Unpack and configure the current version of the tarball:
    $ wget http://frontier.cern.ch/dist/frontier-squid-2.7.STABLE9-9.tar.gz
    $ tar -xvzf frontier-squid-2.7.STABLE9-9.tar.gz
    $ cd frontier-squid-2.7.STABLE9-9
    $ ./configure
 
Changed:
<
<
On prompt enter the directory name where the Squid will be installed. This directory holds the working software, cache, and logs so there should be at least 100 GB available (unless you relocate the cache and logs as described below). This directory is called "/install_dir" below. It should be on a local disk of the computer you are using and not NFS or AFS mounted. Note that the directory you enter should be an absolute (fully qualified) directory name and not a relative one. You may either re-use a previous install directory or create a new one for each release. Creating a new directory for each release makes it easier to back out to a previous release and ensures a clean installation, but it requires a little extra work to set up (described below).
>
>
On prompt enter the directory name where the Squid will be installed. This directory holds the working software, cache, and logs so there should be plenty of space available (unless you relocate the cache and logs as described below). This directory is called "/install_dir" below. It should be on a local disk of the computer you are using and not NFS or AFS mounted. Note that the directory you enter should be an absolute (fully qualified) directory name and not a relative one. You may either re-use a previous install directory or create a new one for each release. Creating a new directory for each release makes it easier to back out to a previous release and ensures a clean installation, but it requires a little extra work to set up (described below).
  If the directory you are installing into does not yet contain customize.sh, you will also be prompted for the old installation path. If customize.sh is found in the old installation path, it will be copied into the source directory and the configure step will be finished. If you like, you can avoid the first two questions by passing "--prefix=/install_dir" and "--oldprefix=/oldinstall_dir" parameters to ./configure. If you have not previously installed a release that supports customize.sh, you will be asked a few additional questions about basic configuration parameters.
Line: 27 to 26
  Examples: 131.154.184.0/255.255.255.0 or 131.154.0.0/255.255.0.0
Changed:
<
<
The script does allow to specify many subnets - just separate them by a blank. If you just hit enter, the standard private network addresses 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 will be allowed. NOTE: The default behavior is to allow any IP address you specify here to use the squid to cache objects coming from any destination address. If you would like a more restrictive policy or other options please see the section below on other ACL options.
>
>
The script does allow to specify many subnets - just separate them by a blank. If you just hit enter, the standard private network addresses 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 will be allowed. NOTE: The default behavior is to allow any IP address you specify here to use the squid to cache objects coming from any destination address. If you would like a more restrictive policy or other options please see the rpm instructions for restricting the destination.
 
Changed:
<
<
On prompt enter the amount of cache memory (in MB) the squid should use. This should be at most 1/8 of your hardware memory. Probably 128 MB would be fine, leaving a lot of memory for disk buffering by the OS because squid performs better for large objects out of the disk cache than the memory cache.
>
>
On prompt enter the amount of cache memory (in MB) the squid should use. This should be at most 1/8 of your hardware memory. 128 MB should be fine, leaving a lot of memory for disk buffering by the OS, because squid performs better for large objects in disk cache buffers than in its own internal memory cache.
 
Changed:
<
<
On prompt enter the amount of disk space (in MB) the squid should use for a cache. One suggestion is to set this size at 70% of the available space in your disk partition to allow room for the executables, log files, etc. It should be at least 20000.
>
>
On prompt enter the amount of disk space (in MB) the squid should use for a cache. One suggestion is to set this size at 70% of the available space in your disk partition to allow room for the executables, log files, etc. It should be at least 20000, but there's no need to make it more than 100000.
  You can double check your responses to the prompts by reading Makefile.conf.inc and edit them there before running make if you wish.

Then do:

Added:
>
>
    $ make
    $ make install
 
Changed:
<
<
make
>
>
After that you should examine /install_dir/frontier-cache/squid/etc/customize.sh and make any changes or other customizations you want to. Comments in the default installation of customize.sh give more details on what can be done with it.
 
Changed:
<
<
make install

After that you should examine /install_dir/frontier-cache/squid/etc/customize.sh and make any changes or other customizations you want to. For details on the editing functions available see /install_dir/frontier-cache/squid/etc/customhelps.awk.

Manual Control of the Server

>
>

Manual control of the server

  To do a manual start/stop of the server (as user dbfrontier):
Changed:
<
<
/install_dir/frontier-cache/utils/bin/fn-local-squid.sh start
>
>
    $ /install_dir/frontier-cache/utils/bin/fn-local-squid.sh start
  You can also stop it if you need to:
Changed:
<
<
/install_dir/frontier-cache/utils/bin/fn-local-squid.sh stop
>
>
    $ /install_dir/frontier-cache/utils/bin/fn-local-squid.sh stop
  Remember to start your server after you have installed it.
Line: 60 to 62
 If you choose to use a different install directory for each release, do the following extra things:

  • Create a symbolic link at a place you will re-use for each new installation, and use that for the cron job described in the next section and in /etc/init.d/frontier-squid.sh described in the following two sections, so those don't need to be reinstalled for every release.
Changed:
<
<
  • Either remember to clean out the old installation's disk cache (in /install_dir/frontier-cache/squid/var/cache) and logs (in /install_dir/frontier-cache/squid/var/logs) each time or (better) edit customize.sh to set the cache_log, pid_filename, and coredump_dir options and the second parameter of the cache_dir option and the first parameter of the access_log option to use common directories that you re-use for each new installation. This has an added advantage of not requiring a lot of disk space where you install the software but rather where you choose to put the cache and logs. For example:
>
>
  • Either remember to clean out the old installation's disk cache (in /install_dir/frontier-cache/squid/var/cache) and logs (in /install_dir/frontier-cache/squid/var/logs) each time or (better) edit customize.sh to set the cache_log, pid_filename, and coredump_dir options and the second parameter of the cache_dir option and the first parameter of the access_log option to use common directories that you re-use for each new installation. This has an added advantage of not requiring a lot of disk space where you install the software but rather where you choose to put the cache and logs. For example:

  setoptionparameter("cache_dir", 2, "/data/squid_cache") setoptionparameter("access_log", 1, "/data/squid_logs/access.log") setoption("cache_log", "/data/squid_logs/cache.log") setoption("pid_filename", "/data/squid_logs/squid.pid") setoption("coredump_dir", "/data/squid_cache")
Changed:
<
<
>
>
 
Changed:
<
<

Set Up Cron Job

>
>

Set up cron jobs

  As user dbfrontier, set up cron jobs to rotate the logs, with crontab entries like this:
Changed:
<
<
7 7 * * * /install_dir/frontier-cache/utils/cron/daily.sh >/dev/null 2>&1
8 * * * * /install_dir/frontier-cache/utils/cron/hourly.sh >/dev/null 2>&1
>
>
    7 7 * * * /install_dir/frontier-cache/utils/cron/daily.sh </dev/null 2<&1
    8 * * * * /install_dir/frontier-cache/utils/cron/hourly.sh </dev/null 2<&1
  You could get the above crontab by doing (with the appropriate value of install_dir)
Changed:
<
<
crontab /install_dir/frontier-cache/utils/cron/crontab.dat
>
>
    $ crontab /install_dir/frontier-cache/utils/cron/crontab.dat
  You can change the hour and minute as you like, but leave hourly.sh to be one minute after daily.sh, and avoid multiples of 5 for the minute because it can interfere with the monitoring probes which happen every 5 minutes. The hourly.sh script will rotate the logs if access.log goes over a given size, default 1GB. You can change that value by setting the environment variable LARGE_ACCESS_LOG to a different number of bytes. For example for 10GB you can use:
Deleted:
<
<
8 * * * * LARGE_ACCESS_LOG=10000000000 /install_dir/frontier-cache/utils/cron/hourly.sh >/dev/null 2>&1

In order to estimate disk usage, note that up to 11 access.log files are kept at a time, and the size can go a bit above the $LARGE_ACCESS_LOG size because the cron job only checks once per hour. If disk space for the logs is a concern see the section on the Access Log Growth Issue below.

As Root, Set Up Start at Boot Time

(This is the only step to be done as root.)

Then as root:

copy install_dir/frontier-cache/utils/init.d/frontier-squid.sh into /etc/init.d

Then after the copy, root should do:

/sbin/chkconfig --add frontier-squid.sh

Testing Your Installation

Download the following python script fnget.py (Do a right-click on the link and save the file as fnget.py )

Test access to the Frontier server at CERN with the following commands:

chmod +x fnget.py #(only first time)

./fnget.py --url=http://cmsfrontier.cern.ch:8000/Frontier/Frontier --sql="select 1 from dual"

This should be the response:

 
Changed:
<
<
Using Frontier URL: http://cmsfrontier.cern.ch:8000/Frontier/Frontier Query: select 1 from dual Decode results: 1 Refresh cache: 0

Frontier Request: http://cmsfrontier.cern.ch:8000/Frontier/Frontier?type=frontier_request:1:DEFAUL T&encoding=BLOBzip&p1=eNorTs1JTS5RMFRIK8rPVUgpTcwBAD0rBmw_

Query started: 05/12/09 13:46:50 EDT WARNING: no timeout available in python older than 2.4 Query ended: 05/12/09 13:46:50 EDT Query time: 0.64064002037 [seconds]

Query result: eJxjY2BgYDRkA5JsfqG+Tq5B7GxgEXYAGs0CVA== <quality error="0" md5="5544fd3e96013e694f13d2e13b44ee3c" records="1" full_si ze="25"/>

Fields: 1 NUMBER

Records: 1

>
>
8 * * * * LARGE_ACCESS_LOG=10000000000 /install_dir/frontier-cache/utils/cron/hourly.sh </dev/null 2>&1
 
Changed:
<
<
This will return whatever you type in the select statement, for example change 1 to 'hello'. The "dual" table is a special debugging feature of Oracle that just returns what you send it.

Now test your squid,

export http_proxy=http://your.squid.url:3128

>
>
In order to estimate disk usage, note that up to 11 access.log files are kept at a time, and the size can go a bit above the $LARGE_ACCESS_LOG size because the cron job only checks once per hour. If disk space for the logs is a concern see the section on the Access log growth issue below.
 
Changed:
<
<
and perform the test again. It should pass through your squid, and cache the response. To see if it worked, look at the squid access log (following excerpted form the access.log file usually in squid/var/logs :
>
>

As root, set up start at boot time

 
Changed:
<
<
128.220.233.179 - - [12/May/2009:08:33:17 +0000] "GET http://cmsfrontier.cern.ch
:8000/Frontier/Frontier?type=frontier_request:1:DEFAULT&encoding=BLOBzip&p1=eNor
Ts1JTS5RMFRIK8rPVUgpTcwBAD0rBmw= HTTP/1.0" 200 810 TCP_MISS:DIRECT 461 "fnget.py
 1.5"
128.220.233.179 - - [12/May/2009:08:33:19 +0000] "GET http://cmsfrontier.cern.ch
:8000/Frontier/Frontier?type=frontier_request:1:DEFAULT&encoding=BLOBzip&p1=eNor
Ts1JTS5RMFRIK8rPVUgpTcwBAD0rBmw= HTTP/1.0" 200 809 TCP_MEM_HIT:NONE - "fnget.py
1.5"
>
>
This is the only step to be done as root.
 
Changed:
<
<
Notice the second entry has a "TCP_MEM_HIT", that means the object was cached in the memory. Any subsequent requests for this object will come from the squid cache.
>
>
    # cp /install_dir/frontier-cache/utils/init.d/frontier-squid.sh /etc/init.d
    # /sbin/chkconfig --add frontier-squid.sh
 
Changed:
<
<
Another possibility for testing your squid is to run the SAM squid test on a worker node by hand.
>
>

Testing your installation

 
Added:
>
>
Do the same test as in rpm testing instructions.
 

Monitoring

Changed:
<
<
The functionality of your squid should be monitored from CERN and Fermilab using SNMP.

To enable this, your site should open port 3401/udp to requests from: 128.142.202.212/255.255.255.255 (or preferably cmsdbsfrontier.cern.ch if you can use a DNS name) and 131.225.240.232/255.255.255.255. The former is the main site, and the latter is a backup site at Fermilab.

The main monitoring site is at http://frontier.cern.ch/squidstats/.

SELinux

SELinux on RHEL 5 does not give the proper context to the default SNMP port (3401) (as of selinux-policy-2.4.6-106.el5) . The command (as root)

semanage port -a -t http_cache_port_t -p udp 3401

takes care of this problem.

>
>
Enable monitoring the same way as in the rpm monitoring instructions.
 

Some Useful Commands

Changed:
<
<
install_dir/frontier-cache/utils/bin/fn-local-squid.sh with any parameter or no parameter will recreate squid.conf after changing customize.sh
>
>
$ /install_dir/frontier-cache/utils/bin/fn-local-squid.sh with any parameter or no parameter will recreate squid.conf after changing customize.sh
 
Changed:
<
<
install_dir/frontier-cache/squid/sbin/squid -k parse will just read squid.conf to see if it makes sense
>
>
$ /install_dir/frontier-cache/squid/sbin/squid -k parse will just read squid.conf to see if it makes sense
 
Changed:
<
<
install_dir/frontier-cache/utils/bin/fn-local-squid.sh reload sends a HUP signal and has squid reread squid.conf
>
>
$ /install_dir/frontier-cache/utils/bin/fn-local-squid.sh reload sends a HUP signal and has squid reread squid.conf
 
Changed:
<
<
install_dir/frontier-cache/utils/bin/fn-local-squid.sh status checks if squid is running
>
>
$ /install_dir/frontier-cache/utils/bin/fn-local-squid.sh status checks if squid is running
 
Changed:
<
<
install_dir/frontier-cache/utils/bin/fn-local-squid.sh restart stops squid and starts squid without clearing the cache
>
>
$ /install_dir/frontier-cache/utils/bin/fn-local-squid.sh restart stops squid and starts squid without clearing the cache
 
Changed:
<
<
install_dir/frontier-cache/utils/bin/fn-local-squid.sh cleancache deletes and recreates the cache, like a start does, but without starting squid
>
>
$ /install_dir/frontier-cache/utils/bin/fn-local-squid.sh cleancache deletes and recreates the cache, like a start does, but without starting squid
 
Changed:
<
<
install_dir/frontier-cache/squid/bin/squidclient mgr:info outputs operational information about your squid
>
>
$ /install_dir/frontier-cache/squid/bin/squidclient mgr:info outputs operational information about your squid
 
Changed:
<
<

Access Log Growth Issue

>
>

Access log growth issue

  With many active clients, it is still possible for the squid access.log to grow to unmanageable size. The squid will crash if it runs out of available diskspace. There are a couple ways to avoid this problem:
Changed:
<
<
1) Make sure that you have the hourly.sh cron job enabled as described in the Set Up Cron Job section above to rotate the log when it grows over a size you choose.

2) The other possibility is to disable writing to access.log by putting the following in install_dir/frontier-cache/squid/etc/customize.sh:

setoption("access_log", "none")

>
>
1) Make sure that you have the hourly.sh cron job enabled as described in the Set up cron jobs section above to rotate the log when it grows over a size you choose.
 
Added:
>
>
2) The other possibility is to disable writing to access.log by putting the following in /install_dir/frontier-cache/squid/etc/customize.sh:
    setoption("access_log", "none")
 and then do
Changed:
<
<
install_dir/frontier-cache/utils/bin/fn-local-squid.sh reload to update squid.conf and load it if the squid is already running, otherwise just use start instead of reload.
>
>
    $ /install_dir/frontier-cache/utils/bin/fn-local-squid.sh reload
to update squid.conf and load it if the squid is already running, otherwise just use start instead of reload.
  The squid installation script has the access log turned on by default. It is recommended that a new installation be installed with it on, the functioning of the squid verified by reading the access log, then if disk space is limited, turn the access log off when the squid is in production. Even if you do turn the access log off, you should still run the daily.sh script once per day to rotate the other logs.
Line: 222 to 149
  At some installations with a very large number of worker nodes it may be possible to see error messages about running out of filedescriptors in your cache.log. It is easy to avoid this problem:
Changed:
<
<
1) First, make sure your squid version is at least squid-2.7.X

2) As root, add the following line to /etc/security/limits.conf

>
>
1) As root, add the following line to /etc/security/limits.conf

 * - nofile 16384
Changed:
<
<
>
>
 
Changed:
<
<
3) Reboot the machine.
>
>
2) Reboot the machine.
  You can check your file descriptor limit and usage by doing:
Changed:
<
<
install_dir/frontier-cache/squid/bin/squidclient mgr:info

Other ACL options

The default behavior is to allow the squid to be used for any destination. If you want to restrict the squid to be used only for CMS Conditions Data, then you simply have to add two lines to customize.sh that enable a couple of lines in squid.conf which are already there commented out:

 uncomment("acl RESTRICT_DEST")
 uncomment("http_access deny !RESTRICT_DEST")

If for some reason you want to have a different destination or destinations you can use a regular expression, for example:

 setoptionparameter("acl RESTRICT_DEST", 3, "^(cmsfrontier.*|cernvm.*)\\.cern\\.ch$")
 uncomment("http_access deny !RESTRICT_DEST")

Another possible configuration is to allow worker nodes at other sites to use your squid, although we discourage that because many worker nodes can use large amounts of bandwidth over the wide area network. If you still want to do it, it can be done by adding extra lines to your customize.sh. The order of these lines is important, so they need to be "anchored" to others, for example like this:

 insertline("acl NET_LOCAL", "acl T2FOO src x.x.x.x/x.x.x.x")
 insertline("acl NET_LOCAL", "acl T2BAR src x.x.x.x/x.x.x.x")
 insertline("http_access allow NET_LOCAL", "http_access allow T2FOO")
 insertline("http_access allow NET_LOCAL", "http_access allow T2BAR")

In addition, you have to make sure there are holes in any site or machine firewalls that allow these other worker nodes access to port 3128 on your squid.

Finally, the remote sites must make an appropriate addition to their site-local-config.xml.

If you modify customize.sh while the squid is running, remember to do a

>
>
    $ /install_dir/frontier-cache/squid/bin/squidclient mgr:info
 
Changed:
<
<
install_dir/frontier-cache/utils/bin/fn-local-squid.sh reload
>
>

Other issues

 
Changed:
<
<
so that the changes get used.
>
>
See also the rpm common issues which also apply to the tarball.
 

Responsible: DaveDykstra

Revision 12012-10-30 - DaveDykstra

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="InstallSquid"
THIS PAGE IS UNDER CONSTRUCTION

Installing frontier-squid from source tarball

We recommend to installing the frontier-squid package from the frontier-squid rpm, but if you want to use the source tarball, which is easily relocatable and can be run under any user id, the instructions are below.

Download and Install Software

The second step is to create an account with username dbfrontier on your hardware. (If for some reason, you can't use the username dbfrontier, any username will work.) Then as user dbfrontier (NOT root) download a tarball into this account. The current version is:

http://frontier.cern.ch/dist/frontier-squid-2.7.STABLE9-9.tar.gz

Unpack the tarball:

tar -xvzf frontier-squid-2.7.STABLE9-9.tar.gz

cd frontier-squid-2.7.STABLE9-9

./configure

On prompt enter the directory name where the Squid will be installed. This directory holds the working software, cache, and logs so there should be at least 100 GB available (unless you relocate the cache and logs as described below). This directory is called "/install_dir" below. It should be on a local disk of the computer you are using and not NFS or AFS mounted. Note that the directory you enter should be an absolute (fully qualified) directory name and not a relative one. You may either re-use a previous install directory or create a new one for each release. Creating a new directory for each release makes it easier to back out to a previous release and ensures a clean installation, but it requires a little extra work to set up (described below).

If the directory you are installing into does not yet contain customize.sh, you will also be prompted for the old installation path. If customize.sh is found in the old installation path, it will be copied into the source directory and the configure step will be finished. If you like, you can avoid the first two questions by passing "--prefix=/install_dir" and "--oldprefix=/oldinstall_dir" parameters to ./configure. If you have not previously installed a release that supports customize.sh, you will be asked a few additional questions about basic configuration parameters.

On prompt enter network/netmask which is allowed to access the Squid.

Examples: 131.154.184.0/255.255.255.0 or 131.154.0.0/255.255.0.0

The script does allow to specify many subnets - just separate them by a blank. If you just hit enter, the standard private network addresses 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 will be allowed. NOTE: The default behavior is to allow any IP address you specify here to use the squid to cache objects coming from any destination address. If you would like a more restrictive policy or other options please see the section below on other ACL options.

On prompt enter the amount of cache memory (in MB) the squid should use. This should be at most 1/8 of your hardware memory. Probably 128 MB would be fine, leaving a lot of memory for disk buffering by the OS because squid performs better for large objects out of the disk cache than the memory cache.

On prompt enter the amount of disk space (in MB) the squid should use for a cache. One suggestion is to set this size at 70% of the available space in your disk partition to allow room for the executables, log files, etc. It should be at least 20000.

You can double check your responses to the prompts by reading Makefile.conf.inc and edit them there before running make if you wish.

Then do:

make

make install

After that you should examine /install_dir/frontier-cache/squid/etc/customize.sh and make any changes or other customizations you want to. For details on the editing functions available see /install_dir/frontier-cache/squid/etc/customhelps.awk.

Manual Control of the Server

To do a manual start/stop of the server (as user dbfrontier):

/install_dir/frontier-cache/utils/bin/fn-local-squid.sh start

You can also stop it if you need to:

/install_dir/frontier-cache/utils/bin/fn-local-squid.sh stop

Remember to start your server after you have installed it.

Setup for different install directories with each release

If you choose to use a different install directory for each release, do the following extra things:

  • Create a symbolic link at a place you will re-use for each new installation, and use that for the cron job described in the next section and in /etc/init.d/frontier-squid.sh described in the following two sections, so those don't need to be reinstalled for every release.
  • Either remember to clean out the old installation's disk cache (in /install_dir/frontier-cache/squid/var/cache) and logs (in /install_dir/frontier-cache/squid/var/logs) each time or (better) edit customize.sh to set the cache_log, pid_filename, and coredump_dir options and the second parameter of the cache_dir option and the first parameter of the access_log option to use common directories that you re-use for each new installation. This has an added advantage of not requiring a lot of disk space where you install the software but rather where you choose to put the cache and logs. For example:
      setoptionparameter("cache_dir", 2, "/data/squid_cache")
      setoptionparameter("access_log", 1, "/data/squid_logs/access.log")
      setoption("cache_log", "/data/squid_logs/cache.log")
      setoption("pid_filename", "/data/squid_logs/squid.pid")
      setoption("coredump_dir", "/data/squid_cache")

Set Up Cron Job

As user dbfrontier, set up cron jobs to rotate the logs, with crontab entries like this:

7 7 * * * /install_dir/frontier-cache/utils/cron/daily.sh >/dev/null 2>&1
8 * * * * /install_dir/frontier-cache/utils/cron/hourly.sh >/dev/null 2>&1

You could get the above crontab by doing (with the appropriate value of install_dir)

crontab /install_dir/frontier-cache/utils/cron/crontab.dat

You can change the hour and minute as you like, but leave hourly.sh to be one minute after daily.sh, and avoid multiples of 5 for the minute because it can interfere with the monitoring probes which happen every 5 minutes. The hourly.sh script will rotate the logs if access.log goes over a given size, default 1GB. You can change that value by setting the environment variable LARGE_ACCESS_LOG to a different number of bytes. For example for 10GB you can use:

8 * * * * LARGE_ACCESS_LOG=10000000000 /install_dir/frontier-cache/utils/cron/hourly.sh >/dev/null 2>&1

In order to estimate disk usage, note that up to 11 access.log files are kept at a time, and the size can go a bit above the $LARGE_ACCESS_LOG size because the cron job only checks once per hour. If disk space for the logs is a concern see the section on the Access Log Growth Issue below.

As Root, Set Up Start at Boot Time

(This is the only step to be done as root.)

Then as root:

copy install_dir/frontier-cache/utils/init.d/frontier-squid.sh into /etc/init.d

Then after the copy, root should do:

/sbin/chkconfig --add frontier-squid.sh

Testing Your Installation

Download the following python script fnget.py (Do a right-click on the link and save the file as fnget.py )

Test access to the Frontier server at CERN with the following commands:

chmod +x fnget.py #(only first time)

./fnget.py --url=http://cmsfrontier.cern.ch:8000/Frontier/Frontier --sql="select 1 from dual"

This should be the response:

Using Frontier URL:  http://cmsfrontier.cern.ch:8000/Frontier/Frontier
Query:  select 1 from dual
Decode results:  1
Refresh cache:  0

Frontier Request:
http://cmsfrontier.cern.ch:8000/Frontier/Frontier?type=frontier_request:1:DEFAUL
T&encoding=BLOBzip&p1=eNorTs1JTS5RMFRIK8rPVUgpTcwBAD0rBmw_

Query started:  05/12/09 13:46:50 EDT
*WARNING:* no timeout available in python older than 2.4
Query ended:  05/12/09 13:46:50 EDT
Query time: 0.64064002037 [seconds]

Query result:
<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE frontier SYSTEM "http://frontier.fnal.gov/frontier.dtd">
<frontier version="3.17" xmlversion="1.0">
 <transaction payloads="1">
  <payload type="frontier_request" version="1" encoding="BLOBzip">
   <data>eJxjY2BgYDRkA5JsfqG+Tq5B7GxgEXYAGs0CVA==</data>
   <quality error="0" md5="5544fd3e96013e694f13d2e13b44ee3c" records="1" full_si
ze="25"/>
  </payload>
 </transaction>
</frontier>


Fields:
     1     NUMBER

Records:
     1

This will return whatever you type in the select statement, for example change 1 to 'hello'. The "dual" table is a special debugging feature of Oracle that just returns what you send it.

Now test your squid,

export http_proxy=http://your.squid.url:3128

and perform the test again. It should pass through your squid, and cache the response. To see if it worked, look at the squid access log (following excerpted form the access.log file usually in squid/var/logs :

128.220.233.179 - - [12/May/2009:08:33:17 +0000] "GET http://cmsfrontier.cern.ch
:8000/Frontier/Frontier?type=frontier_request:1:DEFAULT&encoding=BLOBzip&p1=eNor
Ts1JTS5RMFRIK8rPVUgpTcwBAD0rBmw= HTTP/1.0" 200 810 TCP_MISS:DIRECT 461 "fnget.py
 1.5"
128.220.233.179 - - [12/May/2009:08:33:19 +0000] "GET http://cmsfrontier.cern.ch
:8000/Frontier/Frontier?type=frontier_request:1:DEFAULT&encoding=BLOBzip&p1=eNor
Ts1JTS5RMFRIK8rPVUgpTcwBAD0rBmw= HTTP/1.0" 200 809 TCP_MEM_HIT:NONE - "fnget.py
1.5"

Notice the second entry has a "TCP_MEM_HIT", that means the object was cached in the memory. Any subsequent requests for this object will come from the squid cache.

Another possibility for testing your squid is to run the SAM squid test on a worker node by hand.

Monitoring

The functionality of your squid should be monitored from CERN and Fermilab using SNMP.

To enable this, your site should open port 3401/udp to requests from: 128.142.202.212/255.255.255.255 (or preferably cmsdbsfrontier.cern.ch if you can use a DNS name) and 131.225.240.232/255.255.255.255. The former is the main site, and the latter is a backup site at Fermilab.

The main monitoring site is at http://frontier.cern.ch/squidstats/.

SELinux

SELinux on RHEL 5 does not give the proper context to the default SNMP port (3401) (as of selinux-policy-2.4.6-106.el5) . The command (as root)

semanage port -a -t http_cache_port_t -p udp 3401

takes care of this problem.

Some Useful Commands

install_dir/frontier-cache/utils/bin/fn-local-squid.sh with any parameter or no parameter will recreate squid.conf after changing customize.sh

install_dir/frontier-cache/squid/sbin/squid -k parse will just read squid.conf to see if it makes sense

install_dir/frontier-cache/utils/bin/fn-local-squid.sh reload sends a HUP signal and has squid reread squid.conf

install_dir/frontier-cache/utils/bin/fn-local-squid.sh status checks if squid is running

install_dir/frontier-cache/utils/bin/fn-local-squid.sh restart stops squid and starts squid without clearing the cache

install_dir/frontier-cache/utils/bin/fn-local-squid.sh cleancache deletes and recreates the cache, like a start does, but without starting squid

install_dir/frontier-cache/squid/bin/squidclient mgr:info outputs operational information about your squid

Access Log Growth Issue

With many active clients, it is still possible for the squid access.log to grow to unmanageable size. The squid will crash if it runs out of available diskspace. There are a couple ways to avoid this problem:

1) Make sure that you have the hourly.sh cron job enabled as described in the Set Up Cron Job section above to rotate the log when it grows over a size you choose.

2) The other possibility is to disable writing to access.log by putting the following in install_dir/frontier-cache/squid/etc/customize.sh:

setoption("access_log", "none")

and then do

install_dir/frontier-cache/utils/bin/fn-local-squid.sh reload to update squid.conf and load it if the squid is already running, otherwise just use start instead of reload.

The squid installation script has the access log turned on by default. It is recommended that a new installation be installed with it on, the functioning of the squid verified by reading the access log, then if disk space is limited, turn the access log off when the squid is in production. Even if you do turn the access log off, you should still run the daily.sh script once per day to rotate the other logs.

Filedescriptors

At some installations with a very large number of worker nodes it may be possible to see error messages about running out of filedescriptors in your cache.log. It is easy to avoid this problem:

1) First, make sure your squid version is at least squid-2.7.X

2) As root, add the following line to /etc/security/limits.conf

* - nofile 16384

3) Reboot the machine.

You can check your file descriptor limit and usage by doing:

install_dir/frontier-cache/squid/bin/squidclient mgr:info

Other ACL options

The default behavior is to allow the squid to be used for any destination. If you want to restrict the squid to be used only for CMS Conditions Data, then you simply have to add two lines to customize.sh that enable a couple of lines in squid.conf which are already there commented out:

 uncomment("acl RESTRICT_DEST")
 uncomment("http_access deny !RESTRICT_DEST")

If for some reason you want to have a different destination or destinations you can use a regular expression, for example:

 setoptionparameter("acl RESTRICT_DEST", 3, "^(cmsfrontier.*|cernvm.*)\\.cern\\.ch$")
 uncomment("http_access deny !RESTRICT_DEST")

Another possible configuration is to allow worker nodes at other sites to use your squid, although we discourage that because many worker nodes can use large amounts of bandwidth over the wide area network. If you still want to do it, it can be done by adding extra lines to your customize.sh. The order of these lines is important, so they need to be "anchored" to others, for example like this:

 insertline("acl NET_LOCAL", "acl T2FOO src x.x.x.x/x.x.x.x")
 insertline("acl NET_LOCAL", "acl T2BAR src x.x.x.x/x.x.x.x")
 insertline("http_access allow NET_LOCAL", "http_access allow T2FOO")
 insertline("http_access allow NET_LOCAL", "http_access allow T2BAR")

In addition, you have to make sure there are holes in any site or machine firewalls that allow these other worker nodes access to port 3128 on your squid.

Finally, the remote sites must make an appropriate addition to their site-local-config.xml.

If you modify customize.sh while the squid is running, remember to do a

install_dir/frontier-cache/utils/bin/fn-local-squid.sh reload

so that the changes get used.

Responsible: DaveDykstra

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