Re: Squid TCP_TUNNEL_ABORTED/200

[Emre Oksum <emreoksum@xxxxxxxxx>]

Hi Amos,

>FTR, "debug_options ALL" alone is invalid syntax and will not change
>from the default cache.log output

Yes, you were right! I was surely missing on that one. I changed debug_options ALL to debug_options ALL 5 and now, I found these warnings in cache.log file:

2024/05/03 21:09:30.963 kid4| 28,5| Acl.cc(124) matches: checking (tcp_outgoing_address [aaa:bbb:ccc:ddd:eee:fff:a81b:338c
2024/05/03 21:09:30.963 kid6| 28,3| Acl.cc(151) matches: checked: (tcp_outgoing_address [aaa:bbbb:cccc:dddd:eeee:ffff:7eb8:b2e0 = 0
2024/05/03 21:09:30.963 kid8| 28,5| Acl.cc(124) matches: checking tcp_outgoing_address [aaaa:bbbb:cccc:dddd:eeee:ffff:f92c:14fb]
2024/05/03 21:09:30.963 kid5| 28,3| Ip.cc(538) match: aclIpMatchIp: '[aaaa:bbbb:cccc:dddd:eeee:ffff:4b29:abe5]:1182' NOT found
2024/05/03 21:09:30.963 kid1| 28,5| Acl.cc(124) matches: checking (tcp_outgoing_address [aaaa:bbbb:cccc:dddd:eeee:ffff:2a45:6d20
2024/05/03 21:09:30.963 kid2| 28,3| Acl.cc(151) matches: checked: (tcp_outgoing_address [aaaa:bbbb:cccc:dddd:eeee:ffff:9b7c:68db = 0
2024/05/03 21:09:30.963 kid7| 28,3| Checklist.cc(70) preCheck: 0x7ffd86446f80 checking fast ACLs
2024/05/03 21:09:30.963 kid3| 28,3| Ip.cc(538) match: aclIpMatchIp: '[aaaa:bbbb:cccc:dddd:eeee:ffff:3135:f730]:1182' NOT found
2024/05/03 21:09:30.963 kid4| 28,5| Acl.cc(124) matches: checking binding597
2024/05/03 21:09:30.963 kid6| 28,3| Acl.cc(151) matches: checked: tcp_outgoing_address [aaa:bbbb:cccc:dddd:eeee:ffff:7eb8:b2e0] = 0
2024/05/03 21:09:30.963 kid8| 28,5| Acl.cc(124) matches: checking (tcp_outgoing_address [aaaa:bbbb:cccc:dddd:eeee:ffff:f92c:14fb
2024/05/03 21:09:30.963 kid5| 28,3| Acl.cc(151) matches: checked: binding3010 = 0
2024/05/03 21:09:30.963 kid1| 28,5| Acl.cc(124) matches: checking binding687
2024/05/03 21:09:30.963 kid2| 28,3| Acl.cc(151) matches: checked: tcp_outgoing_address [aaaa:bbbb:cccc:dddd:eeee:ffff:9b7c:68db] = 0
2024/05/03 21:09:30.963 kid7| 28,5| Acl.cc(124) matches: checking tcp_outgoing_address [aaaa:bbbb:cccc:dddd:eeee:ffff:4b16:da82]
2024/05/03 21:09:30.963 kid3| 28,3| Acl.cc(151) matches: checked: binding22 = 0
2024/05/03 21:09:30.963 kid6| 28,3| Checklist.cc(63) markFinished: 0x7ffcdd512440 answer DENIED for ACLs failed to match
2024/05/03 21:09:30.963 kid4| 28,3| Ip.cc(538) match: aclIpMatchIp: '[aaaa:bbbb:cccc:dddd:eeee:ffff:cf41:193c]:1182' NOT found

Is there any chance aclIpMatchIp warnings could be the problem here? Do they generate TCP RST packets to client if that error happens?

Thanks

Emre

Amos Jeffries <squid3@xxxxxxxxxxxxx>, 3 May 2024 Cum, 23:50 tarihinde şunu yazdı:

On 4/05/24 08:33, Emre Oksum wrote:
> Hi Jonathan,
>
>  >> Have you attempted to enable debugging ??
> Yes, debugging was enabled but as I have pointed out, unfortunately it
> didn't give any information about the issue.
> Maybe I was missing something? I don't know. debug_options was ALL in my
> squid.conf.

Sure, "ALL" sections.

But what display level:

  0 (critical only)?
  1 (important)?
  2 (protocol trace)?
  3-6 (debugs)?
  9 (raw I/O data traces)?


FTR, "debug_options ALL" alone is invalid syntax and will not change
from the default cache.log output.


Cheers
Amos
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.squid-cache.org/listinfo/squid-users

_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.squid-cache.org/listinfo/squid-users