<div dir="ltr">Hello ludovit,<br><br>We experienced the similar problems of crashing squid with "signal 6 and status 0" symptoms in the /var/log/messages. There were hundreds of crashes per hour during the working hours. There were also many crashes during night hours. And I had no idea what the cause of the problem was.<br>But your case shed light on the problem.<br><br>I captured network traffic and saw in the dump many requests to IPv6 addresses like this: POST http://[2001:67c:4e8:f004::a]:80/api HTTP/1.1\r\n<br>I think that the requests were generated by the Telegram application, because neighboring similar requests were addressed to Telegram IPv4 pools: POST <a href="http://91.105.192.100:80/api">http://91.105.192.100:80/api</a> HTTP/1.1\r\n<br><br>To fix the problem somehow, I added the following rules to the very beginning of the SQUID configuration:<br> acl urldst_ipv6 url_regex ^http://\[<br> http_access deny urldst_ipv6<br> <br>Now it seems the problem has been solved.<br><br>I was wondering if this is a SQUID bug. In my opinion, SQUID should not crash on requests to IPv6 resources, but should send a response with an error, for example, Bad gateway 502, or Not Acceptable 406.<br><br><br>Kind regards,<br> Ankor.<br><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">ср, 12 окт. 2022 г. в 15:30, Ludovit Koren <<a href="mailto:ludovit.koren@gmail.com">ludovit.koren@gmail.com</a>>:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">>>>>> Amos Jeffries <<a href="mailto:squid3@treenet.co.nz" target="_blank">squid3@treenet.co.nz</a>> writes:<br>
<br>
> On 12/10/22 21:12, Ludovit Koren wrote:<br>
>> Hi,<br>
>> I am running squid-5.7 on FreeBSD 12.3-STABLE r371879. Occasionally<br>
>> I<br>
>> get the following error:<br>
>> <br>
<br>
>> #3 0x000000080111fcb1 in __assert (func=<optimized out>, file=<optimized out>, line=<optimized out>, failedexpr=<optimized out>) at /usr/src/lib/libc/gen/assert.c:51<br>
>> #4 0x0000000000698fcd in Ip::Address::getAddrInfo (this=0x861c04588, dst=<optimized out>, force=0) at Address.cc:663<br>
>> #5 0x000000000068b732 in comm_openex (sock_type=sock_type@entry=1, proto=proto@entry=6, addr=..., flags=1, note=0x85ce42dc0 "[fe80::21f:29ff:fe28:7017]") at comm.cc:347<br>
> ...<br>
<br>
>> The squid is compiled without IPv6 option, so I do not understand<br>
>> why it<br>
>> tries to reach IPv6 address.<br>
>> <br>
<br>
> A client is requiring connection to an IPv6 server. But Squid cannot<br>
> convert that IPv6 address or use on an IPv4-only network. Lack of IPv6 <br>
> support also forbids IPv6 failover handling being used.<br>
<br>
So the solution is to reenable IPv6 in the squid, as well as in the OS<br>
network stack? Am I right?<br>
<br>
Thank you.<br>
<br>
Regards,<br>
<br>
lk<br>
_______________________________________________<br>
squid-users mailing list<br>
<a href="mailto:squid-users@lists.squid-cache.org" target="_blank">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>