[jira] [Updated] (TS-2092) Use of uninitialized member in HdrHeap
[ https://issues.apache.org/jira/browse/TS-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2092: -- Fix Version/s: 3.3.5 Use of uninitialized member in HdrHeap -- Key: TS-2092 URL: https://issues.apache.org/jira/browse/TS-2092 Project: Traffic Server Issue Type: Bug Components: Core Reporter: Leif Hedstrom Assignee: Leif Hedstrom Fix For: 3.3.5 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-2092) Use of uninitialized member in HdrHeap
Leif Hedstrom created TS-2092: - Summary: Use of uninitialized member in HdrHeap Key: TS-2092 URL: https://issues.apache.org/jira/browse/TS-2092 Project: Traffic Server Issue Type: Bug Components: Core Reporter: Leif Hedstrom -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (TS-2092) Use of uninitialized member in HdrHeap
[ https://issues.apache.org/jira/browse/TS-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom reassigned TS-2092: - Assignee: Leif Hedstrom Use of uninitialized member in HdrHeap -- Key: TS-2092 URL: https://issues.apache.org/jira/browse/TS-2092 Project: Traffic Server Issue Type: Bug Components: Core Reporter: Leif Hedstrom Assignee: Leif Hedstrom -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-2093) Plugin API doesn't check stat bounds on creation which can cause assert to trigger
[ https://issues.apache.org/jira/browse/TS-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber updated TS-2093: Labels: C (was: ) Plugin API doesn't check stat bounds on creation which can cause assert to trigger -- Key: TS-2093 URL: https://issues.apache.org/jira/browse/TS-2093 Project: Traffic Server Issue Type: Bug Reporter: Phil Sorber Labels: C Fix For: 3.3.6 The records created for stats for the API are limited by TS_MAX_API_STATS. Trying to create more than that causes an assert to trigger. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-2093) Plugin API doesn't check stat bounds on creation which can cause assert to trigger
Phil Sorber created TS-2093: --- Summary: Plugin API doesn't check stat bounds on creation which can cause assert to trigger Key: TS-2093 URL: https://issues.apache.org/jira/browse/TS-2093 Project: Traffic Server Issue Type: Bug Reporter: Phil Sorber The records created for stats for the API are limited by TS_MAX_API_STATS. Trying to create more than that causes an assert to trigger. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-2093) Plugin API doesn't check stat bounds on creation which can cause assert to trigger
[ https://issues.apache.org/jira/browse/TS-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber updated TS-2093: Fix Version/s: 3.3.6 Plugin API doesn't check stat bounds on creation which can cause assert to trigger -- Key: TS-2093 URL: https://issues.apache.org/jira/browse/TS-2093 Project: Traffic Server Issue Type: Bug Reporter: Phil Sorber Fix For: 3.3.6 The records created for stats for the API are limited by TS_MAX_API_STATS. Trying to create more than that causes an assert to trigger. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-2093) Plugin API doesn't check stat bounds on creation which can cause assert to trigger
[ https://issues.apache.org/jira/browse/TS-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728621#comment-13728621 ] Phil Sorber commented on TS-2093: - Also, id doesn't need to be volatile. Just top_stat which is already defined as such. Plugin API doesn't check stat bounds on creation which can cause assert to trigger -- Key: TS-2093 URL: https://issues.apache.org/jira/browse/TS-2093 Project: Traffic Server Issue Type: Bug Reporter: Phil Sorber Labels: C Fix For: 3.3.6 The records created for stats for the API are limited by TS_MAX_API_STATS. Trying to create more than that causes an assert to trigger. This problem should be superseded by TS-454 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-2093) Plugin API doesn't check stat bounds on creation which can cause assert to trigger
[ https://issues.apache.org/jira/browse/TS-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber updated TS-2093: Description: The records created for stats for the API are limited by TS_MAX_API_STATS. Trying to create more than that causes an assert to trigger. This problem should be superseded by TS-454 was:The records created for stats for the API are limited by TS_MAX_API_STATS. Trying to create more than that causes an assert to trigger. Plugin API doesn't check stat bounds on creation which can cause assert to trigger -- Key: TS-2093 URL: https://issues.apache.org/jira/browse/TS-2093 Project: Traffic Server Issue Type: Bug Reporter: Phil Sorber Labels: C Fix For: 3.3.6 The records created for stats for the API are limited by TS_MAX_API_STATS. Trying to create more than that causes an assert to trigger. This problem should be superseded by TS-454 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (TS-2093) Plugin API doesn't check stat bounds on creation which can cause assert to trigger
[ https://issues.apache.org/jira/browse/TS-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber reassigned TS-2093: --- Assignee: Phil Sorber Plugin API doesn't check stat bounds on creation which can cause assert to trigger -- Key: TS-2093 URL: https://issues.apache.org/jira/browse/TS-2093 Project: Traffic Server Issue Type: Bug Reporter: Phil Sorber Assignee: Phil Sorber Labels: C Fix For: 3.3.6 The records created for stats for the API are limited by TS_MAX_API_STATS. Trying to create more than that causes an assert to trigger. This problem should be superseded by TS-454 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-2093) Plugin API doesn't check stat bounds on creation which can cause assert to trigger
[ https://issues.apache.org/jira/browse/TS-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728622#comment-13728622 ] ASF subversion and git services commented on TS-2093: - Commit 76ef33d435236aa680e2180191e5584af5adb0d1 in branch refs/heads/master from [~psudaemon] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=76ef33d ] TS-2093: Check bounds on plugin stat creation. Plugin API doesn't check stat bounds on creation which can cause assert to trigger -- Key: TS-2093 URL: https://issues.apache.org/jira/browse/TS-2093 Project: Traffic Server Issue Type: Bug Reporter: Phil Sorber Assignee: Phil Sorber Labels: C Fix For: 3.3.6 The records created for stats for the API are limited by TS_MAX_API_STATS. Trying to create more than that causes an assert to trigger. This problem should be superseded by TS-454 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TS-2093) Plugin API doesn't check stat bounds on creation which can cause assert to trigger
[ https://issues.apache.org/jira/browse/TS-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber resolved TS-2093. - Resolution: Fixed Fix Version/s: (was: 3.3.6) 3.3.5 Plugin API doesn't check stat bounds on creation which can cause assert to trigger -- Key: TS-2093 URL: https://issues.apache.org/jira/browse/TS-2093 Project: Traffic Server Issue Type: Bug Reporter: Phil Sorber Assignee: Phil Sorber Labels: C Fix For: 3.3.5 The records created for stats for the API are limited by TS_MAX_API_STATS. Trying to create more than that causes an assert to trigger. This problem should be superseded by TS-454 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TS-2093) Plugin API doesn't check stat bounds on creation which can cause assert to trigger
[ https://issues.apache.org/jira/browse/TS-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber closed TS-2093. --- Plugin API doesn't check stat bounds on creation which can cause assert to trigger -- Key: TS-2093 URL: https://issues.apache.org/jira/browse/TS-2093 Project: Traffic Server Issue Type: Bug Reporter: Phil Sorber Assignee: Phil Sorber Labels: C Fix For: 3.3.5 The records created for stats for the API are limited by TS_MAX_API_STATS. Trying to create more than that causes an assert to trigger. This problem should be superseded by TS-454 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1917) It seems that one of assert in HttpTransact::handle_content_length_header() is unnecessary
[
https://issues.apache.org/jira/browse/TS-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-1917:
--
Fix Version/s: (was: 3.3.5)
3.3.6
It seems that one of assert in HttpTransact::handle_content_length_header()
is unnecessary
---
Key: TS-1917
URL: https://issues.apache.org/jira/browse/TS-1917
Project: Traffic Server
Issue Type: Bug
Components: HTTP
Reporter: Yunkai Zhang
Assignee: James Peach
Fix For: 3.3.6
Attachments: ts-1917.wj.diff
ATS crashed by the following assert in debug mode:
{code}
(gdb) bt
#0 0x003e86c32885 in raise () from /lib64/libc.so.6
#1 0x003e86c34065 in abort () from /lib64/libc.so.6
#2 0x2b349592e234 in ink_die_die_die (retval=1) at ink_error.cc:43
#3 0x2b349592e301 in ink_fatal_va(int, const char *, typedef
__va_list_tag __va_list_tag *) (return_code=1,
message_format=0x2b349594a748 %s:%d: failed assert `%s`,
ap=0x2b34979073a0) at ink_error.cc:65
#4 0x2b349592e3ca in ink_fatal (return_code=1,
message_format=0x2b349594a748 %s:%d: failed assert `%s`) at ink_error.cc:73
#5 0x2b349592d2cc in _ink_assert (expression=0x70fef0 s-range_setup !=
RANGE_NOT_TRANSFORM_REQUESTED, file=0x70a613 HttpTransact.cc, line=6660)
at ink_assert.cc:37
#6 0x0059cb57 in HttpTransact::handle_content_length_header
(s=0x2b34b1207120, header=0x2b34b1207800, base=0x2b36d0030070) at
HttpTransact.cc:6660
#7 0x005a116f in HttpTransact::build_response (s=0x2b34b1207120,
base_response=0x2b36d0030070, outgoing_response=0x2b34b1207800,
outgoing_version=..., status_code=HTTP_STATUS_OK, reason_phrase=0x725709
OK) at HttpTransact.cc:7731
#8 0x00594972 in
HttpTransact::handle_cache_operation_on_forward_server_response
(s=0x2b34b1207120) at HttpTransact.cc:4373
#9 0x005924f8 in HttpTransact::handle_forward_server_connection_open
(s=0x2b34b1207120) at HttpTransact.cc:3818
#10 0x00590c08 in HttpTransact::handle_response_from_server
(s=0x2b34b1207120) at HttpTransact.cc:3495
#11 0x0058f60e in HttpTransact::HandleResponse (s=0x2b34b1207120) at
HttpTransact.cc:3185
#12 0x00575f25 in HttpSM::call_transact_and_set_next_state
(this=0x2b34b12070b0, f=0) at HttpSM.cc:6685
#13 0x00563ca4 in HttpSM::handle_api_return (this=0x2b34b12070b0) at
HttpSM.cc:1555
#14 0x00563a79 in HttpSM::state_api_callout (this=0x2b34b12070b0,
event=0, data=0x0) at HttpSM.cc:1487
#15 0x0056f79b in HttpSM::do_api_callout_internal
(this=0x2b34b12070b0) at HttpSM.cc:4702
#16 0x0057bce8 in HttpSM::do_api_callout (this=0x2b34b12070b0) at
HttpSM.cc:503
#17 0x00564b68 in HttpSM::state_read_server_response_header
(this=0x2b34b12070b0, event=100, data=0x2b35ff9ef5d0) at HttpSM.cc:1869
#18 0x00567140 in HttpSM::main_handler (this=0x2b34b12070b0,
event=100, data=0x2b35ff9ef5d0) at HttpSM.cc:2501
#19 0x004e0f52 in Continuation::handleEvent (this=0x2b34b12070b0,
event=100, data=0x2b35ff9ef5d0) at ../iocore/eventsystem/I_Continuation.h:146
#20 0x006ba540 in read_signal_and_update (event=100,
vc=0x2b35ff9ef4c0) at UnixNetVConnection.cc:138
#21 0x006bae90 in read_from_net (nh=0x2b34960fdbc0,
vc=0x2b35ff9ef4c0, thread=0x2b34960fa010) at UnixNetVConnection.cc:320
#22 0x006bcc7f in UnixNetVConnection::net_read_io
(this=0x2b35ff9ef4c0, nh=0x2b34960fdbc0, lthread=0x2b34960fa010) at
UnixNetVConnection.cc:818
#23 0x006b72e8 in NetHandler::mainNetEvent (this=0x2b34960fdbc0,
event=5, e=0x2b349cf16b40) at UnixNet.cc:377
#24 0x004e0f52 in Continuation::handleEvent (this=0x2b34960fdbc0,
event=5, data=0x2b349cf16b40) at ../iocore/eventsystem/I_Continuation.h:146
#25 0x006dbcd0 in EThread::process_event (this=0x2b34960fa010,
e=0x2b349cf16b40, calling_code=5) at UnixEThread.cc:141
#26 0x006dc2b2 in EThread::execute (this=0x2b34960fa010) at
UnixEThread.cc:265
#27 0x006daedc in spawn_thread_internal (a=0x15e2160) at Thread.cc:88
#28 0x003e878077f1 in start_thread () from /lib64/libpthread.so.0
#29 0x003e86ce5ccd in clone () from /lib64/libc.so.6
{code}
By analyzing the code, it seems that this assertion is unnecessary:
When client sends a request to ATS, and the content hits in cache, but if the
cache is STALE, ATS will sent a request to Original-Server.
In this case, the t_sate.source will be updated to
SOURCE_HTTP_ORIGIN_SERVER(the old value is SOURCE_CACHE), and in
HttpTransact::handle_cache_operation_on_forward_server_response()
= s-state_machine-do_range_setup_if_necessary(), the s-range_setup could
be updated to
[jira] [Resolved] (TS-2081) WCCP Client Address should not be replicated between cluster members.
[ https://issues.apache.org/jira/browse/TS-2081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom resolved TS-2081. --- Resolution: Fixed I made wccp.addr LOCAL,but left wccp.services. I think even if we don't replicate the file (now), it makes sense to replicate the filename. Please revert this if you don't think it's right. WCCP Client Address should not be replicated between cluster members. - Key: TS-2081 URL: https://issues.apache.org/jira/browse/TS-2081 Project: Traffic Server Issue Type: Bug Components: Clustering Reporter: Mario Poier Assignee: Alan M. Carroll Fix For: 3.3.5 The proxy.config.wccp.addr is replicated between cluster members. This replication occurs even when the LOCAL keyword has been defined in the records.config file. Version 3.2.0 (build # 11186) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-2081) WCCP Client Address should not be replicated between cluster members.
[ https://issues.apache.org/jira/browse/TS-2081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728636#comment-13728636 ] ASF subversion and git services commented on TS-2081: - Commit 994d978a060012de934b80857d1dfab817f18a3a in branch refs/heads/master from [~zwoop] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=994d978 ] TS-2081 Make the WCCP addr configuration LOCAL WCCP Client Address should not be replicated between cluster members. - Key: TS-2081 URL: https://issues.apache.org/jira/browse/TS-2081 Project: Traffic Server Issue Type: Bug Components: Clustering Reporter: Mario Poier Assignee: Alan M. Carroll Fix For: 3.3.5 The proxy.config.wccp.addr is replicated between cluster members. This replication occurs even when the LOCAL keyword has been defined in the records.config file. Version 3.2.0 (build # 11186) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TS-2090) Make proxy.config.allocator.enable_reclaim default based on build instructions
[ https://issues.apache.org/jira/browse/TS-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom resolved TS-2090. --- Resolution: Fixed I'm resolving this now, since we didn't get any more changes to it. Make proxy.config.allocator.enable_reclaim default based on build instructions -- Key: TS-2090 URL: https://issues.apache.org/jira/browse/TS-2090 Project: Traffic Server Issue Type: Improvement Components: Build Reporter: Leif Hedstrom Assignee: Leif Hedstrom Fix For: 3.3.5 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-2090) Make proxy.config.allocator.enable_reclaim default based on build instructions
[ https://issues.apache.org/jira/browse/TS-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728649#comment-13728649 ] ASF subversion and git services commented on TS-2090: - Commit 1bb12edf9cd9b0076eaf39b8665909846743ee73 in branch refs/heads/3.3.x from [~zwoop] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=1bb12ed ] Merge branch 'master' into 3.3.x * master: (295 commits) TS-2081 Make the WCCP addr configuration LOCAL TS-2093: Check bounds on plugin stat creation. TS-2092 Use of uninitialized member in HdrHeap. [TS-2052] ET_SSL thread spinning TS-2090 Make proxy.config.allocator.enable_reclaim default based on build instructions TS-1006: adjust some reclaimable-freelist's default configuration Updated newish tests to the gitignore Fix autoconf checks for mcheck_pedantic() Fix configure check for eventfd TS-1330: Fix logging core at checkout_write() add some standard extensions to ignore list TS-1953: remove version check from stable plugins TS-1953: Remove check_ts_version() from experimental plugins TS-1953: remove check_ts_version() from examples Added TS-2086. TS-2086 Remove a few more unused configs Added TS-1685 TS-1685 Remove TS_MICRO and fellas Added Ts-1255 TS-1255 Fix the types for all overridable configs. This was actually a real bug in the code, in that all float configurations were actually treated as integer, rendering them useless ... Make proxy.config.allocator.enable_reclaim default based on build instructions -- Key: TS-2090 URL: https://issues.apache.org/jira/browse/TS-2090 Project: Traffic Server Issue Type: Improvement Components: Build Reporter: Leif Hedstrom Assignee: Leif Hedstrom Fix For: 3.3.5 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1953) remove check_ts_version() from (example) plugins or make it an API
[
https://issues.apache.org/jira/browse/TS-1953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728653#comment-13728653
]
ASF subversion and git services commented on TS-1953:
-
Commit 1bb12edf9cd9b0076eaf39b8665909846743ee73 in branch refs/heads/3.3.x from
[~zwoop]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=1bb12ed ]
Merge branch 'master' into 3.3.x
* master: (295 commits)
TS-2081 Make the WCCP addr configuration LOCAL
TS-2093: Check bounds on plugin stat creation.
TS-2092 Use of uninitialized member in HdrHeap.
[TS-2052] ET_SSL thread spinning
TS-2090 Make proxy.config.allocator.enable_reclaim default based on build
instructions
TS-1006: adjust some reclaimable-freelist's default configuration
Updated newish tests to the gitignore
Fix autoconf checks for mcheck_pedantic()
Fix configure check for eventfd
TS-1330: Fix logging core at checkout_write()
add some standard extensions to ignore list
TS-1953: remove version check from stable plugins
TS-1953: Remove check_ts_version() from experimental plugins
TS-1953: remove check_ts_version() from examples
Added TS-2086.
TS-2086 Remove a few more unused configs
Added TS-1685
TS-1685 Remove TS_MICRO and fellas
Added Ts-1255
TS-1255 Fix the types for all overridable configs. This was actually a real
bug in the code, in that all float configurations were actually treated as
integer, rendering them useless
...
remove check_ts_version() from (example) plugins or make it an API
--
Key: TS-1953
URL: https://issues.apache.org/jira/browse/TS-1953
Project: Traffic Server
Issue Type: Improvement
Components: Plugins
Reporter: Igor Galić
Fix For: sometime
almost every single of our (example) plugins has a function
{{chec_ts_version()}}. If this boiler-code is so crucial to a plugin's
functionality, we should offer an API for it, instead of making developers
write (copy) that code every time.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1685) configure --enable-micro doesn't build
[ https://issues.apache.org/jira/browse/TS-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728658#comment-13728658 ] ASF subversion and git services commented on TS-1685: - Commit 1bb12edf9cd9b0076eaf39b8665909846743ee73 in branch refs/heads/3.3.x from [~zwoop] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=1bb12ed ] Merge branch 'master' into 3.3.x * master: (295 commits) TS-2081 Make the WCCP addr configuration LOCAL TS-2093: Check bounds on plugin stat creation. TS-2092 Use of uninitialized member in HdrHeap. [TS-2052] ET_SSL thread spinning TS-2090 Make proxy.config.allocator.enable_reclaim default based on build instructions TS-1006: adjust some reclaimable-freelist's default configuration Updated newish tests to the gitignore Fix autoconf checks for mcheck_pedantic() Fix configure check for eventfd TS-1330: Fix logging core at checkout_write() add some standard extensions to ignore list TS-1953: remove version check from stable plugins TS-1953: Remove check_ts_version() from experimental plugins TS-1953: remove check_ts_version() from examples Added TS-2086. TS-2086 Remove a few more unused configs Added TS-1685 TS-1685 Remove TS_MICRO and fellas Added Ts-1255 TS-1255 Fix the types for all overridable configs. This was actually a real bug in the code, in that all float configurations were actually treated as integer, rendering them useless ... configure --enable-micro doesn't build -- Key: TS-1685 URL: https://issues.apache.org/jira/browse/TS-1685 Project: Traffic Server Issue Type: Bug Components: Build Reporter: James Peach Assignee: Leif Hedstrom Fix For: 3.3.5 The --enable-micro build configuration doesn't build. We should remove this and any dependent compilation options. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-2093) Plugin API doesn't check stat bounds on creation which can cause assert to trigger
[ https://issues.apache.org/jira/browse/TS-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728661#comment-13728661 ] ASF subversion and git services commented on TS-2093: - Commit 76ef33d435236aa680e2180191e5584af5adb0d1 in branch refs/heads/3.3.x from [~psudaemon] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=76ef33d ] TS-2093: Check bounds on plugin stat creation. Plugin API doesn't check stat bounds on creation which can cause assert to trigger -- Key: TS-2093 URL: https://issues.apache.org/jira/browse/TS-2093 Project: Traffic Server Issue Type: Bug Reporter: Phil Sorber Assignee: Phil Sorber Labels: C Fix For: 3.3.5 The records created for stats for the API are limited by TS_MAX_API_STATS. Trying to create more than that causes an assert to trigger. This problem should be superseded by TS-454 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-2092) Use of uninitialized member in HdrHeap
[ https://issues.apache.org/jira/browse/TS-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728647#comment-13728647 ] ASF subversion and git services commented on TS-2092: - Commit 1bb12edf9cd9b0076eaf39b8665909846743ee73 in branch refs/heads/3.3.x from [~zwoop] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=1bb12ed ] Merge branch 'master' into 3.3.x * master: (295 commits) TS-2081 Make the WCCP addr configuration LOCAL TS-2093: Check bounds on plugin stat creation. TS-2092 Use of uninitialized member in HdrHeap. [TS-2052] ET_SSL thread spinning TS-2090 Make proxy.config.allocator.enable_reclaim default based on build instructions TS-1006: adjust some reclaimable-freelist's default configuration Updated newish tests to the gitignore Fix autoconf checks for mcheck_pedantic() Fix configure check for eventfd TS-1330: Fix logging core at checkout_write() add some standard extensions to ignore list TS-1953: remove version check from stable plugins TS-1953: Remove check_ts_version() from experimental plugins TS-1953: remove check_ts_version() from examples Added TS-2086. TS-2086 Remove a few more unused configs Added TS-1685 TS-1685 Remove TS_MICRO and fellas Added Ts-1255 TS-1255 Fix the types for all overridable configs. This was actually a real bug in the code, in that all float configurations were actually treated as integer, rendering them useless ... Use of uninitialized member in HdrHeap -- Key: TS-2092 URL: https://issues.apache.org/jira/browse/TS-2092 Project: Traffic Server Issue Type: Bug Components: Core Reporter: Leif Hedstrom Assignee: Leif Hedstrom Fix For: 3.3.5 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1953) remove check_ts_version() from (example) plugins or make it an API
[
https://issues.apache.org/jira/browse/TS-1953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728654#comment-13728654
]
ASF subversion and git services commented on TS-1953:
-
Commit 1bb12edf9cd9b0076eaf39b8665909846743ee73 in branch refs/heads/3.3.x from
[~zwoop]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=1bb12ed ]
Merge branch 'master' into 3.3.x
* master: (295 commits)
TS-2081 Make the WCCP addr configuration LOCAL
TS-2093: Check bounds on plugin stat creation.
TS-2092 Use of uninitialized member in HdrHeap.
[TS-2052] ET_SSL thread spinning
TS-2090 Make proxy.config.allocator.enable_reclaim default based on build
instructions
TS-1006: adjust some reclaimable-freelist's default configuration
Updated newish tests to the gitignore
Fix autoconf checks for mcheck_pedantic()
Fix configure check for eventfd
TS-1330: Fix logging core at checkout_write()
add some standard extensions to ignore list
TS-1953: remove version check from stable plugins
TS-1953: Remove check_ts_version() from experimental plugins
TS-1953: remove check_ts_version() from examples
Added TS-2086.
TS-2086 Remove a few more unused configs
Added TS-1685
TS-1685 Remove TS_MICRO and fellas
Added Ts-1255
TS-1255 Fix the types for all overridable configs. This was actually a real
bug in the code, in that all float configurations were actually treated as
integer, rendering them useless
...
remove check_ts_version() from (example) plugins or make it an API
--
Key: TS-1953
URL: https://issues.apache.org/jira/browse/TS-1953
Project: Traffic Server
Issue Type: Improvement
Components: Plugins
Reporter: Igor Galić
Fix For: sometime
almost every single of our (example) plugins has a function
{{chec_ts_version()}}. If this boiler-code is so crucial to a plugin's
functionality, we should offer an API for it, instead of making developers
write (copy) that code every time.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-2093) Plugin API doesn't check stat bounds on creation which can cause assert to trigger
[ https://issues.apache.org/jira/browse/TS-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728646#comment-13728646 ] ASF subversion and git services commented on TS-2093: - Commit 1bb12edf9cd9b0076eaf39b8665909846743ee73 in branch refs/heads/3.3.x from [~zwoop] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=1bb12ed ] Merge branch 'master' into 3.3.x * master: (295 commits) TS-2081 Make the WCCP addr configuration LOCAL TS-2093: Check bounds on plugin stat creation. TS-2092 Use of uninitialized member in HdrHeap. [TS-2052] ET_SSL thread spinning TS-2090 Make proxy.config.allocator.enable_reclaim default based on build instructions TS-1006: adjust some reclaimable-freelist's default configuration Updated newish tests to the gitignore Fix autoconf checks for mcheck_pedantic() Fix configure check for eventfd TS-1330: Fix logging core at checkout_write() add some standard extensions to ignore list TS-1953: remove version check from stable plugins TS-1953: Remove check_ts_version() from experimental plugins TS-1953: remove check_ts_version() from examples Added TS-2086. TS-2086 Remove a few more unused configs Added TS-1685 TS-1685 Remove TS_MICRO and fellas Added Ts-1255 TS-1255 Fix the types for all overridable configs. This was actually a real bug in the code, in that all float configurations were actually treated as integer, rendering them useless ... Plugin API doesn't check stat bounds on creation which can cause assert to trigger -- Key: TS-2093 URL: https://issues.apache.org/jira/browse/TS-2093 Project: Traffic Server Issue Type: Bug Reporter: Phil Sorber Assignee: Phil Sorber Labels: C Fix For: 3.3.5 The records created for stats for the API are limited by TS_MAX_API_STATS. Trying to create more than that causes an assert to trigger. This problem should be superseded by TS-454 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-2086) Remove a few completely unused RecordsConfig.cc settings
[
https://issues.apache.org/jira/browse/TS-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728656#comment-13728656
]
ASF subversion and git services commented on TS-2086:
-
Commit 1bb12edf9cd9b0076eaf39b8665909846743ee73 in branch refs/heads/3.3.x from
[~zwoop]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=1bb12ed ]
Merge branch 'master' into 3.3.x
* master: (295 commits)
TS-2081 Make the WCCP addr configuration LOCAL
TS-2093: Check bounds on plugin stat creation.
TS-2092 Use of uninitialized member in HdrHeap.
[TS-2052] ET_SSL thread spinning
TS-2090 Make proxy.config.allocator.enable_reclaim default based on build
instructions
TS-1006: adjust some reclaimable-freelist's default configuration
Updated newish tests to the gitignore
Fix autoconf checks for mcheck_pedantic()
Fix configure check for eventfd
TS-1330: Fix logging core at checkout_write()
add some standard extensions to ignore list
TS-1953: remove version check from stable plugins
TS-1953: Remove check_ts_version() from experimental plugins
TS-1953: remove check_ts_version() from examples
Added TS-2086.
TS-2086 Remove a few more unused configs
Added TS-1685
TS-1685 Remove TS_MICRO and fellas
Added Ts-1255
TS-1255 Fix the types for all overridable configs. This was actually a real
bug in the code, in that all float configurations were actually treated as
integer, rendering them useless
...
Remove a few completely unused RecordsConfig.cc settings
Key: TS-2086
URL: https://issues.apache.org/jira/browse/TS-2086
Project: Traffic Server
Issue Type: Improvement
Components: Configuration
Reporter: Leif Hedstrom
Assignee: Leif Hedstrom
Fix For: 3.3.5
Found a few more:
{code}
proxy.config.temp_dir
proxy.config.cli_binary
proxy.config.cop_name
proxy.config.manager_name
proxy.config.process_state_dump_mode
proxy.config.server_name
proxy.config.start_script
proxy.config.watch_script
proxy.config.history_info_enabled
{code}
They are truly no-ops (have no purpose). There were a few more (such as
Product name and Vendor), which I left cause they might have some use as
part of a monitoring system.
Please speak up now if you feel any of these do deserve to linger, even
unused. The reason to remove them is to avoid confusing, such as thinking
changing them would have some sort of effect (which neither does).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1685) configure --enable-micro doesn't build
[ https://issues.apache.org/jira/browse/TS-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728657#comment-13728657 ] ASF subversion and git services commented on TS-1685: - Commit 1bb12edf9cd9b0076eaf39b8665909846743ee73 in branch refs/heads/3.3.x from [~zwoop] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=1bb12ed ] Merge branch 'master' into 3.3.x * master: (295 commits) TS-2081 Make the WCCP addr configuration LOCAL TS-2093: Check bounds on plugin stat creation. TS-2092 Use of uninitialized member in HdrHeap. [TS-2052] ET_SSL thread spinning TS-2090 Make proxy.config.allocator.enable_reclaim default based on build instructions TS-1006: adjust some reclaimable-freelist's default configuration Updated newish tests to the gitignore Fix autoconf checks for mcheck_pedantic() Fix configure check for eventfd TS-1330: Fix logging core at checkout_write() add some standard extensions to ignore list TS-1953: remove version check from stable plugins TS-1953: Remove check_ts_version() from experimental plugins TS-1953: remove check_ts_version() from examples Added TS-2086. TS-2086 Remove a few more unused configs Added TS-1685 TS-1685 Remove TS_MICRO and fellas Added Ts-1255 TS-1255 Fix the types for all overridable configs. This was actually a real bug in the code, in that all float configurations were actually treated as integer, rendering them useless ... configure --enable-micro doesn't build -- Key: TS-1685 URL: https://issues.apache.org/jira/browse/TS-1685 Project: Traffic Server Issue Type: Bug Components: Build Reporter: James Peach Assignee: Leif Hedstrom Fix For: 3.3.5 The --enable-micro build configuration doesn't build. We should remove this and any dependent compilation options. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1255) Add more overridable records.config configurations
[
https://issues.apache.org/jira/browse/TS-1255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728659#comment-13728659
]
ASF subversion and git services commented on TS-1255:
-
Commit 1bb12edf9cd9b0076eaf39b8665909846743ee73 in branch refs/heads/3.3.x from
[~zwoop]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=1bb12ed ]
Merge branch 'master' into 3.3.x
* master: (295 commits)
TS-2081 Make the WCCP addr configuration LOCAL
TS-2093: Check bounds on plugin stat creation.
TS-2092 Use of uninitialized member in HdrHeap.
[TS-2052] ET_SSL thread spinning
TS-2090 Make proxy.config.allocator.enable_reclaim default based on build
instructions
TS-1006: adjust some reclaimable-freelist's default configuration
Updated newish tests to the gitignore
Fix autoconf checks for mcheck_pedantic()
Fix configure check for eventfd
TS-1330: Fix logging core at checkout_write()
add some standard extensions to ignore list
TS-1953: remove version check from stable plugins
TS-1953: Remove check_ts_version() from experimental plugins
TS-1953: remove check_ts_version() from examples
Added TS-2086.
TS-2086 Remove a few more unused configs
Added TS-1685
TS-1685 Remove TS_MICRO and fellas
Added Ts-1255
TS-1255 Fix the types for all overridable configs. This was actually a real
bug in the code, in that all float configurations were actually treated as
integer, rendering them useless
...
Add more overridable records.config configurations
--
Key: TS-1255
URL: https://issues.apache.org/jira/browse/TS-1255
Project: Traffic Server
Issue Type: Improvement
Components: TS API
Reporter: Leif Hedstrom
Assignee: Leif Hedstrom
Labels: A
Fix For: 3.3.5
We should examine at least the following configs, and see which ones can (or
can not) be moved to be overridable:
{code}
MgmtInt server_max_connections;
MgmtInt origin_min_keep_alive_connections; // TODO: This one really ought
to be overridable, but difficult right now.
char *proxy_request_via_string;
int proxy_request_via_string_len;
char *proxy_response_via_string;
int proxy_response_via_string_len;
MgmtInt origin_server_pipeline;
MgmtInt user_agent_pipeline;
MgmtInt transaction_active_timeout_in;
MgmtInt accept_no_activity_timeout;
MgmtInt background_fill_active_timeout;
MgmtFloat background_fill_threshold;
MgmtInt parent_connect_attempts;
MgmtInt per_parent_connect_attempts;
MgmtInt parent_connect_timeout;
MgmtByte insert_age_in_response;
MgmtByte avoid_content_spoofing;
MgmtByte enable_http_stats;
MgmtInt max_cache_open_write_retries;
MgmtByte cache_enable_default_vary_headers;
MgmtByte cache_when_to_add_no_cache_to_msie_requests;
MgmtByte cache_range_lookup;
MgmtInt request_hdr_max_size;
MgmtInt response_hdr_max_size;
MgmtByte push_method_enabled;
MgmtByte referer_filter_enabled;
MgmtByte referer_format_redirect;
MgmtByte accept_encoding_filter_enabled;
// WTF!!! Bool ???
/// Accept connections on foreign addresses.
bool client_transparency_enabled;
/// Use client address to connect to origin server.
bool server_transparency_enabled;
MgmtByte negative_revalidating_enabled;
MgmtInt negative_revalidating_lifetime;
MgmtByte ignore_accept_mismatch;
MgmtByte ignore_accept_language_mismatch;
MgmtByte ignore_accept_encoding_mismatch;
MgmtByte ignore_accept_charset_mismatch;
// Optimize gzip alternates //
MgmtByte normalize_ae_gzip;
{code}
Marking this for v3.3.0, it'd be nice to get into 3.2, but I rather have us
just get 3.1.4/3.2 done sooner rather than later.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-2052) ET_SSL thread spinning
[ https://issues.apache.org/jira/browse/TS-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728663#comment-13728663 ] ASF subversion and git services commented on TS-2052: - Commit 94e9830c21f046aafe0247fb9c95198fc0902144 in branch refs/heads/3.3.x from [~briang] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=94e9830 ] [TS-2052] ET_SSL thread spinning ET_SSL thread spinning -- Key: TS-2052 URL: https://issues.apache.org/jira/browse/TS-2052 Project: Traffic Server Issue Type: Bug Components: SSL Reporter: Thomas Jackson Assignee: Brian Geffon Priority: Blocker Fix For: 3.3.5 I'm running ATS 3.2.4 and as I was benchmarking ATS for SSL usage I noticed that the CPU usage would go up dramatically even after I had stopped the test. After running a benchmark I am able to get an ET_SSL thread stuck spinning (100% cpu in top). I am also able to reproduce this off master from git. To reproduce: - setup trafficserver with ssl port - siege -b -c 1000 -n 100 https://hostname/path let it sit for 1-5minutes and one of the ET_SSL threads will be stuck spinning. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-2092) Use of uninitialized member in HdrHeap
[ https://issues.apache.org/jira/browse/TS-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728662#comment-13728662 ] ASF subversion and git services commented on TS-2092: - Commit 4651ca76daeebceb43d2a2c9b899d2faa75ba8aa in branch refs/heads/3.3.x from [~zwoop] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=4651ca7 ] TS-2092 Use of uninitialized member in HdrHeap. Use of uninitialized member in HdrHeap -- Key: TS-2092 URL: https://issues.apache.org/jira/browse/TS-2092 Project: Traffic Server Issue Type: Bug Components: Core Reporter: Leif Hedstrom Assignee: Leif Hedstrom Fix For: 3.3.5 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-2081) WCCP Client Address should not be replicated between cluster members.
[ https://issues.apache.org/jira/browse/TS-2081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728645#comment-13728645 ] ASF subversion and git services commented on TS-2081: - Commit 1bb12edf9cd9b0076eaf39b8665909846743ee73 in branch refs/heads/3.3.x from [~zwoop] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=1bb12ed ] Merge branch 'master' into 3.3.x * master: (295 commits) TS-2081 Make the WCCP addr configuration LOCAL TS-2093: Check bounds on plugin stat creation. TS-2092 Use of uninitialized member in HdrHeap. [TS-2052] ET_SSL thread spinning TS-2090 Make proxy.config.allocator.enable_reclaim default based on build instructions TS-1006: adjust some reclaimable-freelist's default configuration Updated newish tests to the gitignore Fix autoconf checks for mcheck_pedantic() Fix configure check for eventfd TS-1330: Fix logging core at checkout_write() add some standard extensions to ignore list TS-1953: remove version check from stable plugins TS-1953: Remove check_ts_version() from experimental plugins TS-1953: remove check_ts_version() from examples Added TS-2086. TS-2086 Remove a few more unused configs Added TS-1685 TS-1685 Remove TS_MICRO and fellas Added Ts-1255 TS-1255 Fix the types for all overridable configs. This was actually a real bug in the code, in that all float configurations were actually treated as integer, rendering them useless ... WCCP Client Address should not be replicated between cluster members. - Key: TS-2081 URL: https://issues.apache.org/jira/browse/TS-2081 Project: Traffic Server Issue Type: Bug Components: Clustering Reporter: Mario Poier Assignee: Alan M. Carroll Fix For: 3.3.5 The proxy.config.wccp.addr is replicated between cluster members. This replication occurs even when the LOCAL keyword has been defined in the records.config file. Version 3.2.0 (build # 11186) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1330) Logging related segfault in 3.2.0
[
https://issues.apache.org/jira/browse/TS-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728651#comment-13728651
]
ASF subversion and git services commented on TS-1330:
-
Commit 1bb12edf9cd9b0076eaf39b8665909846743ee73 in branch refs/heads/3.3.x from
[~zwoop]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=1bb12ed ]
Merge branch 'master' into 3.3.x
* master: (295 commits)
TS-2081 Make the WCCP addr configuration LOCAL
TS-2093: Check bounds on plugin stat creation.
TS-2092 Use of uninitialized member in HdrHeap.
[TS-2052] ET_SSL thread spinning
TS-2090 Make proxy.config.allocator.enable_reclaim default based on build
instructions
TS-1006: adjust some reclaimable-freelist's default configuration
Updated newish tests to the gitignore
Fix autoconf checks for mcheck_pedantic()
Fix configure check for eventfd
TS-1330: Fix logging core at checkout_write()
add some standard extensions to ignore list
TS-1953: remove version check from stable plugins
TS-1953: Remove check_ts_version() from experimental plugins
TS-1953: remove check_ts_version() from examples
Added TS-2086.
TS-2086 Remove a few more unused configs
Added TS-1685
TS-1685 Remove TS_MICRO and fellas
Added Ts-1255
TS-1255 Fix the types for all overridable configs. This was actually a real
bug in the code, in that all float configurations were actually treated as
integer, rendering them useless
...
Logging related segfault in 3.2.0
-
Key: TS-1330
URL: https://issues.apache.org/jira/browse/TS-1330
Project: Traffic Server
Issue Type: Bug
Components: Logging
Affects Versions: 3.2.0
Environment: ATS 3.2.0 on RHEL 6.2 64-bit
Reporter: David Carlin
Assignee: Yunkai Zhang
Priority: Critical
Labels: A, crash
Fix For: 3.3.5
Attachments: 0001-A-testing-patch-to-verify-my-analysis.patch,
0001-TS-1330-Fix-logging-core-at-checkout_write.patch,
0001-TS-1330-Fix-logging-core-at-checkout_write.patch.V2
I observed the following crash once on one of our ATS boxes - possibly
related to TS-1240
Jul 2 13:56:56 l2 traffic_server[25853]: {0x2b0a391e1700} ERROR:
[SSL_NetVConnection::ssl_read_from_net] SSL_ERROR_SYSCALL, underlying IO
error: Connection reset by peer
Jul 2 13:59:56 l2 kernel: [ET_NET 1][25855]: segfault at c ip
0058e083 sp 2b0a2982b740 error 6
Jul 2 13:59:56 l2 kernel: [ET_NET 3][25857]: segfault at 84 ip
0058e083 sp 2b0a29a31740 error 6 in traffic_server[40+34]
Jul 2 13:59:56 l2 kernel: in traffic_server[40+34]
Jul 2 14:02:59 l2 traffic_cop[25901]: (test) read timeout [18 ]
Jul 2 14:02:59 l2 traffic_cop[25901]: server heartbeat failed [1]
Jul 2 14:03:08 l2 traffic_manager[25826]: {0x7f3f088607e0} FATAL:
[LocalManager::pollMgmtProcessServer] Error in read (errno: 104)
Jul 2 14:03:09 l2 traffic_manager[25826]: {0x7f3f088607e0} FATAL: (last
system error 104: Connection reset by peer)
Jul 2 14:03:09 l2 traffic_cop[25901]: cannot find traffic_server [1]
Jul 2 14:03:09 l2 traffic_manager[25826]: {0x7f3f088607e0} ERROR:
[LocalManager::sendMgmtMsgToProcesses] Error writing message
Jul 2 14:03:09 l2 traffic_manager[25826]: {0x7f3f088607e0} ERROR: (last
system error 32: Broken pipe)
Jul 2 14:03:12 l2 traffic_cop[25901]: cop received child status signal
[25826 35584]
Jul 2 14:03:12 l2 traffic_cop[25901]: traffic_manager not running, making
sure traffic_server is dead
Jul 2 14:03:12 l2 traffic_cop[25901]: spawning traffic_manager
Jul 2 14:03:13 l2 traffic_manager[18267]: NOTE: --- Manager Starting ---
Jul 2 14:03:13 l2 traffic_manager[18267]: NOTE: Manager Version: Apache
Traffic Server - traffic_manager - 3.2.0 - (build # 52518 on Jun 25 2012 at
18:22:12)
Jul 2 14:03:13 l2 traffic_manager[18267]: {0x7fe63de3f7e0} STATUS: opened
/home/y/logs/trafficserver/manager.log
Jul 2 14:03:15 l2 traffic_server[18322]: NOTE: --- Server Starting ---
Jul 2 14:03:15 l2 traffic_server[18322]: NOTE: Server Version: Apache
Traffic Server - traffic_server - 3.2.0 - (build # 52518 on Jun 25 2012 at
18:22:31)
Jul 2 14:03:15 l2 traffic_server[18322]: {0x2b77573ab860} STATUS: opened
/home/y/logs/trafficserver/diags.log
Jul 2 14:03:15 l2 traffic_server[18322]: {0x2b77573ab860} ERROR: Cannot
insert duplicate!
Jul 2 14:03:22 l2 traffic_cop[25901]: server heartbeat succeeded
[Jul 2 13:56:56.304] Server {0x2b0a391e1700} ERROR:
[SSL_NetVConnection::ssl_read_from_net] SSL_ERROR_SYSCALL, underlying IO
error: Connection reset by peer
NOTE: Traffic Server received Sig 11: Segmentation fault
NOTE: Traffic Server received Sig 11: Segmentation fault
/home/y/bin/traffic_server - STACK TRACE:
[jira] [Commented] (TS-1953) remove check_ts_version() from (example) plugins or make it an API
[
https://issues.apache.org/jira/browse/TS-1953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728652#comment-13728652
]
ASF subversion and git services commented on TS-1953:
-
Commit 1bb12edf9cd9b0076eaf39b8665909846743ee73 in branch refs/heads/3.3.x from
[~zwoop]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=1bb12ed ]
Merge branch 'master' into 3.3.x
* master: (295 commits)
TS-2081 Make the WCCP addr configuration LOCAL
TS-2093: Check bounds on plugin stat creation.
TS-2092 Use of uninitialized member in HdrHeap.
[TS-2052] ET_SSL thread spinning
TS-2090 Make proxy.config.allocator.enable_reclaim default based on build
instructions
TS-1006: adjust some reclaimable-freelist's default configuration
Updated newish tests to the gitignore
Fix autoconf checks for mcheck_pedantic()
Fix configure check for eventfd
TS-1330: Fix logging core at checkout_write()
add some standard extensions to ignore list
TS-1953: remove version check from stable plugins
TS-1953: Remove check_ts_version() from experimental plugins
TS-1953: remove check_ts_version() from examples
Added TS-2086.
TS-2086 Remove a few more unused configs
Added TS-1685
TS-1685 Remove TS_MICRO and fellas
Added Ts-1255
TS-1255 Fix the types for all overridable configs. This was actually a real
bug in the code, in that all float configurations were actually treated as
integer, rendering them useless
...
remove check_ts_version() from (example) plugins or make it an API
--
Key: TS-1953
URL: https://issues.apache.org/jira/browse/TS-1953
Project: Traffic Server
Issue Type: Improvement
Components: Plugins
Reporter: Igor Galić
Fix For: sometime
almost every single of our (example) plugins has a function
{{chec_ts_version()}}. If this boiler-code is so crucial to a plugin's
functionality, we should offer an API for it, instead of making developers
write (copy) that code every time.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-2052) ET_SSL thread spinning
[ https://issues.apache.org/jira/browse/TS-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728648#comment-13728648 ] ASF subversion and git services commented on TS-2052: - Commit 1bb12edf9cd9b0076eaf39b8665909846743ee73 in branch refs/heads/3.3.x from [~zwoop] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=1bb12ed ] Merge branch 'master' into 3.3.x * master: (295 commits) TS-2081 Make the WCCP addr configuration LOCAL TS-2093: Check bounds on plugin stat creation. TS-2092 Use of uninitialized member in HdrHeap. [TS-2052] ET_SSL thread spinning TS-2090 Make proxy.config.allocator.enable_reclaim default based on build instructions TS-1006: adjust some reclaimable-freelist's default configuration Updated newish tests to the gitignore Fix autoconf checks for mcheck_pedantic() Fix configure check for eventfd TS-1330: Fix logging core at checkout_write() add some standard extensions to ignore list TS-1953: remove version check from stable plugins TS-1953: Remove check_ts_version() from experimental plugins TS-1953: remove check_ts_version() from examples Added TS-2086. TS-2086 Remove a few more unused configs Added TS-1685 TS-1685 Remove TS_MICRO and fellas Added Ts-1255 TS-1255 Fix the types for all overridable configs. This was actually a real bug in the code, in that all float configurations were actually treated as integer, rendering them useless ... ET_SSL thread spinning -- Key: TS-2052 URL: https://issues.apache.org/jira/browse/TS-2052 Project: Traffic Server Issue Type: Bug Components: SSL Reporter: Thomas Jackson Assignee: Brian Geffon Priority: Blocker Fix For: 3.3.5 I'm running ATS 3.2.4 and as I was benchmarking ATS for SSL usage I noticed that the CPU usage would go up dramatically even after I had stopped the test. After running a benchmark I am able to get an ET_SSL thread stuck spinning (100% cpu in top). I am also able to reproduce this off master from git. To reproduce: - setup trafficserver with ssl port - siege -b -c 1000 -n 100 https://hostname/path let it sit for 1-5minutes and one of the ET_SSL threads will be stuck spinning. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-2081) WCCP Client Address should not be replicated between cluster members.
[ https://issues.apache.org/jira/browse/TS-2081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728660#comment-13728660 ] ASF subversion and git services commented on TS-2081: - Commit 994d978a060012de934b80857d1dfab817f18a3a in branch refs/heads/3.3.x from [~zwoop] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=994d978 ] TS-2081 Make the WCCP addr configuration LOCAL WCCP Client Address should not be replicated between cluster members. - Key: TS-2081 URL: https://issues.apache.org/jira/browse/TS-2081 Project: Traffic Server Issue Type: Bug Components: Clustering Reporter: Mario Poier Assignee: Alan M. Carroll Fix For: 3.3.5 The proxy.config.wccp.addr is replicated between cluster members. This replication occurs even when the LOCAL keyword has been defined in the records.config file. Version 3.2.0 (build # 11186) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-2086) Remove a few completely unused RecordsConfig.cc settings
[
https://issues.apache.org/jira/browse/TS-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728655#comment-13728655
]
ASF subversion and git services commented on TS-2086:
-
Commit 1bb12edf9cd9b0076eaf39b8665909846743ee73 in branch refs/heads/3.3.x from
[~zwoop]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=1bb12ed ]
Merge branch 'master' into 3.3.x
* master: (295 commits)
TS-2081 Make the WCCP addr configuration LOCAL
TS-2093: Check bounds on plugin stat creation.
TS-2092 Use of uninitialized member in HdrHeap.
[TS-2052] ET_SSL thread spinning
TS-2090 Make proxy.config.allocator.enable_reclaim default based on build
instructions
TS-1006: adjust some reclaimable-freelist's default configuration
Updated newish tests to the gitignore
Fix autoconf checks for mcheck_pedantic()
Fix configure check for eventfd
TS-1330: Fix logging core at checkout_write()
add some standard extensions to ignore list
TS-1953: remove version check from stable plugins
TS-1953: Remove check_ts_version() from experimental plugins
TS-1953: remove check_ts_version() from examples
Added TS-2086.
TS-2086 Remove a few more unused configs
Added TS-1685
TS-1685 Remove TS_MICRO and fellas
Added Ts-1255
TS-1255 Fix the types for all overridable configs. This was actually a real
bug in the code, in that all float configurations were actually treated as
integer, rendering them useless
...
Remove a few completely unused RecordsConfig.cc settings
Key: TS-2086
URL: https://issues.apache.org/jira/browse/TS-2086
Project: Traffic Server
Issue Type: Improvement
Components: Configuration
Reporter: Leif Hedstrom
Assignee: Leif Hedstrom
Fix For: 3.3.5
Found a few more:
{code}
proxy.config.temp_dir
proxy.config.cli_binary
proxy.config.cop_name
proxy.config.manager_name
proxy.config.process_state_dump_mode
proxy.config.server_name
proxy.config.start_script
proxy.config.watch_script
proxy.config.history_info_enabled
{code}
They are truly no-ops (have no purpose). There were a few more (such as
Product name and Vendor), which I left cause they might have some use as
part of a monitoring system.
Please speak up now if you feel any of these do deserve to linger, even
unused. The reason to remove them is to avoid confusing, such as thinking
changing them would have some sort of effect (which neither does).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1006) memory management, cut down memory waste ?
[
https://issues.apache.org/jira/browse/TS-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728650#comment-13728650
]
ASF subversion and git services commented on TS-1006:
-
Commit 1bb12edf9cd9b0076eaf39b8665909846743ee73 in branch refs/heads/3.3.x from
[~zwoop]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=1bb12ed ]
Merge branch 'master' into 3.3.x
* master: (295 commits)
TS-2081 Make the WCCP addr configuration LOCAL
TS-2093: Check bounds on plugin stat creation.
TS-2092 Use of uninitialized member in HdrHeap.
[TS-2052] ET_SSL thread spinning
TS-2090 Make proxy.config.allocator.enable_reclaim default based on build
instructions
TS-1006: adjust some reclaimable-freelist's default configuration
Updated newish tests to the gitignore
Fix autoconf checks for mcheck_pedantic()
Fix configure check for eventfd
TS-1330: Fix logging core at checkout_write()
add some standard extensions to ignore list
TS-1953: remove version check from stable plugins
TS-1953: Remove check_ts_version() from experimental plugins
TS-1953: remove check_ts_version() from examples
Added TS-2086.
TS-2086 Remove a few more unused configs
Added TS-1685
TS-1685 Remove TS_MICRO and fellas
Added Ts-1255
TS-1255 Fix the types for all overridable configs. This was actually a real
bug in the code, in that all float configurations were actually treated as
integer, rendering them useless
...
memory management, cut down memory waste ?
--
Key: TS-1006
URL: https://issues.apache.org/jira/browse/TS-1006
Project: Traffic Server
Issue Type: Improvement
Components: Core
Affects Versions: 3.1.1
Reporter: Zhao Yongming
Assignee: Yunkai Zhang
Fix For: 3.3.4
Attachments:
0001-TS-1006-Add-an-enable-reclaimable-freelist-option.patch,
0002-TS-1006-Add-a-new-wrapper-ink_atomic_decrement.patch,
0003-TS-1006-Introduce-a-reclaimable-InkFreeList.patch,
0004-TS-1006-Make-InkFreeList-memory-pool-configurable.patch,
Memory-Usage-After-Introduced-New-Allocator.png, memusage.ods, memusage.ods
when we review the memory usage in the production, there is something
abnormal, ie, looks like TS take much memory than index data + common system
waste, and here is some memory dump result by set
proxy.config.dump_mem_info_frequency
1, the one on a not so busy forwarding system:
physics memory: 32G
RAM cache: 22G
DISK: 6140 GB
average_object_size 64000
{code}
allocated |in-use | type size | free list name
|||--
671088640 | 37748736 |2097152 |
memory/ioBufAllocator[14]
2248146944 | 2135949312 |1048576 |
memory/ioBufAllocator[13]
1711276032 | 1705508864 | 524288 |
memory/ioBufAllocator[12]
1669332992 | 1667760128 | 262144 |
memory/ioBufAllocator[11]
2214592512 | 221184 | 131072 |
memory/ioBufAllocator[10]
2325741568 | 2323775488 | 65536 |
memory/ioBufAllocator[9]
2091909120 | 2089123840 | 32768 |
memory/ioBufAllocator[8]
1956642816 | 1956478976 | 16384 |
memory/ioBufAllocator[7]
2094530560 | 2094071808 | 8192 |
memory/ioBufAllocator[6]
356515840 | 355540992 | 4096 |
memory/ioBufAllocator[5]
1048576 | 14336 | 2048 |
memory/ioBufAllocator[4]
131072 | 0 | 1024 |
memory/ioBufAllocator[3]
65536 | 0 |512 |
memory/ioBufAllocator[2]
32768 | 0 |256 |
memory/ioBufAllocator[1]
16384 | 0 |128 |
memory/ioBufAllocator[0]
0 | 0 |576 |
memory/ICPRequestCont_allocator
0 | 0 |112 |
memory/ICPPeerReadContAllocator
0 | 0 |432 |
memory/PeerReadDataAllocator
0 | 0 | 32 |
memory/MIMEFieldSDKHandle
0 | 0 |240 |
memory/INKVConnAllocator
0 | 0 | 96 |
memory/INKContAllocator
4096 | 0 | 32 |
memory/apiHookAllocator
0 | 0 |288 |
memory/FetchSMAllocator
0 | 0 | 80 |
memory/prefetchLockHandlerAllocator
0 | 0 |176 |
[jira] [Commented] (TS-2091) Persistent stats not working
[ https://issues.apache.org/jira/browse/TS-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728694#comment-13728694 ] Phil Sorber commented on TS-2091: - I think I have a patch for this. Need to test. Persistent stats not working Key: TS-2091 URL: https://issues.apache.org/jira/browse/TS-2091 Project: Traffic Server Issue Type: Bug Affects Versions: 3.3.4 Reporter: Phil Sorber Labels: C Fix For: 3.3.6 When creating TS_STAT_PERSISTENT stats in plugins in 3.3dev I don't see them as reloading properly. I can create them fine, and they get stored. Upon restarting TS I can see them in stats, but when doing TSStatFindName() I always get 0 back with a TS_SUCCESS. So it sees that they are there but does not have the correct ID for them to return. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-2091) Persistent stats not working
[ https://issues.apache.org/jira/browse/TS-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728718#comment-13728718 ] ASF subversion and git services commented on TS-2091: - Commit c6d0fe0e6109fda7f8c8b3791b1b0083fdd09e7b in branch refs/heads/master from [~psudaemon] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=c6d0fe0 ] TS-2091: Fix spacing in separate commit Persistent stats not working Key: TS-2091 URL: https://issues.apache.org/jira/browse/TS-2091 Project: Traffic Server Issue Type: Bug Affects Versions: 3.3.4 Reporter: Phil Sorber Labels: C Fix For: 3.3.6 When creating TS_STAT_PERSISTENT stats in plugins in 3.3dev I don't see them as reloading properly. I can create them fine, and they get stored. Upon restarting TS I can see them in stats, but when doing TSStatFindName() I always get 0 back with a TS_SUCCESS. So it sees that they are there but does not have the correct ID for them to return. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-2091) Persistent stats not working
[ https://issues.apache.org/jira/browse/TS-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728719#comment-13728719 ] ASF subversion and git services commented on TS-2091: - Commit ef06341fddb1823c4364e96a534831a68b9310a7 in branch refs/heads/master from [~psudaemon] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=ef06341 ] TS-2091: Return an error from RecGetRecordOrderAndId if the stat isn't registered Persistent stats not working Key: TS-2091 URL: https://issues.apache.org/jira/browse/TS-2091 Project: Traffic Server Issue Type: Bug Affects Versions: 3.3.4 Reporter: Phil Sorber Labels: C Fix For: 3.3.6 When creating TS_STAT_PERSISTENT stats in plugins in 3.3dev I don't see them as reloading properly. I can create them fine, and they get stored. Upon restarting TS I can see them in stats, but when doing TSStatFindName() I always get 0 back with a TS_SUCCESS. So it sees that they are there but does not have the correct ID for them to return. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TS-2091) Persistent stats not working
[ https://issues.apache.org/jira/browse/TS-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber resolved TS-2091. - Resolution: Fixed After being loaded from the snap file, the stats still need to be registered. The TSStatFindName would return the stat even if it wasn't, and in that case it had an invalid id of 0. Persistent stats not working Key: TS-2091 URL: https://issues.apache.org/jira/browse/TS-2091 Project: Traffic Server Issue Type: Bug Affects Versions: 3.3.4 Reporter: Phil Sorber Labels: C Fix For: 3.3.6 When creating TS_STAT_PERSISTENT stats in plugins in 3.3dev I don't see them as reloading properly. I can create them fine, and they get stored. Upon restarting TS I can see them in stats, but when doing TSStatFindName() I always get 0 back with a TS_SUCCESS. So it sees that they are there but does not have the correct ID for them to return. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TS-2091) Persistent stats not working
[ https://issues.apache.org/jira/browse/TS-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber closed TS-2091. --- Assignee: Phil Sorber Persistent stats not working Key: TS-2091 URL: https://issues.apache.org/jira/browse/TS-2091 Project: Traffic Server Issue Type: Bug Affects Versions: 3.3.4 Reporter: Phil Sorber Assignee: Phil Sorber Labels: C Fix For: 3.3.6 When creating TS_STAT_PERSISTENT stats in plugins in 3.3dev I don't see them as reloading properly. I can create them fine, and they get stored. Upon restarting TS I can see them in stats, but when doing TSStatFindName() I always get 0 back with a TS_SUCCESS. So it sees that they are there but does not have the correct ID for them to return. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
