Re: ICMP pinger problem

On 29/03/2014 8:12 a.m., Christian wrote:
> Hi,
>
> in my cache.log I found the following:
>
> 2014/03/28 20:07:27 kid1| Accepting HTTP Socket connections at
> local=0.0.0.0:3128 remote=[::] FD 30 flags=9
> 2014/03/28 20:07:27| pinger: Initialising ICMP pinger ...
> 2014/03/28 20:07:27| icmp_sock: (1) Operation not permitted
> 2014/03/28 20:07:27| pinger: Unable to start ICMP pinger.
> 2014/03/28 20:07:27| icmp_sock: (97) Address family not supported by
> protocol
> 2014/03/28 20:07:27| pinger: Unable to start ICMPv6 pinger.
> 2014/03/28 20:07:27| FATAL: pinger: Unable to open any ICMP sockets.
>
> Any ideas how to fix ?

Check the pinger is installed with root owner and Squid run as root.
that should fix the IPv4 ICMP socket access. We are still trying to
track down exactly what is going wrong with the IPv6 socket.

> Is this important ?

medium-low. ICMP is one if the ways Squid selects fast peers. So its
importance depends on whether you use peers or not, and whether ICMP is
enabled on your network (pinger uses ICMP echo).

Amos
Received on Sat Mar 29 2014 - 00:00:17 MDT