tcp_miss_aborted driving me crazy !

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

tcp_miss_aborted driving me crazy !

--Ahmad--

Hello Folks :

i have frequent Down on website that using it for IPV6 outgoing addresses :
below logs as you see , some have TCP_Miss and some have problems as TCP_MISS_ABORTED .

the TCP_MISS_ABORTED seems down request and i dont know whats the wrong there as long i see the name is resolved of website and we can ping it

based on logs below , the   website ip address  is — >2400:cb00:2048:1::681b:99de


21/Aug/2018:16:26:42 -0400   5575 94.130.239.213 36722 184.75.223.131 13071 TCP_MISS/200 425 GET http://extlikes.org/ip.php - HIER_DIRECT/ extlikes.org 2400:cb00:2048:1::681b:99de
21/Aug/2018:16:26:42 -0400   5673 94.130.239.213 52172 184.75.223.131 13022 TCP_MISS/200 425 GET http://extlikes.org/ip.php - HIER_DIRECT/ extlikes.org 2400:cb00:2048:1::681b:99de
21/Aug/2018:16:26:42 -0400   5673 94.130.239.213 43942 184.75.223.131 13026 TCP_MISS/200 425 GET http://extlikes.org/ip.php - HIER_DIRECT/ extlikes.org 2400:cb00:2048:1::681b:99de
21/Aug/2018:16:26:42 -0400   5673 94.130.239.213 49560 184.75.223.131 13010 TCP_MISS/200 425 GET http://extlikes.org/ip.php - HIER_DIRECT/ extlikes.org 2400:cb00:2048:1::681b:99de
21/Aug/2018:16:26:42 -0400   5673 94.130.239.213 37166 184.75.223.131 13001 TCP_MISS/200 425 GET http://extlikes.org/ip.php - HIER_DIRECT/ extlikes.org 2400:cb00:2048:1::681b:99de
21/Aug/2018:16:26:42 -0400   5673 94.130.239.213 47320 184.75.223.131 13015 TCP_MISS/200 425 GET http://extlikes.org/ip.php - HIER_DIRECT/ extlikes.org 2400:cb00:2048:1::681b:99de
21/Aug/2018:16:26:42 -0400   5707 94.130.239.213 60090 184.75.223.131 13016 TCP_MISS/200 425 GET http://extlikes.org/ip.php - HIER_DIRECT/ extlikes.org 2400:cb00:2048:1::681b:99de
21/Aug/2018:16:26:36 -0400  38905 94.130.239.213 38342 184.75.223.131 11807 TCP_MISS_ABORTED/0 0 GET http://extlikes.org/ip.php - HIER_DIRECT/ extlikes.org 2400:cb00:2048:1::681b:99de
21/Aug/2018:16:26:36 -0400  38884 94.130.239.213 39622 184.75.223.131 11718 TCP_MISS_ABORTED/0 0 GET http://extlikes.org/ip.php - HIER_DIRECT/ extlikes.org 2400:cb00:2048:1::681b:99de
21/Aug/2018:16:26:36 -0400  38843 94.130.239.213 40526 184.75.223.131 11852 TCP_MISS_ABORTED/0 0 GET http://extlikes.org/ip.php - HIER_DIRECT/ extlikes.org 2400:cb00:2048:1::681b:99de
21/Aug/2018:16:26:36 -0400  38781 94.130.239.213 42524 184.75.223.131 11893 TCP_MISS_ABORTED/0 0 GET http://extlikes.org/ip.php - HIER_DIRECT/ extlikes.org 2400:cb00:2048:1::681b:99de
21/Aug/2018:16:26:36 -0400  38724 94.130.239.213 48742 184.75.223.131 11552 TCP_MISS_ABORTED/0 0 GET http://extlikes.org/ip.php - HIER_DIRECT/ extlikes.org 2400:cb00:2048:1::681b:99de
21/Aug/2018:16:26:35 -0400  38656 94.130.239.213 55278 184.75.223.131 11913 TCP_MISS_ABORTED/0 0 GET http://extlikes.org/ip.php - HIER_DIRECT/ extlikes.org 2400:cb00:2048:1::681b:99de



as you see above , some request go ok and others dont go , and i hope i find explanation why the TCP_miss aborted occurs as long as i can ping it from an iPV6 address .
my outgoing  addresses are IPV6

all is IPV6 purse addresses ,

looking forward to help me out

kind regards
_______________________________________________
squid-users mailing list
[hidden email]
http://lists.squid-cache.org/listinfo/squid-users
Reply | Threaded
Open this post in threaded view
|

Re: tcp_miss_aborted driving me crazy !

Alex Rousskov
On 08/21/2018 03:42 PM, --Ahmad-- wrote:

> the TCP_MISS_ABORTED seems down request and i dont know whats the
> wrong there

Assuming the second column in the sanitized access.log output below is
transaction response time, it looks like the client aborts (i.e. closes
the connection) if it receives no response from Squid for ~38 seconds. I
do not know why the server did not respond for so long or why Squid did
not forward the response to the client for so long. You may be able to
distinguish these two cases using a packet capture.


> 16:26:42  5575 ip1 36722 ip2 13071 TCP_MISS/200 425 GET ...
> 16:26:42  5673 ip1 52172 ip2 13022 TCP_MISS/200 425 GET ...
> 16:26:42  5673 ip1 43942 ip2 13026 TCP_MISS/200 425 GET ...
> 16:26:42  5673 ip1 49560 ip2 13010 TCP_MISS/200 425 GET ...
> 16:26:42  5673 ip1 37166 ip2 13001 TCP_MISS/200 425 GET ...
> 16:26:42  5673 ip1 47320 ip2 13015 TCP_MISS/200 425 GET ...
> 16:26:42  5707 ip1 60090 ip2 13016 TCP_MISS/200 425 GET ...
> 16:26:36 38905 ip1 38342 ip2 11807 TCP_MISS_ABORTED/0 0 GET ...
> 16:26:36 38884 ip1 39622 ip2 11718 TCP_MISS_ABORTED/0 0 GET ...
> 16:26:36 38843 ip1 40526 ip2 11852 TCP_MISS_ABORTED/0 0 GET ...
> 16:26:36 38781 ip1 42524 ip2 11893 TCP_MISS_ABORTED/0 0 GET ...
> 16:26:36 38724 ip1 48742 ip2 11552 TCP_MISS_ABORTED/0 0 GET ...
> 16:26:35 38656 ip1 55278 ip2 11913 TCP_MISS_ABORTED/0 0 GET ...

What logformat do you use? Did you reorder these records or were they
logged by Squid in the decreasing timestamp order?

The requests in each of the two groups above look concurrent to me. Do
you explicitly turn collapsed_forwarding on in your squid.conf? If you
do, does turning collapsed forwarding off solve this problem?


> as long as i can ping it from an iPV6 address

This is probably not an IP connectivity problem but a TCP- or HTTP-level
problem. You may want to try curl or wget to reproduce it without Squid.


HTH,

Alex.
_______________________________________________
squid-users mailing list
[hidden email]
http://lists.squid-cache.org/listinfo/squid-users