hi, i install  libunwind7-dev  package and recompile ats, but the crash.log 
stail says:
Unable to retrieve backtrace: [12] Operation not supported on this platform.

my server environment:
Process:            [ET_NET 0] [4761]
File:               /usr/local/trafficserver-6.0.0/bin/traffic_server
Version:            Traffic Server 6.0.0
System Version:     Linux x86_64 #1 SMP Debian 3.2.65-1 3.2.0-4-amd64
Date:               Mon, 28 Sep 2015 15:24:12 +0800


##################################

the way i use to reproduce the crash:
ab -c 10000 -n 2000000 http://x.y.com/






在 2015-09-24 23:39:32,"James Peach" <[email protected]> 写道:




On Sep 24, 2015, at 7:32 AM, Brian Geffon <[email protected]> wrote:


Unfortunately that crash log is missing the most important piece of information 
because apparently backtraces aren't supported on your platform, James, any 
ideas why that is? 


Probably no libunwind-devel at build time?




Are you familiar with GDB by any chance?


On Thursday, September 24, 2015, Esmq <[email protected]> wrote:

hi, the attachment is the crash.log


-r-------- 1 root          trafficserver  87K  9月 24 20:00 
crash-2015-09-24-200057.log
-r-------- 1 root          trafficserver  88K  9月 24 20:01 
crash-2015-09-24-200103.log
-r-------- 1 root          trafficserver  90K  9月 24 20:02 
crash-2015-09-24-200208.log
-r-------- 1 root          trafficserver  74K  9月 24 20:02 
crash-2015-09-24-200215.log
-r-------- 1 root          trafficserver  73K  9月 24 20:02 
crash-2015-09-24-200221.log
-r-------- 1 root          trafficserver  73K  9月 24 20:02 
crash-2015-09-24-200227.log
-r-------- 1 root          trafficserver  73K  9月 24 20:02 
crash-2015-09-24-200233.log
-r-------- 1 root          trafficserver  90K  9月 24 20:03 
crash-2015-09-24-200344.log
-r-------- 1 root          trafficserver  73K  9月 24 20:03 
crash-2015-09-24-200350.log
-r-------- 1 root          trafficserver  74K  9月 24 20:03 
crash-2015-09-24-200356.log
-r-------- 1 root          trafficserver  73K  9月 24 20:04 
crash-2015-09-24-200402.log
-r-------- 1 root          trafficserver  90K  9月 24 20:05 
crash-2015-09-24-200524.log
-r-------- 1 root          trafficserver  87K  9月 24 20:05 
crash-2015-09-24-200530.log
-r-------- 1 root          trafficserver  87K  9月 24 20:05 
crash-2015-09-24-200536.log
-r-------- 1 root          trafficserver  87K  9月 24 20:05 
crash-2015-09-24-200542.log
-r-------- 1 root          trafficserver  90K  9月 24 20:07 
crash-2015-09-24-200723.log
-r-------- 1 root          trafficserver  73K  9月 24 20:07 
crash-2015-09-24-200730.log
-r-------- 1 root          trafficserver  73K  9月 24 20:07 
crash-2015-09-24-200736.log


At 2015-09-24 10:21:35, "Esmq" <[email protected]> wrote:

i will redeploy v6 on my production environment today,
if any cores or crashlog, i'll attach here.

PS. crash is hard to trigger,
and it seems like to concurrent connections.



