[jira] [Commented] (TS-4104) wrong return value while create a new ticket on ssl_callback_session_ticket()
[
https://issues.apache.org/jira/browse/TS-4104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15095802#comment-15095802
]
ASF GitHub Bot commented on TS-4104:
Github user oknet commented on the pull request:
https://github.com/apache/trafficserver/pull/400#issuecomment-171212463
@bryancall the traffic.out log for current ATS release:
[Dec 28 21:01:12.742] Server {0x2b052fe4b700} DEBUG: (ssl) create ticket
for a new session.
[Dec 28 21:01:12.742] Server {0x2b052fe4b700} DEBUG: (ssl)
ssl_callback_info ssl: 0x2b0544006840 where: 8193 ret: 1
[Dec 28 21:01:12.742] Server {0x2b052fe4b700} DEBUG: (ssl)
ssl_callback_info ssl: 0x2b0544006840 where: 8193 ret: 1
[Dec 28 21:01:12.742] Server {0x2b052fe4b700} DEBUG: (ssl)
ssl_callback_info ssl: 0x2b0544006840 where: 8193 ret: 1
[Dec 28 21:01:12.742] Server {0x2b052fe4b700} DEBUG: (ssl)
ssl_callback_info ssl: 0x2b0544006840 where: 8193 ret: 1
[Dec 28 21:01:12.742] Server {0x2b052fe4b700} DEBUG: (ssl)
ssl_callback_info ssl: 0x2b0544006840 where: 32 ret: 1
[Dec 28 21:01:12.742] Server {0x2b052fe4b700} DEBUG: (ssl)
ssl_callback_info ssl: 0x2b0544006840 where: 8194 ret: 1
[Dec 28 21:01:12.742] Server {0x2b052fe4b700} DEBUG: (ssl) trace=FALSE
[Dec 28 21:01:12.742] Server {0x2b052fe4b700} DEBUG: (ssl) SSL server
handshake completed successfully
the traffic.out log if return 1 here:
[Dec 30 12:47:16.838] Server {0x2b6ec9340700} DEBUG: (ssl) create ticket
for a new session.
[Dec 30 12:47:16.838] Server {0x2b6ec9340700} DEBUG: (ssl) trace=FALSE
[Dec 30 12:47:16.838] Server {0x2b6ec9340700} DEBUG: (ssl) SSL server
handshake completed successfully
> wrong return value while create a new ticket on ssl_callback_session_ticket()
> -
>
> Key: TS-4104
> URL: https://issues.apache.org/jira/browse/TS-4104
> Project: Traffic Server
> Issue Type: Bug
> Components: SSL
>Reporter: Oknet Xu
> Fix For: 6.2.0
>
>
> from openssl online document:
> https://www.openssl.org/docs/manmaster/ssl/SSL_CTX_set_tlsext_ticket_key_cb.html
> The return value of the cb function is used by OpenSSL to determine what
> further processing will occur. The following return values have meaning:
> 2
> This indicates that the ctx and hctx have been set and the session can
> continue on those parameters. Additionally it indicates that the session
> ticket is in a renewal period and should be replaced. The OpenSSL library
> will call cb again with an enc argument of 1 to set the new ticket (see
> RFC5077 3.3 paragraph 2).
> 1
> This indicates that the ctx and hctx have been set and the session can
> continue on those parameters.
> 0
> This indicates that it was not possible to set/retrieve a session ticket and
> the SSL/TLS session will continue by by negotiating a set of cryptographic
> parameters or using the alternate SSL/TLS resumption mechanism, session ids.
> If called with enc equal to 0 the library will call the cb again to get a new
> set of parameters.
> less than 0
> This indicates an error.
> {code}
> 1948 if (enc == 1) {
> 1949 const ssl_ticket_key_t &most_recent_key = keyblock->keys[0];
> 1950 memcpy(keyname, most_recent_key.key_name,
> sizeof(most_recent_key.key_name));
> 1951 RAND_pseudo_bytes(iv, EVP_MAX_IV_LENGTH);
> 1952 EVP_EncryptInit_ex(cipher_ctx, EVP_aes_128_cbc(), NULL,
> most_recent_key.aes_key, iv);
> 1953 HMAC_Init_ex(hctx, most_recent_key.hmac_secret,
> sizeof(most_recent_key.hmac_secret), evp_md_func, NULL);
> 1954
> 1955 Debug("ssl", "create ticket for a new session.");
> 1956 SSL_INCREMENT_DYN_STAT(ssl_total_tickets_created_stat);
> 1957 return 0;
> 1958 } else if (enc == 0) {
> {code}
> the ssl_callback_session_ticket() should return 1 after create a new ticket
> but 0 here.
> and the traffic.out log for current ATS release:
> {code}
> [Dec 28 21:01:12.742] Server {0x2b052fe4b700} DEBUG: (ssl) create ticket for
> a new session.
> [Dec 28 21:01:12.742] Server {0x2b052fe4b700} DEBUG: (ssl) ssl_callback_info
> ssl: 0x2b0544006840 where: 8193 ret: 1
> [Dec 28 21:01:12.742] Server {0x2b052fe4b700} DEBUG: (ssl) ssl_callback_info
> ssl: 0x2b0544006840 where: 8193 ret: 1
> [Dec 28 21:01:12.742] Server {0x2b052fe4b700} DEBUG: (ssl) ssl_callback_info
> ssl: 0x2b0544006840 where: 8193 ret: 1
> [Dec 28 21:01:12.742] Server {0x2b052fe4b700} DEBUG: (ssl) ssl_callback_info
> ssl: 0x2b0544006840 where: 8193 ret: 1
> [Dec 28 21:01:12.742] Server {0x2b052fe4b700} DEBUG: (ssl) ssl_callback_info
> ssl: 0x2b0544006840 where: 32 ret: 1
> [Dec 28 21:01:12.742] Server {0x2b052fe4b700} DEBUG: (ssl) ssl_callback_info
> ssl: 0x2b0544006840 where: 8194 ret: 1
> [Dec 28 21:01:12.742] Server {0x2b052fe4b700} DEBUG: (ssl) tra
[jira] [Created] (TS-4128) traffic_server cored in handling req for cached object with do_global_select_alt() in global context
Shu-Chih created TS-4128:
Summary: traffic_server cored in handling req for cached object
with do_global_select_alt() in global context
Key: TS-4128
URL: https://issues.apache.org/jira/browse/TS-4128
Project: Traffic Server
Issue Type: Bug
Components: Lua
Reporter: Shu-Chih
traffic_server coredumped in handling request for cached object with
do_global_select_alt() in global context.
1. Test setup:
a. ATS: 6.0.0
b. Guest OS: RHEL6.6 (2.6.32-504.23.4.el6.x86_64)
c. Configuration:
[root@mtanjv8cdnc70 lua]# cat ../plugin.config
tslua.so etc/trafficserver/lua/global.lua
[root@mtanjv8cdnc70 lua]# cat global.lua
function do_global_select_alt()
ts.debug('select_alt')
return 0
end
2. Steps to trigger traffic_server to core:
- issue a "curl" command to GET an already cached object
3. Stack trace of traffic_server in debug-build mode:
[root@mtanjv8cdnc70 cores]# gdb /opt/trafficserver/bin/traffic_server
"core-mtanjv8cdnc70-[ET_NET 0]-6-24315-1452640509"
.
.
(gdb) bt
#0 0x2b53c45f2625 in raise () from /lib64/libc.so.6
#1 0x2b53c45f3d8d in abort () from /lib64/libc.so.6
#2 0x2b53c2d1b97d in ink_die_die_die () at ink_error.cc:43
#3 0x2b53c2d1ba34 in ink_fatal_va (fmt=0x2b53c2d2ca68 "%s:%d: failed
assert `%s`", ap=0x7fff12eb86c0) at ink_error.cc:65
#4 0x2b53c2d1baf9 in ink_fatal (message_format=0x2b53c2d2ca68 "%s:%d:
failed assert `%s`") at ink_error.cc:73
#5 0x2b53c2d1967a in _ink_assert (expression=0x7b33d8
"sdk_sanity_check_txn(txnp) == TS_SUCCESS", file=0x7b227d "InkAPI.cc",
line=4525) at ink_assert.cc:37
#6 0x00514a89 in _TSReleaseAssert (text=0x7b33d8
"sdk_sanity_check_txn(txnp) == TS_SUCCESS", file=0x7b227d "InkAPI.cc",
line=4525) at InkAPI.cc:407
#7 0x0051efbc in TSHttpTxnClientReqGet (txnp=0x7fff12eb89c0,
bufp=0x7fff12eb8870, obj=0x7fff12eb8868) at InkAPI.cc:4525
#8 0x2b53ce02740f in globalHookHandler (contp=0x17249c0,
event=TS_EVENT_HTTP_SELECT_ALT, edata=0x7fff12eb89c0) at ts_lua.c:225
#9 0x005159a0 in INKContInternal::handle_event (this=0x17249c0,
event=60010, edata=0x7fff12eb89c0) at InkAPI.cc:1005
#10 0x00500bf6 in Continuation::handleEvent (this=0x17249c0,
event=60010, data=0x7fff12eb89c0) at ../iocore/eventsystem/I_Continuation.h:146
#11 0x005162ec in APIHook::invoke (this=0x1725a20, event=60010,
edata=0x7fff12eb89c0) at InkAPI.cc:1223
#12 0x0063080c in HttpTransactCache::calculate_quality_of_match
(http_config_param=0x2aaae00fa178, client_request=0x1a60fb8,
obj_client_request=0x2aaadbf9d078,
obj_origin_server_response=0x2aaadbf9d0b8) at HttpTransactCache.cc:442
#13 0x0062fa13 in HttpTransactCache::SelectFromAlternates
(cache_vector=0x1a60ff8, client_request=0x1a60fb8,
http_config_params=0x2aaae00fa178) at HttpTransactCache.cc:213
#14 0x00746d00 in CacheVC::openReadStartHead (this=0x1a60ef0,
event=3900, e=0x0) at CacheRead.cc:1058
#15 0x00500bf6 in Continuation::handleEvent (this=0x1a60ef0,
event=3900, data=0x0) at ../iocore/eventsystem/I_Continuation.h:146
#16 0x00722aac in CacheVC::handleReadDone (this=0x1a60ef0, event=3900,
e=0x1a61078) at Cache.cc:2409
#17 0x00500bf6 in Continuation::handleEvent (this=0x1a60ef0,
event=3900, data=0x1a61078) at ../iocore/eventsystem/I_Continuation.h:146
#18 0x00728189 in AIOCallbackInternal::io_complete (this=0x1a61078,
event=1, data=0x2aaabc217e60) at ../../iocore/aio/P_AIO.h:117
#19 0x00500bf6 in Continuation::handleEvent (this=0x1a61078, event=1,
data=0x2aaabc217e60) at ../iocore/eventsystem/I_Continuation.h:146
#20 0x007a8b46 in EThread::process_event (this=0x2b53c5e82010,
e=0x2aaabc217e60, calling_code=1) at UnixEThread.cc:128
#21 0x007a8da5 in EThread::execute (this=0x2b53c5e82010) at
UnixEThread.cc:179
#22 0x00532dda in main (argv=0x7fff12eba3a8) at Main.cc:1812
(gdb)
We have consulted with Kit regarding this issue and was advised to create this
jira for him to resolve.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TS-4128) traffic_server cored in handling req for cached object with do_global_select_alt() in global context
[
https://issues.apache.org/jira/browse/TS-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kit Chan updated TS-4128:
-
Component/s: Plugins
> traffic_server cored in handling req for cached object with
> do_global_select_alt() in global context
>
>
> Key: TS-4128
> URL: https://issues.apache.org/jira/browse/TS-4128
> Project: Traffic Server
> Issue Type: Bug
> Components: Lua, Plugins
>Reporter: Shu-Chih
>
> traffic_server coredumped in handling request for cached object with
> do_global_select_alt() in global context.
> 1. Test setup:
> a. ATS: 6.0.0
> b. Guest OS: RHEL6.6 (2.6.32-504.23.4.el6.x86_64)
> c. Configuration:
> [root@mtanjv8cdnc70 lua]# cat ../plugin.config
> tslua.so etc/trafficserver/lua/global.lua
> [root@mtanjv8cdnc70 lua]# cat global.lua
> function do_global_select_alt()
> ts.debug('select_alt')
> return 0
> end
> 2. Steps to trigger traffic_server to core:
> - issue a "curl" command to GET an already cached object
> 3. Stack trace of traffic_server in debug-build mode:
> [root@mtanjv8cdnc70 cores]# gdb /opt/trafficserver/bin/traffic_server
> "core-mtanjv8cdnc70-[ET_NET 0]-6-24315-1452640509"
> .
> .
> (gdb) bt
> #0 0x2b53c45f2625 in raise () from /lib64/libc.so.6
> #1 0x2b53c45f3d8d in abort () from /lib64/libc.so.6
> #2 0x2b53c2d1b97d in ink_die_die_die () at ink_error.cc:43
> #3 0x2b53c2d1ba34 in ink_fatal_va (fmt=0x2b53c2d2ca68 "%s:%d: failed
> assert `%s`", ap=0x7fff12eb86c0) at ink_error.cc:65
> #4 0x2b53c2d1baf9 in ink_fatal (message_format=0x2b53c2d2ca68 "%s:%d:
> failed assert `%s`") at ink_error.cc:73
> #5 0x2b53c2d1967a in _ink_assert (expression=0x7b33d8
> "sdk_sanity_check_txn(txnp) == TS_SUCCESS", file=0x7b227d "InkAPI.cc",
> line=4525) at ink_assert.cc:37
> #6 0x00514a89 in _TSReleaseAssert (text=0x7b33d8
> "sdk_sanity_check_txn(txnp) == TS_SUCCESS", file=0x7b227d "InkAPI.cc",
> line=4525) at InkAPI.cc:407
> #7 0x0051efbc in TSHttpTxnClientReqGet (txnp=0x7fff12eb89c0,
> bufp=0x7fff12eb8870, obj=0x7fff12eb8868) at InkAPI.cc:4525
> #8 0x2b53ce02740f in globalHookHandler (contp=0x17249c0,
> event=TS_EVENT_HTTP_SELECT_ALT, edata=0x7fff12eb89c0) at ts_lua.c:225
> #9 0x005159a0 in INKContInternal::handle_event (this=0x17249c0,
> event=60010, edata=0x7fff12eb89c0) at InkAPI.cc:1005
> #10 0x00500bf6 in Continuation::handleEvent (this=0x17249c0,
> event=60010, data=0x7fff12eb89c0) at
> ../iocore/eventsystem/I_Continuation.h:146
> #11 0x005162ec in APIHook::invoke (this=0x1725a20, event=60010,
> edata=0x7fff12eb89c0) at InkAPI.cc:1223
> #12 0x0063080c in HttpTransactCache::calculate_quality_of_match
> (http_config_param=0x2aaae00fa178, client_request=0x1a60fb8,
> obj_client_request=0x2aaadbf9d078,
> obj_origin_server_response=0x2aaadbf9d0b8) at HttpTransactCache.cc:442
> #13 0x0062fa13 in HttpTransactCache::SelectFromAlternates
> (cache_vector=0x1a60ff8, client_request=0x1a60fb8,
> http_config_params=0x2aaae00fa178) at HttpTransactCache.cc:213
> #14 0x00746d00 in CacheVC::openReadStartHead (this=0x1a60ef0,
> event=3900, e=0x0) at CacheRead.cc:1058
> #15 0x00500bf6 in Continuation::handleEvent (this=0x1a60ef0,
> event=3900, data=0x0) at ../iocore/eventsystem/I_Continuation.h:146
> #16 0x00722aac in CacheVC::handleReadDone (this=0x1a60ef0,
> event=3900, e=0x1a61078) at Cache.cc:2409
> #17 0x00500bf6 in Continuation::handleEvent (this=0x1a60ef0,
> event=3900, data=0x1a61078) at ../iocore/eventsystem/I_Continuation.h:146
> #18 0x00728189 in AIOCallbackInternal::io_complete (this=0x1a61078,
> event=1, data=0x2aaabc217e60) at ../../iocore/aio/P_AIO.h:117
> #19 0x00500bf6 in Continuation::handleEvent (this=0x1a61078, event=1,
> data=0x2aaabc217e60) at ../iocore/eventsystem/I_Continuation.h:146
> #20 0x007a8b46 in EThread::process_event (this=0x2b53c5e82010,
> e=0x2aaabc217e60, calling_code=1) at UnixEThread.cc:128
> #21 0x007a8da5 in EThread::execute (this=0x2b53c5e82010) at
> UnixEThread.cc:179
> #22 0x00532dda in main (argv=0x7fff12eba3a8) at Main.cc:1812
> (gdb)
> We have consulted with Kit regarding this issue and was advised to create
> this jira for him to resolve.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TS-4128) traffic_server cored in handling req for cached object with do_global_select_alt() in global context
[
https://issues.apache.org/jira/browse/TS-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kit Chan updated TS-4128:
-
Fix Version/s: 6.2.0
> traffic_server cored in handling req for cached object with
> do_global_select_alt() in global context
>
>
> Key: TS-4128
> URL: https://issues.apache.org/jira/browse/TS-4128
> Project: Traffic Server
> Issue Type: Bug
> Components: Lua, Plugins
>Reporter: Shu-Chih
> Fix For: 6.2.0
>
>
> traffic_server coredumped in handling request for cached object with
> do_global_select_alt() in global context.
> 1. Test setup:
> a. ATS: 6.0.0
> b. Guest OS: RHEL6.6 (2.6.32-504.23.4.el6.x86_64)
> c. Configuration:
> [root@mtanjv8cdnc70 lua]# cat ../plugin.config
> tslua.so etc/trafficserver/lua/global.lua
> [root@mtanjv8cdnc70 lua]# cat global.lua
> function do_global_select_alt()
> ts.debug('select_alt')
> return 0
> end
> 2. Steps to trigger traffic_server to core:
> - issue a "curl" command to GET an already cached object
> 3. Stack trace of traffic_server in debug-build mode:
> [root@mtanjv8cdnc70 cores]# gdb /opt/trafficserver/bin/traffic_server
> "core-mtanjv8cdnc70-[ET_NET 0]-6-24315-1452640509"
> .
> .
> (gdb) bt
> #0 0x2b53c45f2625 in raise () from /lib64/libc.so.6
> #1 0x2b53c45f3d8d in abort () from /lib64/libc.so.6
> #2 0x2b53c2d1b97d in ink_die_die_die () at ink_error.cc:43
> #3 0x2b53c2d1ba34 in ink_fatal_va (fmt=0x2b53c2d2ca68 "%s:%d: failed
> assert `%s`", ap=0x7fff12eb86c0) at ink_error.cc:65
> #4 0x2b53c2d1baf9 in ink_fatal (message_format=0x2b53c2d2ca68 "%s:%d:
> failed assert `%s`") at ink_error.cc:73
> #5 0x2b53c2d1967a in _ink_assert (expression=0x7b33d8
> "sdk_sanity_check_txn(txnp) == TS_SUCCESS", file=0x7b227d "InkAPI.cc",
> line=4525) at ink_assert.cc:37
> #6 0x00514a89 in _TSReleaseAssert (text=0x7b33d8
> "sdk_sanity_check_txn(txnp) == TS_SUCCESS", file=0x7b227d "InkAPI.cc",
> line=4525) at InkAPI.cc:407
> #7 0x0051efbc in TSHttpTxnClientReqGet (txnp=0x7fff12eb89c0,
> bufp=0x7fff12eb8870, obj=0x7fff12eb8868) at InkAPI.cc:4525
> #8 0x2b53ce02740f in globalHookHandler (contp=0x17249c0,
> event=TS_EVENT_HTTP_SELECT_ALT, edata=0x7fff12eb89c0) at ts_lua.c:225
> #9 0x005159a0 in INKContInternal::handle_event (this=0x17249c0,
> event=60010, edata=0x7fff12eb89c0) at InkAPI.cc:1005
> #10 0x00500bf6 in Continuation::handleEvent (this=0x17249c0,
> event=60010, data=0x7fff12eb89c0) at
> ../iocore/eventsystem/I_Continuation.h:146
> #11 0x005162ec in APIHook::invoke (this=0x1725a20, event=60010,
> edata=0x7fff12eb89c0) at InkAPI.cc:1223
> #12 0x0063080c in HttpTransactCache::calculate_quality_of_match
> (http_config_param=0x2aaae00fa178, client_request=0x1a60fb8,
> obj_client_request=0x2aaadbf9d078,
> obj_origin_server_response=0x2aaadbf9d0b8) at HttpTransactCache.cc:442
> #13 0x0062fa13 in HttpTransactCache::SelectFromAlternates
> (cache_vector=0x1a60ff8, client_request=0x1a60fb8,
> http_config_params=0x2aaae00fa178) at HttpTransactCache.cc:213
> #14 0x00746d00 in CacheVC::openReadStartHead (this=0x1a60ef0,
> event=3900, e=0x0) at CacheRead.cc:1058
> #15 0x00500bf6 in Continuation::handleEvent (this=0x1a60ef0,
> event=3900, data=0x0) at ../iocore/eventsystem/I_Continuation.h:146
> #16 0x00722aac in CacheVC::handleReadDone (this=0x1a60ef0,
> event=3900, e=0x1a61078) at Cache.cc:2409
> #17 0x00500bf6 in Continuation::handleEvent (this=0x1a60ef0,
> event=3900, data=0x1a61078) at ../iocore/eventsystem/I_Continuation.h:146
> #18 0x00728189 in AIOCallbackInternal::io_complete (this=0x1a61078,
> event=1, data=0x2aaabc217e60) at ../../iocore/aio/P_AIO.h:117
> #19 0x00500bf6 in Continuation::handleEvent (this=0x1a61078, event=1,
> data=0x2aaabc217e60) at ../iocore/eventsystem/I_Continuation.h:146
> #20 0x007a8b46 in EThread::process_event (this=0x2b53c5e82010,
> e=0x2aaabc217e60, calling_code=1) at UnixEThread.cc:128
> #21 0x007a8da5 in EThread::execute (this=0x2b53c5e82010) at
> UnixEThread.cc:179
> #22 0x00532dda in main (argv=0x7fff12eba3a8) at Main.cc:1812
> (gdb)
> We have consulted with Kit regarding this issue and was advised to create
> this jira for him to resolve.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (TS-4128) traffic_server cored in handling req for cached object with do_global_select_alt() in global context
[
https://issues.apache.org/jira/browse/TS-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kit Chan reassigned TS-4128:
Assignee: Kit Chan
> traffic_server cored in handling req for cached object with
> do_global_select_alt() in global context
>
>
> Key: TS-4128
> URL: https://issues.apache.org/jira/browse/TS-4128
> Project: Traffic Server
> Issue Type: Bug
> Components: Lua, Plugins
>Reporter: Shu-Chih
>Assignee: Kit Chan
> Fix For: 6.2.0
>
>
> traffic_server coredumped in handling request for cached object with
> do_global_select_alt() in global context.
> 1. Test setup:
> a. ATS: 6.0.0
> b. Guest OS: RHEL6.6 (2.6.32-504.23.4.el6.x86_64)
> c. Configuration:
> [root@mtanjv8cdnc70 lua]# cat ../plugin.config
> tslua.so etc/trafficserver/lua/global.lua
> [root@mtanjv8cdnc70 lua]# cat global.lua
> function do_global_select_alt()
> ts.debug('select_alt')
> return 0
> end
> 2. Steps to trigger traffic_server to core:
> - issue a "curl" command to GET an already cached object
> 3. Stack trace of traffic_server in debug-build mode:
> [root@mtanjv8cdnc70 cores]# gdb /opt/trafficserver/bin/traffic_server
> "core-mtanjv8cdnc70-[ET_NET 0]-6-24315-1452640509"
> .
> .
> (gdb) bt
> #0 0x2b53c45f2625 in raise () from /lib64/libc.so.6
> #1 0x2b53c45f3d8d in abort () from /lib64/libc.so.6
> #2 0x2b53c2d1b97d in ink_die_die_die () at ink_error.cc:43
> #3 0x2b53c2d1ba34 in ink_fatal_va (fmt=0x2b53c2d2ca68 "%s:%d: failed
> assert `%s`", ap=0x7fff12eb86c0) at ink_error.cc:65
> #4 0x2b53c2d1baf9 in ink_fatal (message_format=0x2b53c2d2ca68 "%s:%d:
> failed assert `%s`") at ink_error.cc:73
> #5 0x2b53c2d1967a in _ink_assert (expression=0x7b33d8
> "sdk_sanity_check_txn(txnp) == TS_SUCCESS", file=0x7b227d "InkAPI.cc",
> line=4525) at ink_assert.cc:37
> #6 0x00514a89 in _TSReleaseAssert (text=0x7b33d8
> "sdk_sanity_check_txn(txnp) == TS_SUCCESS", file=0x7b227d "InkAPI.cc",
> line=4525) at InkAPI.cc:407
> #7 0x0051efbc in TSHttpTxnClientReqGet (txnp=0x7fff12eb89c0,
> bufp=0x7fff12eb8870, obj=0x7fff12eb8868) at InkAPI.cc:4525
> #8 0x2b53ce02740f in globalHookHandler (contp=0x17249c0,
> event=TS_EVENT_HTTP_SELECT_ALT, edata=0x7fff12eb89c0) at ts_lua.c:225
> #9 0x005159a0 in INKContInternal::handle_event (this=0x17249c0,
> event=60010, edata=0x7fff12eb89c0) at InkAPI.cc:1005
> #10 0x00500bf6 in Continuation::handleEvent (this=0x17249c0,
> event=60010, data=0x7fff12eb89c0) at
> ../iocore/eventsystem/I_Continuation.h:146
> #11 0x005162ec in APIHook::invoke (this=0x1725a20, event=60010,
> edata=0x7fff12eb89c0) at InkAPI.cc:1223
> #12 0x0063080c in HttpTransactCache::calculate_quality_of_match
> (http_config_param=0x2aaae00fa178, client_request=0x1a60fb8,
> obj_client_request=0x2aaadbf9d078,
> obj_origin_server_response=0x2aaadbf9d0b8) at HttpTransactCache.cc:442
> #13 0x0062fa13 in HttpTransactCache::SelectFromAlternates
> (cache_vector=0x1a60ff8, client_request=0x1a60fb8,
> http_config_params=0x2aaae00fa178) at HttpTransactCache.cc:213
> #14 0x00746d00 in CacheVC::openReadStartHead (this=0x1a60ef0,
> event=3900, e=0x0) at CacheRead.cc:1058
> #15 0x00500bf6 in Continuation::handleEvent (this=0x1a60ef0,
> event=3900, data=0x0) at ../iocore/eventsystem/I_Continuation.h:146
> #16 0x00722aac in CacheVC::handleReadDone (this=0x1a60ef0,
> event=3900, e=0x1a61078) at Cache.cc:2409
> #17 0x00500bf6 in Continuation::handleEvent (this=0x1a60ef0,
> event=3900, data=0x1a61078) at ../iocore/eventsystem/I_Continuation.h:146
> #18 0x00728189 in AIOCallbackInternal::io_complete (this=0x1a61078,
> event=1, data=0x2aaabc217e60) at ../../iocore/aio/P_AIO.h:117
> #19 0x00500bf6 in Continuation::handleEvent (this=0x1a61078, event=1,
> data=0x2aaabc217e60) at ../iocore/eventsystem/I_Continuation.h:146
> #20 0x007a8b46 in EThread::process_event (this=0x2b53c5e82010,
> e=0x2aaabc217e60, calling_code=1) at UnixEThread.cc:128
> #21 0x007a8da5 in EThread::execute (this=0x2b53c5e82010) at
> UnixEThread.cc:179
> #22 0x00532dda in main (argv=0x7fff12eba3a8) at Main.cc:1812
> (gdb)
> We have consulted with Kit regarding this issue and was advised to create
> this jira for him to resolve.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TS-4128) traffic_server cored in handling req for cached object with do_global_select_alt() in global context
[
https://issues.apache.org/jira/browse/TS-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15096474#comment-15096474
]
Kit Chan commented on TS-4128:
--
Will take a look.
> traffic_server cored in handling req for cached object with
> do_global_select_alt() in global context
>
>
> Key: TS-4128
> URL: https://issues.apache.org/jira/browse/TS-4128
> Project: Traffic Server
> Issue Type: Bug
> Components: Lua, Plugins
>Reporter: Shu-Chih
>Assignee: Kit Chan
> Fix For: 6.2.0
>
>
> traffic_server coredumped in handling request for cached object with
> do_global_select_alt() in global context.
> 1. Test setup:
> a. ATS: 6.0.0
> b. Guest OS: RHEL6.6 (2.6.32-504.23.4.el6.x86_64)
> c. Configuration:
> [root@mtanjv8cdnc70 lua]# cat ../plugin.config
> tslua.so etc/trafficserver/lua/global.lua
> [root@mtanjv8cdnc70 lua]# cat global.lua
> function do_global_select_alt()
> ts.debug('select_alt')
> return 0
> end
> 2. Steps to trigger traffic_server to core:
> - issue a "curl" command to GET an already cached object
> 3. Stack trace of traffic_server in debug-build mode:
> [root@mtanjv8cdnc70 cores]# gdb /opt/trafficserver/bin/traffic_server
> "core-mtanjv8cdnc70-[ET_NET 0]-6-24315-1452640509"
> .
> .
> (gdb) bt
> #0 0x2b53c45f2625 in raise () from /lib64/libc.so.6
> #1 0x2b53c45f3d8d in abort () from /lib64/libc.so.6
> #2 0x2b53c2d1b97d in ink_die_die_die () at ink_error.cc:43
> #3 0x2b53c2d1ba34 in ink_fatal_va (fmt=0x2b53c2d2ca68 "%s:%d: failed
> assert `%s`", ap=0x7fff12eb86c0) at ink_error.cc:65
> #4 0x2b53c2d1baf9 in ink_fatal (message_format=0x2b53c2d2ca68 "%s:%d:
> failed assert `%s`") at ink_error.cc:73
> #5 0x2b53c2d1967a in _ink_assert (expression=0x7b33d8
> "sdk_sanity_check_txn(txnp) == TS_SUCCESS", file=0x7b227d "InkAPI.cc",
> line=4525) at ink_assert.cc:37
> #6 0x00514a89 in _TSReleaseAssert (text=0x7b33d8
> "sdk_sanity_check_txn(txnp) == TS_SUCCESS", file=0x7b227d "InkAPI.cc",
> line=4525) at InkAPI.cc:407
> #7 0x0051efbc in TSHttpTxnClientReqGet (txnp=0x7fff12eb89c0,
> bufp=0x7fff12eb8870, obj=0x7fff12eb8868) at InkAPI.cc:4525
> #8 0x2b53ce02740f in globalHookHandler (contp=0x17249c0,
> event=TS_EVENT_HTTP_SELECT_ALT, edata=0x7fff12eb89c0) at ts_lua.c:225
> #9 0x005159a0 in INKContInternal::handle_event (this=0x17249c0,
> event=60010, edata=0x7fff12eb89c0) at InkAPI.cc:1005
> #10 0x00500bf6 in Continuation::handleEvent (this=0x17249c0,
> event=60010, data=0x7fff12eb89c0) at
> ../iocore/eventsystem/I_Continuation.h:146
> #11 0x005162ec in APIHook::invoke (this=0x1725a20, event=60010,
> edata=0x7fff12eb89c0) at InkAPI.cc:1223
> #12 0x0063080c in HttpTransactCache::calculate_quality_of_match
> (http_config_param=0x2aaae00fa178, client_request=0x1a60fb8,
> obj_client_request=0x2aaadbf9d078,
> obj_origin_server_response=0x2aaadbf9d0b8) at HttpTransactCache.cc:442
> #13 0x0062fa13 in HttpTransactCache::SelectFromAlternates
> (cache_vector=0x1a60ff8, client_request=0x1a60fb8,
> http_config_params=0x2aaae00fa178) at HttpTransactCache.cc:213
> #14 0x00746d00 in CacheVC::openReadStartHead (this=0x1a60ef0,
> event=3900, e=0x0) at CacheRead.cc:1058
> #15 0x00500bf6 in Continuation::handleEvent (this=0x1a60ef0,
> event=3900, data=0x0) at ../iocore/eventsystem/I_Continuation.h:146
> #16 0x00722aac in CacheVC::handleReadDone (this=0x1a60ef0,
> event=3900, e=0x1a61078) at Cache.cc:2409
> #17 0x00500bf6 in Continuation::handleEvent (this=0x1a60ef0,
> event=3900, data=0x1a61078) at ../iocore/eventsystem/I_Continuation.h:146
> #18 0x00728189 in AIOCallbackInternal::io_complete (this=0x1a61078,
> event=1, data=0x2aaabc217e60) at ../../iocore/aio/P_AIO.h:117
> #19 0x00500bf6 in Continuation::handleEvent (this=0x1a61078, event=1,
> data=0x2aaabc217e60) at ../iocore/eventsystem/I_Continuation.h:146
> #20 0x007a8b46 in EThread::process_event (this=0x2b53c5e82010,
> e=0x2aaabc217e60, calling_code=1) at UnixEThread.cc:128
> #21 0x007a8da5 in EThread::execute (this=0x2b53c5e82010) at
> UnixEThread.cc:179
> #22 0x00532dda in main (argv=0x7fff12eba3a8) at Main.cc:1812
> (gdb)
> We have consulted with Kit regarding this issue and was advised to create
> this jira for him to resolve.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TS-4099) replace XML statistics with Lua
[
https://issues.apache.org/jira/browse/TS-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15096492#comment-15096492
]
ASF subversion and git services commented on TS-4099:
-
Commit 63ca6d80dedc0e6f185e4c76f7f697fc499803d1 in trafficserver's branch
refs/heads/master from [~jpe...@apache.org]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=63ca6d8 ]
TS-4099: add const to WebOverview methods
> replace XML statistics with Lua
> ---
>
> Key: TS-4099
> URL: https://issues.apache.org/jira/browse/TS-4099
> Project: Traffic Server
> Issue Type: New Feature
> Components: Lua, Manager, Metrics
>Reporter: James Peach
>Assignee: James Peach
> Fix For: 6.2.0
>
>
> The custom metrics XML format is undocumented and difficult to use and
> extend. Since we plan to use Lua for configuration programmability, lets make
> a start by replacing this subsystem with Lua.
> It turns out that Lua is mostly more readable and easier to understand.
> Performance is roughly similar.
> Example syntax:
> {code}
> float 'proxy.node.user_agent_total_bytes_avg_10s' [[
> local self = ...
> return interval_delta_of_10s(self, function()
> return proxy.node.user_agent_total_bytes
> end)
> ]]
> counter 'proxy.node.origin_server_total_bytes' [[
> return proxy.node.http.origin_server_total_request_bytes +
> proxy.node.http.origin_server_total_response_bytes +
> proxy.node.http.parent_proxy_total_request_bytes +
> proxy.node.http.parent_proxy_total_response_bytes
> ]]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TS-4099) replace XML statistics with Lua
[
https://issues.apache.org/jira/browse/TS-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15096491#comment-15096491
]
ASF subversion and git services commented on TS-4099:
-
Commit f9c717f1ffe289fa3a8e60e0e18bfe3e8ed5b1b8 in trafficserver's branch
refs/heads/master from [~jpe...@apache.org]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=f9c717f ]
TS-4099: fix HTTP counter metric data types
> replace XML statistics with Lua
> ---
>
> Key: TS-4099
> URL: https://issues.apache.org/jira/browse/TS-4099
> Project: Traffic Server
> Issue Type: New Feature
> Components: Lua, Manager, Metrics
>Reporter: James Peach
>Assignee: James Peach
> Fix For: 6.2.0
>
>
> The custom metrics XML format is undocumented and difficult to use and
> extend. Since we plan to use Lua for configuration programmability, lets make
> a start by replacing this subsystem with Lua.
> It turns out that Lua is mostly more readable and easier to understand.
> Performance is roughly similar.
> Example syntax:
> {code}
> float 'proxy.node.user_agent_total_bytes_avg_10s' [[
> local self = ...
> return interval_delta_of_10s(self, function()
> return proxy.node.user_agent_total_bytes
> end)
> ]]
> counter 'proxy.node.origin_server_total_bytes' [[
> return proxy.node.http.origin_server_total_request_bytes +
> proxy.node.http.origin_server_total_response_bytes +
> proxy.node.http.parent_proxy_total_request_bytes +
> proxy.node.http.parent_proxy_total_response_bytes
> ]]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Failed: trafficserver (latest)
Build Failed for trafficserver (latest) Error: Failed to import project You can find out more about this failure here: https://readthedocs.org/projects/trafficserver/builds/3634451/ If you have questions, a good place to start is the FAQ: https://docs.readthedocs.org/en/latest/faq.html Keep documenting, Read the Docs -- http://readthedocs.org
Failed: trafficserver (latest)
Build Failed for trafficserver (latest) Error: Failed to import project You can find out more about this failure here: https://readthedocs.org/projects/trafficserver/builds/3634470/ If you have questions, a good place to start is the FAQ: https://docs.readthedocs.org/en/latest/faq.html Keep documenting, Read the Docs -- http://readthedocs.org
[jira] [Commented] (TS-4107) proxy.process.ssl.total_success_handshake_count_in has wrong record type
[
https://issues.apache.org/jira/browse/TS-4107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15096490#comment-15096490
]
ASF subversion and git services commented on TS-4107:
-
Commit 980c525edcdb5beacfb1e59e9c7854fa29191954 in trafficserver's branch
refs/heads/master from [~jpe...@apache.org]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=980c525 ]
TS-4107: backwards compatibility for StatsProcessor metrics
> proxy.process.ssl.total_success_handshake_count_in has wrong record type
>
>
> Key: TS-4107
> URL: https://issues.apache.org/jira/browse/TS-4107
> Project: Traffic Server
> Issue Type: Bug
> Components: Metrics, SSL
>Reporter: James Peach
>Assignee: James Peach
> Fix For: 6.2.0
>
>
> {{proxy.process.ssl.total_success_handshake_count_in}} is the only SSL metric
> registered in {{RecordsConfig.cc}} where it is incorrectly registered as a
> node metric, rather than a process metric.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TS-4037) various table of contents errors
[
https://issues.apache.org/jira/browse/TS-4037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15096618#comment-15096618
]
ASF GitHub Bot commented on TS-4037:
GitHub user jsime opened a pull request:
https://github.com/apache/trafficserver/pull/419
Docs: build cleanups and multiple Jira issues.
[TS-4037] Table of Contents fixes
[TS-4086] Minimum size for proxy.config.log.rolling_size_mb
[TS-4077] Doc build warnings and errors
[TS-3704] ^^
[TS-3703] ^^
[TS-3288] Confirmed documentation is accurate that any uid != 0 is accepted
by traffic_manager
As well as the addition of documentation entries for the following missing
configuration variables:
proxy.config.http.chunking.size
proxy.config.http.server_tcp_init_cwnd
proxy.config.http.auth_server_session_private
proxy.config.http.server_session_sharing.match
proxy.config.http.accept_encoding_filter_enabled
proxy.config.http.default_buffer_size
proxy.config.http.default_buffer_water_mark
proxy.config.http.request_header_max_size
proxy.config.http.response_header_max_size
proxy.config.http.global_user_agent_header
proxy.config.http.negative_revalidating_enabled
proxy.config.http.negative_revalidating_lifetime
proxy.config.http.doc_in_cache_skip_dns
proxy.config.cache.min_average_object_size
proxy.config.cache.alt_rewrite_max_size
proxy.config.http.cache.guaranteed_min_lifetime
proxy.config.http.cache.guaranteed_max_lifetime
proxy.config.ssl.server.cipher_suite
proxy.config.icp.multicast_enabled
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jsime/trafficserver docs-build-warnings
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/trafficserver/pull/419.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #419
commit 16269d5e2917c5d58a04d1f8682f5bd451ebac9f
Author: Jon Sime
Date: 2016-01-13T17:19:45Z
Docs: build cleanups and multiple Jira issues.
[TS-4037] Table of Contents fixes
[TS-4086] Minimum size for proxy.config.log.rolling_size_mb
[TS-4077] Doc build warnings and errors
[TS-3704] ^^
[TS-3703] ^^
[TS-3288] Confirmed documentation is accurate that any uid != 0 is accepted
by traffic_manager
> various table of contents errors
>
>
> Key: TS-4037
> URL: https://issues.apache.org/jira/browse/TS-4037
> Project: Traffic Server
> Issue Type: Bug
> Components: Documentation
>Reporter: James Peach
>Assignee: Jon Sime
> Fix For: Docs
>
>
> Building the HTML docs on Fedora 22:
> {code}
> ...
> /opt/home/src/trafficserver.git/doc/admin-guide/configuration/index.en.rst:25:
> WARNING: toctree contains reference to nonexisting document
> u'admin-guide/configuration/reverse-proxying.en'
> /opt/home/src/trafficserver.git/doc/admin-guide/index.en.rst:27: WARNING:
> toctree contains reference to nonexisting document
> u'admin-guide/troubleshooting.en'
> /opt/home/src/trafficserver.git/doc/admin-guide/monitoring/monitoring/third-party/index.en.rst:25:
> WARNING: toctree contains reference to nonexisting document
> u'admin-guide/monitoring/monitoring/third-party/circonus.en'
> /opt/home/src/trafficserver.git/doc/admin-guide/monitoring/monitoring/third-party/index.en.rst:25:
> WARNING: toctree contains reference to nonexisting document
> u'admin-guide/monitoring/monitoring/third-party/logstash.en'
> /opt/home/src/trafficserver.git/doc/admin-guide/monitoring/monitoring/third-party/index.en.rst:25:
> WARNING: toctree contains reference to nonexisting document
> u'admin-guide/monitoring/monitoring/third-party/nagios.en'
> /opt/home/src/trafficserver.git/doc/admin-guide/monitoring/monitoring/third-party/index.en.rst:25:
> WARNING: toctree contains reference to nonexisting document
> u'admin-guide/monitoring/monitoring/third-party/zabbix.en'
> ...
> /opt/home/src/trafficserver.git/doc/developer-guide/introduction/audience.en.rst:25:
> WARNING: toctree contains reference to nonexisting document
> u'developer-guide/introduction/preface/how-to-use-this-book.en'
> /opt/home/src/trafficserver.git/doc/developer-guide/introduction/audience.en.rst:25:
> WARNING: toctree contains reference to nonexisting document
> u'developer-guide/introduction/preface/typographical-conventions.en'
> /opt/home/src/trafficserver.git/doc/developer-guide/plugins/adding-statistics.en.rst:34:
> WARNING: toctree contains reference to nonexisting document
> u'developer-guide/plugins/adding-statistics/coupled-statistics.en'
> /opt/home/src/trafficserver.git/doc/developer-guide/plugins/adding-statistics.en.rst
[jira] [Updated] (TS-4127) Add documentation for the escalate plugin
[ https://issues.apache.org/jira/browse/TS-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-4127: -- Component/s: (was: Docs) Documentation > Add documentation for the escalate plugin > - > > Key: TS-4127 > URL: https://issues.apache.org/jira/browse/TS-4127 > Project: Traffic Server > Issue Type: Improvement > Components: Documentation >Reporter: Leif Hedstrom >Assignee: Leif Hedstrom > Fix For: Docs > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-4127) Add documentation for the escalate plugin
[ https://issues.apache.org/jira/browse/TS-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-4127: -- Assignee: Jon Sime (was: Leif Hedstrom) > Add documentation for the escalate plugin > - > > Key: TS-4127 > URL: https://issues.apache.org/jira/browse/TS-4127 > Project: Traffic Server > Issue Type: Improvement > Components: Documentation >Reporter: Leif Hedstrom >Assignee: Jon Sime > Fix For: Docs > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (TS-4121) Doc: Add proxy.config.http.request_via_str
[ https://issues.apache.org/jira/browse/TS-4121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom reopened TS-4121: --- > Doc: Add proxy.config.http.request_via_str > -- > > Key: TS-4121 > URL: https://issues.apache.org/jira/browse/TS-4121 > Project: Traffic Server > Issue Type: Improvement > Components: Docs, Documentation >Reporter: Hiroaki Nakamura >Assignee: Leif Hedstrom > Fix For: 6.2.0 > > > Add proxy.config.http.request_via_str to the document. > I created the pull request for this issue: > https://github.com/apache/trafficserver/pull/413 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (TS-4121) Doc: Add proxy.config.http.request_via_str
[ https://issues.apache.org/jira/browse/TS-4121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom reassigned TS-4121: - Assignee: Leif Hedstrom > Doc: Add proxy.config.http.request_via_str > -- > > Key: TS-4121 > URL: https://issues.apache.org/jira/browse/TS-4121 > Project: Traffic Server > Issue Type: Improvement > Components: Docs, Documentation >Reporter: Hiroaki Nakamura >Assignee: Leif Hedstrom > Fix For: 6.2.0 > > > Add proxy.config.http.request_via_str to the document. > I created the pull request for this issue: > https://github.com/apache/trafficserver/pull/413 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TS-4121) Doc: Add proxy.config.http.request_via_str
[ https://issues.apache.org/jira/browse/TS-4121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom resolved TS-4121. --- Resolution: Fixed Fix Version/s: (was: 6.2.0) Docs > Doc: Add proxy.config.http.request_via_str > -- > > Key: TS-4121 > URL: https://issues.apache.org/jira/browse/TS-4121 > Project: Traffic Server > Issue Type: Improvement > Components: Docs, Documentation >Reporter: Hiroaki Nakamura >Assignee: Leif Hedstrom > Fix For: Docs > > > Add proxy.config.http.request_via_str to the document. > I created the pull request for this issue: > https://github.com/apache/trafficserver/pull/413 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-3288) Document user restrictions of proxy.config.admin.user_id
[
https://issues.apache.org/jira/browse/TS-3288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15096756#comment-15096756
]
ASF subversion and git services commented on TS-3288:
-
Commit 40500c710b8b4aad0bf223c1ae4962cdf0725973 in trafficserver's branch
refs/heads/master from [~jsime]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=40500c7 ]
Docs: build cleanups and multiple Jira issues.
[TS-4037] Table of Contents fixes
[TS-4086] Minimum size for proxy.config.log.rolling_size_mb
[TS-4077] Doc build warnings and errors
[TS-3704] ^^
[TS-3703] ^^
[TS-3288] Confirmed documentation is accurate that any uid != 0 is accepted by
traffic_manager
This closes #419
> Document user restrictions of proxy.config.admin.user_id
>
>
> Key: TS-3288
> URL: https://issues.apache.org/jira/browse/TS-3288
> Project: Traffic Server
> Issue Type: Improvement
> Components: Documentation
>Reporter: Karl Richter
>Assignee: Jon Sime
> Fix For: Docs
>
>
> The documentation of `proxy.config.admin.user_id`, e.g. at
>
> http://trafficserver.readthedocs.org/en/latest/reference/configuration/records.config.en.html#proxy-config-admin-user-id
> doesn't contain any statement on restrictions for valid effective users,
> except that root is forbidden if not bypassed. They must exist because
> specifying a user the same entry in `/etc/passwd` like `nobody` except a uid
> and gid differing by 1 causes requests to be rejected after
> `bin/trafficserver restart`.
> The consequence of {{--with-group}} and {{--with-user}} of {{configure}}
> should be mentioned as well, as well if there's none.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TS-4086) Documentation for proxy.config.log.rolling_size_mb doesn't mention minimum size
[ https://issues.apache.org/jira/browse/TS-4086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15096752#comment-15096752 ] ASF subversion and git services commented on TS-4086: - Commit 40500c710b8b4aad0bf223c1ae4962cdf0725973 in trafficserver's branch refs/heads/master from [~jsime] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=40500c7 ] Docs: build cleanups and multiple Jira issues. [TS-4037] Table of Contents fixes [TS-4086] Minimum size for proxy.config.log.rolling_size_mb [TS-4077] Doc build warnings and errors [TS-3704] ^^ [TS-3703] ^^ [TS-3288] Confirmed documentation is accurate that any uid != 0 is accepted by traffic_manager This closes #419 > Documentation for proxy.config.log.rolling_size_mb doesn't mention minimum > size > > > Key: TS-4086 > URL: https://issues.apache.org/jira/browse/TS-4086 > Project: Traffic Server > Issue Type: Bug > Components: Logging >Reporter: Daniel Xu >Assignee: Jon Sime > Fix For: Docs > > > The minimum size to roll with is 10mb, but the documentation doesn't mention > this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-4037) various table of contents errors
[
https://issues.apache.org/jira/browse/TS-4037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15096757#comment-15096757
]
ASF GitHub Bot commented on TS-4037:
Github user asfgit closed the pull request at:
https://github.com/apache/trafficserver/pull/419
> various table of contents errors
>
>
> Key: TS-4037
> URL: https://issues.apache.org/jira/browse/TS-4037
> Project: Traffic Server
> Issue Type: Bug
> Components: Documentation
>Reporter: James Peach
>Assignee: Jon Sime
> Fix For: Docs
>
>
> Building the HTML docs on Fedora 22:
> {code}
> ...
> /opt/home/src/trafficserver.git/doc/admin-guide/configuration/index.en.rst:25:
> WARNING: toctree contains reference to nonexisting document
> u'admin-guide/configuration/reverse-proxying.en'
> /opt/home/src/trafficserver.git/doc/admin-guide/index.en.rst:27: WARNING:
> toctree contains reference to nonexisting document
> u'admin-guide/troubleshooting.en'
> /opt/home/src/trafficserver.git/doc/admin-guide/monitoring/monitoring/third-party/index.en.rst:25:
> WARNING: toctree contains reference to nonexisting document
> u'admin-guide/monitoring/monitoring/third-party/circonus.en'
> /opt/home/src/trafficserver.git/doc/admin-guide/monitoring/monitoring/third-party/index.en.rst:25:
> WARNING: toctree contains reference to nonexisting document
> u'admin-guide/monitoring/monitoring/third-party/logstash.en'
> /opt/home/src/trafficserver.git/doc/admin-guide/monitoring/monitoring/third-party/index.en.rst:25:
> WARNING: toctree contains reference to nonexisting document
> u'admin-guide/monitoring/monitoring/third-party/nagios.en'
> /opt/home/src/trafficserver.git/doc/admin-guide/monitoring/monitoring/third-party/index.en.rst:25:
> WARNING: toctree contains reference to nonexisting document
> u'admin-guide/monitoring/monitoring/third-party/zabbix.en'
> ...
> /opt/home/src/trafficserver.git/doc/developer-guide/introduction/audience.en.rst:25:
> WARNING: toctree contains reference to nonexisting document
> u'developer-guide/introduction/preface/how-to-use-this-book.en'
> /opt/home/src/trafficserver.git/doc/developer-guide/introduction/audience.en.rst:25:
> WARNING: toctree contains reference to nonexisting document
> u'developer-guide/introduction/preface/typographical-conventions.en'
> /opt/home/src/trafficserver.git/doc/developer-guide/plugins/adding-statistics.en.rst:34:
> WARNING: toctree contains reference to nonexisting document
> u'developer-guide/plugins/adding-statistics/coupled-statistics.en'
> /opt/home/src/trafficserver.git/doc/developer-guide/plugins/adding-statistics.en.rst:34:
> WARNING: toctree contains reference to nonexisting document
> u'developer-guide/plugins/adding-statistics/viewing-statistics-using-traffic-line.en'
> /opt/home/src/trafficserver.git/doc/developer-guide/plugins/hooks-and-transactions/index.en.rst:157:
> WARNING: toctree contains reference to nonexisting document
> u'developer-guide/plugins/hooks-and-transactions/trafficserver-timers.en'
> /opt/home/src/trafficserver.git/doc/developer-guide/plugins/new-protocol-plugins.en.rst:None:
> WARNING: image file not readable:
> developer-guide/plugins/../static/images/sdk/Protocol_state_diagram.jpg
> /opt/home/src/trafficserver.git/doc/developer-guide/plugins/new-protocol-plugins.en.rst:None:
> WARNING: image file not readable:
> developer-guide/plugins/../static/images/sdk/protocol_sm_big.jpg
> /opt/home/src/trafficserver.git/doc/developer-guide/plugins/new-protocol-plugins.en.rst:None:
> WARNING: image file not readable:
> developer-guide/plugins/../static/images/sdk/protocol_evt.jpg
> /opt/home/src/trafficserver.git/doc/developer-guide/plugins/new-protocol-plugins.en.rst:None:
> WARNING: image file not readable:
> developer-guide/plugins/../static/images/sdk/txn_sm.jpg
> /opt/home/src/trafficserver.git/doc/developer-guide/troubleshooting-tips.en.rst:23:
> WARNING: toctree contains reference to nonexisting document
> u'developer-guide/troubleshooting-tips/unable-to-debug-tags.en'
> /opt/home/src/trafficserver.git/doc/developer-guide/troubleshooting-tips.en.rst:23:
> WARNING: toctree contains reference to nonexisting document
> u'developer-guide/troubleshooting-tips/using-a-debugger.en'
> /opt/home/src/trafficserver.git/doc/developer-guide/troubleshooting-tips.en.rst:23:
> WARNING: toctree contains reference to nonexisting document
> u'developer-guide/troubleshooting-tips/debugging-memory-leaks.en'
> ...checking consistency...
> /opt/home/src/trafficserver.git/doc/admin-guide/configuring-traffic-server.en.rst::
> WARNING: document isn't included in any toctree
> /opt/home/src/trafficserver.git/doc/admin-guide/hierachical-caching.en.rst::
> WARNING: document isn't included in any toctree
> /opt/home/src/trafficserver.git/doc/admin-guide/tran
[jira] [Commented] (TS-4037) various table of contents errors
[
https://issues.apache.org/jira/browse/TS-4037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15096751#comment-15096751
]
ASF subversion and git services commented on TS-4037:
-
Commit 40500c710b8b4aad0bf223c1ae4962cdf0725973 in trafficserver's branch
refs/heads/master from [~jsime]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=40500c7 ]
Docs: build cleanups and multiple Jira issues.
[TS-4037] Table of Contents fixes
[TS-4086] Minimum size for proxy.config.log.rolling_size_mb
[TS-4077] Doc build warnings and errors
[TS-3704] ^^
[TS-3703] ^^
[TS-3288] Confirmed documentation is accurate that any uid != 0 is accepted by
traffic_manager
This closes #419
> various table of contents errors
>
>
> Key: TS-4037
> URL: https://issues.apache.org/jira/browse/TS-4037
> Project: Traffic Server
> Issue Type: Bug
> Components: Documentation
>Reporter: James Peach
>Assignee: Jon Sime
> Fix For: Docs
>
>
> Building the HTML docs on Fedora 22:
> {code}
> ...
> /opt/home/src/trafficserver.git/doc/admin-guide/configuration/index.en.rst:25:
> WARNING: toctree contains reference to nonexisting document
> u'admin-guide/configuration/reverse-proxying.en'
> /opt/home/src/trafficserver.git/doc/admin-guide/index.en.rst:27: WARNING:
> toctree contains reference to nonexisting document
> u'admin-guide/troubleshooting.en'
> /opt/home/src/trafficserver.git/doc/admin-guide/monitoring/monitoring/third-party/index.en.rst:25:
> WARNING: toctree contains reference to nonexisting document
> u'admin-guide/monitoring/monitoring/third-party/circonus.en'
> /opt/home/src/trafficserver.git/doc/admin-guide/monitoring/monitoring/third-party/index.en.rst:25:
> WARNING: toctree contains reference to nonexisting document
> u'admin-guide/monitoring/monitoring/third-party/logstash.en'
> /opt/home/src/trafficserver.git/doc/admin-guide/monitoring/monitoring/third-party/index.en.rst:25:
> WARNING: toctree contains reference to nonexisting document
> u'admin-guide/monitoring/monitoring/third-party/nagios.en'
> /opt/home/src/trafficserver.git/doc/admin-guide/monitoring/monitoring/third-party/index.en.rst:25:
> WARNING: toctree contains reference to nonexisting document
> u'admin-guide/monitoring/monitoring/third-party/zabbix.en'
> ...
> /opt/home/src/trafficserver.git/doc/developer-guide/introduction/audience.en.rst:25:
> WARNING: toctree contains reference to nonexisting document
> u'developer-guide/introduction/preface/how-to-use-this-book.en'
> /opt/home/src/trafficserver.git/doc/developer-guide/introduction/audience.en.rst:25:
> WARNING: toctree contains reference to nonexisting document
> u'developer-guide/introduction/preface/typographical-conventions.en'
> /opt/home/src/trafficserver.git/doc/developer-guide/plugins/adding-statistics.en.rst:34:
> WARNING: toctree contains reference to nonexisting document
> u'developer-guide/plugins/adding-statistics/coupled-statistics.en'
> /opt/home/src/trafficserver.git/doc/developer-guide/plugins/adding-statistics.en.rst:34:
> WARNING: toctree contains reference to nonexisting document
> u'developer-guide/plugins/adding-statistics/viewing-statistics-using-traffic-line.en'
> /opt/home/src/trafficserver.git/doc/developer-guide/plugins/hooks-and-transactions/index.en.rst:157:
> WARNING: toctree contains reference to nonexisting document
> u'developer-guide/plugins/hooks-and-transactions/trafficserver-timers.en'
> /opt/home/src/trafficserver.git/doc/developer-guide/plugins/new-protocol-plugins.en.rst:None:
> WARNING: image file not readable:
> developer-guide/plugins/../static/images/sdk/Protocol_state_diagram.jpg
> /opt/home/src/trafficserver.git/doc/developer-guide/plugins/new-protocol-plugins.en.rst:None:
> WARNING: image file not readable:
> developer-guide/plugins/../static/images/sdk/protocol_sm_big.jpg
> /opt/home/src/trafficserver.git/doc/developer-guide/plugins/new-protocol-plugins.en.rst:None:
> WARNING: image file not readable:
> developer-guide/plugins/../static/images/sdk/protocol_evt.jpg
> /opt/home/src/trafficserver.git/doc/developer-guide/plugins/new-protocol-plugins.en.rst:None:
> WARNING: image file not readable:
> developer-guide/plugins/../static/images/sdk/txn_sm.jpg
> /opt/home/src/trafficserver.git/doc/developer-guide/troubleshooting-tips.en.rst:23:
> WARNING: toctree contains reference to nonexisting document
> u'developer-guide/troubleshooting-tips/unable-to-debug-tags.en'
> /opt/home/src/trafficserver.git/doc/developer-guide/troubleshooting-tips.en.rst:23:
> WARNING: toctree contains reference to nonexisting document
> u'developer-guide/troubleshooting-tips/using-a-debugger.en'
> /opt/home/src/trafficserver.git/doc/developer-guide/troubleshooting-tips.en.rst:23:
> WARNING: toctree contains reference to none
[jira] [Commented] (TS-3704) fix broken links during "make html" part 2
[
https://issues.apache.org/jira/browse/TS-3704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15096754#comment-15096754
]
ASF subversion and git services commented on TS-3704:
-
Commit 40500c710b8b4aad0bf223c1ae4962cdf0725973 in trafficserver's branch
refs/heads/master from [~jsime]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=40500c7 ]
Docs: build cleanups and multiple Jira issues.
[TS-4037] Table of Contents fixes
[TS-4086] Minimum size for proxy.config.log.rolling_size_mb
[TS-4077] Doc build warnings and errors
[TS-3704] ^^
[TS-3703] ^^
[TS-3288] Confirmed documentation is accurate that any uid != 0 is accepted by
traffic_manager
This closes #419
> fix broken links during "make html" part 2
> --
>
> Key: TS-3704
> URL: https://issues.apache.org/jira/browse/TS-3704
> Project: Traffic Server
> Issue Type: Bug
> Components: Docs
>Reporter: Oknet Xu
>Assignee: Jon Sime
> Fix For: Docs
>
>
> here is the patch:
> {code}
> diff --git a/doc/arch/cache/cache-arch.en.rst
> b/doc/arch/cache/cache-arch.en.rst
> index b870a88..6b36347 100644
> --- a/doc/arch/cache/cache-arch.en.rst
> +++ b/doc/arch/cache/cache-arch.en.rst
> @@ -36,7 +36,7 @@ discussed only to the extent needed to understand the
> internal mechanisms. This
> document will be useful primarily to |TS| developers working on the |TS|
> codebase or plugins for |TS|. It is assumed the reader is already familiar
> with
> the :ref:`admin-guide` and specifically with :ref:`http-proxy-caching` and
> -:ref:`configuring-the-cache` along with the associated configuration files
> and
> +:ref:`admin-configuring-the-cache` along with the associated configuration
> files and
> values.
>
> Unfortunately, the internal terminology is not particularly consistent, so
> this
> @@ -789,7 +789,7 @@ information. This will always contain the HTTP headers
> for all
> There is provision in the code to support *read while write*, that is,
> serving an object from cache in one transaction while it is being written
> in
> another. Several settings are needed for it to be used. See
> - :ref:`reducing-origin-server-requests-avoiding-the-thundering-herd`. It
> must
> + :ref:`admin-reducing-origin-server-requests`. It must
> specifically enabled in :file:`records.config` and if not, a cache read
> will
> fail if the object is currently be written or updated.
>
> diff --git a/doc/reference/commands/traffic_server.en.rst
> b/doc/reference/commands/traffic_server.en.rst
> index abbee2a..75c11ea 100644
> --- a/doc/reference/commands/traffic_server.en.rst
> +++ b/doc/reference/commands/traffic_server.en.rst
> @@ -15,7 +15,7 @@
>specific language governing permissions and limitations
>under the License.
>
> -.. _traffic-server:
> +.. _traffic_server:
>
> ==
> traffic_server
> diff --git a/doc/reference/commands/traffic_via.en.rst
> b/doc/reference/commands/traffic_via.en.rst
> index 94a82fd..26aa057 100644
> --- a/doc/reference/commands/traffic_via.en.rst
> +++ b/doc/reference/commands/traffic_via.en.rst
> @@ -71,7 +71,7 @@ Decode the Via header from command-line arguments::
> Parent proxy connection status :no parent proxy
> or unknown
> Origin server connection status:connection open
> failed
>
> -Decode the Via header from a curl request, using the :ref:`X-Debug
> <_xdebug_plugin>` plugin::
> +Decode the Via header from a curl request, using the :ref:`X-Debug
> ` plugin::
>
> $ curl -H "X-Debug: Via" -I http://test.example.com | traffic_via -
> Via header is uScMsSf pSeN:t cCMi p sS, Length is 24
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TS-4077) Clean up doc build warnings
[ https://issues.apache.org/jira/browse/TS-4077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15096753#comment-15096753 ] ASF subversion and git services commented on TS-4077: - Commit 40500c710b8b4aad0bf223c1ae4962cdf0725973 in trafficserver's branch refs/heads/master from [~jsime] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=40500c7 ] Docs: build cleanups and multiple Jira issues. [TS-4037] Table of Contents fixes [TS-4086] Minimum size for proxy.config.log.rolling_size_mb [TS-4077] Doc build warnings and errors [TS-3704] ^^ [TS-3703] ^^ [TS-3288] Confirmed documentation is accurate that any uid != 0 is accepted by traffic_manager This closes #419 > Clean up doc build warnings > --- > > Key: TS-4077 > URL: https://issues.apache.org/jira/browse/TS-4077 > Project: Traffic Server > Issue Type: Bug > Components: Documentation >Reporter: Miles Libbey >Assignee: Jon Sime > Fix For: Docs > > > When building the documentation, there are a bunch of warnings about options, > invalid syntax etc. We should clean these up. > From a clean git repo: > trafficserver/doc/admin-guide/configuration/cache-basics.en.rst:160: WARNING: > Malformed :option: u'traffic_ctl config reload', does not contain option > marker - or -- or / > trafficserver/doc/admin-guide/configuration/cache-basics.en.rst:176: WARNING: > Malformed :option: u'traffic_ctl config reload', does not contain option > marker - or -- or / > trafficserver/doc/admin-guide/configuration/cache-basics.en.rst:195: WARNING: > Malformed :option: u'traffic_ctl config reload', does not contain option > marker - or -- or / > trafficserver/doc/admin-guide/configuration/cache-basics.en.rst:281: WARNING: > Malformed :option: u'traffic_ctl config reload', does not contain option > marker - or -- or / > trafficserver/doc/admin-guide/configuration/cache-basics.en.rst:305: WARNING: > Malformed :option: u'traffic_ctl config reload', does not contain option > marker - or -- or / > trafficserver/doc/admin-guide/configuration/cache-basics.en.rst:360: WARNING: > Malformed :option: u'traffic_ctl config reload', does not contain option > marker - or -- or / > trafficserver/doc/admin-guide/configuration/cache-basics.en.rst:413: WARNING: > Malformed :option: u'traffic_ctl config reload', does not contain option > marker - or -- or / > trafficserver/doc/admin-guide/configuration/cache-basics.en.rst:457: WARNING: > Malformed :option: u'traffic_ctl config reload', does not contain option > marker - or -- or / > trafficserver/doc/admin-guide/configuration/cache-basics.en.rst:483: WARNING: > Malformed :option: u'traffic_ctl config reload', does not contain option > marker - or -- or / > trafficserver/doc/admin-guide/configuration/cache-basics.en.rst:520: WARNING: > Malformed :option: u'traffic_ctl config reload', does not contain option > marker - or -- or / > trafficserver/doc/admin-guide/configuration/cache-basics.en.rst:541: WARNING: > Malformed :option: u'traffic_ctl config reload', does not contain option > marker - or -- or / > trafficserver/doc/admin-guide/configuration/cache-basics.en.rst:568: WARNING: > Malformed :option: u'traffic_ctl config reload', does not contain option > marker - or -- or / > trafficserver/doc/admin-guide/configuration/cache-basics.en.rst:584: WARNING: > Malformed :option: u'traffic_ctl config reload', does not contain option > marker - or -- or / > trafficserver/doc/admin-guide/configuration/cache-basics.en.rst:612: WARNING: > Malformed :option: u'traffic_ctl config reload', does not contain option > marker - or -- or / > trafficserver/doc/admin-guide/configuration/cache-basics.en.rst:640: WARNING: > Malformed :option: u'traffic_ctl config reload', does not contain option > marker - or -- or / > trafficserver/doc/admin-guide/configuration/cache-basics.en.rst:672: WARNING: > Malformed :option: u'traffic_ctl config reload', does not contain option > marker - or -- or / > trafficserver/doc/admin-guide/configuration/hierachical-caching.en.rst:18: > SEVERE: Problems with "include" directive path: > InputError: [Errno 2] No such file or directory: 'admin-guide/common.defs'. > trafficserver/doc/admin-guide/configuration/hierachical-caching.en.rst:173: > WARNING: Malformed :option: u'traffic_ctl config reload', does not contain > option marker - or -- or / > trafficserver/doc/admin-guide/configuration/hierachical-caching.en.rst:221: > WARNING: Malformed :option: u'traffic_ctl config reload', does not contain > option marker - or -- or / > trafficserver/doc/admin-guide/configuration/redirecting-http-requests.en.rst:265: > WARNING: Malformed :option: u'traffic_ctl config reload', does not contain > option marker - or -- or / > trafficserver/doc/admin-guide/configuration/redirecting-h
[jira] [Commented] (TS-3703) fix broken links during "make html"
[
https://issues.apache.org/jira/browse/TS-3703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15096755#comment-15096755
]
ASF subversion and git services commented on TS-3703:
-
Commit 40500c710b8b4aad0bf223c1ae4962cdf0725973 in trafficserver's branch
refs/heads/master from [~jsime]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=40500c7 ]
Docs: build cleanups and multiple Jira issues.
[TS-4037] Table of Contents fixes
[TS-4086] Minimum size for proxy.config.log.rolling_size_mb
[TS-4077] Doc build warnings and errors
[TS-3704] ^^
[TS-3703] ^^
[TS-3288] Confirmed documentation is accurate that any uid != 0 is accepted by
traffic_manager
This closes #419
> fix broken links during "make html"
> ---
>
> Key: TS-3703
> URL: https://issues.apache.org/jira/browse/TS-3703
> Project: Traffic Server
> Issue Type: Bug
> Components: Docs
>Reporter: Oknet Xu
>Assignee: Jon Sime
> Fix For: Docs
>
>
> here is the patch:
> {code}
> diff --git a/doc/admin/configuring-cache.en.rst
> b/doc/admin/configuring-cache.en.rst
> index 22a31e0..5b5a75f 100644
> --- a/doc/admin/configuring-cache.en.rst
> +++ b/doc/admin/configuring-cache.en.rst
> @@ -1,4 +1,4 @@
> -.. _configuring-the-cache:
> +.. _admin-configuring-the-cache:
>
> Configuring the Cache
> *
> diff --git a/doc/admin/event-logging-formats.en.rst
> b/doc/admin/event-logging-formats.en.rst
> index 4e1c7cc..c16b452 100644
> --- a/doc/admin/event-logging-formats.en.rst
> +++ b/doc/admin/event-logging-formats.en.rst
> @@ -1,4 +1,4 @@
> -.. _event-logging-formats:
> +.. _admin-event-logging-formats:
>
> Event Logging Formats
> *
> diff --git a/doc/admin/hierachical-caching.en.rst
> b/doc/admin/hierachical-caching.en.rst
> index 5c4443e..743534b 100644
> --- a/doc/admin/hierachical-caching.en.rst
> +++ b/doc/admin/hierachical-caching.en.rst
> @@ -1,4 +1,4 @@
> -.. _hierarchical-caching:
> +.. _admin-hierarchical-caching:
>
> Hierarchical Caching
>
> diff --git a/doc/admin/http-proxy-caching.en.rst
> b/doc/admin/http-proxy-caching.en.rst
> index 2ef0700..a2ac5c7 100644
> --- a/doc/admin/http-proxy-caching.en.rst
> +++ b/doc/admin/http-proxy-caching.en.rst
> @@ -701,7 +701,7 @@ Traffic Server does network I/O in large chunks (32K or
> so) and therefore the
> granularity of transaction buffering control is limited to a similar
> precision.
>
> The buffer size calculations include all elements in the transaction,
> including
> -any buffers associated with :ref:`transform plugins `.
> +any buffers associated with :ref:`transform-plugins
> `.
>
> Transaction buffering control can be enabled globally by using configuration
> variables or by :c:func:`TSHttpTxnConfigIntSet` in a plugin.
> @@ -720,7 +720,7 @@ mark. If you set only one, the other will be set to the
> same value.
> If using :c:func:`TSHttpTxnConfigIntSet`, it must be called no later than
> :c:data:`TS_HTTP_READ_RESPONSE_HDR_HOOK`.
>
> -.. _reducing-origin-server-requests:
> +.. _admin-reducing-origin-server-requests:
>
> Reducing Origin Server Requests (Avoiding the Thundering Herd)
> ==
> diff --git a/doc/admin/security-options.en.rst
> b/doc/admin/security-options.en.rst
> index a2afccb..6641303 100644
> --- a/doc/admin/security-options.en.rst
> +++ b/doc/admin/security-options.en.rst
> @@ -78,7 +78,7 @@ termination option.
> - Enable and configure SSL termination for Traffic Server/origin server
> connections: :ref:`admin-traffic-server-and-origin-server-connections`
>
> -.. _client-and-traffic-server-connections:
> +.. _admin-client-and-traffic-server-connections:
>
> Client and Traffic Server Connections
> -
> @@ -173,7 +173,7 @@ Client/Traffic Server connections, you must do the
> following:
> local node or :option:`traffic_line -M` to restart Traffic Server on all
> the nodes in a cluster.
>
> -.. _traffic-server-and-origin-server-connections:
> +.. _admin-traffic-server-and-origin-server-connections:
>
> Traffic Server and Origin Server Connections
>
> diff --git a/doc/admin/working-log-files.en.rst
> b/doc/admin/working-log-files.en.rst
> index 85f1fd3..3266edc 100644
> --- a/doc/admin/working-log-files.en.rst
> +++ b/doc/admin/working-log-files.en.rst
> @@ -725,7 +725,7 @@ To configure Traffic Server to collate event log files,
> you must perform
> the following tasks:
>
> - Either :ref:`admin-configuring-traffic-server-to-be-a-collation-server`
> or install
> - and configure a :ref:`admin-using-a-standalone-collator:`.
> + and configure a :ref:`admin-using-a-standalone-collator`.
>
>
[jira] [Updated] (TS-3922) Add independent WebSocket timeouts
[ https://issues.apache.org/jira/browse/TS-3922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Geffon updated TS-3922: - Fix Version/s: (was: 6.2.0) > Add independent WebSocket timeouts > -- > > Key: TS-3922 > URL: https://issues.apache.org/jira/browse/TS-3922 > Project: Traffic Server > Issue Type: Improvement > Components: Core >Reporter: Brian Geffon >Assignee: Brian Geffon > > Right now WebSockets fall under the active/inactive transaction timeouts. > Obviously the inactivate timeout isn't a problem but the active timeout is. > We need at minimum a new timeout for active WS connections, I'll likely add a > new timeout for inactive state too. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TS-4094) Clean up RD type junk in ControlMatcher
[
https://issues.apache.org/jira/browse/TS-4094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan M. Carroll resolved TS-4094.
-
Resolution: Fixed
> Clean up RD type junk in ControlMatcher
> ---
>
> Key: TS-4094
> URL: https://issues.apache.org/jira/browse/TS-4094
> Project: Traffic Server
> Issue Type: Improvement
> Components: Cleanup
>Reporter: Alan M. Carroll
>Assignee: Alan M. Carroll
> Fix For: 6.2.0
>
>
> The RD type information for {{RequestData}} in {{ControlMatcher}} is used
> only one place and even there it could be done better and more robustly with
> {{dynamic_cast}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TS-1611) async http request in lua remap plugin
[ https://issues.apache.org/jira/browse/TS-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15097298#comment-15097298 ] Kit Chan commented on TS-1611: -- this is done in 04/2015. forgot to close it. > async http request in lua remap plugin > -- > > Key: TS-1611 > URL: https://issues.apache.org/jira/browse/TS-1611 > Project: Traffic Server > Issue Type: Improvement > Components: Lua, Plugins >Reporter: Luca Rea >Assignee: Kit Chan > Fix For: 6.0.0 > > Attachments: > 0001-TS-1611-async-http-request-in-lua-remap-plugin.patch, > 0002-TS-1611-add-ts_lua_constant.c.patch, > 0003-TS-1611-refine-doc-for-ts_lua.patch > > > Hi, > can you add support for async http requests in lua remap plugin please? > Thank you -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-1611) async http request in lua remap plugin
[ https://issues.apache.org/jira/browse/TS-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kit Chan updated TS-1611: - Fix Version/s: (was: sometime) 6.0.0 > async http request in lua remap plugin > -- > > Key: TS-1611 > URL: https://issues.apache.org/jira/browse/TS-1611 > Project: Traffic Server > Issue Type: Improvement > Components: Lua, Plugins >Reporter: Luca Rea >Assignee: Kit Chan > Fix For: 6.0.0 > > Attachments: > 0001-TS-1611-async-http-request-in-lua-remap-plugin.patch, > 0002-TS-1611-add-ts_lua_constant.c.patch, > 0003-TS-1611-refine-doc-for-ts_lua.patch > > > Hi, > can you add support for async http requests in lua remap plugin please? > Thank you -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TS-1611) async http request in lua remap plugin
[ https://issues.apache.org/jira/browse/TS-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kit Chan resolved TS-1611. -- Resolution: Fixed > async http request in lua remap plugin > -- > > Key: TS-1611 > URL: https://issues.apache.org/jira/browse/TS-1611 > Project: Traffic Server > Issue Type: Improvement > Components: Lua, Plugins >Reporter: Luca Rea >Assignee: Kit Chan > Fix For: 6.0.0 > > Attachments: > 0001-TS-1611-async-http-request-in-lua-remap-plugin.patch, > 0002-TS-1611-add-ts_lua_constant.c.patch, > 0003-TS-1611-refine-doc-for-ts_lua.patch > > > Hi, > can you add support for async http requests in lua remap plugin please? > Thank you -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-4114) ASAN based build fails with gcc 5
[ https://issues.apache.org/jira/browse/TS-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kit Chan updated TS-4114: - Assignee: (was: Kit Chan) > ASAN based build fails with gcc 5 > - > > Key: TS-4114 > URL: https://issues.apache.org/jira/browse/TS-4114 > Project: Traffic Server > Issue Type: Bug > Components: Build >Reporter: Jason Kenny > Fix For: 6.2.0 > > > When building with gcc 5.x and asan on, the build will fail with memory leak > issues in lua. > ==1442==ERROR: LeakSanitizer: detected memory leaks > Direct leak of 4112 byte(s) in 1 object(s) allocated from: > #0 0x47f8ea in __interceptor_malloc > (/home/jkenny/yats_build/asan_build/lib/luajit/src/host/buildvm+0x47f8ea) > #1 0x407c8d in build_code host/buildvm.c:204 > #2 0x407c8d in main host/buildvm.c:446 > #3 0x3a5201ed5c in __libc_start_main (/lib64/libc.so.6+0x3a5201ed5c) > Direct leak of 1304 byte(s) in 1 object(s) allocated from: > #0 0x47fa51 in calloc > (/home/jkenny/yats_build/asan_build/lib/luajit/src/host/buildvm+0x47fa51) > #1 0x405666 in build_code host/buildvm.c:177 > #2 0x405666 in main host/buildvm.c:446 > #3 0x3a5201ed5c in __libc_start_main (/lib64/libc.so.6+0x3a5201ed5c) > Direct leak of 372 byte(s) in 1 object(s) allocated from: > #0 0x47f8ea in __interceptor_malloc > (/home/jkenny/yats_build/asan_build/lib/luajit/src/host/buildvm+0x47f8ea) > #1 0x407cae in build_code host/buildvm.c:206 > #2 0x407cae in main host/buildvm.c:446 > #3 0x3a5201ed5c in __libc_start_main (/lib64/libc.so.6+0x3a5201ed5c) > Direct leak of 296 byte(s) in 1 object(s) allocated from: > #0 0x47f8ea in __interceptor_malloc > (/home/jkenny/yats_build/asan_build/lib/luajit/src/host/buildvm+0x47f8ea) > #1 0x40568d in build_code host/buildvm.c:182 > #2 0x40568d in main host/buildvm.c:446 > #3 0x3a5201ed5c in __libc_start_main (/lib64/libc.so.6+0x3a5201ed5c) > Direct leak of 16 byte(s) in 1 object(s) allocated from: > #0 0x47f8ea in __interceptor_malloc > (/home/jkenny/yats_build/asan_build/lib/luajit/src/host/buildvm+0x47f8ea) > #1 0x407c58 in sym_decorate host/buildvm.c:122 > #2 0x407c58 in build_code host/buildvm.c:203 > #3 0x407c58 in main host/buildvm.c:446 > #4 0x3a5201ed5c in __libc_start_main (/lib64/libc.so.6+0x3a5201ed5c) > Indirect leak of 14758 byte(s) in 1 object(s) allocated from: > #0 0x47f8ea in __interceptor_malloc > (/home/jkenny/yats_build/asan_build/lib/luajit/src/host/buildvm+0x47f8ea) > #1 0x407bbc in build_code host/buildvm.c:199 > #2 0x407bbc in main host/buildvm.c:446 > #3 0x3a5201ed5c in __libc_start_main (/lib64/libc.so.6+0x3a5201ed5c) > Indirect leak of 2425 byte(s) in 156 object(s) allocated from: > #0 0x47f8ea in __interceptor_malloc > (/home/jkenny/yats_build/asan_build/lib/luajit/src/host/buildvm+0x47f8ea) > #1 0x4b129c in sym_decorate host/buildvm.c:122 > #2 0x4b129c in sym_insert host/buildvm.c:166 > #3 0x407ed5 in build_code host/buildvm.c:230 > #4 0x407ed5 in main host/buildvm.c:446 > #5 0x3a5201ed5c in __libc_start_main (/lib64/libc.so.6+0x3a5201ed5c) > Indirect leak of 1082 byte(s) in 93 object(s) allocated from: > #0 0x47f8ea in __interceptor_malloc > (/home/jkenny/yats_build/asan_build/lib/luajit/src/host/buildvm+0x47f8ea) > #1 0x4b129c in sym_decorate host/buildvm.c:122 > #2 0x4b129c in sym_insert host/buildvm.c:166 > #3 0x407e72 in build_code host/buildvm.c:217 > #4 0x407e72 in main host/buildvm.c:446 > #5 0x3a5201ed5c in __libc_start_main (/lib64/libc.so.6+0x3a5201ed5c) > Indirect leak of 525 byte(s) in 37 object(s) allocated from: > #0 0x47f8ea in __interceptor_malloc > (/home/jkenny/yats_build/asan_build/lib/luajit/src/host/buildvm+0x47f8ea) > #1 0x4b4722 in sym_decorate host/buildvm.c:122 > #2 0x4b4722 in collect_reloc host/buildvm.c:140 > #3 0x4b4722 in dasm_encode ../dynasm/dasm_x86.h:425 > #4 0x407bce in build_code host/buildvm.c:200 > #5 0x407bce in main host/buildvm.c:446 > #6 0x3a5201ed5c in __libc_start_main (/lib64/libc.so.6+0x3a5201ed5c) > Indirect leak of 1 byte(s) in 1 object(s) allocated from: > #0 0x47f8ea in __interceptor_malloc > (/home/jkenny/yats_build/asan_build/lib/luajit/src/host/buildvm+0x47f8ea) > #1 0x4b129c in sym_decorate host/buildvm.c:122 > #2 0x4b129c in sym_insert host/buildvm.c:166 > #3 0x407fc9 in build_code host/buildvm.c:235 > #4 0x407fc9 in main host/buildvm.c:446 > #5 0x3a5201ed5c in __libc_start_main (/lib64/libc.so.6+0x3a5201ed5c) > SUMMARY: AddressSanitizer: 24891 byte(s) leaked in 293 allocation(s). > make[5]: *** [lj_ffdef.h] Error 23 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-4114) ASAN based build fails with gcc 5
[ https://issues.apache.org/jira/browse/TS-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15097303#comment-15097303 ] Kit Chan commented on TS-4114: -- I don't think i can help too much with this. let me know otherwise. > ASAN based build fails with gcc 5 > - > > Key: TS-4114 > URL: https://issues.apache.org/jira/browse/TS-4114 > Project: Traffic Server > Issue Type: Bug > Components: Build >Reporter: Jason Kenny > Fix For: 6.2.0 > > > When building with gcc 5.x and asan on, the build will fail with memory leak > issues in lua. > ==1442==ERROR: LeakSanitizer: detected memory leaks > Direct leak of 4112 byte(s) in 1 object(s) allocated from: > #0 0x47f8ea in __interceptor_malloc > (/home/jkenny/yats_build/asan_build/lib/luajit/src/host/buildvm+0x47f8ea) > #1 0x407c8d in build_code host/buildvm.c:204 > #2 0x407c8d in main host/buildvm.c:446 > #3 0x3a5201ed5c in __libc_start_main (/lib64/libc.so.6+0x3a5201ed5c) > Direct leak of 1304 byte(s) in 1 object(s) allocated from: > #0 0x47fa51 in calloc > (/home/jkenny/yats_build/asan_build/lib/luajit/src/host/buildvm+0x47fa51) > #1 0x405666 in build_code host/buildvm.c:177 > #2 0x405666 in main host/buildvm.c:446 > #3 0x3a5201ed5c in __libc_start_main (/lib64/libc.so.6+0x3a5201ed5c) > Direct leak of 372 byte(s) in 1 object(s) allocated from: > #0 0x47f8ea in __interceptor_malloc > (/home/jkenny/yats_build/asan_build/lib/luajit/src/host/buildvm+0x47f8ea) > #1 0x407cae in build_code host/buildvm.c:206 > #2 0x407cae in main host/buildvm.c:446 > #3 0x3a5201ed5c in __libc_start_main (/lib64/libc.so.6+0x3a5201ed5c) > Direct leak of 296 byte(s) in 1 object(s) allocated from: > #0 0x47f8ea in __interceptor_malloc > (/home/jkenny/yats_build/asan_build/lib/luajit/src/host/buildvm+0x47f8ea) > #1 0x40568d in build_code host/buildvm.c:182 > #2 0x40568d in main host/buildvm.c:446 > #3 0x3a5201ed5c in __libc_start_main (/lib64/libc.so.6+0x3a5201ed5c) > Direct leak of 16 byte(s) in 1 object(s) allocated from: > #0 0x47f8ea in __interceptor_malloc > (/home/jkenny/yats_build/asan_build/lib/luajit/src/host/buildvm+0x47f8ea) > #1 0x407c58 in sym_decorate host/buildvm.c:122 > #2 0x407c58 in build_code host/buildvm.c:203 > #3 0x407c58 in main host/buildvm.c:446 > #4 0x3a5201ed5c in __libc_start_main (/lib64/libc.so.6+0x3a5201ed5c) > Indirect leak of 14758 byte(s) in 1 object(s) allocated from: > #0 0x47f8ea in __interceptor_malloc > (/home/jkenny/yats_build/asan_build/lib/luajit/src/host/buildvm+0x47f8ea) > #1 0x407bbc in build_code host/buildvm.c:199 > #2 0x407bbc in main host/buildvm.c:446 > #3 0x3a5201ed5c in __libc_start_main (/lib64/libc.so.6+0x3a5201ed5c) > Indirect leak of 2425 byte(s) in 156 object(s) allocated from: > #0 0x47f8ea in __interceptor_malloc > (/home/jkenny/yats_build/asan_build/lib/luajit/src/host/buildvm+0x47f8ea) > #1 0x4b129c in sym_decorate host/buildvm.c:122 > #2 0x4b129c in sym_insert host/buildvm.c:166 > #3 0x407ed5 in build_code host/buildvm.c:230 > #4 0x407ed5 in main host/buildvm.c:446 > #5 0x3a5201ed5c in __libc_start_main (/lib64/libc.so.6+0x3a5201ed5c) > Indirect leak of 1082 byte(s) in 93 object(s) allocated from: > #0 0x47f8ea in __interceptor_malloc > (/home/jkenny/yats_build/asan_build/lib/luajit/src/host/buildvm+0x47f8ea) > #1 0x4b129c in sym_decorate host/buildvm.c:122 > #2 0x4b129c in sym_insert host/buildvm.c:166 > #3 0x407e72 in build_code host/buildvm.c:217 > #4 0x407e72 in main host/buildvm.c:446 > #5 0x3a5201ed5c in __libc_start_main (/lib64/libc.so.6+0x3a5201ed5c) > Indirect leak of 525 byte(s) in 37 object(s) allocated from: > #0 0x47f8ea in __interceptor_malloc > (/home/jkenny/yats_build/asan_build/lib/luajit/src/host/buildvm+0x47f8ea) > #1 0x4b4722 in sym_decorate host/buildvm.c:122 > #2 0x4b4722 in collect_reloc host/buildvm.c:140 > #3 0x4b4722 in dasm_encode ../dynasm/dasm_x86.h:425 > #4 0x407bce in build_code host/buildvm.c:200 > #5 0x407bce in main host/buildvm.c:446 > #6 0x3a5201ed5c in __libc_start_main (/lib64/libc.so.6+0x3a5201ed5c) > Indirect leak of 1 byte(s) in 1 object(s) allocated from: > #0 0x47f8ea in __interceptor_malloc > (/home/jkenny/yats_build/asan_build/lib/luajit/src/host/buildvm+0x47f8ea) > #1 0x4b129c in sym_decorate host/buildvm.c:122 > #2 0x4b129c in sym_insert host/buildvm.c:166 > #3 0x407fc9 in build_code host/buildvm.c:235 > #4 0x407fc9 in main host/buildvm.c:446 > #5 0x3a5201ed5c in __libc_start_main (/lib64/libc.so.6+0x3a5201ed5c) > SUMMARY: AddressSanitizer: 24891 byte(s) leaked in 293 allocation(s). > make[5]: *** [lj_ffdef.h] Error 23 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-4129) Support TSContSchedule in ts_lua plugin
[ https://issues.apache.org/jira/browse/TS-4129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kit Chan updated TS-4129: - Fix Version/s: 6.2.0 > Support TSContSchedule in ts_lua plugin > --- > > Key: TS-4129 > URL: https://issues.apache.org/jira/browse/TS-4129 > Project: Traffic Server > Issue Type: New Feature > Components: Lua, Plugins >Reporter: Kit Chan >Assignee: Kit Chan > Fix For: 6.2.0 > > > We want to allow to write lua script for ts_lua plugin to use > TSContSchedule() -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TS-4129) Support TSContSchedule in ts_lua plugin
Kit Chan created TS-4129: Summary: Support TSContSchedule in ts_lua plugin Key: TS-4129 URL: https://issues.apache.org/jira/browse/TS-4129 Project: Traffic Server Issue Type: New Feature Components: Lua, Plugins Reporter: Kit Chan We want to allow to write lua script for ts_lua plugin to use TSContSchedule() -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (TS-4129) Support TSContSchedule in ts_lua plugin
[ https://issues.apache.org/jira/browse/TS-4129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kit Chan reassigned TS-4129: Assignee: Kit Chan > Support TSContSchedule in ts_lua plugin > --- > > Key: TS-4129 > URL: https://issues.apache.org/jira/browse/TS-4129 > Project: Traffic Server > Issue Type: New Feature > Components: Lua, Plugins >Reporter: Kit Chan >Assignee: Kit Chan > Fix For: 6.2.0 > > > We want to allow to write lua script for ts_lua plugin to use > TSContSchedule() -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-4129) Support TSContSchedule in ts_lua plugin
[ https://issues.apache.org/jira/browse/TS-4129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15097308#comment-15097308 ] ASF GitHub Bot commented on TS-4129: GitHub user shukitchan opened a pull request: https://github.com/apache/trafficserver/pull/420 [TS-4129] Support TSContSchedule in ts_lua plugin @jpeach , pls help to take a look. You can merge this pull request into a Git repository by running: $ git pull https://github.com/shukitchan/trafficserver schedule-patch Alternatively you can review and apply these changes as the patch at: https://github.com/apache/trafficserver/pull/420.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #420 commit b4af1ede8e1a1d2cfeaa6fcb9addc8f44250d3d8 Author: Kit Chan Date: 2016-01-04T20:34:25Z support TSContSchedule() in ts_lua commit 6849a45f3e4ee710aab48b711ebf72d64e3682c7 Author: Kit Chan Date: 2016-01-04T20:49:34Z add an example > Support TSContSchedule in ts_lua plugin > --- > > Key: TS-4129 > URL: https://issues.apache.org/jira/browse/TS-4129 > Project: Traffic Server > Issue Type: New Feature > Components: Lua, Plugins >Reporter: Kit Chan >Assignee: Kit Chan > Fix For: 6.2.0 > > > We want to allow to write lua script for ts_lua plugin to use > TSContSchedule() -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TS-4130) wrong value assigned
northstar created TS-4130: - Summary: wrong value assigned Key: TS-4130 URL: https://issues.apache.org/jira/browse/TS-4130 Project: Traffic Server Issue Type: Bug Components: Core Reporter: northstar In the NetHandler::manage_active_queue() function: vc_next is not assigned. In the NetHandler::manage_keep_alive_queue() function: vc_next is assigned wrong value. It should be vc>keep_alive_queue_link.next. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-4130) wrong value assigned
[ https://issues.apache.org/jira/browse/TS-4130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15097522#comment-15097522 ] ASF GitHub Bot commented on TS-4130: GitHub user zuobeixing opened a pull request: https://github.com/apache/trafficserver/pull/421 TS-4130: wrong value assigned In the NetHandler::manage_active_queue() function: vc_next is not assigned. In the NetHandler::manage_keep_alive_queue() function: vc_next is assigned wrong value. It should be vc->keep_alive_queue_link.next. You can merge this pull request into a Git repository by running: $ git pull https://github.com/zuobeixing/trafficserver master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/trafficserver/pull/421.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #421 commit e4418da69544044e04628e3355d8e90e230cb920 Author: zuobeixing Date: 2016-01-14T03:10:27Z fix NetHandler::manage_keep_alive_queue and NetHandler::manage_active_queue bug In the NetHandler::manage_active_queue() function: vc_next is not assigned. In the NetHandler::manage_keep_alive_queue() function: vc_next is assigned wrong value. It should be vc->keep_alive_queue_link.next. > wrong value assigned > > > Key: TS-4130 > URL: https://issues.apache.org/jira/browse/TS-4130 > Project: Traffic Server > Issue Type: Bug > Components: Core >Reporter: northstar > > In the NetHandler::manage_active_queue() function: > vc_next is not assigned. > In the NetHandler::manage_keep_alive_queue() function: > vc_next is assigned wrong value. It should be vc>keep_alive_queue_link.next. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-4118) CID 1347871: Memory - illegal accesses in RegressionHPACK.cc
[
https://issues.apache.org/jira/browse/TS-4118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15097620#comment-15097620
]
ASF GitHub Bot commented on TS-4118:
GitHub user masaori335 opened a pull request:
https://github.com/apache/trafficserver/pull/423
TS-4118: CID 1347871: Add error handling in HPACK_Encode
[TS-4118](https://issues.apache.org/jira/browse/TS-4118)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/masaori335/trafficserver TS-4118
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/trafficserver/pull/423.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #423
commit 96b4d52015549e211d1b2ee9d5c773f18f408153
Author: Masaori Koshiba
Date: 2016-01-12T01:07:56Z
TS-4118: CID 1347871: Add error handling in HPACK_Encode
> CID 1347871: Memory - illegal accesses in RegressionHPACK.cc
> -
>
> Key: TS-4118
> URL: https://issues.apache.org/jira/browse/TS-4118
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP/2
>Reporter: Masaori Koshiba
>Assignee: Masaori Koshiba
> Fix For: 6.2.0
>
>
> {code}
> *** CID 1347871: Memory - illegal accesses (NEGATIVE_RETURNS)
> /proxy/http2/RegressionHPACK.cc: 428 in
> RegressionTest_HPACK_Encode(RegressionTest *, int, int *)()
> 422 uint64_t buf_len = BUFSIZE_FOR_REGRESSION_TEST;
> 423 int64_t len = http2_write_psuedo_headers(headers, buf, buf_len,
> indexing_table);
> 424 buf_len -= len;
> 425
> 426 MIMEFieldIter field_iter;
> 427 bool cont = false;
>CID 1347871: Memory - illegal accesses (NEGATIVE_RETURNS)
>Using variable "len" as an index to array "buf".
> 428 len += http2_write_header_fragment(headers, field_iter, buf +
> len, buf_len, indexing_table, cont);
> 429
> 430 box.check(len ==
> encoded_field_response_test_case[i].encoded_field_len, "encoded length was %"
> PRId64 ", expecting %d", len,
> 431 encoded_field_response_test_case[i].encoded_field_len);
> 432 box.check(len > 0 && memcmp(buf,
> encoded_field_response_test_case[i].encoded_field, len) == 0, "encoded value
> was invalid");
> 433
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TS-4130) wrong value assigned
[ https://issues.apache.org/jira/browse/TS-4130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-4130: -- Fix Version/s: 6.1.0 > wrong value assigned > > > Key: TS-4130 > URL: https://issues.apache.org/jira/browse/TS-4130 > Project: Traffic Server > Issue Type: Bug > Components: Core >Reporter: northstar > Fix For: 6.1.0 > > > In the NetHandler::manage_active_queue() function: > vc_next is not assigned. > In the NetHandler::manage_keep_alive_queue() function: > vc_next is assigned wrong value. It should be vc>keep_alive_queue_link.next. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-2354) improve documentation about different type of timeouts
[ https://issues.apache.org/jira/browse/TS-2354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15097760#comment-15097760 ] Oknet Xu commented on TS-2354: -- Referer to the comments in iocore/net/I_NetVConnection.h: /** 在状态机使用此NetVC一定时间之后，会收到VC_EVENT_ACTIVE_TIMEOUT事件。 如果读、写都未在此NetVC激活，那么此值会被忽略。 这个功能防止状态机较长时间的保持连接的打开状态。 Sets time after which SM should be notified. Sets the amount of time (in nanoseconds) after which the state machine using the NetVConnection should receive a VC_EVENT_ACTIVE_TIMEOUT event. The timeout is value is ignored if neither the read side nor the write side of the connection is currently active. The timer is reset if the function is called repeatedly This call can be used by SMs to make sure that it does not keep any connections open for a really long time. ... */ virtual void set_active_timeout(ink_hrtime timeout_in) = 0; /** 当状态机请求在此NetVC执行的IO操作没有完成时， 在读写都处于IDLE状态一定时间之后，状态机会收到VC_EVENT_INACTIVITY_TIMEOUT事件 任何读写操作的发生，都会导致计时器被重置。 如果读、写都未在此NetVC激活，那么此值会被忽略。 Sets time after which SM should be notified if the requested IO could not be performed. Sets the amount of time (in nanoseconds), if the NetVConnection is idle on both the read or write side, after which the state machine using the NetVConnection should receive a VC_EVENT_INACTIVITY_TIMEOUT event. Either read or write traffic will cause timer to be reset. Calling this function again also resets the timer. The timeout is value is ignored if neither the read side nor the write side of the connection is currently active. See section on timeout semantics above. */ virtual void set_inactivity_timeout(ink_hrtime timeout_in) = 0; I think that : Active Timeout means a NetVC life cycle time, after which the SM using the NetVConnection should close the NetVC to avoid connection flood attack. Inactivity Timeout means a NetVC max idle time, that implement a traditional timeout control, for example: connect to a remote server by non-block mode. > improve documentation about different type of timeouts > -- > > Key: TS-2354 > URL: https://issues.apache.org/jira/browse/TS-2354 > Project: Traffic Server > Issue Type: Task > Components: Documentation >Reporter: Daniel Vitor Morilha >Assignee: Jon Sime > Fix For: Docs > > > Traffic Server provides different types of timeouts: > - dns > - connect > - no activity > - active > I found no documentation about the timeouts, specially no activity and active. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
