[jira] [Updated] (TS-4816) ATS 6.2.0 - crashing with broken pipe, sig11 segmentation fault

2016-09-09 Thread David Brodin (JIRA)

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

David Brodin updated TS-4816:
-
Attachment: gdb-traffic_server-160909.txt

Hi [-zwoop] and [-jamespeach], {{traffic_server}} just crashed, I got some 
output from gdbs {{bt}} and {{info locals}}. I'm attaching the output in the 
file {{gdb-traffic_server-160909.txt}}.

> ATS 6.2.0 - crashing with broken pipe, sig11 segmentation fault
> ---
>
> Key: TS-4816
> URL: https://issues.apache.org/jira/browse/TS-4816
> Project: Traffic Server
>  Issue Type: Bug
>  Components: Manager
>Reporter: David Brodin
>  Labels: crash
> Fix For: 7.0.0
>
> Attachments: ats_gdb-160905.txt, ats_manager-gdb-160906.txt, 
> crash-2016-09-05-075309.log, est_socks-ats_6.2.0.png, 
> gdb-traffic_server-160909.txt
>
>
> Hi,
> We just upgraded to ATS 6.2.0 via FreeBSD ports:
> {noformat}
> [root@ ~]# uname -a
> FreeBSD  10.3-RELEASE-p7 FreeBSD 10.3-RELEASE-p7 #0: Thu Aug 11 
> 18:38:15 UTC 2016 
> r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64
> [root@ ~]# pkg info | grep traff
> trafficserver-6.2.0Fast, scalable and extensible HTTP proxy server
> {noformat}
> We are experiencing crashes, usually during the day, hardly any during "low" 
> loads, but the mest affecting crashes occur in the early mornings. Along with 
> this we can see a memory leak aswell
> We are using ATS as an enterprise proxy to the Internet, and as we have a 
> very good Internet-connection we have also disabled caching.
> I'm not sure how I would attach files so here goes :)
> manager.log
> {noformat}
> [Sep  2 11:48:28.017] Manager {0x804006400} ERROR: 
> [LocalManager::sendMgmtMsgToProcesses] Error writing message
> [Sep  2 11:48:28.017] Manager {0x804006400} ERROR:  (mgmt_elog)>  (last system error 32: Broken pipe)
> [Sep  2 11:48:38.305] {0x804006400} STATUS: opened 
> /var/log/trafficserver/manager.log
> [Sep  2 11:48:38.305] {0x804006400} NOTE:  (reconfigure_diags)> updated diags config
> [Sep  2 11:48:38.311] Manager {0x804006400} NOTE: [ClusterCom::ClusterCom] 
> Node running on OS: 'FreeBSD' Release: '10.3-RELEASE-p7'
> [Sep  2 11:48:38.312] Manager {0x804006400} NOTE: 
> [LocalManager::listenForProxy] Listening on port: 8080 (IPv4)
> [Sep  2 11:48:38.313] Manager {0x804006400} NOTE: 
> [LocalManager::listenForProxy] Listening on port: 8080 (IPv6)
> [Sep  2 11:48:38.313] Manager {0x804006400} NOTE: [TrafficManager] Setup 
> complete
> [Sep  2 11:48:39.321] Manager {0x804006400} NOTE: [LocalManager::startProxy] 
> Launching ts process
> [Sep  2 11:48:39.336] Manager {0x804006400} NOTE: 
> [LocalManager::pollMgmtProcessServer] New process connecting fd '17'
> [Sep  2 11:48:39.336] Manager {0x804006400} NOTE: [Alarms::signalAlarm] 
> Server Process born
> [Sep  2 11:51:32.574] Manager {0x804006400} ERROR: 
> [LocalManager::sendMgmtMsgToProcesses] Error writing message
> [Sep  2 11:51:32.574] Manager {0x804006400} ERROR:  (mgmt_elog)>  (last system error 32: Broken pipe)
> [Sep  2 11:51:32.669] Manager {0x804006400} ERROR: 
> [LocalManager::pollMgmtProcessServer] Server Process terminated due to Sig 
> 11: Segmentation fault
> [Sep  2 11:51:32.669] Manager {0x804006400} ERROR: [Alarms::signalAlarm] 
> Server Process was reset
> [Sep  2 11:51:33.674] Manager {0x804006400} NOTE: [LocalManager::startProxy] 
> Launching ts process
> [Sep  2 11:51:33.689] Manager {0x804006400} NOTE: 
> [LocalManager::pollMgmtProcessServer] New process connecting fd '13'
> [Sep  2 11:51:33.690] Manager {0x804006400} NOTE: [Alarms::signalAlarm] 
> Server Process born
> [Sep  3 04:14:35.380] Manager {0x804006400} ERROR: 
> [LocalManager::sendMgmtMsgToProcesses] Error writing message
> [Sep  3 04:14:35.380] Manager {0x804006400} ERROR:  (mgmt_elog)>  (last system error 32: Broken pipe)
> [Sep  3 04:14:35.748] Manager {0x804006400} ERROR: 
> [LocalManager::pollMgmtProcessServer] Server Process terminated due to Sig 
> 11: Segmentation fault
> [Sep  3 04:14:35.748] Manager {0x804006400} ERROR: [Alarms::signalAlarm] 
> Server Process was reset
> [Sep  3 04:14:36.814] Manager {0x804006400} NOTE: [LocalManager::startProxy] 
> Launching ts process
> [Sep  3 04:14:36.828] Manager {0x804006400} NOTE: 
> [LocalManager::pollMgmtProcessServer] New process connecting fd '13'
> [Sep  3 04:14:36.829] Manager {0x804006400} NOTE: [Alarms::signalAlarm] 
> Server Process born
> {noformat}
> traffic.out - since this isnt timestamped I'm not sure if I'm leaving some of 
> the stacktrace out:
> {noformat}
> traffic_server[TrafficManager] ==> Cleaning up and reissuing signal #15
> : Terminated
> traffic_server: Terminatedtraffic_servertraffic_servertraffic_server: 
> Segmentation fault
> traffic_server - STACK TRACE:
> 0x4af409 

