Installation guide

The /var/l o g /sq ui d /access. l o g file on the load balancer should contain information similar

to the following:

1377540630.159

97 192.168.100.19 TCP_MISS/200 1515 POST https://lb.example.com/XMLRPC -

ROUNDROBIN_PARENT/proxya.example.com text/base64

1377540630.733

529 192.168.100.19 TCP_MISS/200 1409 POST https://lb.example.com/XMLRPC -

ROUNDROBIN_PARENT/proxyb.example.com text/xml

1377540639.968

87 192.168.100.19 TCP_MISS/200 3742 POST https://lb.example.com/XMLRPC -

ROUNDROBIN_PARENT/proxya.example.com text/xml

1377540644.273

83 192.168.100.19 TCP_MEM_HIT/200 2238956 GET

https://lb.example.com/XMLRPC/GET-REQ/rhel-x86_64-server-

6/getPackage/zsh-4.3.10-5.el6.x86_64.rpm - NONE/- application/octet-

stream

1377540646.765

100 192.168.100.19 TCP_MISS/200 1515 POST https://lb.example.com/XMLRPC -

ROUNDROBIN_PARENT/proxyb.example.com text/base64

1377540647.291

485 192.168.100.19 TCP_MISS/200 1409 POST https://lb.example.com/XMLRPC -

ROUNDROBIN_PARENT/proxya.example.com text/xml

This example shows that the client requests are balanced between the two different proxies. A single

yum package install is still shared between the multiple proxies because multiple requests are

involved during a package installation. The client IP address is 192.168.100.19 and you can see the

named pro xya. exampl e. co m and pro xyb. exampl e. co m cache peers corresponding to the two

different Satellite Proxies.

Sq u id Load Balan cer Lo g Files

Refer to the following log files to monitor load balancer activity:

/var/l o g /sq ui d /access. l o g for watching requests arriving from the client

/var/l o g /sq ui d /cache. l o g for debugging SSL startup issues and cache peers on ports 80

and 443

You can use the netstat command to ensure that the squid load balancer is listening on the correct

ports:

# netstat -tulpn | grep squid | grep tcp

tcp 0 0 :::80 :::* LISTEN

29120/(squid)

tcp 0 0 :::443 :::* LISTEN

29120/(squid)

Red Hat Sat ellit e 5.7 Proxy In st allat ion G uide