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

[Tomas Mozes]

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

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.

How can I help tracing this issue?

Thanks,
Tomas Mozes
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20160524/ad4eca37/attachment.html>