You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "zhiyuanfu (JIRA)" <ji...@apache.org> on 2013/12/22 16:40:53 UTC
[jira] [Commented] (TS-1935) ERR_UNKNOWN/000 showing up 10.4% of
the time in production logs
[ https://issues.apache.org/jira/browse/TS-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13855192#comment-13855192 ]
zhiyuanfu commented on TS-1935:
-------------------------------
4.1.2,forward proxy.
387720805 12 222.16.21.169 ERR_UNKNOWN 000 0 - http://-e
1387720805 2 110.65.97.98 ERR_UNKNOWN 000 0 - http://-e
1387720805 21 222.16.29.146 ERR_UNKNOWN 000 0 - http://-e
1387720805 39 110.65.98.247 ERR_UNKNOWN 000 0 - http://-e
1387720805 42 110.65.101.15 ERR_UNKNOWN 000 0 - http://-e
1387720805 39 110.65.96.164 ERR_UNKNOWN 000 0 - http://-e
1387720805 11 222.16.21.229 ERR_UNKNOWN 000 0 - http://-e
1387720805 11 110.65.99.250 ERR_UNKNOWN 000 0 - http://-e
1387720805 11 110.65.96.85 ERR_UNKNOWN 000 0 - http://-e
1387720805 11 110.65.97.98 ERR_UNKNOWN 000 0 - http://-e
1387720805 22 222.16.29.223 ERR_UNKNOWN 000 0 - http://-e
1387720805 32 222.16.21.229 ERR_UNKNOWN 000 0 - http://-e
1387720805 31 222.16.20.203 ERR_UNKNOWN 000 0 - http://-e
1387720805 31 110.65.104.56 ERR_UNKNOWN 000 0 - http://-e
1387720873 0 222.16.28.139 ERR_UNKNOWN 000 0 - http://-
1387720873 2 110.65.99.58 ERR_UNKNOWN 000 0 - http://-
1387720873 2 110.65.107.13 ERR_UNKNOWN 000 0 - http://-
1387720873 1 110.65.106.199 ERR_UNKNOWN 000 0 - http://-
1387720873 0 110.65.96.154 ERR_UNKNOWN 000 0 - http://-
1387720873 12 222.16.21.167 ERR_UNKNOWN 000 0 - http://-
1387720873 12 110.65.98.190 ERR_UNKNOWN 000 0 - http://-
###############
Then the ats is Fatal and start to restart.
> ERR_UNKNOWN/000 showing up 10.4% of the time in production logs
> ---------------------------------------------------------------
>
> Key: TS-1935
> URL: https://issues.apache.org/jira/browse/TS-1935
> Project: Traffic Server
> Issue Type: Bug
> Reporter: Bryan Call
> Fix For: 5.0.0
>
>
> Need to investigate in what conditions this happens.
> * Keep-alive or not
> * If any requests have happened on the connection
> * Is the client or the server closing the connection at the time
> * Verify no bytes have been sent from the client, looking at the code it looks like it
> Ideally if the client has not sent any bytes (has not attempted to make a request) then we shouldn't log the error message. If it is possible a state machine should not be created in this scenario.
> related bug:
> TS-1056
> related checkin:
> 425e3d7dcb16b40075c7678e71d00b2fcb4b4705
> I also see this happening in on my forward proxy using Chrome:
> [bcall@homer trafficserver]$ traffic_logcat -f squid.blog | grep 000
> 1370281253.174 0 192.168.1.30 ERR_UNKNOWN/000 0 - / - EMPTY/- - -
> 1370281253.450 0 192.168.1.30 ERR_UNKNOWN/000 0 - / - EMPTY/- - -
> 1370281253.891 0 192.168.1.30 ERR_UNKNOWN/000 0 - / - EMPTY/- - -
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)