[squid-users] pinger crash - Bad opcode: 112

Amos Jeffries squid3 at treenet.co.nz
Thu May 26 06:04:36 UTC 2016

On 24/05/2016 7:52 p.m., Tomas Mozes wrote:
> Hello,
> on two different squid servers I've observed a crash of pinger. First it
> appeared on version 3.5.15 and later on version 3.5.17.
> Cache.log contains these lines:
> (pinger): Address.cc:671: void Ip::Address::getAddrInfo(addrinfo*&, int)
> const: Assertion `false' failed.
> 2016/05/14 21:55:25 kid1| Bad opcode: 112 from
> [6661:6c73:6522:2061:7420:6c69:6e65:2036]
> 2016/05/14 21:59:13 kid1| recv: (111) Connection refused
> 2016/05/14 21:59:13 kid1| Closing Pinger socket on FD 17
> On both servers, that IPv6 address was the same -
> 6661:6c73:6522:2061:7420:6c69:6e65:2036

That is the hexadecimal representation of the error:
 false" at line 6

Which means that your kernel is producing garbage when asked to resolve
an IPv6 address or respond to an ICMPv6 packet.

> A quick google search for that showed problems with Squid from the past:
> http://www.squid-cache.org/mail-archive/squid-users/201301/0251.html
> The strange thing is that I have IPv6 disabled in the system (not even as a
> module in the Linux kernel) and Squid was compiled without ipv6 support.

Support for IPv6 has been mandatory for all IP network connected devices
since 2012.

"Disabling" IPv6 in Squid simply means it will not attempt to use IPv6
for HTTP connections. It must still be able to identify IPv6 addresses.
Which requires kernel support for IPv6.

If you don't want IPv6 to take place "the right way" to do it is to
configure your network interfaces not to have IPv6 address assignments
and your machines firewall to block IPv6 traffic.


More information about the squid-users mailing list