You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2013/05/29 23:50:21 UTC

[jira] [Updated] (TS-1711) Crash on NetHandler::mainNetEvent

     [ https://issues.apache.org/jira/browse/TS-1711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leif Hedstrom updated TS-1711:
------------------------------

    Fix Version/s:     (was: 3.3.3)
                   3.3.4
    
> Crash on NetHandler::mainNetEvent
> ---------------------------------
>
>                 Key: TS-1711
>                 URL: https://issues.apache.org/jira/browse/TS-1711
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Clustering, Logging, Network
>    Affects Versions: 3.2.4, 3.2.0
>            Reporter: Andrew Younan
>             Fix For: 3.3.4
>
>
> ATS 3.2.0 is installed on two RHEL6.2 nodes in cluster mode. IMHO, issue is not resolved in 3.2.4 as I can see.
> Two crashes are taking place: 1) One as described in Bug TS-1686 (https://issues.apache.org/jira/browse/TS-1686) and the other one below upon the mainNetEvent.
> For issue TS-1686, once logging was disabled the crashes did not reoccur. The below still occurs. Both are must fix.
> NOTE: Traffic Server received Sig 11: Segmentation fault
> /usr/bin/traffic_server - STACK TRACE:
> /lib64/libpthread.so.0[0x3caf80f4a0]
> /usr/bin/traffic_server[0x67697c]
> /usr/bin/traffic_server(_ZN10NetHandler12mainNetEventEiP5Event+0x1f2)[0x66e0f2]
> /usr/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0xb4)[0x696d04]
> /usr/bin/traffic_server(_ZN7EThread7executeEv+0x4c3)[0x697693]
> /usr/bin/traffic_server[0x695cd2]
> /lib64/libpthread.so.0[0x3caf8077f1]
> /lib64/libc.so.6(clone+0x6d)[0x3caf4e570d]
> Coredump currently being analyzed (cannot be provided at the moment - 9GB); your assistance is urgently needed.
> Thanks,
> Andrew

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira