[jira] [Created] (TS-1715) Possibly range related crashing since upgrading to 3.2.4

["David Carlin (JIRA)" <ji...@apache.org>]

David Carlin created TS-1715:
--------------------------------

             Summary: Possibly range related crashing since upgrading to 3.2.4
                 Key: TS-1715
                 URL: https://issues.apache.org/jira/browse/TS-1715
             Project: Traffic Server
          Issue Type: Bug
          Components: Cache, Core
            Reporter: David Carlin


This might be related to TS-1574

I upgraded one box to 3.2.4, and and I am experiencing the following crash approximately twice a day:

Backtraces - the first happens more frequently:

#0  RangeTransform::transform_to_range (this=0x2b40e40973d0) at Transform.cc:843
#1  0x00000000004e52e8 in RangeTransform::handle_event (this=0x2b40e40973d0, event=<value optimized out>, edata=<value optimized out>) at Transform.cc:816
#2  0x00000000006970f4 in handleEvent (this=0x2b40b9762010, e=0x2b40dc47f9e0, calling_code=1) at I_Continuation.h:146
#3  EThread::process_event (this=0x2b40b9762010, e=0x2b40dc47f9e0, calling_code=1) at UnixEThread.cc:142
#4  0x0000000000697b6b in EThread::execute (this=0x2b40b9762010) at UnixEThread.cc:191
#5  0x00000000006960c2 in spawn_thread_internal (a=0x15e04a0) at Thread.cc:88
#6  0x00000031f8c07851 in start_thread () from /lib64/libpthread.so.0
#7  0x00000031f88e76dd in clone () from /lib64/libc.so.6

#0  RangeTransform::transform_to_range (this=0x2b11441773f0) at Transform.cc:843
#1  0x00000000004e52e8 in RangeTransform::handle_event (this=0x2b11441773f0, event=<value optimized out>, edata=<value optimized out>) at Transform.cc:816
#2  0x00000000006970f4 in handleEvent (this=0x2b109f266010, e=0x2b110006f360, calling_code=1) at I_Continuation.h:146
#3  EThread::process_event (this=0x2b109f266010, e=0x2b110006f360, calling_code=1) at UnixEThread.cc:142
#4  0x0000000000697b6b in EThread::execute (this=0x2b109f266010) at UnixEThread.cc:191
#5  0x00000000004c28c9 in main (argc=<value optimized out>, argv=<value optimized out>) at Main.cc:1822

>From /var/log/messages:

Feb 16 11:43:26 l4 kernel: [ET_NET 18][16876]: segfault at 155 ip
0000000000567571 sp 00002b04d1412b40 error 4 in
traffic_server[400000+341000]

>From traffic.out:

NOTE: Traffic Server received Sig 11: Segmentation fault
/home/y/bin/traffic_server - STACK TRACE:
/lib64/libpthread.so.0[0x31f8c0f500]
/home/y/bin/traffic_server(_ZN10HttpTunnel15chain_abort_allEP18HttpTunnelPr
oducer+0xe1)[0x567571]
/home/y/bin/traffic_server(_ZN6HttpSM17tunnel_handler_uaEiP18HttpTunnelCons
umer+0x354)[0x5205b4]
/home/y/bin/traffic_server(_ZN10HttpTunnel16consumer_handlerEiP18HttpTunnel
Consumer+0x96)[0x56b716]
/home/y/bin/traffic_server(_ZN10HttpTunnel12main_handlerEiPv+0x11d)[0x56bf6
d]
/home/y/bin/traffic_server(_ZN6HttpSM28state_watch_for_client_abortEiPv+0x2
aa)[0x523d2a]
/home/y/bin/traffic_server(_ZN6HttpSM12main_handlerEiPv+0xe8)[0x52b2f8]
/home/y/bin/traffic_server[0x672b5b]
/home/y/bin/traffic_server(_ZN18UnixNetVConnection9mainEventEiP5Event+0x5df
)[0x674f5f]
/home/y/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0xb4)[0x6970
f4]
/home/y/bin/traffic_server(_ZN7EThread7executeEv+0x633)[0x697bf3]
/home/y/bin/traffic_server[0x6960c2]
/lib64/libpthread.so.0[0x31f8c07851]
/lib64/libc.so.6(clone+0x6d)[0x31f88e76dd]
[Feb 16 11:43:27.240] Manager {0x7f217b8d07e0} FATAL:
[LocalManager::pollMgmtProcessServer] Error in read (errno: 104)
[Feb 16 11:43:27.240] Manager {0x7f217b8d07e0} FATAL:  (last system error
104: Connection reset by peer)
[Feb 16 11:43:27.240] Manager {0x7f217b8d07e0} NOTE:
[LocalManager::mgmtShutdown] Executing shutdown request.
[Feb 16 11:43:27.240] Manager {0x7f217b8d07e0} NOTE:
[LocalManager::processShutdown] Executing process shutdown request.
[Feb 16 11:43:27.241] Manager {0x7f217b8d07e0} ERROR:
[LocalManager::sendMgmtMsgToProcesses] Error writing message
[Feb 16 11:43:27.241] Manager {0x7f217b8d07e0} ERROR:  (last system error
32: Broken pipe)


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