[
https://issues.apache.org/jira/browse/TS-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14601707#comment-14601707
]
Bryan Call edited comment on TS-1935 at 6/25/15 6:44 PM:
---------------------------------------------------------
This is no longer an issue with HTTPS since the state machine is not created if
there are no bytes sent from the client for ATS 6.0.0.
Debug of client closing the connection:
{code}
[Jun 25 11:41:48.512] Server {0x7fff73d0f300} DEBUG: <SSLNetVConnection.cc:201
(ssl_read_from_net)> (ssl) [SSL_NetVConnection::ssl_read_from_net]
b->write_avail()=4096
[Jun 25 11:41:48.512] Server {0x7fff73d0f300} DEBUG: <SSLNetVConnection.cc:208
(ssl_read_from_net)> (ssl) [SSL_NetVConnection::ssl_read_from_net] nread=0
[Jun 25 11:41:48.512] Server {0x7fff73d0f300} DEBUG: <SSLNetVConnection.cc:767
(do_io_close)> (ssl-shutdown) previous shutdown state 0x0
[Jun 25 11:41:48.512] Server {0x7fff73d0f300} DEBUG: <SSLNetVConnection.cc:773
(do_io_close)> (ssl-shutdown) new SSL_set_shutdown 0x2
[Jun 25 11:41:48.512] Server {0x7fff73d0f300} DEBUG: <SSLNetVConnection.cc:589
(net_read_io)> (ssl) read_from_net, read finished - 0 useful bytes read, bytes
used by SSL layer
{code}
Debug of server closing the connection:
{code}
[Jun 25 11:42:52.362] Server {0x7fff73d0f300} DEBUG: <SSLNetVConnection.cc:767
(do_io_close)> (ssl-shutdown) previous shutdown state 0x0
[Jun 25 11:42:52.362] Server {0x7fff73d0f300} DEBUG: <SSLNetVConnection.cc:773
(do_io_close)> (ssl-shutdown) new SSL_set_shutdown 0x2
[Jun 25 11:42:52.362] Server {0x7fff73d0f300} DEBUG: <SSLUtils.cc:1588
(ssl_callback_info)> (ssl) ssl_callback_info ssl: 0x7fdf80f4d580 where: 16392
ret: 256
[Jun 25 11:42:52.362] Server {0x7fff73d0f300} DEBUG: <SSLNetVConnection.cc:788
(do_io_close)> (ssl-shutdown) SSL_shutdown success
{code}
was (Author: bcall):
This is no longer an issue with HTTPS since the state machine is not created if
there are no bytes sent for ATS 6.0.0.
Debug of client closing the connection:
{code}
[Jun 25 11:41:48.512] Server {0x7fff73d0f300} DEBUG: <SSLNetVConnection.cc:201
(ssl_read_from_net)> (ssl) [SSL_NetVConnection::ssl_read_from_net]
b->write_avail()=4096
[Jun 25 11:41:48.512] Server {0x7fff73d0f300} DEBUG: <SSLNetVConnection.cc:208
(ssl_read_from_net)> (ssl) [SSL_NetVConnection::ssl_read_from_net] nread=0
[Jun 25 11:41:48.512] Server {0x7fff73d0f300} DEBUG: <SSLNetVConnection.cc:767
(do_io_close)> (ssl-shutdown) previous shutdown state 0x0
[Jun 25 11:41:48.512] Server {0x7fff73d0f300} DEBUG: <SSLNetVConnection.cc:773
(do_io_close)> (ssl-shutdown) new SSL_set_shutdown 0x2
[Jun 25 11:41:48.512] Server {0x7fff73d0f300} DEBUG: <SSLNetVConnection.cc:589
(net_read_io)> (ssl) read_from_net, read finished - 0 useful bytes read, bytes
used by SSL layer
{code}
Debug of server closing the connection:
{code}
[Jun 25 11:42:52.362] Server {0x7fff73d0f300} DEBUG: <SSLNetVConnection.cc:767
(do_io_close)> (ssl-shutdown) previous shutdown state 0x0
[Jun 25 11:42:52.362] Server {0x7fff73d0f300} DEBUG: <SSLNetVConnection.cc:773
(do_io_close)> (ssl-shutdown) new SSL_set_shutdown 0x2
[Jun 25 11:42:52.362] Server {0x7fff73d0f300} DEBUG: <SSLUtils.cc:1588
(ssl_callback_info)> (ssl) ssl_callback_info ssl: 0x7fdf80f4d580 where: 16392
ret: 256
[Jun 25 11:42:52.362] Server {0x7fff73d0f300} DEBUG: <SSLNetVConnection.cc:788
(do_io_close)> (ssl-shutdown) SSL_shutdown success
{code}
> 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: 6.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.3.4#6332)