[jira] [Updated] (TS-4816) ATS 6.2.0 - crashing with broken pipe, sig11 segmentation fault

2016-09-07 Thread David Brodin (JIRA)

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

David Brodin updated TS-4816:
-
Attachment: ats_manager-gdb-160906.txt

> ATS 6.2.0 - crashing with broken pipe, sig11 segmentation fault
> ---
>
> Key: TS-4816
> URL: https://issues.apache.org/jira/browse/TS-4816
> Project: Traffic Server
>  Issue Type: Bug
>  Components: Manager
>Reporter: David Brodin
>  Labels: crash
> Fix For: 7.0.0
>
> Attachments: ats_gdb-160905.txt, ats_manager-gdb-160906.txt, 
> crash-2016-09-05-075309.log, est_socks-ats_6.2.0.png
>
>
> Hi,
> We just upgraded to ATS 6.2.0 via FreeBSD ports:
> {noformat}
> [root@ ~]# uname -a
> FreeBSD  10.3-RELEASE-p7 FreeBSD 10.3-RELEASE-p7 #0: Thu Aug 11 
> 18:38:15 UTC 2016 
> r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64
> [root@ ~]# pkg info | grep traff
> trafficserver-6.2.0Fast, scalable and extensible HTTP proxy server
> {noformat}
> We are experiencing crashes, usually during the day, hardly any during "low" 
> loads, but the mest affecting crashes occur in the early mornings. Along with 
> this we can see a memory leak aswell
> We are using ATS as an enterprise proxy to the Internet, and as we have a 
> very good Internet-connection we have also disabled caching.
> I'm not sure how I would attach files so here goes :)
> manager.log
> {noformat}
> [Sep  2 11:48:28.017] Manager {0x804006400} ERROR: 
> [LocalManager::sendMgmtMsgToProcesses] Error writing message
> [Sep  2 11:48:28.017] Manager {0x804006400} ERROR:  (mgmt_elog)>  (last system error 32: Broken pipe)
> [Sep  2 11:48:38.305] {0x804006400} STATUS: opened 
> /var/log/trafficserver/manager.log
> [Sep  2 11:48:38.305] {0x804006400} NOTE:  (reconfigure_diags)> updated diags config
> [Sep  2 11:48:38.311] Manager {0x804006400} NOTE: [ClusterCom::ClusterCom] 
> Node running on OS: 'FreeBSD' Release: '10.3-RELEASE-p7'
> [Sep  2 11:48:38.312] Manager {0x804006400} NOTE: 
> [LocalManager::listenForProxy] Listening on port: 8080 (IPv4)
> [Sep  2 11:48:38.313] Manager {0x804006400} NOTE: 
> [LocalManager::listenForProxy] Listening on port: 8080 (IPv6)
> [Sep  2 11:48:38.313] Manager {0x804006400} NOTE: [TrafficManager] Setup 
> complete
> [Sep  2 11:48:39.321] Manager {0x804006400} NOTE: [LocalManager::startProxy] 
> Launching ts process
> [Sep  2 11:48:39.336] Manager {0x804006400} NOTE: 
> [LocalManager::pollMgmtProcessServer] New process connecting fd '17'
> [Sep  2 11:48:39.336] Manager {0x804006400} NOTE: [Alarms::signalAlarm] 
> Server Process born
> [Sep  2 11:51:32.574] Manager {0x804006400} ERROR: 
> [LocalManager::sendMgmtMsgToProcesses] Error writing message
> [Sep  2 11:51:32.574] Manager {0x804006400} ERROR:  (mgmt_elog)>  (last system error 32: Broken pipe)
> [Sep  2 11:51:32.669] Manager {0x804006400} ERROR: 
> [LocalManager::pollMgmtProcessServer] Server Process terminated due to Sig 
> 11: Segmentation fault
> [Sep  2 11:51:32.669] Manager {0x804006400} ERROR: [Alarms::signalAlarm] 
> Server Process was reset
> [Sep  2 11:51:33.674] Manager {0x804006400} NOTE: [LocalManager::startProxy] 
> Launching ts process
> [Sep  2 11:51:33.689] Manager {0x804006400} NOTE: 
> [LocalManager::pollMgmtProcessServer] New process connecting fd '13'
> [Sep  2 11:51:33.690] Manager {0x804006400} NOTE: [Alarms::signalAlarm] 
> Server Process born
> [Sep  3 04:14:35.380] Manager {0x804006400} ERROR: 
> [LocalManager::sendMgmtMsgToProcesses] Error writing message
> [Sep  3 04:14:35.380] Manager {0x804006400} ERROR:  (mgmt_elog)>  (last system error 32: Broken pipe)
> [Sep  3 04:14:35.748] Manager {0x804006400} ERROR: 
> [LocalManager::pollMgmtProcessServer] Server Process terminated due to Sig 
> 11: Segmentation fault
> [Sep  3 04:14:35.748] Manager {0x804006400} ERROR: [Alarms::signalAlarm] 
> Server Process was reset
> [Sep  3 04:14:36.814] Manager {0x804006400} NOTE: [LocalManager::startProxy] 
> Launching ts process
> [Sep  3 04:14:36.828] Manager {0x804006400} NOTE: 
> [LocalManager::pollMgmtProcessServer] New process connecting fd '13'
> [Sep  3 04:14:36.829] Manager {0x804006400} NOTE: [Alarms::signalAlarm] 
> Server Process born
> {noformat}
> traffic.out - since this isnt timestamped I'm not sure if I'm leaving some of 
> the stacktrace out:
> {noformat}
> traffic_server[TrafficManager] ==> Cleaning up and reissuing signal #15
> : Terminated
> traffic_server: Terminatedtraffic_servertraffic_servertraffic_server: 
> Segmentation fault
> traffic_server - STACK TRACE:
> 0x4af409 <_Z19crash_logger_invokeiP9__siginfoPv+0x69> at 
> /usr/local/bin/traffic_server
> 0x802735b37  at /lib/libthr.so.3
> 0x80273522c  at /lib/libthr.so.3
> getpeereid -> 0 (54, Connection reset by 

[jira] [Updated] (TS-4816) ATS 6.2.0 - crashing with broken pipe, sig11 segmentation fault

2016-09-06 Thread David Brodin (JIRA)

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

David Brodin updated TS-4816:
-
Attachment: est_socks-ats_6.2.0.png

No worries James!
But I'm sorry guys, I'm unable to produce a coredump. Gdb isn't letting up 
anything more than before. I even attached gdb to the traffic_manager process 
to see if that did something else, but nothing :(

I have the output before {{bt}} of traffic_manager on another computer, so I'll 
have to upload that tomorrow, if that is interesting that is.
I'm attaching a Cacti screenshot of the amount of EST-sockets and the crashes 
(most of the jagged graph is the crash, 3-5 of them are me restarting ATS). 
Notice the difference of EST sockets on 5.1.1 vs 6.2.0.

Any ideas? Should I build from source instead of ports? Go to a Debian instead 
of FreeBSD?

> ATS 6.2.0 - crashing with broken pipe, sig11 segmentation fault
> ---
>
> Key: TS-4816
> URL: https://issues.apache.org/jira/browse/TS-4816
> Project: Traffic Server
>  Issue Type: Bug
>  Components: Manager
>Reporter: David Brodin
>  Labels: crash
> Fix For: 7.0.0
>
> Attachments: ats_gdb-160905.txt, crash-2016-09-05-075309.log, 
> est_socks-ats_6.2.0.png
>
>
> Hi,
> We just upgraded to ATS 6.2.0 via FreeBSD ports:
> {noformat}
> [root@ ~]# uname -a
> FreeBSD  10.3-RELEASE-p7 FreeBSD 10.3-RELEASE-p7 #0: Thu Aug 11 
> 18:38:15 UTC 2016 
> r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64
> [root@ ~]# pkg info | grep traff
> trafficserver-6.2.0Fast, scalable and extensible HTTP proxy server
> {noformat}
> We are experiencing crashes, usually during the day, hardly any during "low" 
> loads, but the mest affecting crashes occur in the early mornings. Along with 
> this we can see a memory leak aswell
> We are using ATS as an enterprise proxy to the Internet, and as we have a 
> very good Internet-connection we have also disabled caching.
> I'm not sure how I would attach files so here goes :)
> manager.log
> {noformat}
> [Sep  2 11:48:28.017] Manager {0x804006400} ERROR: 
> [LocalManager::sendMgmtMsgToProcesses] Error writing message
> [Sep  2 11:48:28.017] Manager {0x804006400} ERROR:  (mgmt_elog)>  (last system error 32: Broken pipe)
> [Sep  2 11:48:38.305] {0x804006400} STATUS: opened 
> /var/log/trafficserver/manager.log
> [Sep  2 11:48:38.305] {0x804006400} NOTE:  (reconfigure_diags)> updated diags config
> [Sep  2 11:48:38.311] Manager {0x804006400} NOTE: [ClusterCom::ClusterCom] 
> Node running on OS: 'FreeBSD' Release: '10.3-RELEASE-p7'
> [Sep  2 11:48:38.312] Manager {0x804006400} NOTE: 
> [LocalManager::listenForProxy] Listening on port: 8080 (IPv4)
> [Sep  2 11:48:38.313] Manager {0x804006400} NOTE: 
> [LocalManager::listenForProxy] Listening on port: 8080 (IPv6)
> [Sep  2 11:48:38.313] Manager {0x804006400} NOTE: [TrafficManager] Setup 
> complete
> [Sep  2 11:48:39.321] Manager {0x804006400} NOTE: [LocalManager::startProxy] 
> Launching ts process
> [Sep  2 11:48:39.336] Manager {0x804006400} NOTE: 
> [LocalManager::pollMgmtProcessServer] New process connecting fd '17'
> [Sep  2 11:48:39.336] Manager {0x804006400} NOTE: [Alarms::signalAlarm] 
> Server Process born
> [Sep  2 11:51:32.574] Manager {0x804006400} ERROR: 
> [LocalManager::sendMgmtMsgToProcesses] Error writing message
> [Sep  2 11:51:32.574] Manager {0x804006400} ERROR:  (mgmt_elog)>  (last system error 32: Broken pipe)
> [Sep  2 11:51:32.669] Manager {0x804006400} ERROR: 
> [LocalManager::pollMgmtProcessServer] Server Process terminated due to Sig 
> 11: Segmentation fault
> [Sep  2 11:51:32.669] Manager {0x804006400} ERROR: [Alarms::signalAlarm] 
> Server Process was reset
> [Sep  2 11:51:33.674] Manager {0x804006400} NOTE: [LocalManager::startProxy] 
> Launching ts process
> [Sep  2 11:51:33.689] Manager {0x804006400} NOTE: 
> [LocalManager::pollMgmtProcessServer] New process connecting fd '13'
> [Sep  2 11:51:33.690] Manager {0x804006400} NOTE: [Alarms::signalAlarm] 
> Server Process born
> [Sep  3 04:14:35.380] Manager {0x804006400} ERROR: 
> [LocalManager::sendMgmtMsgToProcesses] Error writing message
> [Sep  3 04:14:35.380] Manager {0x804006400} ERROR:  (mgmt_elog)>  (last system error 32: Broken pipe)
> [Sep  3 04:14:35.748] Manager {0x804006400} ERROR: 
> [LocalManager::pollMgmtProcessServer] Server Process terminated due to Sig 
> 11: Segmentation fault
> [Sep  3 04:14:35.748] Manager {0x804006400} ERROR: [Alarms::signalAlarm] 
> Server Process was reset
> [Sep  3 04:14:36.814] Manager {0x804006400} NOTE: [LocalManager::startProxy] 
> Launching ts process
> [Sep  3 04:14:36.828] Manager {0x804006400} NOTE: 
> [LocalManager::pollMgmtProcessServer] New process connecting fd '13'
> [Sep  3 04:14:36.829] Manager {0x804006400} NOTE: 

[jira] [Updated] (TS-4816) ATS 6.2.0 - crashing with broken pipe, sig11 segmentation fault

2016-09-05 Thread David Brodin (JIRA)

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

David Brodin updated TS-4816:
-
Attachment: ats_gdb-160905.txt

Attached is the output from gdb.
Nothing super-exciting to me, but maybe to you.

Anything else I can do to get better logs?

> ATS 6.2.0 - crashing with broken pipe, sig11 segmentation fault
> ---
>
> Key: TS-4816
> URL: https://issues.apache.org/jira/browse/TS-4816
> Project: Traffic Server
>  Issue Type: Bug
>  Components: Manager
>Reporter: David Brodin
>  Labels: crash
> Fix For: 7.0.0
>
> Attachments: ats_gdb-160905.txt, crash-2016-09-05-075309.log
>
>
> Hi,
> We just upgraded to ATS 6.2.0 via FreeBSD ports:
> {noformat}
> [root@ ~]# uname -a
> FreeBSD  10.3-RELEASE-p7 FreeBSD 10.3-RELEASE-p7 #0: Thu Aug 11 
> 18:38:15 UTC 2016 
> r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64
> [root@ ~]# pkg info | grep traff
> trafficserver-6.2.0Fast, scalable and extensible HTTP proxy server
> {noformat}
> We are experiencing crashes, usually during the day, hardly any during "low" 
> loads, but the mest affecting crashes occur in the early mornings. Along with 
> this we can see a memory leak aswell
> We are using ATS as an enterprise proxy to the Internet, and as we have a 
> very good Internet-connection we have also disabled caching.
> I'm not sure how I would attach files so here goes :)
> manager.log
> {noformat}
> [Sep  2 11:48:28.017] Manager {0x804006400} ERROR: 
> [LocalManager::sendMgmtMsgToProcesses] Error writing message
> [Sep  2 11:48:28.017] Manager {0x804006400} ERROR:  (mgmt_elog)>  (last system error 32: Broken pipe)
> [Sep  2 11:48:38.305] {0x804006400} STATUS: opened 
> /var/log/trafficserver/manager.log
> [Sep  2 11:48:38.305] {0x804006400} NOTE:  (reconfigure_diags)> updated diags config
> [Sep  2 11:48:38.311] Manager {0x804006400} NOTE: [ClusterCom::ClusterCom] 
> Node running on OS: 'FreeBSD' Release: '10.3-RELEASE-p7'
> [Sep  2 11:48:38.312] Manager {0x804006400} NOTE: 
> [LocalManager::listenForProxy] Listening on port: 8080 (IPv4)
> [Sep  2 11:48:38.313] Manager {0x804006400} NOTE: 
> [LocalManager::listenForProxy] Listening on port: 8080 (IPv6)
> [Sep  2 11:48:38.313] Manager {0x804006400} NOTE: [TrafficManager] Setup 
> complete
> [Sep  2 11:48:39.321] Manager {0x804006400} NOTE: [LocalManager::startProxy] 
> Launching ts process
> [Sep  2 11:48:39.336] Manager {0x804006400} NOTE: 
> [LocalManager::pollMgmtProcessServer] New process connecting fd '17'
> [Sep  2 11:48:39.336] Manager {0x804006400} NOTE: [Alarms::signalAlarm] 
> Server Process born
> [Sep  2 11:51:32.574] Manager {0x804006400} ERROR: 
> [LocalManager::sendMgmtMsgToProcesses] Error writing message
> [Sep  2 11:51:32.574] Manager {0x804006400} ERROR:  (mgmt_elog)>  (last system error 32: Broken pipe)
> [Sep  2 11:51:32.669] Manager {0x804006400} ERROR: 
> [LocalManager::pollMgmtProcessServer] Server Process terminated due to Sig 
> 11: Segmentation fault
> [Sep  2 11:51:32.669] Manager {0x804006400} ERROR: [Alarms::signalAlarm] 
> Server Process was reset
> [Sep  2 11:51:33.674] Manager {0x804006400} NOTE: [LocalManager::startProxy] 
> Launching ts process
> [Sep  2 11:51:33.689] Manager {0x804006400} NOTE: 
> [LocalManager::pollMgmtProcessServer] New process connecting fd '13'
> [Sep  2 11:51:33.690] Manager {0x804006400} NOTE: [Alarms::signalAlarm] 
> Server Process born
> [Sep  3 04:14:35.380] Manager {0x804006400} ERROR: 
> [LocalManager::sendMgmtMsgToProcesses] Error writing message
> [Sep  3 04:14:35.380] Manager {0x804006400} ERROR:  (mgmt_elog)>  (last system error 32: Broken pipe)
> [Sep  3 04:14:35.748] Manager {0x804006400} ERROR: 
> [LocalManager::pollMgmtProcessServer] Server Process terminated due to Sig 
> 11: Segmentation fault
> [Sep  3 04:14:35.748] Manager {0x804006400} ERROR: [Alarms::signalAlarm] 
> Server Process was reset
> [Sep  3 04:14:36.814] Manager {0x804006400} NOTE: [LocalManager::startProxy] 
> Launching ts process
> [Sep  3 04:14:36.828] Manager {0x804006400} NOTE: 
> [LocalManager::pollMgmtProcessServer] New process connecting fd '13'
> [Sep  3 04:14:36.829] Manager {0x804006400} NOTE: [Alarms::signalAlarm] 
> Server Process born
> {noformat}
> traffic.out - since this isnt timestamped I'm not sure if I'm leaving some of 
> the stacktrace out:
> {noformat}
> traffic_server[TrafficManager] ==> Cleaning up and reissuing signal #15
> : Terminated
> traffic_server: Terminatedtraffic_servertraffic_servertraffic_server: 
> Segmentation fault
> traffic_server - STACK TRACE:
> 0x4af409 <_Z19crash_logger_invokeiP9__siginfoPv+0x69> at 
> /usr/local/bin/traffic_server
> 0x802735b37  at /lib/libthr.so.3
> 0x80273522c  at 

[jira] [Updated] (TS-4816) ATS 6.2.0 - crashing with broken pipe, sig11 segmentation fault

2016-09-03 Thread Leif Hedstrom (JIRA)

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

Leif Hedstrom updated TS-4816:
--
Fix Version/s: 7.0.0

> ATS 6.2.0 - crashing with broken pipe, sig11 segmentation fault
> ---
>
> Key: TS-4816
> URL: https://issues.apache.org/jira/browse/TS-4816
> Project: Traffic Server
>  Issue Type: Bug
>  Components: Manager
>Reporter: David Brodin
> Fix For: 7.0.0
>
>
> Hi,
> We just upgraded to ATS 6.2.0 via FreeBSD ports:
> {noformat}
> [root@ ~]# uname -a
> FreeBSD  10.3-RELEASE-p7 FreeBSD 10.3-RELEASE-p7 #0: Thu Aug 11 
> 18:38:15 UTC 2016 
> r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64
> [root@ ~]# pkg info | grep traff
> trafficserver-6.2.0Fast, scalable and extensible HTTP proxy server
> {noformat}
> We are experiencing crashes, usually during the day, hardly any during "low" 
> loads, but the mest affecting crashes occur in the early mornings. Along with 
> this we can see a memory leak aswell
> We are using ATS as an enterprise proxy to the Internet, and as we have a 
> very good Internet-connection we have also disabled caching.
> I'm not sure how I would attach files so here goes :)
> manager.log
> {noformat}
> [Sep  2 11:48:28.017] Manager {0x804006400} ERROR: 
> [LocalManager::sendMgmtMsgToProcesses] Error writing message
> [Sep  2 11:48:28.017] Manager {0x804006400} ERROR:  (mgmt_elog)>  (last system error 32: Broken pipe)
> [Sep  2 11:48:38.305] {0x804006400} STATUS: opened 
> /var/log/trafficserver/manager.log
> [Sep  2 11:48:38.305] {0x804006400} NOTE:  (reconfigure_diags)> updated diags config
> [Sep  2 11:48:38.311] Manager {0x804006400} NOTE: [ClusterCom::ClusterCom] 
> Node running on OS: 'FreeBSD' Release: '10.3-RELEASE-p7'
> [Sep  2 11:48:38.312] Manager {0x804006400} NOTE: 
> [LocalManager::listenForProxy] Listening on port: 8080 (IPv4)
> [Sep  2 11:48:38.313] Manager {0x804006400} NOTE: 
> [LocalManager::listenForProxy] Listening on port: 8080 (IPv6)
> [Sep  2 11:48:38.313] Manager {0x804006400} NOTE: [TrafficManager] Setup 
> complete
> [Sep  2 11:48:39.321] Manager {0x804006400} NOTE: [LocalManager::startProxy] 
> Launching ts process
> [Sep  2 11:48:39.336] Manager {0x804006400} NOTE: 
> [LocalManager::pollMgmtProcessServer] New process connecting fd '17'
> [Sep  2 11:48:39.336] Manager {0x804006400} NOTE: [Alarms::signalAlarm] 
> Server Process born
> [Sep  2 11:51:32.574] Manager {0x804006400} ERROR: 
> [LocalManager::sendMgmtMsgToProcesses] Error writing message
> [Sep  2 11:51:32.574] Manager {0x804006400} ERROR:  (mgmt_elog)>  (last system error 32: Broken pipe)
> [Sep  2 11:51:32.669] Manager {0x804006400} ERROR: 
> [LocalManager::pollMgmtProcessServer] Server Process terminated due to Sig 
> 11: Segmentation fault
> [Sep  2 11:51:32.669] Manager {0x804006400} ERROR: [Alarms::signalAlarm] 
> Server Process was reset
> [Sep  2 11:51:33.674] Manager {0x804006400} NOTE: [LocalManager::startProxy] 
> Launching ts process
> [Sep  2 11:51:33.689] Manager {0x804006400} NOTE: 
> [LocalManager::pollMgmtProcessServer] New process connecting fd '13'
> [Sep  2 11:51:33.690] Manager {0x804006400} NOTE: [Alarms::signalAlarm] 
> Server Process born
> [Sep  3 04:14:35.380] Manager {0x804006400} ERROR: 
> [LocalManager::sendMgmtMsgToProcesses] Error writing message
> [Sep  3 04:14:35.380] Manager {0x804006400} ERROR:  (mgmt_elog)>  (last system error 32: Broken pipe)
> [Sep  3 04:14:35.748] Manager {0x804006400} ERROR: 
> [LocalManager::pollMgmtProcessServer] Server Process terminated due to Sig 
> 11: Segmentation fault
> [Sep  3 04:14:35.748] Manager {0x804006400} ERROR: [Alarms::signalAlarm] 
> Server Process was reset
> [Sep  3 04:14:36.814] Manager {0x804006400} NOTE: [LocalManager::startProxy] 
> Launching ts process
> [Sep  3 04:14:36.828] Manager {0x804006400} NOTE: 
> [LocalManager::pollMgmtProcessServer] New process connecting fd '13'
> [Sep  3 04:14:36.829] Manager {0x804006400} NOTE: [Alarms::signalAlarm] 
> Server Process born
> {noformat}
> traffic.out - since this isnt timestamped I'm not sure if I'm leaving some of 
> the stacktrace out:
> {noformat}
> traffic_server[TrafficManager] ==> Cleaning up and reissuing signal #15
> : Terminated
> traffic_server: Terminatedtraffic_servertraffic_servertraffic_server: 
> Segmentation fault
> traffic_server - STACK TRACE:
> 0x4af409 <_Z19crash_logger_invokeiP9__siginfoPv+0x69> at 
> /usr/local/bin/traffic_server
> 0x802735b37  at /lib/libthr.so.3
> 0x80273522c  at /lib/libthr.so.3
> getpeereid -> 0 (54, Connection reset by peer)[TrafficManager] ==> Cleaning 
> up and reissuing signal #15
> traffic_server: Terminated
> traffic_server: Terminated
> traffic_server: using root directory '/usr/local'
>