[jira] [Updated] (TS-2750) Crash with SPDY on production environment in HttpAcceptCont::mainEvent
[ https://issues.apache.org/jira/browse/TS-2750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudheer Vinukonda updated TS-2750: -- Labels: SPDY_ATS spdy yahoo (was: spdy yahoo) Crash with SPDY on production environment in HttpAcceptCont::mainEvent -- Key: TS-2750 URL: https://issues.apache.org/jira/browse/TS-2750 Project: Traffic Server Issue Type: Bug Components: SPDY Reporter: Sudheer Vinukonda Assignee: Yunkai Zhang Labels: SPDY_ATS, spdy, yahoo Fix For: 5.0.0 After applying patches to ts-2742 (removing the ipv4 assert) and ts-2743 (w/ a temporary fix still using the TS API, before a permanent fix is available), noticed the below new core. {code} NOTE: Traffic Server received Sig 11: Segmentation fault /home/y/bin/traffic_server - STACK TRACE: /lib64/libpthread.so.0(+0x329720f500)[0x2b64e0a7a500] /home/y/bin/traffic_server(_ZN14HttpAcceptCont9mainEventEiPv+0x147)[0x563337] /home/y/bin/traffic_server(_ZN12PluginVCCore17state_send_acceptEiPv+0x9b)[0x4db38b] /home/y/bin/traffic_server(_ZN12PluginVCCore7connectEv+0x23)[0x4db673] /home/y/bin/traffic_server(TSHttpConnectWithProtoStack+0x83)[0x4b4b53] /home/y/bin/traffic_server(_ZN7FetchSM10ext_lanuchEv+0x3b)[0x4c621b] /home/y/bin/traffic_server[0x5d263c] /home/y/bin/traffic_server(_Z26spdy_on_ctrl_recv_callbackP15spdylay_session18spdylay_frame_typeP13spdylay_framePv+0x6fe)[0x5d33de] /home/y/bin/traffic_server(spdylay_session_on_syn_stream_received+0xe0)[0x718c10] /home/y/bin/traffic_server(spdylay_session_mem_recv+0xb47)[0x719917] /home/y/bin/traffic_server(spdylay_session_recv+0x49)[0x719b49] /home/y/bin/traffic_server[0x5d0aa8] /home/y/bin/traffic_server(_ZN18UnixNetVConnection19readSignalAndUpdateEi+0x27)[0x6ed9e7] /home/y/bin/traffic_server(_ZN17SSLNetVConnection11net_read_ioEP10NetHandlerP7EThread+0xf37)[0x6ddbe7] /home/y/bin/traffic_server(_ZN10NetHandler12mainNetEventEiP5Event+0x1f2)[0x6e5052] /home/y/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x8f)[0x712fef] /home/y/bin/traffic_server(_ZN7EThread7executeEv+0x493)[0x713993] /home/y/bin/traffic_server[0x71239a] /lib64/libpthread.so.0(+0x3297207851)[0x2b64e0a72851] /lib64/libc.so.6(clone+0x6d)[0x3296ee890d] {code} -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2750) Crash with SPDY on production environment in HttpAcceptCont::mainEvent
[ https://issues.apache.org/jira/browse/TS-2750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Call updated TS-2750: --- Labels: spdy yahoo (was: SPDY_ATS) Crash with SPDY on production environment in HttpAcceptCont::mainEvent -- Key: TS-2750 URL: https://issues.apache.org/jira/browse/TS-2750 Project: Traffic Server Issue Type: Bug Components: SPDY Reporter: Sudheer Vinukonda Assignee: Yunkai Zhang Labels: spdy, yahoo Fix For: sometime After applying patches to ts-2742 (removing the ipv4 assert) and ts-2743 (w/ a temporary fix still using the TS API, before a permanent fix is available), noticed the below new core. {code} NOTE: Traffic Server received Sig 11: Segmentation fault /home/y/bin/traffic_server - STACK TRACE: /lib64/libpthread.so.0(+0x329720f500)[0x2b64e0a7a500] /home/y/bin/traffic_server(_ZN14HttpAcceptCont9mainEventEiPv+0x147)[0x563337] /home/y/bin/traffic_server(_ZN12PluginVCCore17state_send_acceptEiPv+0x9b)[0x4db38b] /home/y/bin/traffic_server(_ZN12PluginVCCore7connectEv+0x23)[0x4db673] /home/y/bin/traffic_server(TSHttpConnectWithProtoStack+0x83)[0x4b4b53] /home/y/bin/traffic_server(_ZN7FetchSM10ext_lanuchEv+0x3b)[0x4c621b] /home/y/bin/traffic_server[0x5d263c] /home/y/bin/traffic_server(_Z26spdy_on_ctrl_recv_callbackP15spdylay_session18spdylay_frame_typeP13spdylay_framePv+0x6fe)[0x5d33de] /home/y/bin/traffic_server(spdylay_session_on_syn_stream_received+0xe0)[0x718c10] /home/y/bin/traffic_server(spdylay_session_mem_recv+0xb47)[0x719917] /home/y/bin/traffic_server(spdylay_session_recv+0x49)[0x719b49] /home/y/bin/traffic_server[0x5d0aa8] /home/y/bin/traffic_server(_ZN18UnixNetVConnection19readSignalAndUpdateEi+0x27)[0x6ed9e7] /home/y/bin/traffic_server(_ZN17SSLNetVConnection11net_read_ioEP10NetHandlerP7EThread+0xf37)[0x6ddbe7] /home/y/bin/traffic_server(_ZN10NetHandler12mainNetEventEiP5Event+0x1f2)[0x6e5052] /home/y/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x8f)[0x712fef] /home/y/bin/traffic_server(_ZN7EThread7executeEv+0x493)[0x713993] /home/y/bin/traffic_server[0x71239a] /lib64/libpthread.so.0(+0x3297207851)[0x2b64e0a72851] /lib64/libc.so.6(clone+0x6d)[0x3296ee890d] {code} -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2750) Crash with SPDY on production environment in HttpAcceptCont::mainEvent
[ https://issues.apache.org/jira/browse/TS-2750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Call updated TS-2750: --- Fix Version/s: (was: sometime) 5.0.0 Crash with SPDY on production environment in HttpAcceptCont::mainEvent -- Key: TS-2750 URL: https://issues.apache.org/jira/browse/TS-2750 Project: Traffic Server Issue Type: Bug Components: SPDY Reporter: Sudheer Vinukonda Assignee: Yunkai Zhang Labels: spdy, yahoo Fix For: 5.0.0 After applying patches to ts-2742 (removing the ipv4 assert) and ts-2743 (w/ a temporary fix still using the TS API, before a permanent fix is available), noticed the below new core. {code} NOTE: Traffic Server received Sig 11: Segmentation fault /home/y/bin/traffic_server - STACK TRACE: /lib64/libpthread.so.0(+0x329720f500)[0x2b64e0a7a500] /home/y/bin/traffic_server(_ZN14HttpAcceptCont9mainEventEiPv+0x147)[0x563337] /home/y/bin/traffic_server(_ZN12PluginVCCore17state_send_acceptEiPv+0x9b)[0x4db38b] /home/y/bin/traffic_server(_ZN12PluginVCCore7connectEv+0x23)[0x4db673] /home/y/bin/traffic_server(TSHttpConnectWithProtoStack+0x83)[0x4b4b53] /home/y/bin/traffic_server(_ZN7FetchSM10ext_lanuchEv+0x3b)[0x4c621b] /home/y/bin/traffic_server[0x5d263c] /home/y/bin/traffic_server(_Z26spdy_on_ctrl_recv_callbackP15spdylay_session18spdylay_frame_typeP13spdylay_framePv+0x6fe)[0x5d33de] /home/y/bin/traffic_server(spdylay_session_on_syn_stream_received+0xe0)[0x718c10] /home/y/bin/traffic_server(spdylay_session_mem_recv+0xb47)[0x719917] /home/y/bin/traffic_server(spdylay_session_recv+0x49)[0x719b49] /home/y/bin/traffic_server[0x5d0aa8] /home/y/bin/traffic_server(_ZN18UnixNetVConnection19readSignalAndUpdateEi+0x27)[0x6ed9e7] /home/y/bin/traffic_server(_ZN17SSLNetVConnection11net_read_ioEP10NetHandlerP7EThread+0xf37)[0x6ddbe7] /home/y/bin/traffic_server(_ZN10NetHandler12mainNetEventEiP5Event+0x1f2)[0x6e5052] /home/y/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x8f)[0x712fef] /home/y/bin/traffic_server(_ZN7EThread7executeEv+0x493)[0x713993] /home/y/bin/traffic_server[0x71239a] /lib64/libpthread.so.0(+0x3297207851)[0x2b64e0a72851] /lib64/libc.so.6(clone+0x6d)[0x3296ee890d] {code} -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2750) Crash with SPDY on production environment in HttpAcceptCont::mainEvent
[ https://issues.apache.org/jira/browse/TS-2750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Peach updated TS-2750: Description: After applying patches to ts-2742 (removing the ipv4 assert) and ts-2743 (w/ a temporary fix still using the TS API, before a permanent fix is available), noticed the below new core. {code} NOTE: Traffic Server received Sig 11: Segmentation fault /home/y/bin/traffic_server - STACK TRACE: /lib64/libpthread.so.0(+0x329720f500)[0x2b64e0a7a500] /home/y/bin/traffic_server(_ZN14HttpAcceptCont9mainEventEiPv+0x147)[0x563337] /home/y/bin/traffic_server(_ZN12PluginVCCore17state_send_acceptEiPv+0x9b)[0x4db38b] /home/y/bin/traffic_server(_ZN12PluginVCCore7connectEv+0x23)[0x4db673] /home/y/bin/traffic_server(TSHttpConnectWithProtoStack+0x83)[0x4b4b53] /home/y/bin/traffic_server(_ZN7FetchSM10ext_lanuchEv+0x3b)[0x4c621b] /home/y/bin/traffic_server[0x5d263c] /home/y/bin/traffic_server(_Z26spdy_on_ctrl_recv_callbackP15spdylay_session18spdylay_frame_typeP13spdylay_framePv+0x6fe)[0x5d33de] /home/y/bin/traffic_server(spdylay_session_on_syn_stream_received+0xe0)[0x718c10] /home/y/bin/traffic_server(spdylay_session_mem_recv+0xb47)[0x719917] /home/y/bin/traffic_server(spdylay_session_recv+0x49)[0x719b49] /home/y/bin/traffic_server[0x5d0aa8] /home/y/bin/traffic_server(_ZN18UnixNetVConnection19readSignalAndUpdateEi+0x27)[0x6ed9e7] /home/y/bin/traffic_server(_ZN17SSLNetVConnection11net_read_ioEP10NetHandlerP7EThread+0xf37)[0x6ddbe7] /home/y/bin/traffic_server(_ZN10NetHandler12mainNetEventEiP5Event+0x1f2)[0x6e5052] /home/y/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x8f)[0x712fef] /home/y/bin/traffic_server(_ZN7EThread7executeEv+0x493)[0x713993] /home/y/bin/traffic_server[0x71239a] /lib64/libpthread.so.0(+0x3297207851)[0x2b64e0a72851] /lib64/libc.so.6(clone+0x6d)[0x3296ee890d] {code} was: After applying patches to ts-2742 (removing the ipv4 assert) and ts-2743 (w/ a temporary fix still using the TS API, before a permanent fix is available), noticed the below new core. NOTE: Traffic Server received Sig 11: Segmentation fault /home/y/bin/traffic_server - STACK TRACE: /lib64/libpthread.so.0(+0x329720f500)[0x2b64e0a7a500] /home/y/bin/traffic_server(_ZN14HttpAcceptCont9mainEventEiPv+0x147)[0x563337] /home/y/bin/traffic_server(_ZN12PluginVCCore17state_send_acceptEiPv+0x9b)[0x4db38b] /home/y/bin/traffic_server(_ZN12PluginVCCore7connectEv+0x23)[0x4db673] /home/y/bin/traffic_server(TSHttpConnectWithProtoStack+0x83)[0x4b4b53] /home/y/bin/traffic_server(_ZN7FetchSM10ext_lanuchEv+0x3b)[0x4c621b] /home/y/bin/traffic_server[0x5d263c] /home/y/bin/traffic_server(_Z26spdy_on_ctrl_recv_callbackP15spdylay_session18spdylay_frame_typeP13spdylay_framePv+0x6fe)[0x5d33de] /home/y/bin/traffic_server(spdylay_session_on_syn_stream_received+0xe0)[0x718c10] /home/y/bin/traffic_server(spdylay_session_mem_recv+0xb47)[0x719917] /home/y/bin/traffic_server(spdylay_session_recv+0x49)[0x719b49] /home/y/bin/traffic_server[0x5d0aa8] /home/y/bin/traffic_server(_ZN18UnixNetVConnection19readSignalAndUpdateEi+0x27)[0x6ed9e7] /home/y/bin/traffic_server(_ZN17SSLNetVConnection11net_read_ioEP10NetHandlerP7EThread+0xf37)[0x6ddbe7] /home/y/bin/traffic_server(_ZN10NetHandler12mainNetEventEiP5Event+0x1f2)[0x6e5052] /home/y/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x8f)[0x712fef] /home/y/bin/traffic_server(_ZN7EThread7executeEv+0x493)[0x713993] /home/y/bin/traffic_server[0x71239a] /lib64/libpthread.so.0(+0x3297207851)[0x2b64e0a72851] /lib64/libc.so.6(clone+0x6d)[0x3296ee890d] Crash with SPDY on production environment in HttpAcceptCont::mainEvent -- Key: TS-2750 URL: https://issues.apache.org/jira/browse/TS-2750 Project: Traffic Server Issue Type: Bug Components: SPDY Reporter: Sudheer Vinukonda Assignee: Yunkai Zhang Labels: SPDY_ATS Fix For: sometime After applying patches to ts-2742 (removing the ipv4 assert) and ts-2743 (w/ a temporary fix still using the TS API, before a permanent fix is available), noticed the below new core. {code} NOTE: Traffic Server received Sig 11: Segmentation fault /home/y/bin/traffic_server - STACK TRACE: /lib64/libpthread.so.0(+0x329720f500)[0x2b64e0a7a500] /home/y/bin/traffic_server(_ZN14HttpAcceptCont9mainEventEiPv+0x147)[0x563337] /home/y/bin/traffic_server(_ZN12PluginVCCore17state_send_acceptEiPv+0x9b)[0x4db38b] /home/y/bin/traffic_server(_ZN12PluginVCCore7connectEv+0x23)[0x4db673] /home/y/bin/traffic_server(TSHttpConnectWithProtoStack+0x83)[0x4b4b53] /home/y/bin/traffic_server(_ZN7FetchSM10ext_lanuchEv+0x3b)[0x4c621b] /home/y/bin/traffic_server[0x5d263c] /home/y/bin/traffic_server(_Z26spdy_on_ctrl_recv_callbackP15spdylay_session18spdylay_frame_typeP13spdylay_framePv+0x6fe)[0x5d33de]
[jira] [Updated] (TS-2750) Crash with SPDY on production environment in HttpAcceptCont::mainEvent
[ https://issues.apache.org/jira/browse/TS-2750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yunkai Zhang updated TS-2750: - Attachment: (was: 0001-TS-2742-FetchSM-can-accept-both-IPv4-and-IPv6-now.patch) Crash with SPDY on production environment in HttpAcceptCont::mainEvent -- Key: TS-2750 URL: https://issues.apache.org/jira/browse/TS-2750 Project: Traffic Server Issue Type: Bug Components: SPDY Reporter: Sudheer Vinukonda Assignee: Yunkai Zhang Labels: SPDY_ATS After applying patches to ts-2742 (removing the ipv4 assert) and ts-2743 (w/ a temporary fix still using the TS API, before a permanent fix is available), noticed the below new core. NOTE: Traffic Server received Sig 11: Segmentation fault /home/y/bin/traffic_server - STACK TRACE: /lib64/libpthread.so.0(+0x329720f500)[0x2b64e0a7a500] /home/y/bin/traffic_server(_ZN14HttpAcceptCont9mainEventEiPv+0x147)[0x563337] /home/y/bin/traffic_server(_ZN12PluginVCCore17state_send_acceptEiPv+0x9b)[0x4db38b] /home/y/bin/traffic_server(_ZN12PluginVCCore7connectEv+0x23)[0x4db673] /home/y/bin/traffic_server(TSHttpConnectWithProtoStack+0x83)[0x4b4b53] /home/y/bin/traffic_server(_ZN7FetchSM10ext_lanuchEv+0x3b)[0x4c621b] /home/y/bin/traffic_server[0x5d263c] /home/y/bin/traffic_server(_Z26spdy_on_ctrl_recv_callbackP15spdylay_session18spdylay_frame_typeP13spdylay_framePv+0x6fe)[0x5d33de] /home/y/bin/traffic_server(spdylay_session_on_syn_stream_received+0xe0)[0x718c10] /home/y/bin/traffic_server(spdylay_session_mem_recv+0xb47)[0x719917] /home/y/bin/traffic_server(spdylay_session_recv+0x49)[0x719b49] /home/y/bin/traffic_server[0x5d0aa8] /home/y/bin/traffic_server(_ZN18UnixNetVConnection19readSignalAndUpdateEi+0x27)[0x6ed9e7] /home/y/bin/traffic_server(_ZN17SSLNetVConnection11net_read_ioEP10NetHandlerP7EThread+0xf37)[0x6ddbe7] /home/y/bin/traffic_server(_ZN10NetHandler12mainNetEventEiP5Event+0x1f2)[0x6e5052] /home/y/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x8f)[0x712fef] /home/y/bin/traffic_server(_ZN7EThread7executeEv+0x493)[0x713993] /home/y/bin/traffic_server[0x71239a] /lib64/libpthread.so.0(+0x3297207851)[0x2b64e0a72851] /lib64/libc.so.6(clone+0x6d)[0x3296ee890d] -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2750) Crash with SPDY on production environment in HttpAcceptCont::mainEvent
[ https://issues.apache.org/jira/browse/TS-2750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2750: -- Fix Version/s: sometime Crash with SPDY on production environment in HttpAcceptCont::mainEvent -- Key: TS-2750 URL: https://issues.apache.org/jira/browse/TS-2750 Project: Traffic Server Issue Type: Bug Components: SPDY Reporter: Sudheer Vinukonda Assignee: Yunkai Zhang Labels: SPDY_ATS Fix For: sometime After applying patches to ts-2742 (removing the ipv4 assert) and ts-2743 (w/ a temporary fix still using the TS API, before a permanent fix is available), noticed the below new core. NOTE: Traffic Server received Sig 11: Segmentation fault /home/y/bin/traffic_server - STACK TRACE: /lib64/libpthread.so.0(+0x329720f500)[0x2b64e0a7a500] /home/y/bin/traffic_server(_ZN14HttpAcceptCont9mainEventEiPv+0x147)[0x563337] /home/y/bin/traffic_server(_ZN12PluginVCCore17state_send_acceptEiPv+0x9b)[0x4db38b] /home/y/bin/traffic_server(_ZN12PluginVCCore7connectEv+0x23)[0x4db673] /home/y/bin/traffic_server(TSHttpConnectWithProtoStack+0x83)[0x4b4b53] /home/y/bin/traffic_server(_ZN7FetchSM10ext_lanuchEv+0x3b)[0x4c621b] /home/y/bin/traffic_server[0x5d263c] /home/y/bin/traffic_server(_Z26spdy_on_ctrl_recv_callbackP15spdylay_session18spdylay_frame_typeP13spdylay_framePv+0x6fe)[0x5d33de] /home/y/bin/traffic_server(spdylay_session_on_syn_stream_received+0xe0)[0x718c10] /home/y/bin/traffic_server(spdylay_session_mem_recv+0xb47)[0x719917] /home/y/bin/traffic_server(spdylay_session_recv+0x49)[0x719b49] /home/y/bin/traffic_server[0x5d0aa8] /home/y/bin/traffic_server(_ZN18UnixNetVConnection19readSignalAndUpdateEi+0x27)[0x6ed9e7] /home/y/bin/traffic_server(_ZN17SSLNetVConnection11net_read_ioEP10NetHandlerP7EThread+0xf37)[0x6ddbe7] /home/y/bin/traffic_server(_ZN10NetHandler12mainNetEventEiP5Event+0x1f2)[0x6e5052] /home/y/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x8f)[0x712fef] /home/y/bin/traffic_server(_ZN7EThread7executeEv+0x493)[0x713993] /home/y/bin/traffic_server[0x71239a] /lib64/libpthread.so.0(+0x3297207851)[0x2b64e0a72851] /lib64/libc.so.6(clone+0x6d)[0x3296ee890d] -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2750) Crash with SPDY on production environment in HttpAcceptCont::mainEvent
[ https://issues.apache.org/jira/browse/TS-2750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yunkai Zhang updated TS-2750: - Attachment: 0001-TS-2742-FetchSM-can-accept-both-IPv4-and-IPv6-now.patch Crash with SPDY on production environment in HttpAcceptCont::mainEvent -- Key: TS-2750 URL: https://issues.apache.org/jira/browse/TS-2750 Project: Traffic Server Issue Type: Bug Components: SPDY Reporter: Sudheer Vinukonda Assignee: Yunkai Zhang Labels: SPDY_ATS Attachments: 0001-TS-2742-FetchSM-can-accept-both-IPv4-and-IPv6-now.patch After applying patches to ts-2742 (removing the ipv4 assert) and ts-2743 (w/ a temporary fix still using the TS API, before a permanent fix is available), noticed the below new core. NOTE: Traffic Server received Sig 11: Segmentation fault /home/y/bin/traffic_server - STACK TRACE: /lib64/libpthread.so.0(+0x329720f500)[0x2b64e0a7a500] /home/y/bin/traffic_server(_ZN14HttpAcceptCont9mainEventEiPv+0x147)[0x563337] /home/y/bin/traffic_server(_ZN12PluginVCCore17state_send_acceptEiPv+0x9b)[0x4db38b] /home/y/bin/traffic_server(_ZN12PluginVCCore7connectEv+0x23)[0x4db673] /home/y/bin/traffic_server(TSHttpConnectWithProtoStack+0x83)[0x4b4b53] /home/y/bin/traffic_server(_ZN7FetchSM10ext_lanuchEv+0x3b)[0x4c621b] /home/y/bin/traffic_server[0x5d263c] /home/y/bin/traffic_server(_Z26spdy_on_ctrl_recv_callbackP15spdylay_session18spdylay_frame_typeP13spdylay_framePv+0x6fe)[0x5d33de] /home/y/bin/traffic_server(spdylay_session_on_syn_stream_received+0xe0)[0x718c10] /home/y/bin/traffic_server(spdylay_session_mem_recv+0xb47)[0x719917] /home/y/bin/traffic_server(spdylay_session_recv+0x49)[0x719b49] /home/y/bin/traffic_server[0x5d0aa8] /home/y/bin/traffic_server(_ZN18UnixNetVConnection19readSignalAndUpdateEi+0x27)[0x6ed9e7] /home/y/bin/traffic_server(_ZN17SSLNetVConnection11net_read_ioEP10NetHandlerP7EThread+0xf37)[0x6ddbe7] /home/y/bin/traffic_server(_ZN10NetHandler12mainNetEventEiP5Event+0x1f2)[0x6e5052] /home/y/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x8f)[0x712fef] /home/y/bin/traffic_server(_ZN7EThread7executeEv+0x493)[0x713993] /home/y/bin/traffic_server[0x71239a] /lib64/libpthread.so.0(+0x3297207851)[0x2b64e0a72851] /lib64/libc.so.6(clone+0x6d)[0x3296ee890d] -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2750) Crash with SPDY on production environment in HttpAcceptCont::mainEvent
[ https://issues.apache.org/jira/browse/TS-2750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudheer Vinukonda updated TS-2750: -- Summary: Crash with SPDY on production environment in HttpAcceptCont::mainEvent (was: SPDY_ATS - Crash with SPDY on production environment in HttpAcceptCont::mainEvent) Crash with SPDY on production environment in HttpAcceptCont::mainEvent -- Key: TS-2750 URL: https://issues.apache.org/jira/browse/TS-2750 Project: Traffic Server Issue Type: Bug Components: SPDY Reporter: Sudheer Vinukonda Labels: SPDY_ATS After applying patches to ts-2742 (removing the ipv4 assert) and ts-2743 (w/ a temporary fix still using the TS API, before a permanent fix is available), noticed the below new core. NOTE: Traffic Server received Sig 11: Segmentation fault /home/y/bin/traffic_server - STACK TRACE: /lib64/libpthread.so.0(+0x329720f500)[0x2b64e0a7a500] /home/y/bin/traffic_server(_ZN14HttpAcceptCont9mainEventEiPv+0x147)[0x563337] /home/y/bin/traffic_server(_ZN12PluginVCCore17state_send_acceptEiPv+0x9b)[0x4db38b] /home/y/bin/traffic_server(_ZN12PluginVCCore7connectEv+0x23)[0x4db673] /home/y/bin/traffic_server(TSHttpConnectWithProtoStack+0x83)[0x4b4b53] /home/y/bin/traffic_server(_ZN7FetchSM10ext_lanuchEv+0x3b)[0x4c621b] /home/y/bin/traffic_server[0x5d263c] /home/y/bin/traffic_server(_Z26spdy_on_ctrl_recv_callbackP15spdylay_session18spdylay_frame_typeP13spdylay_framePv+0x6fe)[0x5d33de] /home/y/bin/traffic_server(spdylay_session_on_syn_stream_received+0xe0)[0x718c10] /home/y/bin/traffic_server(spdylay_session_mem_recv+0xb47)[0x719917] /home/y/bin/traffic_server(spdylay_session_recv+0x49)[0x719b49] /home/y/bin/traffic_server[0x5d0aa8] /home/y/bin/traffic_server(_ZN18UnixNetVConnection19readSignalAndUpdateEi+0x27)[0x6ed9e7] /home/y/bin/traffic_server(_ZN17SSLNetVConnection11net_read_ioEP10NetHandlerP7EThread+0xf37)[0x6ddbe7] /home/y/bin/traffic_server(_ZN10NetHandler12mainNetEventEiP5Event+0x1f2)[0x6e5052] /home/y/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x8f)[0x712fef] /home/y/bin/traffic_server(_ZN7EThread7executeEv+0x493)[0x713993] /home/y/bin/traffic_server[0x71239a] /lib64/libpthread.so.0(+0x3297207851)[0x2b64e0a72851] /lib64/libc.so.6(clone+0x6d)[0x3296ee890d] -- This message was sent by Atlassian JIRA (v6.2#6252)