[ https://issues.apache.org/jira/browse/TS-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Susan Hinrichs updated TS-1935: ------------------------------- Assignee: Bryan Call > 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 > Assignee: Bryan Call > Fix For: 5.2.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.3.4#6332)