[jira] [Comment Edited] (TS-4816) ATS 6.2.0 - crashing with broken pipe, sig11 segmentation fault
[
https://issues.apache.org/jira/browse/TS-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15476204#comment-15476204
]
David Brodin edited comment on TS-4816 at 9/9/16 7:33 AM:
--
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}}.
Hope there's something there for you guys :s
Edit: this was running the downloaded source from ATS-web, not installed from
FreeBSD ports.
was (Author: durd):
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}}.
Hope there's something there for you guys :s
> 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.
[jira] [Comment Edited] (TS-4816) ATS 6.2.0 - crashing with broken pipe, sig11 segmentation fault
[
https://issues.apache.org/jira/browse/TS-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15476204#comment-15476204
]
David Brodin edited comment on TS-4816 at 9/9/16 7:32 AM:
--
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}}.
Hope there's something there for you guys :s
was (Author: durd):
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 n
[jira] [Comment Edited] (TS-4816) ATS 6.2.0 - crashing with broken pipe, sig11 segmentation fault
[
https://issues.apache.org/jira/browse/TS-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15476204#comment-15476204
]
David Brodin edited comment on TS-4816 at 9/9/16 7:32 AM:
--
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}}.
was (Author: durd):
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 stacktr
[jira] [Comment Edited] (TS-4816) ATS 6.2.0 - crashing with broken pipe, sig11 segmentation fault
[
https://issues.apache.org/jira/browse/TS-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15474085#comment-15474085
]
Leif Hedstrom edited comment on TS-4816 at 9/8/16 3:00 PM:
---
Without getting a core / stack trace, there's no hope of getting closer to
understanding what is wrong I think :-/. What happens when you attach gdb to
the running traffic_server process?
Update: I see your attached gdb.txt, that's unfortunately not useful. You have
to catch this without the process going away. Can you just run traffic_server
without traffic_manager / traffic_cop, under gdb ?
was (Author: zwoop):
Without getting a core / stack trace, there's no hope of getting closer to
understanding what is wrong I think :-/. What happens when you attach gdb to
the running traffic_server process?
> 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
[jira] [Comment Edited] (TS-4816) ATS 6.2.0 - crashing with broken pipe, sig11 segmentation fault
[
https://issues.apache.org/jira/browse/TS-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15474085#comment-15474085
]
Leif Hedstrom edited comment on TS-4816 at 9/8/16 2:59 PM:
---
Without getting a core / stack trace, there's no hope of getting closer to
understanding what is wrong I think :-/. What happens when you attach gdb to
the running traffic_server process?
was (Author: zwoop):
Without getting a core / stack trace, there's no hope of getting closer to
understanding what is wrong I think :-/.
> 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
>
[jira] [Comment Edited] (TS-4816) ATS 6.2.0 - crashing with broken pipe, sig11 segmentation fault
[
https://issues.apache.org/jira/browse/TS-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15471866#comment-15471866
]
David Brodin edited comment on TS-4816 at 9/7/16 9:31 PM:
--
Yay, it's not only me! :D
Joke aside, I want to make clear that my two servers (5.1.1 & 6.2.0) are not
clustered in any way.
I also downloaded the source from ATS-webpage and compiled from there. We'll
see tomorrow morning if there is a difference.
was (Author: durd):
Yay, it's not only me! :D
Joke aside, I want to make clear that my two servers (5.1.1 & 6.2.0) are not
clustered in any way.
> 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[Traff
[jira] [Comment Edited] (TS-4816) ATS 6.2.0 - crashing with broken pipe, sig11 segmentation fault
[
https://issues.apache.org/jira/browse/TS-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15467811#comment-15467811
]
David Brodin edited comment on TS-4816 at 9/7/16 7:53 PM:
--
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? Go back to 5.1.1?
Edit: Must be a bug/new feature in FreeBSD or net-snmp, tcpCurrEstab shows
7000. {{netstat -an | grep ESTAB | wc -l}} shows only 700...
was (Author: durd):
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? Go back to 5.1.1?
> 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 {0x
[jira] [Comment Edited] (TS-4816) ATS 6.2.0 - crashing with broken pipe, sig11 segmentation fault
[
https://issues.apache.org/jira/browse/TS-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15467811#comment-15467811
]
David Brodin edited comment on TS-4816 at 9/6/16 4:23 PM:
--
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? Go back to 5.1.1?
was (Author: durd):
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
[jira] [Comment Edited] (TS-4816) ATS 6.2.0 - crashing with broken pipe, sig11 segmentation fault
[
https://issues.apache.org/jira/browse/TS-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15464189#comment-15464189
]
David Brodin edited comment on TS-4816 at 9/5/16 6:07 AM:
--
Found the traffic_crashlog command.
ATS crashed again this morning, but no coredump even with the records.config
set.
I'll try to attach gdb to the process instead as according to the wiki.
> 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: 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_serve
[jira] [Comment Edited] (TS-4816) ATS 6.2.0 - crashing with broken pipe, sig11 segmentation fault
[
https://issues.apache.org/jira/browse/TS-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15461702#comment-15461702
]
David Brodin edited comment on TS-4816 at 9/3/16 9:14 PM:
--
Nope, no core file or anything except for the logs provided.
Ive tried to find out how I enable coredumping, but just now found the wiki.
Ive enabled dumping and will attach the dump when that happens.
Might be earliest monday as this seems to be occuring when ATS is under load.
Sorry for spending your time, I thought the logs provided would show something
at least.
Edit: Is there anything I can do while waiting? Other logs, conf-files, ...?
was (Author: durd):
Nope, no core file or anything except for the logs provided.
Ive tried to find out how I enable coredumping, but just now found the wiki.
Ive enabled dumping and will attach the dump when that happens.
Might be earliest monday as this seems to be occuring when ATS is under load.
Sorry for spending your time, I thought the logs provided would show something
at least.
> 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
>
>
> 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:
> [L
[jira] [Comment Edited] (TS-4816) ATS 6.2.0 - crashing with broken pipe, sig11 segmentation fault
[
https://issues.apache.org/jira/browse/TS-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15461702#comment-15461702
]
David Brodin edited comment on TS-4816 at 9/3/16 9:08 PM:
--
Nope, no core file or anything except for the logs provided.
Ive tried to find out how I enable coredumping, but just now found the wiki.
Ive enabled dumping and will attach the dump when that happens.
Might be earliest monday as this seems to be occuring when ATS is under load.
Sorry for spending your time, I thought the logs provided would show something
at least.
was (Author: durd):
Nope, no core file or anything except for the logs provided.
Ive tried to find out how I enabled coredumping, but just now found the wiki.
Ive enabled dumping and will attach the dump when that happens.
Might be earliest monday as this seems to be occuring when ATS is under load.
Sorry for spending your time, I thought the logs provided would show something
at least.
> 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
>
>
> 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
