Jan-Frode Myklebust created TS-1618:
---------------------------------------
Summary: crash with 3.2.3
Key: TS-1618
URL: https://issues.apache.org/jira/browse/TS-1618
Project: Traffic Server
Issue Type: Bug
Reporter: Jan-Frode Myklebust
We're seeing crashes with 3.2.3 on RHEL6...
NOTE: Traffic Server received Sig 11: Segmentation fault
/usr/bin/traffic_server - STACK TRACE:
/lib64/libpthread.so.0(+0xf500)[0x2b73de262500]
/usr/bin/traffic_server(_ZN7CacheVC16is_pread_capableEv+0x7)[0x628db7]
/usr/bin/traffic_server(_ZN6HttpSM27do_range_setup_if_necessaryEv+0x1d0)[0x523270]
/usr/bin/traffic_server(_ZN12HttpTransact25build_response_from_cacheEPNS_5StateE15HTTPWarningCode+0x242)[0x552672]
/usr/bin/traffic_server(_ZN12HttpTransact22HandleCacheOpenReadHitEPNS_5StateE+0x4e1)[0x553711]
/usr/bin/traffic_server(_ZN6HttpSM32call_transact_and_set_next_stateEPFvPN12HttpTransact5StateEE+0x62)[0x51af92]
/usr/bin/traffic_server(_ZN6HttpSM17handle_api_returnEv+0x31a)[0x534b8a]
/usr/bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x18a)[0x5334ea]
/usr/bin/traffic_server(_ZN6HttpSM17handle_api_returnEv+0x31a)[0x534b8a]
/usr/bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x18a)[0x5334ea]
/usr/bin/traffic_server(_ZN6HttpSM21state_cache_open_readEiPv+0xfe)[0x5291be]
/usr/bin/traffic_server(_ZN6HttpSM12main_handlerEiPv+0xe8)[0x52b558]
/usr/bin/traffic_server(_ZN11HttpCacheSM21state_cache_open_readEiPv+0x1a2)[0x50a912]
/usr/bin/traffic_server(_ZN7CacheVC8callcontEi+0x27)[0x64af07]
/usr/bin/traffic_server(_ZN7CacheVC17openReadStartHeadEiP5Event+0x7e2)[0x646b42]
/usr/bin/traffic_server(_ZN5Cache9open_readEP12ContinuationP7INK_MD5P7HTTPHdrP21CacheLookupHttpConfig13CacheFragTypePci+0x383)[0x647843]
/usr/bin/traffic_server(_ZN14CacheProcessor9open_readEP12ContinuationP3URLP7HTTPHdrP21CacheLookupHttpConfigl13CacheFragType+0x158)[0x624dd8]
/usr/bin/traffic_server(_ZN11HttpCacheSM9open_readEP3URLP7HTTPHdrP21CacheLookupHttpConfigl+0x84)[0x50a364]
/usr/bin/traffic_server(_ZN6HttpSM24do_cache_lookup_and_readEv+0xf3)[0x51c263]
/usr/bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x6d1)[0x533a31]
/usr/bin/traffic_server(_ZN6HttpSM17handle_api_returnEv+0x31a)[0x534b8a]
/usr/bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x18a)[0x5334ea]
/usr/bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x7c4)[0x533b24]
/usr/bin/traffic_server(_ZN6HttpSM17handle_api_returnEv+0x31a)[0x534b8a]
/usr/bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x18a)[0x5334ea]
/usr/bin/traffic_server(_ZN6HttpSM17handle_api_returnEv+0x31a)[0x534b8a]
/usr/bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x18a)[0x5334ea]
/usr/bin/traffic_server(_ZN6HttpSM32state_read_client_request_headerEiPv+0x6b7)[0x52d527]
/usr/bin/traffic_server(_ZN6HttpSM12main_handlerEiPv+0xe8)[0x52b558]
/usr/bin/traffic_server(_ZN18UnixNetVConnection19readSignalAndUpdateEi+0x27)[0x6724a7]
/usr/bin/traffic_server(_ZN17SSLNetVConnection11net_read_ioEP10NetHandlerP7EThread+0x832)[0x666bc2]
/usr/bin/traffic_server(_ZN10NetHandler12mainNetEventEiP5Event+0x1f2)[0x66da12]
/usr/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0xb4)[0x6966e4]
/usr/bin/traffic_server(_ZN7EThread7executeEv+0x4c3)[0x697073]
/usr/bin/traffic_server[0x6956b2]
/lib64/libpthread.so.0(+0x7851)[0x2b73de25a851]
/lib64/libc.so.6(clone+0x6d)[0x2b73e06e467d]
[Dec 11 15:55:04.099] Manager {0x7f2ef4f7d7e0} FATAL:
[LocalManager::pollMgmtProcessServer] Error in read (errno: 104)
[Dec 11 15:55:04.099] Manager {0x7f2ef4f7d7e0} FATAL: (last system error 104:
Connection reset by peer)
[Dec 11 15:55:04.099] Manager {0x7f2ef4f7d7e0} NOTE:
[LocalManager::mgmtShutdown] Executing shutdown request.
[Dec 11 15:55:04.099] Manager {0x7f2ef4f7d7e0} NOTE:
[LocalManager::processShutdown] Executing process shutdown request.
[Dec 11 15:55:04.100] Manager {0x7f2ef4f7d7e0} ERROR:
[LocalManager::sendMgmtMsgToProcesses] Error writing message
[Dec 11 15:55:04.100] Manager {0x7f2ef4f7d7e0} ERROR: (last system error 32:
Broken pipe)
Please let me know if there's anything else I can provide to debug this.
--
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