At 2015-09-24 01:36:57, "James Peach" <[email protected]> wrote:
>
>> On Sep 23, 2015, at 8:41 AM, Leif Hedstrom <[email protected]> wrote:
>> 
>>> 
>>> On Sep 23, 2015, at 1:15 AM, Esmq <[email protected]> wrote:
>>> 
>>> hi,all
>>> after upgrade to ats v6, i observed ats crash for several times on all of 
>>> my servers.
>>> and it seems that when crash,  it will crash again in 2 minutes.
>>> 
>>> grep enabled diags.log 
>>> [Sep 14 12:02:54.705] Server {0x2b6938756700} NOTE: cache enabled
>>> [Sep 14 12:04:05.086] Server {0x2b6b1c76c700} NOTE: cache enabled
>>> [Sep 14 12:58:31.390] Server {0x2b13966fa700} NOTE: cache enabled
>>> [Sep 14 12:58:37.324] Server {0x2b8681047700} NOTE: cache enabled
>>> [Sep 14 13:00:48.937] Server {0x2ad1405be700} NOTE: cache enabled
>>> 
>> 
>> 
>> Did you get a core file? Also, please file a Jira. This looks like it might 
>> be related to the new connection management features? bcall?
>
>Please also attach the crash log (after reviewing it for any information you 
>don't want made public!)
>
>
>> 
>> — Leif
>> 
>> 
>>> following is crash log in traffic.out,
>>> ##################################################################
>>> traffic_server: Segmentation fault (Address not mapped to object [0x20])
>>> traffic_server - STACK TRACE:
>>> /usr/local/trafficserver-6.0.0/bin/traffic_server(_Z19crash_logger_invokeiP7siginfoPv+0x99)[0x4bce49]
>>> /lib/x86_64-linux-gnu/libc.so.6(+0x321e0)[0x2af280d3d1e0]
>>> /usr/local/trafficserver-6.0.0/bin/traffic_server(_ZN18UnixNetVConnection9mainEventEiP5Event+0x30)[0x72f130]
>>> /usr/local/trafficserver-6.0.0/bin/traffic_server(_ZN10NetHandler9_close_vcEP18UnixNetVConnectionlRiS2_S2_S2_+0x20f)[0x7232bf]
>>> /usr/local/trafficserver-6.0.0/bin/traffic_server(_ZN10NetHandler23manage_keep_alive_queueEv+0x9d)[0x7234ad]
>>> /usr/local/trafficserver-6.0.0/bin/traffic_server(_ZN17HttpClientSession7releaseEP14IOBufferReader+0x1eb)[0x58b4ab]
>>> /usr/local/trafficserver-6.0.0/bin/traffic_server(_ZN6HttpSM17tunnel_handler_uaEiP18HttpTunnelConsumer+0x265)[0x598a35]
>>> /usr/local/trafficserver-6.0.0/bin/traffic_server(_ZN10HttpTunnel16consumer_handlerEiP18HttpTunnelConsumer+0x9f)[0x5e71ff]
>>> /usr/local/trafficserver-6.0.0/bin/traffic_server(_ZN10HttpTunnel12main_handlerEiPv+0x110)[0x5e76b0]
>>> /usr/local/trafficserver-6.0.0/bin/traffic_server(_Z15write_to_net_ioP10NetHandlerP18UnixNetVConnectionP7EThread+0x12e1)[0x730a11]
>>> /usr/local/trafficserver-6.0.0/bin/traffic_server(_ZN10NetHandler12mainNetEventEiP5Event+0x273)[0x722a83]
>>> /usr/local/trafficserver-6.0.0/bin/traffic_server(_ZN7EThread7executeEv+0x8b0)[0x752dc0]
>>> /usr/local/trafficserver-6.0.0/bin/traffic_server(main+0x14cf)[0x4a5aaf]
>>> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd)[0x2af280d29ead]
>>> /usr/local/trafficserver-6.0.0/bin/traffic_server[0x4aad1d]
>>> traffic_server: using root directory '/usr/local/trafficserver-6.0.0'
>>> traffic_server: Segmentation fault (Address not mapped to object [0x20])
>>> traffic_server - STACK TRACE:
>>> /usr/local/trafficserver-6.0.0/bin/traffic_server(_Z19crash_logger_invokeiP7siginfoPv+0x99)[0x4bce49]
>>> /lib/x86_64-linux-gnu/libc.so.6(+0x321e0)[0x2b6ca31a01e0]
>>> /usr/local/trafficserver-6.0.0/bin/traffic_server(_ZN18UnixNetVConnection9mainEventEiP5Event+0x30)[0x72f130]
>>> /usr/local/trafficserver-6.0.0/bin/traffic_server(_ZN10NetHandler9_close_vcEP18UnixNetVConnectionlRiS2_S2_S2_+0x20f)[0x7232bf]
>>> /usr/local/trafficserver-6.0.0/bin/traffic_server(_ZN10NetHandler23manage_keep_alive_queueEv+0x9d)[0x7234ad]
>>> /usr/local/trafficserver-6.0.0/bin/traffic_server(_ZN17HttpClientSession7releaseEP14IOBufferReader+0x1eb)[0x58b4ab]
>>> /usr/local/trafficserver-6.0.0/bin/traffic_server(_ZN6HttpSM17tunnel_handler_uaEiP18HttpTunnelConsumer+0x265)[0x598a35]
>>> /usr/local/trafficserver-6.0.0/bin/traffic_server(_ZN10HttpTunnel16consumer_handlerEiP18HttpTunnelConsumer+0x9f)[0x5e71ff]
>>> /usr/local/trafficserver-6.0.0/bin/traffic_server(_ZN10HttpTunnel12main_handlerEiPv+0x110)[0x5e76b0]
>>> /usr/local/trafficserver-6.0.0/bin/traffic_server(_Z15write_to_net_ioP10NetHandlerP18UnixNetVConnectionP7EThread+0x12e1)[0x730a11]
>>> /usr/local/trafficserver-6.0.0/bin/traffic_server(_ZN10NetHandler12mainNetEventEiP5Event+0x273)[0x722a83]
>>> /usr/local/trafficserver-6.0.0/bin/traffic_server(_ZN7EThread7executeEv+0x8b0)[0x752dc0]
>>> /usr/local/trafficserver-6.0.0/bin/traffic_server[0x75141a]
>>> /lib/x86_64-linux-gnu/libpthread.so.0(+0x6b50)[0x2b6ca3500b50]
>>> /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x2b6ca324a70d]
>>> traffic_server: using root directory '/usr/local/trafficserver-6.0.0'
>





 





 

Reply via email to