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

James Peach updated TS-1603:
----------------------------

    Labels: crash  (was: )
    
> crash at ClusterHandler::mainClusterEvent
> -----------------------------------------
>
>                 Key: TS-1603
>                 URL: https://issues.apache.org/jira/browse/TS-1603
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Clustering
>    Affects Versions: 3.2.0
>            Reporter: Bin Chen
>            Assignee: Bin Chen
>              Labels: crash
>
> {code}
> #0  0x00000000006556c4 in ClusterHandler::mainClusterEvent 
> (this=0x2ab444c1e4e0, event=2, e=0x0) at ClusterHandler.cc:2469
> /usr/src/debug/trafficserver-3.2.0/iocore/cluster/ClusterHandler.cc:2469:81142:beg:0x6556c4
> Missing separate debuginfos, use: debuginfo-install 
> expat-2.0.1-9.1.el6.x86_64 glibc-2.12-1.47.el6.x86_64 
> keyutils-libs-1.4-3.el6.x86_64 krb5-libs-1.9-22.el6.x86_64 
> libcom_err-1.41.12-11.el6.x86_64 libgcc-4.4.6-3.el6.x86_64 
> libselinux-2.0.94-5.2.el6.x86_64 libstdc++-4.4.6-3.el6.x86_64 
> ncurses-libs-5.7-3.20090208.el6.x86_64 openssl-1.0.0-20.el6.x86_64 
> pcre-7.8-3.1.el6.x86_64 readline-6.0-3.el6.x86_64 tcl-8.5.7-6.el6.x86_64 
> xz-libs-4.999.9-0.3.beta.20091007git.el6.x86_64 zlib-1.2.3-27.el6.x86_64
> (gdb) bt
> #0  0x00000000006556c4 in ClusterHandler::mainClusterEvent 
> (this=0x2ab444c1e4e0, event=2, e=0x0) at ClusterHandler.cc:2469
> #1  0x000000000065d6a3 in ClusterHandler::protoZombieEvent 
> (this=0x2ab444c1e4e0, event=1, e=0x0)
>     at ClusterHandlerBase.cc:1219
> #2  0x00000000004e6fae in Continuation::handleEvent (this=0x2ab444c1e4e0, 
> event=1, data=0x0)
>     at ../iocore/eventsystem/I_Continuation.h:146
> #3  0x000000000065b081 in ClusterState::IOComplete (this=0x2ab444c1e840) at 
> ClusterHandlerBase.cc:584
> #4  0x000000000065ae1a in ClusterState::doIO_read_event (this=0x2ab444c1e840, 
> event=104, d=0x2ab3613601d8)
>     at ClusterHandlerBase.cc:496
> #5  0x00000000004e6fae in Continuation::handleEvent (this=0x2ab444c1e840, 
> event=104, data=0x2ab3613601d8)
>     at ../iocore/eventsystem/I_Continuation.h:146
> #6  0x00000000006b806c in read_signal_and_update (event=104, 
> vc=0x2ab3613600d0) at UnixNetVConnection.cc:129
> #7  0x00000000006b81bd in read_signal_done (event=104, nh=0x2ab35f1211e8, 
> vc=0x2ab3613600d0) at UnixNetVConnection.cc:159
> #8  0x00000000006b8707 in read_from_net (nh=0x2ab35f1211e8, 
> vc=0x2ab3613600d0, thread=0x2ab35f11e010)
>     at UnixNetVConnection.cc:282
> #9  0x00000000006ba351 in UnixNetVConnection::net_read_io 
> (this=0x2ab3613600d0, nh=0x2ab35f1211e8, lthread=0x2ab35f11e010)
>     at UnixNetVConnection.cc:802
> #10 0x00000000006b5064 in NetHandler::mainNetEvent (this=0x2ab35f1211e8, 
> event=5, e=0x2ab33c536dd0) at UnixNet.cc:337
> #11 0x00000000004e6fae in Continuation::handleEvent (this=0x2ab35f1211e8, 
> event=5, data=0x2ab33c536dd0)
>     at ../iocore/eventsystem/I_Continuation.h:146
> #12 0x00000000006d99b8 in EThread::process_event (this=0x2ab35f11e010, 
> e=0x2ab33c536dd0, calling_code=5)
>     at UnixEThread.cc:189
> #13 0x00000000006d9e55 in EThread::execute (this=0x2ab35f11e010) at 
> UnixEThread.cc:301
> #14 0x00000000006d89e7 in spawn_thread_internal (a=0x2ab344334f20) at 
> Thread.cc:88
> #15 0x00000037a14077f1 in start_thread () from /lib64/libpthread.so.0
> #16 0x00000037a10e570d in clone () from /lib64/libc.so.6
> (gdb) f 0
> #0  0x00000000006556c4 in ClusterHandler::mainClusterEvent 
> (this=0x2ab444c1e4e0, event=2, e=0x0) at ClusterHandler.cc:2469
> /usr/src/debug/trafficserver-3.2.0/iocore/cluster/ClusterHandler.cc:2469:81142:beg:0x6556c4
> (gdb) l
> 2464      thread = (EThread *) e;
> 2465    } else {
> 2466      if (io_callback) {
> 2467        thread = this_ethread();
> 2468      } else {
> 2469        thread = e->ethread;
> 2470      }
> 2471    }
> 2472  
> 2473    int io_activity = 1;
> (gdb) p e
> $1 = (Event *) 0x0
> {code}

--
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

Reply via email to