[jira] [Commented] (TS-1026) Changes to improve docs formatting
[ https://issues.apache.org/jira/browse/TS-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13162498#comment-13162498 ] zoe slattery commented on TS-1026: -- Thanks... I just tested the site on IE7, IE8 and IE9. All look fine (although all I tested was the front page and docs). Changes to improve docs formatting -- Key: TS-1026 URL: https://issues.apache.org/jira/browse/TS-1026 Project: Traffic Server Issue Type: Improvement Components: Web site Reporter: zoe slattery Assignee: Igor Galić Priority: Minor Attachments: docspage.diff, docspage.diff, docspagethml.diff, downloadshtml.diff, indexhtml.diff, indexhtml.diff, stylescss.diff, stylescss.diff, stylescss.diff, stylescss.diff Remove the 'banner' class in styles.css and make all heading formats the same. Modify the docs template to use class blurbbox, this will leave margins around text. Still to do - fix the header of docs pages. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TS-1030) hash collation in hdrtoken_hash
[ https://issues.apache.org/jira/browse/TS-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Galić resolved TS-1030. Resolution: Fixed hash collation in hdrtoken_hash --- Key: TS-1030 URL: https://issues.apache.org/jira/browse/TS-1030 Project: Traffic Server Issue Type: Bug Components: HTTP Affects Versions: 3.1.2, 3.0.1 Reporter: Zhao Yongming Assignee: Leif Hedstrom Priority: Critical Fix For: 3.1.2, 3.0.2 we have find out a 3 characters collation: SPX == PUT that will crash TS, we need to take more care of those hash, or bad guys may put some magic headers and crash all TS in your production, that is the most powerful DOS -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1027) remap.config limited to ~255 entries
[
https://issues.apache.org/jira/browse/TS-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13162566#comment-13162566
]
Conan Wang commented on TS-1027:
btw: Is there a limit? Will growing number of remap rule impact the
performance? There are a lot of map http://ban.com http://org.ban.com
@action=deny in my remap.config.
remap.config limited to ~255 entries
Key: TS-1027
URL: https://issues.apache.org/jira/browse/TS-1027
Project: Traffic Server
Issue Type: Bug
Components: Configuration
Affects Versions: 3.0.2
Reporter: Greg Dallavalle
Remap.config errors out trafficserver when the entries exceed ~249
Due to issue TS-1024 I am using a large number of remaps to workaround the
issue. With this limit I'm unable to proceed with ATS. If there are ways to
overcome these problems, by all means, I'd be happy to listen and test.
The errors from traffic.out:
[Nov 21 15:20:08.572] Server {1080866016} ERROR: Cannot insert duplicate!
[Nov 21 15:20:08.573] Server {1080866016} ERROR: Couldn't insert into trie!
[Nov 21 15:20:08.573] Server {1080866016} ERROR: Could not insert new mapping
[Nov 21 15:20:08.573] Server {1080866016} WARNING: Could not add rule at line
#249; Aborting!
[Nov 21 15:20:08.578] Server {1080866016} WARNING: [ReverseProxy] Unable to
add mapping rule to lookup table at line 249
FATAL: [ReverseProxy] Unable to add mapping rule to lookup table at line 249
/usr/bin/traffic_server - STACK TRACE:
/usr/lib/trafficserver/libtsutil.so.3(ink_fatal_va+0xf7)[0x400301a7]
/usr/lib/trafficserver/libtsutil.so.3(ink_fatal+0x2c)[0x4003020c]
/usr/bin/traffic_server(_ZN10UrlRewrite10BuildTableEv+0x5a2)[0x819b402]
/usr/bin/traffic_server(_ZN10UrlRewriteC1EPKc+0x337)[0x819da87]
/usr/bin/traffic_server(_Z18init_reverse_proxyv+0x9a)[0x810bb6a]
/usr/bin/traffic_server(_Z20init_HttpProxyServerv+0xb)[0x814664b]
/usr/bin/traffic_server(main+0x12bb)[0x80b547b]
/lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0x40561113]
/usr/bin/traffic_server[0x80baffd]
[Nov 21 15:20:08.638] Manager {3072087760} ERROR:
[LocalManager::pollMgmtProcessServer] Server Process terminated due to Sig 6:
Aborted
[Nov 21 15:20:08.639] Manager {3072087760} ERROR: (last system error 2: No
such file or directory)
[Nov 21 15:20:08.639] Manager {3072087760} ERROR: [Alarms::signalAlarm]
Server Process was reset
[Nov 21 15:20:08.639] Manager {3072087760} ERROR: (last system error 2: No
such file or directory)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (TS-857) Crash Report: HttpTunnel::chain_abort_all - HttpServerSession::do_io_close - UnixNetVConnection::do_io_close
[
https://issues.apache.org/jira/browse/TS-857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom reopened TS-857:
--
Crash Report: HttpTunnel::chain_abort_all - HttpServerSession::do_io_close
- UnixNetVConnection::do_io_close
--
Key: TS-857
URL: https://issues.apache.org/jira/browse/TS-857
Project: Traffic Server
Issue Type: Bug
Components: HTTP, Network
Affects Versions: 3.1.0
Environment: in my branch that is something same as 3.0.x
Reporter: Zhao Yongming
Assignee: weijin
Fix For: 3.1.1
Attachments: ts-857.diff, ts-857.diff
here is the bt from the crash, some of the information is missing due to we
have not enable the --enable-debug configure options.
{code}
[New process 7532]
#0 ink_stack_trace_get (stack=value optimized out, len=value optimized
out, signalhandler_frame=value optimized out)
at ink_stack_trace.cc:68
68fp = (void **) (*fp);
(gdb) bt
#0 ink_stack_trace_get (stack=value optimized out, len=value optimized
out, signalhandler_frame=value optimized out)
at ink_stack_trace.cc:68
#1 0x2ba641dccef1 in ink_stack_trace_dump (sighandler_frame=value
optimized out) at ink_stack_trace.cc:114
#2 0x004df020 in signal_handler (sig=value optimized out) at
signals.cc:225
#3 signal handler called
#4 0x006a1ea9 in UnixNetVConnection::do_io_close (this=0x1cc9bd20,
alerrno=value optimized out)
at ../../iocore/eventsystem/I_Lock.h:297
#5 0x0051f1d0 in HttpServerSession::do_io_close
(this=0x2aaab0042c80, alerrno=20600) at HttpServerSession.cc:127
#6 0x0056d1e9 in HttpTunnel::chain_abort_all (this=0x2aabeeffdd70,
p=0x2aabeeffdf68) at HttpTunnel.cc:1300
#7 0x005269ca in HttpSM::tunnel_handler_ua (this=0x2aabeeffc070,
event=104, c=0x2aabeeffdda8) at HttpSM.cc:2987
#8 0x00571dfc in HttpTunnel::consumer_handler (this=0x2aabeeffdd70,
event=104, c=0x2aabeeffdda8) at HttpTunnel.cc:1232
#9 0x00572032 in HttpTunnel::main_handler (this=0x2aabeeffdd70,
event=1088608784, data=value optimized out)
at HttpTunnel.cc:1456
#10 0x006a6307 in write_to_net_io (nh=0x2b12d688, vc=0x1cc876e0,
thread=value optimized out)
at ../../iocore/eventsystem/I_Continuation.h:146
#11 0x0069ce97 in NetHandler::mainNetEvent (this=0x2b12d688,
event=value optimized out, e=0x171c1ed0) at UnixNet.cc:405
#12 0x006cddaf in EThread::process_event (this=0x2b12c010,
e=0x171c1ed0, calling_code=5) at I_Continuation.h:146
#13 0x006ce6bc in EThread::execute (this=0x2b12c010) at
UnixEThread.cc:262
#14 0x006cd0ee in spawn_thread_internal (a=0x171b58f0) at Thread.cc:88
#15 0x003c33c064a7 in start_thread () from /lib64/libpthread.so.0
#16 0x003c330d3c2d in clone () from /lib64/libc.so.6
(gdb) info f
Stack level 0, frame at 0x40e2b790:
rip = 0x2ba641dccdf3 in ink_stack_trace_get(void**, int, int)
(ink_stack_trace.cc:68); saved rip 0x2ba641dccef1
called by frame at 0x40e2bbe0
source language c++.
Arglist at 0x40e2b770, args: stack=value optimized out, len=value
optimized out, signalhandler_frame=value optimized out
Locals at 0x40e2b770, Previous frame's sp is 0x40e2b790
Saved registers:
rbx at 0x40e2b778, rbp at 0x40e2b780, rip at 0x40e2b788
(gdb)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1027) remap.config limited to ~255 entries
[
https://issues.apache.org/jira/browse/TS-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13162588#comment-13162588
]
Leif Hedstrom commented on TS-1027:
---
Test it :). Yes, there will be some penalty, but it also depends on your
configs. There's an initial hash on the hostname, so if you have unique
hostnames on each remap rule, it ought to be O(1). However, degenerated cases
with lots of rules for the same host could have some performance implications
(however, it does a trie on the prefix part of the path in that case).
This is in theory though, things might have changed. If you are seeing
performance problems, we should investigate. At a minimum, rules with unique
hostnames should be O(1) always (it's a simple hash table lookup).
remap.config limited to ~255 entries
Key: TS-1027
URL: https://issues.apache.org/jira/browse/TS-1027
Project: Traffic Server
Issue Type: Bug
Components: Configuration
Affects Versions: 3.0.2
Reporter: Greg Dallavalle
Remap.config errors out trafficserver when the entries exceed ~249
Due to issue TS-1024 I am using a large number of remaps to workaround the
issue. With this limit I'm unable to proceed with ATS. If there are ways to
overcome these problems, by all means, I'd be happy to listen and test.
The errors from traffic.out:
[Nov 21 15:20:08.572] Server {1080866016} ERROR: Cannot insert duplicate!
[Nov 21 15:20:08.573] Server {1080866016} ERROR: Couldn't insert into trie!
[Nov 21 15:20:08.573] Server {1080866016} ERROR: Could not insert new mapping
[Nov 21 15:20:08.573] Server {1080866016} WARNING: Could not add rule at line
#249; Aborting!
[Nov 21 15:20:08.578] Server {1080866016} WARNING: [ReverseProxy] Unable to
add mapping rule to lookup table at line 249
FATAL: [ReverseProxy] Unable to add mapping rule to lookup table at line 249
/usr/bin/traffic_server - STACK TRACE:
/usr/lib/trafficserver/libtsutil.so.3(ink_fatal_va+0xf7)[0x400301a7]
/usr/lib/trafficserver/libtsutil.so.3(ink_fatal+0x2c)[0x4003020c]
/usr/bin/traffic_server(_ZN10UrlRewrite10BuildTableEv+0x5a2)[0x819b402]
/usr/bin/traffic_server(_ZN10UrlRewriteC1EPKc+0x337)[0x819da87]
/usr/bin/traffic_server(_Z18init_reverse_proxyv+0x9a)[0x810bb6a]
/usr/bin/traffic_server(_Z20init_HttpProxyServerv+0xb)[0x814664b]
/usr/bin/traffic_server(main+0x12bb)[0x80b547b]
/lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0x40561113]
/usr/bin/traffic_server[0x80baffd]
[Nov 21 15:20:08.638] Manager {3072087760} ERROR:
[LocalManager::pollMgmtProcessServer] Server Process terminated due to Sig 6:
Aborted
[Nov 21 15:20:08.639] Manager {3072087760} ERROR: (last system error 2: No
such file or directory)
[Nov 21 15:20:08.639] Manager {3072087760} ERROR: [Alarms::signalAlarm]
Server Process was reset
[Nov 21 15:20:08.639] Manager {3072087760} ERROR: (last system error 2: No
such file or directory)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
