[prev in list] [next in list] [prev in thread] [next in thread]
List: squid-users
Subject: Re: [squid-users] pinger crash - Bad opcode: 112
From: Tomas Mozes <hydrapolic () gmail ! com>
Date: 2016-05-31 9:56:19
Message-ID: CAG6MAzQpEQNA1nv_GfNcWvQTccA7ZejyCoOiscsQS51C5FBcdQ () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Thu, May 26, 2016 at 8:04 AM, Amos Jeffries <squid3@treenet.co.nz> wrote:
> 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.
>
Cannot we prevent Squid from crashing in these cases?
>
>
> > 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.
>
> Amos
>
> _______________________________________________
> squid-users mailing list
> squid-users@lists.squid-cache.org
> http://lists.squid-cache.org/listinfo/squid-users
>
[Attachment #5 (text/html)]
<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, May \
26, 2016 at 8:04 AM, Amos Jeffries <span dir="ltr"><<a \
href="mailto:squid3@treenet.co.nz" \
target="_blank">squid3@treenet.co.nz</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><span class="">On 24/05/2016 7:52 p.m., Tomas Mozes \
wrote:<br> > Hello,<br>
> on two different squid servers I've observed a crash of pinger. First it<br>
> appeared on version 3.5.15 and later on version 3.5.17.<br>
><br>
> Cache.log contains these lines:<br>
><br>
> (pinger): Address.cc:671: void Ip::Address::getAddrInfo(addrinfo*&, int)<br>
> const: Assertion `false' failed.<br>
> 2016/05/14 21:55:25 kid1| Bad opcode: 112 from<br>
> [6661:6c73:6522:2061:7420:6c69:6e65:2036]<br>
> 2016/05/14 21:59:13 kid1| recv: (111) Connection refused<br>
> 2016/05/14 21:59:13 kid1| Closing Pinger socket on FD 17<br>
><br>
> On both servers, that IPv6 address was the same -<br>
> 6661:6c73:6522:2061:7420:6c69:6e65:2036<br>
><br>
<br>
</span>That is the hexadecimal representation of the error:<br>
false" at line 6<br>
<br>
Which means that your kernel is producing garbage when asked to resolve<br>
an IPv6 address or respond to an ICMPv6 packet.<br></blockquote><div><br>Cannot we \
prevent Squid from crashing in these cases?<br></div><div> </div><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> <span class=""><br>
<br>
> A quick google search for that showed problems with Squid from the past:<br>
> <a href="http://www.squid-cache.org/mail-archive/squid-users/201301/0251.html" \
rel="noreferrer" target="_blank">http://www.squid-cache.org/mail-archive/squid-users/201301/0251.html</a><br>
><br>
> The strange thing is that I have IPv6 disabled in the system (not even as a<br>
> module in the Linux kernel) and Squid was compiled without ipv6 support.<br>
><br>
<br>
</span>Support for IPv6 has been mandatory for all IP network connected devices<br>
since 2012.<br>
<br>
"Disabling" IPv6 in Squid simply means it will not attempt to use IPv6<br>
for HTTP connections. It must still be able to identify IPv6 addresses.<br>
Which requires kernel support for IPv6.<br>
<br>
If you don't want IPv6 to take place "the right way" to do it is to<br>
configure your network interfaces not to have IPv6 address assignments<br>
and your machines firewall to block IPv6 traffic.<br>
<br>
Amos<br>
<br>
_______________________________________________<br>
squid-users mailing list<br>
<a href="mailto:squid-users@lists.squid-cache.org">squid-users@lists.squid-cache.org</a><br>
<a href="http://lists.squid-cache.org/listinfo/squid-users" rel="noreferrer" \
target="_blank">http://lists.squid-cache.org/listinfo/squid-users</a><br> \
</blockquote></div><br></div></div>
[Attachment #6 (text/plain)]
_______________________________________________
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic