[jira] [Commented] (TS-2669) ATS crash, then restart with all cached objects cleared
[
https://issues.apache.org/jira/browse/TS-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13950437#comment-13950437
]
Zhao Yongming commented on TS-2669:
---
well, maybe something that need more check, please findout the diags.log lines
like:
{code}
[Mar 27 20:31:25.948] {0x2b02748fde00} STATUS: opened
/var/log/trafficserver/diags.log
[Mar 27 20:31:25.948] {0x2b02748fde00} NOTE: updated diags config
[Mar 27 20:31:25.954] Server {0x2b02748fde00} NOTE: cache clustering disabled
[Mar 27 20:31:25.964] Server {0x2b02748fde00} NOTE: ip_allow.config updated,
reloading
[Mar 27 20:31:25.969] Server {0x2b02748fde00} NOTE: loading SSL certificate
configuration from /etc/trafficserver/ssl_multicert.config
[Mar 27 20:31:25.976] Server {0x2b02748fde00} NOTE: cache clustering disabled
[Mar 27 20:31:25.977] Server {0x2b02748fde00} NOTE: logging initialized[15],
logging_mode = 3
[Mar 27 20:31:25.978] Server {0x2b02748fde00} NOTE: loading plugin
'/usr/lib64/trafficserver/plugins/libloader.so'
[Mar 27 20:31:25.982] Server {0x2b02748fde00} NOTE: loading plugin
'/usr/local/ironbee/libexec/ts_ironbee.so'
[Mar 27 20:31:25.983] Server {0x2b02748fde00} NOTE: Rolling interval adjusted
from 0 sec to 300 sec for /var/log/trafficserver/ts-ironbee.log
[Mar 27 20:31:25.992] Server {0x2b02748fde00} NOTE: traffic server running
[Mar 27 20:31:26.077] Server {0x2b0275d8e700} NOTE: cache enabled
{code}
you may find out that ' traffic server running' indicates that ATS is running,
and 'cache enabled' show that cache is working. due to your system is crash and
cache is not enabled, I will suspect that your ATS does not have that 'cache
enabled' line.
this is often caused by something like privilege issue, that ATS server process
does not have the write privilege on the disk block device files etc. or
anything else you may findout in the diags.log or even system logs.
the interim cache aio bugs may cause you lose the saved data, interim cache
may cause you lose the data while server process restart, and AIO may get all
data clear. but all those bugs fixed in the v4.1.0 release.
ATS crash, then restart with all cached objects cleared
---
Key: TS-2669
URL: https://issues.apache.org/jira/browse/TS-2669
Project: Traffic Server
Issue Type: Bug
Reporter: AnDao
Hi all,
I'm using ATS 4.1.2, my ATS is just crashed and restart and clean all the
cached objects, cause my backend servers overload. Why ATS do clean all the
cached objects when crash and restart?
The log is:
* manager.log
[Mar 27 12:57:13.022] Manager {0x7f597e3477e0} FATAL:
[LocalManager::pollMgmtProcessServer] Error in read (errno: 104)
[Mar 27 12:57:13.022] Manager {0x7f597e3477e0} NOTE:
[LocalManager::mgmtShutdown] Executing shutdown request.
[Mar 27 12:57:13.022] Manager {0x7f597e3477e0} NOTE:
[LocalManager::processShutdown] Executing process shutdown request.
[Mar 27 12:57:13.028] Manager {0x7f597e3477e0} ERROR:
[LocalManager::sendMgmtMsgToProcesses] Error writing message
[Mar 27 12:57:13.028] Manager {0x7f597e3477e0} ERROR: (last system error 32:
Broken pipe)
[Mar 27 12:57:13.174] {0x7ffaeec7e7e0} STATUS: opened
/zserver/log/trafficserver/manager.log
[Mar 27 12:57:13.174] {0x7ffaeec7e7e0} NOTE: updated diags config
[Mar 27 12:57:13.520] Manager {0x7ffaeec7e7e0} NOTE: [ClusterCom::ClusterCom]
Node running on OS: 'Linux' Release: '2.6.32-358.6.2.el6.x86_64'
[Mar 27 12:57:13.550] Manager {0x7ffaeec7e7e0} NOTE:
[LocalManager::listenForProxy] Listening on port: 80
[Mar 27 12:57:13.550] Manager {0x7ffaeec7e7e0} NOTE: [TrafficManager] Setup
complete
[Mar 27 12:57:14.618] Manager {0x7ffaeec7e7e0} NOTE:
[LocalManager::startProxy] Launching ts process
[Mar 27 12:57:14.632] Manager {0x7ffaeec7e7e0} NOTE:
[LocalManager::pollMgmtProcessServer] New process connecting fd '15'
[Mar 27 12:57:14.632] Manager {0x7ffaeec7e7e0} NOTE: [Alarms::signalAlarm]
Server Process born
*** traffic.out ***
[E. Mgmt] log == [TrafficManager] using root directory
'/zserver/trafficserver-4.1.2'
[TrafficServer] using root directory '/zserver/trafficserver-4.1.2'
NOTE: Traffic Server received Sig 15: Terminated
[E. Mgmt] log == [TrafficManager] using root directory
'/zserver/trafficserver-4.1.2'
[TrafficServer] using root directory '/zserver/trafficserver-4.1.2'
NOTE: Traffic Server received Sig 11: Segmentation fault
/zserver/trafficserver-4.1.2/bin/traffic_server - STACK TRACE:
/lib64/libpthread.so.0(+0x35a360f500)[0x2b3b55819500]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN12HttpTransact47change_response_header_because_of_range_requestEPNS_5StateEP7HTTPHdr+0x240)[0x54b8a0]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN12HttpTransact28handle_content_length_headerEPNS_5StateEP7HTTPHdrS3_+0x2c8)[0x54bc38]
[jira] [Commented] (TS-2669) ATS crash, then restart with all cached objects cleared
[
https://issues.apache.org/jira/browse/TS-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13950457#comment-13950457
]
AnDao commented on TS-2669:
---
Dear Zhao Yongming,
Sure that my ATS cache enabled. You can see my attached images.
I'm very worry if it can be happen again, that will impact much to our business.
Thanks.
ATS crash, then restart with all cached objects cleared
---
Key: TS-2669
URL: https://issues.apache.org/jira/browse/TS-2669
Project: Traffic Server
Issue Type: Bug
Reporter: AnDao
Attachments: cachobjecs.png, storage.png
Hi all,
I'm using ATS 4.1.2, my ATS is just crashed and restart and clean all the
cached objects, cause my backend servers overload. Why ATS do clean all the
cached objects when crash and restart?
The log is:
* manager.log
[Mar 27 12:57:13.022] Manager {0x7f597e3477e0} FATAL:
[LocalManager::pollMgmtProcessServer] Error in read (errno: 104)
[Mar 27 12:57:13.022] Manager {0x7f597e3477e0} NOTE:
[LocalManager::mgmtShutdown] Executing shutdown request.
[Mar 27 12:57:13.022] Manager {0x7f597e3477e0} NOTE:
[LocalManager::processShutdown] Executing process shutdown request.
[Mar 27 12:57:13.028] Manager {0x7f597e3477e0} ERROR:
[LocalManager::sendMgmtMsgToProcesses] Error writing message
[Mar 27 12:57:13.028] Manager {0x7f597e3477e0} ERROR: (last system error 32:
Broken pipe)
[Mar 27 12:57:13.174] {0x7ffaeec7e7e0} STATUS: opened
/zserver/log/trafficserver/manager.log
[Mar 27 12:57:13.174] {0x7ffaeec7e7e0} NOTE: updated diags config
[Mar 27 12:57:13.520] Manager {0x7ffaeec7e7e0} NOTE: [ClusterCom::ClusterCom]
Node running on OS: 'Linux' Release: '2.6.32-358.6.2.el6.x86_64'
[Mar 27 12:57:13.550] Manager {0x7ffaeec7e7e0} NOTE:
[LocalManager::listenForProxy] Listening on port: 80
[Mar 27 12:57:13.550] Manager {0x7ffaeec7e7e0} NOTE: [TrafficManager] Setup
complete
[Mar 27 12:57:14.618] Manager {0x7ffaeec7e7e0} NOTE:
[LocalManager::startProxy] Launching ts process
[Mar 27 12:57:14.632] Manager {0x7ffaeec7e7e0} NOTE:
[LocalManager::pollMgmtProcessServer] New process connecting fd '15'
[Mar 27 12:57:14.632] Manager {0x7ffaeec7e7e0} NOTE: [Alarms::signalAlarm]
Server Process born
*** traffic.out ***
[E. Mgmt] log == [TrafficManager] using root directory
'/zserver/trafficserver-4.1.2'
[TrafficServer] using root directory '/zserver/trafficserver-4.1.2'
NOTE: Traffic Server received Sig 15: Terminated
[E. Mgmt] log == [TrafficManager] using root directory
'/zserver/trafficserver-4.1.2'
[TrafficServer] using root directory '/zserver/trafficserver-4.1.2'
NOTE: Traffic Server received Sig 11: Segmentation fault
/zserver/trafficserver-4.1.2/bin/traffic_server - STACK TRACE:
/lib64/libpthread.so.0(+0x35a360f500)[0x2b3b55819500]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN12HttpTransact47change_response_header_because_of_range_requestEPNS_5StateEP7HTTPHdr+0x240)[0x54b8a0]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN12HttpTransact28handle_content_length_headerEPNS_5StateEP7HTTPHdrS3_+0x2c8)[0x54bc38]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN12HttpTransact14build_responseEPNS_5StateEP7HTTPHdrS3_11HTTPVersion10HTTPStatusPKc+0x3e3)[0x54c0c3]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN12HttpTransact22handle_transform_readyEPNS_5StateE+0x70)[0x54ca40]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN6HttpSM32call_transact_and_set_next_stateEPFvPN12HttpTransact5StateEE+0x28)[0x51b418]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN6HttpSM38state_response_wait_for_transform_readEiPv+0xed)[0x52988d]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN6HttpSM12main_handlerEiPv+0xd8)[0x533178]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN17TransformTerminus12handle_eventEiPv+0x1d2)[0x4e8c62]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x8f)[0x6a5a0f]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN7EThread7executeEv+0x63b)[0x6a658b]
/zserver/trafficserver-4.1.2/bin/traffic_server[0x6a48aa]
/lib64/libpthread.so.0(+0x35a3607851)[0x2b3b55811851]
/lib64/libc.so.6(clone+0x6d)[0x35a32e890d]
[E. Mgmt] log == [TrafficManager] using root directory
'/zserver/trafficserver-4.1.2'
[TrafficServer] using root directory '/zserver/trafficserver-4.1.2'
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (TS-2669) ATS crash, then restart with all cached objects cleared
[
https://issues.apache.org/jira/browse/TS-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
AnDao updated TS-2669:
--
Attachment: storage.png
cachobjecs.png
ATS 4.1.2 crash, then restart with all cached objects cleared.
ATS crash, then restart with all cached objects cleared
---
Key: TS-2669
URL: https://issues.apache.org/jira/browse/TS-2669
Project: Traffic Server
Issue Type: Bug
Reporter: AnDao
Attachments: cachobjecs.png, storage.png
Hi all,
I'm using ATS 4.1.2, my ATS is just crashed and restart and clean all the
cached objects, cause my backend servers overload. Why ATS do clean all the
cached objects when crash and restart?
The log is:
* manager.log
[Mar 27 12:57:13.022] Manager {0x7f597e3477e0} FATAL:
[LocalManager::pollMgmtProcessServer] Error in read (errno: 104)
[Mar 27 12:57:13.022] Manager {0x7f597e3477e0} NOTE:
[LocalManager::mgmtShutdown] Executing shutdown request.
[Mar 27 12:57:13.022] Manager {0x7f597e3477e0} NOTE:
[LocalManager::processShutdown] Executing process shutdown request.
[Mar 27 12:57:13.028] Manager {0x7f597e3477e0} ERROR:
[LocalManager::sendMgmtMsgToProcesses] Error writing message
[Mar 27 12:57:13.028] Manager {0x7f597e3477e0} ERROR: (last system error 32:
Broken pipe)
[Mar 27 12:57:13.174] {0x7ffaeec7e7e0} STATUS: opened
/zserver/log/trafficserver/manager.log
[Mar 27 12:57:13.174] {0x7ffaeec7e7e0} NOTE: updated diags config
[Mar 27 12:57:13.520] Manager {0x7ffaeec7e7e0} NOTE: [ClusterCom::ClusterCom]
Node running on OS: 'Linux' Release: '2.6.32-358.6.2.el6.x86_64'
[Mar 27 12:57:13.550] Manager {0x7ffaeec7e7e0} NOTE:
[LocalManager::listenForProxy] Listening on port: 80
[Mar 27 12:57:13.550] Manager {0x7ffaeec7e7e0} NOTE: [TrafficManager] Setup
complete
[Mar 27 12:57:14.618] Manager {0x7ffaeec7e7e0} NOTE:
[LocalManager::startProxy] Launching ts process
[Mar 27 12:57:14.632] Manager {0x7ffaeec7e7e0} NOTE:
[LocalManager::pollMgmtProcessServer] New process connecting fd '15'
[Mar 27 12:57:14.632] Manager {0x7ffaeec7e7e0} NOTE: [Alarms::signalAlarm]
Server Process born
*** traffic.out ***
[E. Mgmt] log == [TrafficManager] using root directory
'/zserver/trafficserver-4.1.2'
[TrafficServer] using root directory '/zserver/trafficserver-4.1.2'
NOTE: Traffic Server received Sig 15: Terminated
[E. Mgmt] log == [TrafficManager] using root directory
'/zserver/trafficserver-4.1.2'
[TrafficServer] using root directory '/zserver/trafficserver-4.1.2'
NOTE: Traffic Server received Sig 11: Segmentation fault
/zserver/trafficserver-4.1.2/bin/traffic_server - STACK TRACE:
/lib64/libpthread.so.0(+0x35a360f500)[0x2b3b55819500]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN12HttpTransact47change_response_header_because_of_range_requestEPNS_5StateEP7HTTPHdr+0x240)[0x54b8a0]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN12HttpTransact28handle_content_length_headerEPNS_5StateEP7HTTPHdrS3_+0x2c8)[0x54bc38]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN12HttpTransact14build_responseEPNS_5StateEP7HTTPHdrS3_11HTTPVersion10HTTPStatusPKc+0x3e3)[0x54c0c3]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN12HttpTransact22handle_transform_readyEPNS_5StateE+0x70)[0x54ca40]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN6HttpSM32call_transact_and_set_next_stateEPFvPN12HttpTransact5StateEE+0x28)[0x51b418]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN6HttpSM38state_response_wait_for_transform_readEiPv+0xed)[0x52988d]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN6HttpSM12main_handlerEiPv+0xd8)[0x533178]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN17TransformTerminus12handle_eventEiPv+0x1d2)[0x4e8c62]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x8f)[0x6a5a0f]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN7EThread7executeEv+0x63b)[0x6a658b]
/zserver/trafficserver-4.1.2/bin/traffic_server[0x6a48aa]
/lib64/libpthread.so.0(+0x35a3607851)[0x2b3b55811851]
/lib64/libc.so.6(clone+0x6d)[0x35a32e890d]
[E. Mgmt] log == [TrafficManager] using root directory
'/zserver/trafficserver-4.1.2'
[TrafficServer] using root directory '/zserver/trafficserver-4.1.2'
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (TS-2669) ATS crash, then restart with all cached objects cleared
[
https://issues.apache.org/jira/browse/TS-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13950510#comment-13950510
]
Zhao Yongming commented on TS-2669:
---
please attach the server start log in diags.log file, as I attached. and please
tell us how is your storage is configured.
ATS crash, then restart with all cached objects cleared
---
Key: TS-2669
URL: https://issues.apache.org/jira/browse/TS-2669
Project: Traffic Server
Issue Type: Bug
Reporter: AnDao
Attachments: cachobjecs.png, storage.png
Hi all,
I'm using ATS 4.1.2, my ATS is just crashed and restart and clean all the
cached objects, cause my backend servers overload. Why ATS do clean all the
cached objects when crash and restart?
The log is:
* manager.log
[Mar 27 12:57:13.022] Manager {0x7f597e3477e0} FATAL:
[LocalManager::pollMgmtProcessServer] Error in read (errno: 104)
[Mar 27 12:57:13.022] Manager {0x7f597e3477e0} NOTE:
[LocalManager::mgmtShutdown] Executing shutdown request.
[Mar 27 12:57:13.022] Manager {0x7f597e3477e0} NOTE:
[LocalManager::processShutdown] Executing process shutdown request.
[Mar 27 12:57:13.028] Manager {0x7f597e3477e0} ERROR:
[LocalManager::sendMgmtMsgToProcesses] Error writing message
[Mar 27 12:57:13.028] Manager {0x7f597e3477e0} ERROR: (last system error 32:
Broken pipe)
[Mar 27 12:57:13.174] {0x7ffaeec7e7e0} STATUS: opened
/zserver/log/trafficserver/manager.log
[Mar 27 12:57:13.174] {0x7ffaeec7e7e0} NOTE: updated diags config
[Mar 27 12:57:13.520] Manager {0x7ffaeec7e7e0} NOTE: [ClusterCom::ClusterCom]
Node running on OS: 'Linux' Release: '2.6.32-358.6.2.el6.x86_64'
[Mar 27 12:57:13.550] Manager {0x7ffaeec7e7e0} NOTE:
[LocalManager::listenForProxy] Listening on port: 80
[Mar 27 12:57:13.550] Manager {0x7ffaeec7e7e0} NOTE: [TrafficManager] Setup
complete
[Mar 27 12:57:14.618] Manager {0x7ffaeec7e7e0} NOTE:
[LocalManager::startProxy] Launching ts process
[Mar 27 12:57:14.632] Manager {0x7ffaeec7e7e0} NOTE:
[LocalManager::pollMgmtProcessServer] New process connecting fd '15'
[Mar 27 12:57:14.632] Manager {0x7ffaeec7e7e0} NOTE: [Alarms::signalAlarm]
Server Process born
*** traffic.out ***
[E. Mgmt] log == [TrafficManager] using root directory
'/zserver/trafficserver-4.1.2'
[TrafficServer] using root directory '/zserver/trafficserver-4.1.2'
NOTE: Traffic Server received Sig 15: Terminated
[E. Mgmt] log == [TrafficManager] using root directory
'/zserver/trafficserver-4.1.2'
[TrafficServer] using root directory '/zserver/trafficserver-4.1.2'
NOTE: Traffic Server received Sig 11: Segmentation fault
/zserver/trafficserver-4.1.2/bin/traffic_server - STACK TRACE:
/lib64/libpthread.so.0(+0x35a360f500)[0x2b3b55819500]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN12HttpTransact47change_response_header_because_of_range_requestEPNS_5StateEP7HTTPHdr+0x240)[0x54b8a0]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN12HttpTransact28handle_content_length_headerEPNS_5StateEP7HTTPHdrS3_+0x2c8)[0x54bc38]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN12HttpTransact14build_responseEPNS_5StateEP7HTTPHdrS3_11HTTPVersion10HTTPStatusPKc+0x3e3)[0x54c0c3]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN12HttpTransact22handle_transform_readyEPNS_5StateE+0x70)[0x54ca40]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN6HttpSM32call_transact_and_set_next_stateEPFvPN12HttpTransact5StateEE+0x28)[0x51b418]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN6HttpSM38state_response_wait_for_transform_readEiPv+0xed)[0x52988d]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN6HttpSM12main_handlerEiPv+0xd8)[0x533178]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN17TransformTerminus12handle_eventEiPv+0x1d2)[0x4e8c62]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x8f)[0x6a5a0f]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN7EThread7executeEv+0x63b)[0x6a658b]
/zserver/trafficserver-4.1.2/bin/traffic_server[0x6a48aa]
/lib64/libpthread.so.0(+0x35a3607851)[0x2b3b55811851]
/lib64/libc.so.6(clone+0x6d)[0x35a32e890d]
[E. Mgmt] log == [TrafficManager] using root directory
'/zserver/trafficserver-4.1.2'
[TrafficServer] using root directory '/zserver/trafficserver-4.1.2'
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (TS-2669) ATS crash, then restart with all cached objects cleared
[
https://issues.apache.org/jira/browse/TS-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13950554#comment-13950554
]
AnDao commented on TS-2669:
---
Hi,
Here is diags.log after ATS restart:
.
[Mar 27 12:31:15.227] Server {0x2b3b56ee8700} WARNING: cache directory overflow
on '/data/trafficserver-4.x/cache.db' segment 23, purging...
[Mar 27 12:33:43.270] Server {0x2b3b56be5700} WARNING: cache directory overflow
on '/data/trafficserver-4.x/cache.db' segment 36, purging...
[Mar 27 12:48:17.352] Server {0x2b3b56067420} WARNING: cache directory overflow
on '/data/trafficserver-4.x/cache.db' segment 35, purging...
[Mar 27 12:57:15.648] {0x2ba3c9258420} STATUS: opened
/zserver/trafficserver-4.1.2/var/log/trafficserver/diags.log
[Mar 27 12:57:15.648] {0x2ba3c9258420} NOTE: updated diags config
[Mar 27 12:57:15.661] Server {0x2ba3c9258420} NOTE: cache clustering disabled
[Mar 27 12:57:15.682] Server {0x2ba3c9258420} NOTE: ip_allow.config updated,
reloading
[Mar 27 12:57:15.704] Server {0x2ba3c9258420} NOTE: cache clustering disabled
[Mar 27 12:57:15.706] Server {0x2ba3c9258420} NOTE: logging initialized[15],
logging_mode = 0
[Mar 27 12:57:15.707] Server {0x2ba3c9258420} NOTE: loading plugin
'/zserver/trafficserver-4.1.2/libexec/trafficserver/cacheurl.so'
[Mar 27 12:57:15.749] Server {0x2ba3c9258420} NOTE: traffic server running
[Mar 27 12:57:15.931] Server {0x2ba3c9ed7700} NOTE: no good directory, clearing
'/data/trafficserver-4.x/cache.db 57344:28835833'
[Mar 27 12:57:18.325] Server {0x2ba3c9cd5700} NOTE: cache enabled
##3
ATS crash, then restart with all cached objects cleared
---
Key: TS-2669
URL: https://issues.apache.org/jira/browse/TS-2669
Project: Traffic Server
Issue Type: Bug
Reporter: AnDao
Attachments: cachobjecs.png, storage.png
Hi all,
I'm using ATS 4.1.2, my ATS is just crashed and restart and clean all the
cached objects, cause my backend servers overload. Why ATS do clean all the
cached objects when crash and restart?
The log is:
* manager.log
[Mar 27 12:57:13.022] Manager {0x7f597e3477e0} FATAL:
[LocalManager::pollMgmtProcessServer] Error in read (errno: 104)
[Mar 27 12:57:13.022] Manager {0x7f597e3477e0} NOTE:
[LocalManager::mgmtShutdown] Executing shutdown request.
[Mar 27 12:57:13.022] Manager {0x7f597e3477e0} NOTE:
[LocalManager::processShutdown] Executing process shutdown request.
[Mar 27 12:57:13.028] Manager {0x7f597e3477e0} ERROR:
[LocalManager::sendMgmtMsgToProcesses] Error writing message
[Mar 27 12:57:13.028] Manager {0x7f597e3477e0} ERROR: (last system error 32:
Broken pipe)
[Mar 27 12:57:13.174] {0x7ffaeec7e7e0} STATUS: opened
/zserver/log/trafficserver/manager.log
[Mar 27 12:57:13.174] {0x7ffaeec7e7e0} NOTE: updated diags config
[Mar 27 12:57:13.520] Manager {0x7ffaeec7e7e0} NOTE: [ClusterCom::ClusterCom]
Node running on OS: 'Linux' Release: '2.6.32-358.6.2.el6.x86_64'
[Mar 27 12:57:13.550] Manager {0x7ffaeec7e7e0} NOTE:
[LocalManager::listenForProxy] Listening on port: 80
[Mar 27 12:57:13.550] Manager {0x7ffaeec7e7e0} NOTE: [TrafficManager] Setup
complete
[Mar 27 12:57:14.618] Manager {0x7ffaeec7e7e0} NOTE:
[LocalManager::startProxy] Launching ts process
[Mar 27 12:57:14.632] Manager {0x7ffaeec7e7e0} NOTE:
[LocalManager::pollMgmtProcessServer] New process connecting fd '15'
[Mar 27 12:57:14.632] Manager {0x7ffaeec7e7e0} NOTE: [Alarms::signalAlarm]
Server Process born
*** traffic.out ***
[E. Mgmt] log == [TrafficManager] using root directory
'/zserver/trafficserver-4.1.2'
[TrafficServer] using root directory '/zserver/trafficserver-4.1.2'
NOTE: Traffic Server received Sig 15: Terminated
[E. Mgmt] log == [TrafficManager] using root directory
'/zserver/trafficserver-4.1.2'
[TrafficServer] using root directory '/zserver/trafficserver-4.1.2'
NOTE: Traffic Server received Sig 11: Segmentation fault
/zserver/trafficserver-4.1.2/bin/traffic_server - STACK TRACE:
/lib64/libpthread.so.0(+0x35a360f500)[0x2b3b55819500]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN12HttpTransact47change_response_header_because_of_range_requestEPNS_5StateEP7HTTPHdr+0x240)[0x54b8a0]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN12HttpTransact28handle_content_length_headerEPNS_5StateEP7HTTPHdrS3_+0x2c8)[0x54bc38]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN12HttpTransact14build_responseEPNS_5StateEP7HTTPHdrS3_11HTTPVersion10HTTPStatusPKc+0x3e3)[0x54c0c3]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN12HttpTransact22handle_transform_readyEPNS_5StateE+0x70)[0x54ca40]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN6HttpSM32call_transact_and_set_next_stateEPFvPN12HttpTransact5StateEE+0x28)[0x51b418]
[jira] [Commented] (TS-2669) ATS crash, then restart with all cached objects cleared
[
https://issues.apache.org/jira/browse/TS-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13950563#comment-13950563
]
AnDao commented on TS-2669:
---
And the storage configure:
]#cat storage.config
/data/trafficserver-4.x/ 220G
ATS crash, then restart with all cached objects cleared
---
Key: TS-2669
URL: https://issues.apache.org/jira/browse/TS-2669
Project: Traffic Server
Issue Type: Bug
Reporter: AnDao
Attachments: cachobjecs.png, storage.png
Hi all,
I'm using ATS 4.1.2, my ATS is just crashed and restart and clean all the
cached objects, cause my backend servers overload. Why ATS do clean all the
cached objects when crash and restart?
The log is:
* manager.log
[Mar 27 12:57:13.022] Manager {0x7f597e3477e0} FATAL:
[LocalManager::pollMgmtProcessServer] Error in read (errno: 104)
[Mar 27 12:57:13.022] Manager {0x7f597e3477e0} NOTE:
[LocalManager::mgmtShutdown] Executing shutdown request.
[Mar 27 12:57:13.022] Manager {0x7f597e3477e0} NOTE:
[LocalManager::processShutdown] Executing process shutdown request.
[Mar 27 12:57:13.028] Manager {0x7f597e3477e0} ERROR:
[LocalManager::sendMgmtMsgToProcesses] Error writing message
[Mar 27 12:57:13.028] Manager {0x7f597e3477e0} ERROR: (last system error 32:
Broken pipe)
[Mar 27 12:57:13.174] {0x7ffaeec7e7e0} STATUS: opened
/zserver/log/trafficserver/manager.log
[Mar 27 12:57:13.174] {0x7ffaeec7e7e0} NOTE: updated diags config
[Mar 27 12:57:13.520] Manager {0x7ffaeec7e7e0} NOTE: [ClusterCom::ClusterCom]
Node running on OS: 'Linux' Release: '2.6.32-358.6.2.el6.x86_64'
[Mar 27 12:57:13.550] Manager {0x7ffaeec7e7e0} NOTE:
[LocalManager::listenForProxy] Listening on port: 80
[Mar 27 12:57:13.550] Manager {0x7ffaeec7e7e0} NOTE: [TrafficManager] Setup
complete
[Mar 27 12:57:14.618] Manager {0x7ffaeec7e7e0} NOTE:
[LocalManager::startProxy] Launching ts process
[Mar 27 12:57:14.632] Manager {0x7ffaeec7e7e0} NOTE:
[LocalManager::pollMgmtProcessServer] New process connecting fd '15'
[Mar 27 12:57:14.632] Manager {0x7ffaeec7e7e0} NOTE: [Alarms::signalAlarm]
Server Process born
*** traffic.out ***
[E. Mgmt] log == [TrafficManager] using root directory
'/zserver/trafficserver-4.1.2'
[TrafficServer] using root directory '/zserver/trafficserver-4.1.2'
NOTE: Traffic Server received Sig 15: Terminated
[E. Mgmt] log == [TrafficManager] using root directory
'/zserver/trafficserver-4.1.2'
[TrafficServer] using root directory '/zserver/trafficserver-4.1.2'
NOTE: Traffic Server received Sig 11: Segmentation fault
/zserver/trafficserver-4.1.2/bin/traffic_server - STACK TRACE:
/lib64/libpthread.so.0(+0x35a360f500)[0x2b3b55819500]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN12HttpTransact47change_response_header_because_of_range_requestEPNS_5StateEP7HTTPHdr+0x240)[0x54b8a0]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN12HttpTransact28handle_content_length_headerEPNS_5StateEP7HTTPHdrS3_+0x2c8)[0x54bc38]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN12HttpTransact14build_responseEPNS_5StateEP7HTTPHdrS3_11HTTPVersion10HTTPStatusPKc+0x3e3)[0x54c0c3]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN12HttpTransact22handle_transform_readyEPNS_5StateE+0x70)[0x54ca40]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN6HttpSM32call_transact_and_set_next_stateEPFvPN12HttpTransact5StateEE+0x28)[0x51b418]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN6HttpSM38state_response_wait_for_transform_readEiPv+0xed)[0x52988d]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN6HttpSM12main_handlerEiPv+0xd8)[0x533178]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN17TransformTerminus12handle_eventEiPv+0x1d2)[0x4e8c62]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x8f)[0x6a5a0f]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN7EThread7executeEv+0x63b)[0x6a658b]
/zserver/trafficserver-4.1.2/bin/traffic_server[0x6a48aa]
/lib64/libpthread.so.0(+0x35a3607851)[0x2b3b55811851]
/lib64/libc.so.6(clone+0x6d)[0x35a32e890d]
[E. Mgmt] log == [TrafficManager] using root directory
'/zserver/trafficserver-4.1.2'
[TrafficServer] using root directory '/zserver/trafficserver-4.1.2'
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (TS-2669) ATS crash, then restart with all cached objects cleared
[
https://issues.apache.org/jira/browse/TS-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-2669:
--
Assignee: Alan M. Carroll
ATS crash, then restart with all cached objects cleared
---
Key: TS-2669
URL: https://issues.apache.org/jira/browse/TS-2669
Project: Traffic Server
Issue Type: Bug
Reporter: AnDao
Assignee: Alan M. Carroll
Attachments: cachobjecs.png, storage.png
Hi all,
I'm using ATS 4.1.2, my ATS is just crashed and restart and clean all the
cached objects, cause my backend servers overload. Why ATS do clean all the
cached objects when crash and restart?
The log is:
* manager.log
[Mar 27 12:57:13.022] Manager {0x7f597e3477e0} FATAL:
[LocalManager::pollMgmtProcessServer] Error in read (errno: 104)
[Mar 27 12:57:13.022] Manager {0x7f597e3477e0} NOTE:
[LocalManager::mgmtShutdown] Executing shutdown request.
[Mar 27 12:57:13.022] Manager {0x7f597e3477e0} NOTE:
[LocalManager::processShutdown] Executing process shutdown request.
[Mar 27 12:57:13.028] Manager {0x7f597e3477e0} ERROR:
[LocalManager::sendMgmtMsgToProcesses] Error writing message
[Mar 27 12:57:13.028] Manager {0x7f597e3477e0} ERROR: (last system error 32:
Broken pipe)
[Mar 27 12:57:13.174] {0x7ffaeec7e7e0} STATUS: opened
/zserver/log/trafficserver/manager.log
[Mar 27 12:57:13.174] {0x7ffaeec7e7e0} NOTE: updated diags config
[Mar 27 12:57:13.520] Manager {0x7ffaeec7e7e0} NOTE: [ClusterCom::ClusterCom]
Node running on OS: 'Linux' Release: '2.6.32-358.6.2.el6.x86_64'
[Mar 27 12:57:13.550] Manager {0x7ffaeec7e7e0} NOTE:
[LocalManager::listenForProxy] Listening on port: 80
[Mar 27 12:57:13.550] Manager {0x7ffaeec7e7e0} NOTE: [TrafficManager] Setup
complete
[Mar 27 12:57:14.618] Manager {0x7ffaeec7e7e0} NOTE:
[LocalManager::startProxy] Launching ts process
[Mar 27 12:57:14.632] Manager {0x7ffaeec7e7e0} NOTE:
[LocalManager::pollMgmtProcessServer] New process connecting fd '15'
[Mar 27 12:57:14.632] Manager {0x7ffaeec7e7e0} NOTE: [Alarms::signalAlarm]
Server Process born
*** traffic.out ***
[E. Mgmt] log == [TrafficManager] using root directory
'/zserver/trafficserver-4.1.2'
[TrafficServer] using root directory '/zserver/trafficserver-4.1.2'
NOTE: Traffic Server received Sig 15: Terminated
[E. Mgmt] log == [TrafficManager] using root directory
'/zserver/trafficserver-4.1.2'
[TrafficServer] using root directory '/zserver/trafficserver-4.1.2'
NOTE: Traffic Server received Sig 11: Segmentation fault
/zserver/trafficserver-4.1.2/bin/traffic_server - STACK TRACE:
/lib64/libpthread.so.0(+0x35a360f500)[0x2b3b55819500]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN12HttpTransact47change_response_header_because_of_range_requestEPNS_5StateEP7HTTPHdr+0x240)[0x54b8a0]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN12HttpTransact28handle_content_length_headerEPNS_5StateEP7HTTPHdrS3_+0x2c8)[0x54bc38]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN12HttpTransact14build_responseEPNS_5StateEP7HTTPHdrS3_11HTTPVersion10HTTPStatusPKc+0x3e3)[0x54c0c3]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN12HttpTransact22handle_transform_readyEPNS_5StateE+0x70)[0x54ca40]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN6HttpSM32call_transact_and_set_next_stateEPFvPN12HttpTransact5StateEE+0x28)[0x51b418]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN6HttpSM38state_response_wait_for_transform_readEiPv+0xed)[0x52988d]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN6HttpSM12main_handlerEiPv+0xd8)[0x533178]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN17TransformTerminus12handle_eventEiPv+0x1d2)[0x4e8c62]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x8f)[0x6a5a0f]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN7EThread7executeEv+0x63b)[0x6a658b]
/zserver/trafficserver-4.1.2/bin/traffic_server[0x6a48aa]
/lib64/libpthread.so.0(+0x35a3607851)[0x2b3b55811851]
/lib64/libc.so.6(clone+0x6d)[0x35a32e890d]
[E. Mgmt] log == [TrafficManager] using root directory
'/zserver/trafficserver-4.1.2'
[TrafficServer] using root directory '/zserver/trafficserver-4.1.2'
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Comment Edited] (TS-2656) Determine server connection scheme immediately before connecting.
[
https://issues.apache.org/jira/browse/TS-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13950815#comment-13950815
]
Ron Barber edited comment on TS-2656 at 3/28/14 2:58 PM:
-
Previous patch was incomplete and did not handle the case where the
server_request URL was never set. In that case it should take the scheme from
the client_request URL.
This patch has run on one of our lesser production farms (ct ycs) for 12 plus
hours without any noticeable issue. Also ran for a short time on a production
server (ycpi) which get our most diverse traffic without any noticeable issue.
was (Author: rwbarber2):
Previous patch was incomplete and did not handle the case where the
server_request URL was never set. In that case it should take the scheme from
the client_request URL.
Determine server connection scheme immediately before connecting.
-
Key: TS-2656
URL: https://issues.apache.org/jira/browse/TS-2656
Project: Traffic Server
Issue Type: Improvement
Reporter: Ron Barber
Assignee: Leif Hedstrom
Fix For: 5.0.0
Attachments: TS-2656_2.patch
ATS currently sets the server connection scheme (sm-t_state.scheme) after
remapping has occurred based on the server URL. Plugin's that desire to
modify the connection scheme after remapping (such as in the
TS_EVENT_HTTP_OS_DNS event) have no method to do so. I propose adding the
following getter/setter API functions:
{code}
/**
Retrieves the server connection scheme for the specified
transaction @a txnp. TSHttpTxnServerSchemeGet() places the length of
the string in the length argument. If the length is NULL then no
attempt is made to dereference it.
@note This function is useful if the server connection scheme needs to
retrieved post remapping.
@param txnp The transaction whose connection scheme to be retrieved
@param length length of the returned string.
@return The connection scheme for the server connection, as a string,
or NULL if not set.
*/
tsapi const char* TSHttpTxnServerSchemeGet(TSHttpTxn txnp, int *length);
/** Set the connection scheme to the server (http or https) for the
specified transaction @a txnp to the string value. If length is -1
then TSHttpTxnServerSchemeSet() assumes that value is null-terminated.
Otherwise, the length of the string value is taken to be length.
@note This function is useful if the server connection scheme needs to
change post remapping.
@param txnp The transaction whose connection scheme to be set
@param value value to set the scheme to.
@param length string stored in value.
@return @c TS_SUCCESS if scheme is recognized, else @c TS_ERROR
*/
tsapi TSReturnCode TSHttpTxnServerSchemeSet(TSHttpTxn txnp,
const char* value,
int length);
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (TS-2673) Remove more remnants of register
Leif Hedstrom created TS-2673: - Summary: Remove more remnants of register Key: TS-2673 URL: https://issues.apache.org/jira/browse/TS-2673 Project: Traffic Server Issue Type: Improvement Components: Core Reporter: Leif Hedstrom There are still a couple of files that uses the register storage class specifier. We should eliminate those. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2656) Determine server connection scheme immediately before connecting.
[
https://issues.apache.org/jira/browse/TS-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ron Barber updated TS-2656:
---
Attachment: TS-2656_2.patch
Previous patch was incomplete and did not handle the case where the
server_request URL was never set. In that case it should take the scheme from
the client_request URL.
Determine server connection scheme immediately before connecting.
-
Key: TS-2656
URL: https://issues.apache.org/jira/browse/TS-2656
Project: Traffic Server
Issue Type: Improvement
Reporter: Ron Barber
Assignee: Leif Hedstrom
Fix For: 5.0.0
Attachments: TS-2656_2.patch
ATS currently sets the server connection scheme (sm-t_state.scheme) after
remapping has occurred based on the server URL. Plugin's that desire to
modify the connection scheme after remapping (such as in the
TS_EVENT_HTTP_OS_DNS event) have no method to do so. I propose adding the
following getter/setter API functions:
{code}
/**
Retrieves the server connection scheme for the specified
transaction @a txnp. TSHttpTxnServerSchemeGet() places the length of
the string in the length argument. If the length is NULL then no
attempt is made to dereference it.
@note This function is useful if the server connection scheme needs to
retrieved post remapping.
@param txnp The transaction whose connection scheme to be retrieved
@param length length of the returned string.
@return The connection scheme for the server connection, as a string,
or NULL if not set.
*/
tsapi const char* TSHttpTxnServerSchemeGet(TSHttpTxn txnp, int *length);
/** Set the connection scheme to the server (http or https) for the
specified transaction @a txnp to the string value. If length is -1
then TSHttpTxnServerSchemeSet() assumes that value is null-terminated.
Otherwise, the length of the string value is taken to be length.
@note This function is useful if the server connection scheme needs to
change post remapping.
@param txnp The transaction whose connection scheme to be set
@param value value to set the scheme to.
@param length string stored in value.
@return @c TS_SUCCESS if scheme is recognized, else @c TS_ERROR
*/
tsapi TSReturnCode TSHttpTxnServerSchemeSet(TSHttpTxn txnp,
const char* value,
int length);
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Assigned] (TS-2673) Remove more remnants of register
[ https://issues.apache.org/jira/browse/TS-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom reassigned TS-2673: - Assignee: Leif Hedstrom Remove more remnants of register Key: TS-2673 URL: https://issues.apache.org/jira/browse/TS-2673 Project: Traffic Server Issue Type: Improvement Components: Core Reporter: Leif Hedstrom Assignee: Leif Hedstrom There are still a couple of files that uses the register storage class specifier. We should eliminate those. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2669) ATS crash, then restart with all cached objects cleared
[
https://issues.apache.org/jira/browse/TS-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13950778#comment-13950778
]
Leif Hedstrom commented on TS-2669:
---
That is not a recommended configuration. In fact, I can not stress enough how
important it is to use the raw devices. My recommendation is that you
reconfigure your disk, and make a 220GB partition, and assign that partition to
ATS. Running on file system cache like this is intended for testing /
development.
That much said, I don't know why it has to purge your segments. Maybe [~amc]
does, but not sure.
ATS crash, then restart with all cached objects cleared
---
Key: TS-2669
URL: https://issues.apache.org/jira/browse/TS-2669
Project: Traffic Server
Issue Type: Bug
Reporter: AnDao
Attachments: cachobjecs.png, storage.png
Hi all,
I'm using ATS 4.1.2, my ATS is just crashed and restart and clean all the
cached objects, cause my backend servers overload. Why ATS do clean all the
cached objects when crash and restart?
The log is:
* manager.log
[Mar 27 12:57:13.022] Manager {0x7f597e3477e0} FATAL:
[LocalManager::pollMgmtProcessServer] Error in read (errno: 104)
[Mar 27 12:57:13.022] Manager {0x7f597e3477e0} NOTE:
[LocalManager::mgmtShutdown] Executing shutdown request.
[Mar 27 12:57:13.022] Manager {0x7f597e3477e0} NOTE:
[LocalManager::processShutdown] Executing process shutdown request.
[Mar 27 12:57:13.028] Manager {0x7f597e3477e0} ERROR:
[LocalManager::sendMgmtMsgToProcesses] Error writing message
[Mar 27 12:57:13.028] Manager {0x7f597e3477e0} ERROR: (last system error 32:
Broken pipe)
[Mar 27 12:57:13.174] {0x7ffaeec7e7e0} STATUS: opened
/zserver/log/trafficserver/manager.log
[Mar 27 12:57:13.174] {0x7ffaeec7e7e0} NOTE: updated diags config
[Mar 27 12:57:13.520] Manager {0x7ffaeec7e7e0} NOTE: [ClusterCom::ClusterCom]
Node running on OS: 'Linux' Release: '2.6.32-358.6.2.el6.x86_64'
[Mar 27 12:57:13.550] Manager {0x7ffaeec7e7e0} NOTE:
[LocalManager::listenForProxy] Listening on port: 80
[Mar 27 12:57:13.550] Manager {0x7ffaeec7e7e0} NOTE: [TrafficManager] Setup
complete
[Mar 27 12:57:14.618] Manager {0x7ffaeec7e7e0} NOTE:
[LocalManager::startProxy] Launching ts process
[Mar 27 12:57:14.632] Manager {0x7ffaeec7e7e0} NOTE:
[LocalManager::pollMgmtProcessServer] New process connecting fd '15'
[Mar 27 12:57:14.632] Manager {0x7ffaeec7e7e0} NOTE: [Alarms::signalAlarm]
Server Process born
*** traffic.out ***
[E. Mgmt] log == [TrafficManager] using root directory
'/zserver/trafficserver-4.1.2'
[TrafficServer] using root directory '/zserver/trafficserver-4.1.2'
NOTE: Traffic Server received Sig 15: Terminated
[E. Mgmt] log == [TrafficManager] using root directory
'/zserver/trafficserver-4.1.2'
[TrafficServer] using root directory '/zserver/trafficserver-4.1.2'
NOTE: Traffic Server received Sig 11: Segmentation fault
/zserver/trafficserver-4.1.2/bin/traffic_server - STACK TRACE:
/lib64/libpthread.so.0(+0x35a360f500)[0x2b3b55819500]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN12HttpTransact47change_response_header_because_of_range_requestEPNS_5StateEP7HTTPHdr+0x240)[0x54b8a0]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN12HttpTransact28handle_content_length_headerEPNS_5StateEP7HTTPHdrS3_+0x2c8)[0x54bc38]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN12HttpTransact14build_responseEPNS_5StateEP7HTTPHdrS3_11HTTPVersion10HTTPStatusPKc+0x3e3)[0x54c0c3]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN12HttpTransact22handle_transform_readyEPNS_5StateE+0x70)[0x54ca40]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN6HttpSM32call_transact_and_set_next_stateEPFvPN12HttpTransact5StateEE+0x28)[0x51b418]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN6HttpSM38state_response_wait_for_transform_readEiPv+0xed)[0x52988d]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN6HttpSM12main_handlerEiPv+0xd8)[0x533178]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN17TransformTerminus12handle_eventEiPv+0x1d2)[0x4e8c62]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x8f)[0x6a5a0f]
/zserver/trafficserver-4.1.2/bin/traffic_server(_ZN7EThread7executeEv+0x63b)[0x6a658b]
/zserver/trafficserver-4.1.2/bin/traffic_server[0x6a48aa]
/lib64/libpthread.so.0(+0x35a3607851)[0x2b3b55811851]
/lib64/libc.so.6(clone+0x6d)[0x35a32e890d]
[E. Mgmt] log == [TrafficManager] using root directory
'/zserver/trafficserver-4.1.2'
[TrafficServer] using root directory '/zserver/trafficserver-4.1.2'
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (TS-2554) New plugin: detect 206 responses from origin, and do a background fill on the entire object
[ https://issues.apache.org/jira/browse/TS-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13950974#comment-13950974 ] ASF subversion and git services commented on TS-2554: - Commit 82cc8c12ad8cf37efcc7dd61d749f74f40f10756 in trafficserver's branch refs/heads/master from [~zwoop] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=82cc8c1 ] TS-2554 Reorder the tests slightly, such that the most common checks goes first New plugin: detect 206 responses from origin, and do a background fill on the entire object --- Key: TS-2554 URL: https://issues.apache.org/jira/browse/TS-2554 Project: Traffic Server Issue Type: New Feature Components: Plugins Reporter: Leif Hedstrom Assignee: Leif Hedstrom Fix For: 5.0.0 This is one solution to the caching partial objects problem, in that it allows the server to automatically detect objects which should be cached, and setup a background task to do so. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (TS-2674) tstop flashes debug message trying to find proxy.process.http.user_agent_response_document_total_size
Greg Henry created TS-2674: -- Summary: tstop flashes debug message trying to find proxy.process.http.user_agent_response_document_total_size Key: TS-2674 URL: https://issues.apache.org/jira/browse/TS-2674 Project: Traffic Server Issue Type: Bug Reporter: Greg Henry tstop displays a logging message while working it flashes this trying to find proxy.process.http.origin_server_response_document_total_size there are a variety of these messages this is an example. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (TS-2674) tstop flashes debug message trying to find proxy.process.http.user_agent_response_document_total_size
[ https://issues.apache.org/jira/browse/TS-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom reassigned TS-2674: - Assignee: Leif Hedstrom tstop flashes debug message trying to find proxy.process.http.user_agent_response_document_total_size --- Key: TS-2674 URL: https://issues.apache.org/jira/browse/TS-2674 Project: Traffic Server Issue Type: Bug Reporter: Greg Henry Assignee: Leif Hedstrom Fix For: 5.0.0 tstop displays a logging message while working it flashes this trying to find proxy.process.http.origin_server_response_document_total_size there are a variety of these messages this is an example. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2674) tstop flashes debug message trying to find proxy.process.http.user_agent_response_document_total_size
[ https://issues.apache.org/jira/browse/TS-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2674: -- Fix Version/s: 5.0.0 tstop flashes debug message trying to find proxy.process.http.user_agent_response_document_total_size --- Key: TS-2674 URL: https://issues.apache.org/jira/browse/TS-2674 Project: Traffic Server Issue Type: Bug Reporter: Greg Henry Fix For: 5.0.0 tstop displays a logging message while working it flashes this trying to find proxy.process.http.origin_server_response_document_total_size there are a variety of these messages this is an example. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (TS-2674) tstop flashes debug message trying to find proxy.process.http.user_agent_response_document_total_size
[ https://issues.apache.org/jira/browse/TS-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom resolved TS-2674. --- Resolution: Fixed tstop flashes debug message trying to find proxy.process.http.user_agent_response_document_total_size --- Key: TS-2674 URL: https://issues.apache.org/jira/browse/TS-2674 Project: Traffic Server Issue Type: Bug Components: Tools Reporter: Greg Henry Assignee: Leif Hedstrom Fix For: 5.0.0 tstop displays a logging message while working it flashes this trying to find proxy.process.http.origin_server_response_document_total_size there are a variety of these messages this is an example. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2674) tstop flashes debug message trying to find proxy.process.http.user_agent_response_document_total_size
[ https://issues.apache.org/jira/browse/TS-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13951158#comment-13951158 ] ASF subversion and git services commented on TS-2674: - Commit 7233291924911da7e6b62101b51912987b9a1a48 in trafficserver's branch refs/heads/master from [~zwoop] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=7233291 ] TS-2674 Remove debug printf() from traffic_top. tstop flashes debug message trying to find proxy.process.http.user_agent_response_document_total_size --- Key: TS-2674 URL: https://issues.apache.org/jira/browse/TS-2674 Project: Traffic Server Issue Type: Bug Components: Tools Reporter: Greg Henry Assignee: Leif Hedstrom Fix For: 5.0.0 tstop displays a logging message while working it flashes this trying to find proxy.process.http.origin_server_response_document_total_size there are a variety of these messages this is an example. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2674) tstop flashes debug message trying to find proxy.process.http.user_agent_response_document_total_size
[ https://issues.apache.org/jira/browse/TS-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2674: -- Component/s: Tools tstop flashes debug message trying to find proxy.process.http.user_agent_response_document_total_size --- Key: TS-2674 URL: https://issues.apache.org/jira/browse/TS-2674 Project: Traffic Server Issue Type: Bug Components: Tools Reporter: Greg Henry Assignee: Leif Hedstrom Fix For: 5.0.0 tstop displays a logging message while working it flashes this trying to find proxy.process.http.origin_server_response_document_total_size there are a variety of these messages this is an example. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2656) Determine server connection scheme immediately before connecting.
[
https://issues.apache.org/jira/browse/TS-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ron Barber updated TS-2656:
---
Attachment: (was: TS-2656_2.patch)
Determine server connection scheme immediately before connecting.
-
Key: TS-2656
URL: https://issues.apache.org/jira/browse/TS-2656
Project: Traffic Server
Issue Type: Improvement
Reporter: Ron Barber
Assignee: Leif Hedstrom
Fix For: 5.0.0
ATS currently sets the server connection scheme (sm-t_state.scheme) after
remapping has occurred based on the server URL. Plugin's that desire to
modify the connection scheme after remapping (such as in the
TS_EVENT_HTTP_OS_DNS event) have no method to do so. I propose adding the
following getter/setter API functions:
{code}
/**
Retrieves the server connection scheme for the specified
transaction @a txnp. TSHttpTxnServerSchemeGet() places the length of
the string in the length argument. If the length is NULL then no
attempt is made to dereference it.
@note This function is useful if the server connection scheme needs to
retrieved post remapping.
@param txnp The transaction whose connection scheme to be retrieved
@param length length of the returned string.
@return The connection scheme for the server connection, as a string,
or NULL if not set.
*/
tsapi const char* TSHttpTxnServerSchemeGet(TSHttpTxn txnp, int *length);
/** Set the connection scheme to the server (http or https) for the
specified transaction @a txnp to the string value. If length is -1
then TSHttpTxnServerSchemeSet() assumes that value is null-terminated.
Otherwise, the length of the string value is taken to be length.
@note This function is useful if the server connection scheme needs to
change post remapping.
@param txnp The transaction whose connection scheme to be set
@param value value to set the scheme to.
@param length string stored in value.
@return @c TS_SUCCESS if scheme is recognized, else @c TS_ERROR
*/
tsapi TSReturnCode TSHttpTxnServerSchemeSet(TSHttpTxn txnp,
const char* value,
int length);
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (TS-2675) metalink: Fix crash and plug memory leaks
Jack Bates created TS-2675: -- Summary: metalink: Fix crash and plug memory leaks Key: TS-2675 URL: https://issues.apache.org/jira/browse/TS-2675 Project: Traffic Server Issue Type: Bug Reporter: Jack Bates Fix crash if INKVConnInternal::do_io_close() gets called after a message is already complete, plug memory leaks reported by Valgrind, and don't finish computing the digest more than once. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2670) trafficserver process dies with SEGFAULT (failed assert `masksum == mh-m_presence_bits`)
[
https://issues.apache.org/jira/browse/TS-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13950801#comment-13950801
]
Leif Hedstrom commented on TS-2670:
---
Yeah, it is a different trace, but we know there are issues around this exact
code, so crossing my finger it's the same :).
trafficserver process dies with SEGFAULT (failed assert `masksum ==
mh-m_presence_bits`)
-
Key: TS-2670
URL: https://issues.apache.org/jira/browse/TS-2670
Project: Traffic Server
Issue Type: Bug
Components: HTTP
Reporter: Timur Irmatov
Assignee: Alan M. Carroll
Fix For: 5.0.0
I have upgraded our installation of TrafficServer from 4.1.2 to 4.2.0. ATS is
running as a forward proxy (to save internet bandwidth). As soon as traffic
grows to our normal levels ATS crashes because of segmentation fault:
{noformat}
[ET_NET 0][11682]: segfault at 1c ip 005c2d50 sp 7fff35b5a168
error 4 in traffic_server[40+35f000]
{noformat}
I have recompiled ATS with --enable-debug. Then ATS dies with failed
assertion:
{noformat}
traffic_server[4003]: FATAL: MIME.cc:599: failed assert `masksum ==
mh-m_presence_bits`
{noformat}
Stack trace:
{noformat}
% sudo gdb /opt/ts/bin/traffic_server /opt/ts/core
GNU gdb (GDB) 7.6.1-ubuntu
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type show copying
and show warranty for details.
This GDB was configured as x86_64-linux-gnu.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/...
Reading symbols from /opt/ts/bin/traffic_server...done.
warning: core file may not match specified executable file.
[New LWP 4003]
[New LWP 4004]
[New LWP 4021]
[New LWP 4022]
[New LWP 4023]
[New LWP 4024]
[New LWP 4025]
[New LWP 4026]
warning: Can't read pathname for load map: Input/output error.
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
Core was generated by `/opt/ts/bin/traffic_server -M --httpport
3129:fd=7:tr-full'.
Program terminated with signal 6, Aborted.
#0 0x2b222a363f77 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
56 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0 0x2b222a363f77 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1 0x2b222a3675e8 in __GI_abort () at abort.c:90
#2 0x2b222830d25e in ink_die_die_die (retval=1) at ink_error.cc:43
#3 0x2b222830d349 in ink_fatal_va(int, const char *, typedef
__va_list_tag __va_list_tag *) (return_code=1, message_format=0x2b222831b6c8
%s:%d: failed assert `%s`, ap=0x7fff793cc408)
at ink_error.cc:65
#4 0x2b222830d3f4 in ink_fatal (return_code=1,
message_format=0x2b222831b6c8 %s:%d: failed assert `%s`) at ink_error.cc:73
#5 0x2b222830bf37 in _ink_assert (expression=0x7409e8 masksum ==
mh-m_presence_bits, file=0x74075f MIME.cc, line=599) at ink_assert.cc:37
#6 0x006127cd in mime_hdr_sanity_check (mh=0x2b2233aeb588) at
MIME.cc:599
#7 0x006140fa in mime_hdr_copy_onto (s_mh=0x2b2233aeb588,
s_heap=0x2b2233aeb4d0, d_mh=0x2b2233a138c8, d_heap=0x2b2233a13810,
inherit_strs=false) at MIME.cc:1102
#8 0x00606a0e in http_hdr_copy_onto (s_hh=0x2b2233aeb558,
s_heap=0x2b2233aeb4d0, d_hh=0x2b2233a13898, d_heap=0x2b2233a13810,
inherit_strs=true) at HTTP.cc:357
#9 0x00606a7f in http_hdr_clone (s_hh=0x2b2233aeb558,
s_heap=0x2b2233aeb4d0, d_heap=0x2b2233a13810) at HTTP.cc:375
#10 0x005086ce in HTTPHdr::copy (this=0x2765bb0, hdr=0x2b2233aeaea8)
at ./hdrs/HTTP.h:866
#11 0x00508dba in HTTPInfo::response_set (this=0x2b22339f3868,
resp=0x2b2233aeaea8) at ./hdrs/HTTP.h:1403
#12 0x0059ccf4 in
HttpTransact::merge_and_update_headers_for_cache_update (s=0x2b22339f3800) at
HttpTransact.cc:4657
#13 0x0059bde6 in
HttpTransact::handle_cache_operation_on_forward_server_response
(s=0x2b22339f3800) at HttpTransact.cc:4463
#14 0x00599cf6 in HttpTransact::handle_forward_server_connection_open
(s=0x2b22339f3800) at HttpTransact.cc:3966
#15 0x00598440 in HttpTransact::handle_response_from_server
(s=0x2b22339f3800) at HttpTransact.cc:3643
#16 0x00596e28 in HttpTransact::HandleResponse (s=0x2b22339f3800) at
HttpTransact.cc:3334
#17 0x0057d4f1 in HttpSM::call_transact_and_set_next_state
(this=0x2b22339f3790, f=0x0) at HttpSM.cc:6779
#18 0x0056a7f3 in HttpSM::handle_api_return
[jira] [Resolved] (TS-2673) Remove more remnants of register
[ https://issues.apache.org/jira/browse/TS-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom resolved TS-2673. --- Resolution: Invalid Meh, this is a dud, bad implementation on the resolver macros ... Remove more remnants of register Key: TS-2673 URL: https://issues.apache.org/jira/browse/TS-2673 Project: Traffic Server Issue Type: Improvement Components: Core Reporter: Leif Hedstrom Assignee: Leif Hedstrom There are still a couple of files that uses the register storage class specifier. We should eliminate those. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2553) Fix a segfault in the Metalink plugin reported by Faysal Banna and preserve the Content-Length header
[ https://issues.apache.org/jira/browse/TS-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13951191#comment-13951191 ] ASF GitHub Bot commented on TS-2553: Github user jablko commented on the pull request: https://github.com/apache/trafficserver/pull/63#issuecomment-38952957 The metalink/test/pipeliningDisconnect script in commit 45393e reproduces the crash two out of three times on my system, but if it's a race condition it might manifest with different frequency on different systems? Unfortunately I haven't figured out yet how to exercise it deterministically from outside Traffic Server (by using just a combination of requests/responses and config settings). Any advice on how to expose it more predictably? Fix a segfault in the Metalink plugin reported by Faysal Banna and preserve the Content-Length header - Key: TS-2553 URL: https://issues.apache.org/jira/browse/TS-2553 Project: Traffic Server Issue Type: Bug Components: Plugins Reporter: Jack Bates Assignee: James Peach Fix For: 5.0.0 Fix a segfault in the Metalink plugin reported by Faysal Banna: https://github.com/jablko/dedup/issues/1 Copy the upstream nbytes (if known) downstream to preserve the Content-Length header. Improve comments in the plugin code. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2554) New plugin: detect 206 responses from origin, and do a background fill on the entire object
[ https://issues.apache.org/jira/browse/TS-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13951308#comment-13951308 ] ASF subversion and git services commented on TS-2554: - Commit 88a0d3bcd2a030a58aea166b954431d9ced8ee03 in trafficserver's branch refs/heads/master from [~zwoop] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=88a0d3b ] TS-2554 Ignore return from fwrite() New plugin: detect 206 responses from origin, and do a background fill on the entire object --- Key: TS-2554 URL: https://issues.apache.org/jira/browse/TS-2554 Project: Traffic Server Issue Type: New Feature Components: Plugins Reporter: Leif Hedstrom Assignee: Leif Hedstrom Fix For: 5.0.0 This is one solution to the caching partial objects problem, in that it allows the server to automatically detect objects which should be cached, and setup a background task to do so. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2675) metalink: Fix crash and plug memory leaks
[ https://issues.apache.org/jira/browse/TS-2675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13951580#comment-13951580 ] ASF subversion and git services commented on TS-2675: - Commit f88a72606610ee79c458cee32b9ea34c16695c6b in trafficserver's branch refs/heads/master from [~nottheoilrig] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=f88a726 ] TS-2675: metalink: Send our own TS_EVENT_VCONN_WRITE_COMPLETE event upstream Send our own TS_EVENT_VCONN_WRITE_COMPLETE event upstream when the input is complete otherwise HttpSM::update_stats() won't get called and the transaction won't get logged. (If there are upstream transformations they won't get a chance to clean up otherwise!) metalink: Fix crash and plug memory leaks - Key: TS-2675 URL: https://issues.apache.org/jira/browse/TS-2675 Project: Traffic Server Issue Type: Bug Reporter: Jack Bates Fix For: 5.0.0 Fix crash if INKVConnInternal::do_io_close() gets called after a message is already complete, plug memory leaks reported by Valgrind, and don't finish computing the digest more than once. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2675) metalink: Fix crash and plug memory leaks
[ https://issues.apache.org/jira/browse/TS-2675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13951583#comment-13951583 ] ASF subversion and git services commented on TS-2675: - Commit a9a0b7ccbbff448fd14ea2b22930ce6fc8b2c95f in trafficserver's branch refs/heads/master from [~nottheoilrig] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=a9a0b7c ] TS-2675: metalink: Reformat comments metalink: Clarify that we *must* check TSVConnClosedGet(), if only to clean up allocated data metalink: Fix crash and plug memory leaks - Key: TS-2675 URL: https://issues.apache.org/jira/browse/TS-2675 Project: Traffic Server Issue Type: Bug Reporter: Jack Bates Fix For: 5.0.0 Fix crash if INKVConnInternal::do_io_close() gets called after a message is already complete, plug memory leaks reported by Valgrind, and don't finish computing the digest more than once. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2675) metalink: Fix crash and plug memory leaks
[ https://issues.apache.org/jira/browse/TS-2675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13951582#comment-13951582 ] ASF subversion and git services commented on TS-2675: - Commit f9d74b9feefa2f7a4c8d59b6633efe9de8415d50 in trafficserver's branch refs/heads/master from [~nottheoilrig] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=f9d74b9 ] TS-2675: metalink: Don't finish computing the digest more than once and test that the proxy rewrites the Location header if the file is already cached metalink: Fix crash and plug memory leaks - Key: TS-2675 URL: https://issues.apache.org/jira/browse/TS-2675 Project: Traffic Server Issue Type: Bug Reporter: Jack Bates Fix For: 5.0.0 Fix crash if INKVConnInternal::do_io_close() gets called after a message is already complete, plug memory leaks reported by Valgrind, and don't finish computing the digest more than once. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2675) metalink: Fix crash and plug memory leaks
[ https://issues.apache.org/jira/browse/TS-2675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13951584#comment-13951584 ] ASF subversion and git services commented on TS-2675: - Commit ad6806ea71218e760e64e658909bd202177e65de in trafficserver's branch refs/heads/master from [~jpe...@apache.org] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=ad6806e ] Update CHANGES for TS-2675 metalink: Fix crash and plug memory leaks - Key: TS-2675 URL: https://issues.apache.org/jira/browse/TS-2675 Project: Traffic Server Issue Type: Bug Reporter: Jack Bates Fix For: 5.0.0 Fix crash if INKVConnInternal::do_io_close() gets called after a message is already complete, plug memory leaks reported by Valgrind, and don't finish computing the digest more than once. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (TS-2675) metalink: Fix crash and plug memory leaks
[ https://issues.apache.org/jira/browse/TS-2675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Peach resolved TS-2675. - Resolution: Fixed Fix Version/s: 5.0.0 Assignee: James Peach metalink: Fix crash and plug memory leaks - Key: TS-2675 URL: https://issues.apache.org/jira/browse/TS-2675 Project: Traffic Server Issue Type: Bug Reporter: Jack Bates Assignee: James Peach Fix For: 5.0.0 Fix crash if INKVConnInternal::do_io_close() gets called after a message is already complete, plug memory leaks reported by Valgrind, and don't finish computing the digest more than once. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (TS-2676) crash when enable --enable-linux-native-aio
bettydramit created TS-2676:
---
Summary: crash when enable --enable-linux-native-aio
Key: TS-2676
URL: https://issues.apache.org/jira/browse/TS-2676
Project: Traffic Server
Issue Type: Bug
Reporter: bettydramit
Centos 6 x86_64 gitmaster version
when enable --enable-linux-native-aio ,ATS will be crash
(gdb) bt
#0 0x006bb2e2 in QueueAIOCallback, Continuation::Link_link::enqueue
(this=0x8040, e=0x2b2077f60180) at ../../lib/ts/List.h:290
#1 0x006bad5b in ink_aio_read (op=0x2b2077f60180) at AIO.cc:605
#2 0x006800d5 in CacheVC::handleRead (this=0x2b2077f6) at
Cache.cc:2605
#3 0x00687922 in CacheVC::do_read_call (this=0x2b2077f6,
akey=0x2b2077f60038) at P_CacheInternal.h:703
#4 0x0068088a in CacheVC::removeEvent (this=0x2b2077f6) at
Cache.cc:2733
#5 0x00680c8b in Cache::remove (this=0x3f62270, cont=0x2b1ea8a764e0,
key=0x103fbb40, type=CACHE_FRAG_TYPE_NONE, hostname=0x0,
host_len=0) at Cache.cc:2787
#6 0x0050e60e in CacheProcessor::remove (this=0xf91ef0,
cont=0x2b1ea8a764e0, key=0x103fbb40, cluster_cache_local=true,
frag_type=CACHE_FRAG_TYPE_NONE, rm_user_agents=true, rm_link=false,
hostname=0x0, host_len=0) at ../iocore/cache/P_CacheInternal.h:1254
#7 0x00507365 in TSCacheRemove (contp=0x2b1ea8a764e0, key=0x103fbb40)
at InkAPI.cc:6644
(gdb) f 1
#1 0x006bad5b in ink_aio_read (op=0x2b2077f60180) at AIO.cc:605
605 this_ethread()-diskHandler-ready_list.enqueue(op);
(gdb) list
600 int
601 ink_aio_read(AIOCallback *op, int /* fromAPI ATS_UNUSED */) {
602 op-aiocb.aio_reqprio = AIO_DEFAULT_PRIORITY;
603 op-aiocb.aio_lio_opcode = IO_CMD_PREAD;
604 op-aiocb.data = op;
605 this_ethread()-diskHandler-ready_list.enqueue(op);
606
607 return 1;
608 }
609
--
This message was sent by Atlassian JIRA
(v6.2#6252)
