[squid-users] help with the error TCP_MISS_ABORTED/000

[L A Walsh]

Juan Manuel P wrote:
> I am using Squid Cache: Version 3.5.12, but some pages give me the 
> next error:
>
> 1/Feb/2018:18:14:40 -0300 || - || 10.12.43.20 || 
> TCP_MISS_ABORTED/000|| GET || 
> http://www.rionegro.gov.ar/download/images/00033494.jpg 
> <http://www.rionegro.gov.ar/download/images/00033494.jpg> || -
----
    I don't know what causes it, but I see it frequently and have for a few
years.  Currently am running 3.15.3.  Was told it might be due to some
cache corruption -- but having removed it several times over the past
few years, I sorta doubt that.  Also, I'm attempting https interception, now
but wasn't when I first encountered this message...

    Out of last 5000 requests in my squid log, I see 101 of the miss_aborted
statuses.  I just wrote a note on stackexchange, then went to look for
something on amazon (this is output from a squid log compression tool
that was mostly for listing site, request time and size:  A few lines
from no more than 15 minutes ago (usually shows time between requests, but
periodically, there's a full timestamp)...

    Part of my shortening process removes the TCP_ before error messages,
thus my error is just "MISS_ABORTED".

Since this is a grep of that shortened log, the time increments since
last message are not referring to line immediately above in the grep:


[0227_172940.00]  379ms; 0    (0/0) MISS_ABORTED/000 <Athenae [GET 
https://qa.sockets.stackexchange.com/ - 198.252.206.25 -]
  +0.38   372ms; 0    (0/0) MISS_ABORTED/000 <Athenae [GET  
https://qa.sockets.stackexchange.com/ - 198.252.206.25 -]
  +0.01     1ms; 0    (0/0) MISS_ABORTED/000 <Athenae [GET 
https://images-na.ssl-images-amazon.com/images/I/61x0MG3xpeL._AC_UL160_SR160,160_.jpg 
- 54.230.117.34 -]
  +0.00     0ms; 0    (-/-) MISS_ABORTED/000 <Athenae [GET 
https://images-na.ssl-images-amazon.com/images/I/813zL5eetaL._AC_UL160_SR160,160_.jpg 
- 54.230.117.34 -]
  +0.00     0ms; 0    (-/-) MISS_ABORTED/000 <Athenae [GET 
https://images-na.ssl-images-amazon.com/images/I/61Uo2hXZlpL._AC_UL160_SR160,160_.jpg 
- 54.230.117.34 -]
  +0.00     0ms; 0    (-/-) MISS_ABORTED/000 <Athenae [GET 
https://images-na.ssl-images-amazon.com/images/I/71XggjYZ7qL._AC_UL160_SR160,160_.jpg 
- 54.230.117.34 -]
  +0.00     1ms; 0    (-/0) MISS_ABORTED/000 <Athenae [GET 
https://images-na.ssl-images-amazon.com/images/I/71LT8PAs-OL._AC_UL160_SR160,160_.jpg 
- 54.230.117.34 -]
  +0.00     1ms; 0    (-/0) MISS_ABORTED/000 <Athenae [GET 
https://images-na.ssl-images-amazon.com/images/I/51X+70QICxL._AC_UL160_SR160,160_.jpg 
- 54.230.117.34 -]
[0227_173215.00]   16ms; 0    (0/0) MISS_ABORTED/000 <Athenae [GET 
https://www.amazon.com/gp/uedata?ul&v=0.200071.0&id=TXSV6J9MMKFJ764232PB&ctb=1&m=1&sc=TXSV6J9MMKFJ764232PB&pc=3758697&tc=-286&hob=1&hoe=3&ul=3758697&t=1519781535329&csmtags=mouseHit&pty=Detail&spty=Glance&pti=B079GH97R9&tid=TXSV6J9MMKFJ764232PB&aftb=1 
- 23.192.244.68 -]
====================================


Of note -- a bunch were in trying to fetch a sockets address on 
stackexchange, , while most of the amazon lines seem to be referring to 
jpgs.  Anyway, I too would be interested if you find the answer.

Just thought I'd mention that your seeing the message isn't unique.

Found someone else who asked the same question back in May 2015...