[jira] [Updated] (TS-4068) Change default for server_ports to include IPv6
[
https://issues.apache.org/jira/browse/TS-4068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-4068:
--
Fix Version/s: 7.0.0
> Change default for server_ports to include IPv6
> ---
>
> Key: TS-4068
> URL: https://issues.apache.org/jira/browse/TS-4068
> Project: Traffic Server
> Issue Type: Improvement
> Components: Configuration
>Reporter: Leif Hedstrom
> Labels: compatibility
> Fix For: 7.0.0
>
>
> With the world finally moving towards universal IPv6 deployment, maybe for
> 7.0 we should change the default server ports? E.g.
> {code}
> CONFIG proxy.config.http.server_ports STRING 80 80:ipv6 443:ssl 443:ipv6:ssl
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (TS-4068) Change default for server_ports to include IPv6
[
https://issues.apache.org/jira/browse/TS-4068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom reassigned TS-4068:
-
Assignee: Leif Hedstrom
> Change default for server_ports to include IPv6
> ---
>
> Key: TS-4068
> URL: https://issues.apache.org/jira/browse/TS-4068
> Project: Traffic Server
> Issue Type: Improvement
> Components: Configuration
>Reporter: Leif Hedstrom
>Assignee: Leif Hedstrom
>Priority: Blocker
> Labels: compatibility
> Fix For: 7.0.0
>
>
> With the world finally moving towards universal IPv6 deployment, maybe for
> 7.0 we should change the default server ports? E.g.
> {code}
> CONFIG proxy.config.http.server_ports STRING 80 80:ipv6 443:ssl 443:ipv6:ssl
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TS-4067) memory leaks in parent selection regression tests
[
https://issues.apache.org/jira/browse/TS-4067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-4067:
--
Fix Version/s: 6.1.0
> memory leaks in parent selection regression tests
> -
>
> Key: TS-4067
> URL: https://issues.apache.org/jira/browse/TS-4067
> Project: Traffic Server
> Issue Type: Bug
> Components: Quality, Tests
>Reporter: James Peach
>Assignee: John Rushford
> Fix For: 6.1.0
>
>
> {code}
> $ sudo env MallocStackLogging=1 ./proxy/traffic_server -R 1 -r PARENTSELECTION
> ...
> leaks Report Version: 2.0
> Process 94249: 30288 nodes malloced for 53365 KB
> Failed to map remote region: [0x7ffcd000-0x7ffce000] r-x shared
> memory (1 page) [root] (error: 1)
> Process 94249: 502 leaks for 577728 total leaked bytes.
> Leak: 0x1081f000 size=299008 zone: DefaultMallocZone_0xcf5f000
> 0x0001 0x 0xefbeadde 0xefbeadde
> 0xefbeadde 0xefbeadde 0xefbeadde 0xefbeadde
> 0xefbeadde 0xefbeadde 0xefbeadde 0xefbeadde
> 0xefbeadde 0xefbeadde 0xefbeadde 0xefbeadde
> 0xefbeadde 0xefbeadde 0xefbeadde 0xefbeadde
> 0xefbeadde 0xefbeadde 0xefbeadde 0xefbeadde
> 0xefbeadde 0xefbeadde 0xefbeadde 0xefbeadde
> 0xefbeadde 0xefbeadde 0xefbeadde 0xefbeadde
> ...
> Call stack: [thread 0x7fff7c1c]: | start | main Main.cc:1793 |
> HostDBProcessor::start(int, unsigned long) HostDB.cc:531 |
> ClassAllocator::alloc() Allocator.h:122 |
> ink_freelist_new ink_queue.cc:181 | freelist_new(_InkFreeList*)
> ink_queue.cc:211 | ats_memalign ink_memory.cc:100 | posix_memalign |
> malloc_zone_memalign
> Leak: 0x11c4e000 size=262144 zone: DefaultMallocZone_0xcf5f000
> 0x0001 0x 0xefbeadde 0xefbeadde
> 0xefbeadde 0xefbeadde 0xefbeadde 0xefbeadde
> 0xefbeadde 0xefbeadde 0xefbeadde 0xefbeadde
> 0xefbeadde 0xefbeadde 0xefbeadde 0xefbeadde
> 0xefbeadde 0xefbeadde 0xefbeadde 0xefbeadde
> 0xefbeadde 0xefbeadde 0xefbeadde 0xefbeadde
> 0xefbeadde 0xefbeadde 0xefbeadde 0xefbeadde
> 0xefbeadde 0xefbeadde 0xefbeadde 0xefbeadde
> ...
> Call stack: [thread 0x70287000]: | thread_start | _pthread_body |
> _pthread_body | spawn_thread_internal(void*) Thread.cc:87 |
> EThread::execute() UnixEThread.cc:200 | EThread::process_event(Event*, int)
> UnixEThread.cc:128 | Continuation::handleEvent(int, void*)
> I_Continuation.h:146 | RegressionCont::mainEvent(int, Event*) Main.cc:1248 |
> RegressionTest::run(char*) Regression.cc:105 | RegressionTest::run_some()
> Regression.cc:126 | start_test(RegressionTest*) Regression.cc:79 |
> RegressionTest_PARENTSELECTION(RegressionTest*, int, int*)
> ParentSelection.cc:1023 | br(HttpRequestData*, char const*, sockaddr const*)
> ParentSelection.cc:1114 | HTTPHdr::create(HTTPType, HdrHeap*) HTTP.h:802 |
> new_HdrHeap(int) HdrHeap.cc:121 | thread_alloc(Allocator&, ProxyAllocator&)
> ProxyAllocator.cc:41 | Allocator::alloc_void() Allocator.h:63 |
> ink_freelist_new ink_queue.cc:181 | freelist_new(_InkFreeList*)
> ink_queue.cc:211 | ats_memalign ink_memory.cc:100 | posix_memalign |
> malloc_zone_memalign
> Leak: 0x7ff172d1cfd0 size=16 zone: DefaultMallocZone_0xcf5f000 length: 15
> "i.am.rabbit.net"
> Call stack: [thread 0x70287000]: | thread_start | _pthread_body |
> _pthread_body | spawn_thread_internal(void*) Thread.cc:87 |
> EThread::execute() UnixEThread.cc:200 | EThread::process_event(Event*, int)
> UnixEThread.cc:128 | Continuation::handleEvent(int, void*)
> I_Continuation.h:146 | RegressionCont::mainEvent(int, Event*) Main.cc:1248 |
> RegressionTest::run(char*) Regression.cc:105 | RegressionTest::run_some()
> Regression.cc:126 | start_test(RegressionTest*) Regression.cc:79 |
> RegressionTest_PARENTSELECTION(RegressionTest*, int, int*)
> ParentSelection.cc:1023 | br(HttpRequestData*, char const*, sockaddr const*)
> ParentSelection.cc:1114 | _xstrdup ink_memory.cc:225 | ats_malloc
> ink_memory.cc:54 | malloc | malloc_zone_malloc
> Leak: 0x7ff172d1e230 size=16 zone: DefaultMallocZone_0xcf5f000
> 0x 0x 0x 0x00010100
> {code}
> I think most of the leaks are from the sloppy implementation of the
> regression test, but I haven't looked at them all carefully. We should fix
> the regressions so that real problems are visible.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TS-4068) Change default for server_ports to include IPv6
[
https://issues.apache.org/jira/browse/TS-4068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-4068:
--
Priority: Blocker (was: Major)
> Change default for server_ports to include IPv6
> ---
>
> Key: TS-4068
> URL: https://issues.apache.org/jira/browse/TS-4068
> Project: Traffic Server
> Issue Type: Improvement
> Components: Configuration
>Reporter: Leif Hedstrom
>Priority: Blocker
> Labels: compatibility
> Fix For: 7.0.0
>
>
> With the world finally moving towards universal IPv6 deployment, maybe for
> 7.0 we should change the default server ports? E.g.
> {code}
> CONFIG proxy.config.http.server_ports STRING 80 80:ipv6 443:ssl 443:ipv6:ssl
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TS-4065) change metrics to counters where appropriate
[
https://issues.apache.org/jira/browse/TS-4065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-4065:
--
Fix Version/s: sometime
> change metrics to counters where appropriate
>
>
> Key: TS-4065
> URL: https://issues.apache.org/jira/browse/TS-4065
> Project: Traffic Server
> Issue Type: Bug
> Components: Management API, Metrics
>Reporter: James Peach
> Fix For: sometime
>
>
> In {{mgmt/RecordsConfig.cc}} almost all the metrics are registered as
> {{RECT_INT}} even though many (most?) of them have counter semantics. We
> should register the counters as {{RECT_COUNTER}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TS-4055) Segmentation fault
[
https://issues.apache.org/jira/browse/TS-4055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15051462#comment-15051462
]
Leif Hedstrom commented on TS-4055:
---
Can the OP verify that the fix from TS-3710 fixes this as well?
> Segmentation fault
> ---
>
> Key: TS-4055
> URL: https://issues.apache.org/jira/browse/TS-4055
> Project: Traffic Server
> Issue Type: Bug
>Affects Versions: 6.0.1
>Reporter: bettydramit
>
> {code}
> c++filt traffic_server: Segmentation fault (Address not mapped to object [0x8])
> traffic_server - STACK TRACE:
> /usr/bin/traffic_server(crash_logger_invoke(int, siginfo_t*,
> void*)+0x8e)[0x4abf4e]
> /lib64/libpthread.so.0(+0x10430)[0x2abaac562430]
> /usr/bin/traffic_server(HttpSM::handle_server_setup_error(int,
> void*)+0x25b)[0x5b5d0b]
> /usr/bin/traffic_server(HttpSM::state_send_server_request_header(int,
> void*)+0x142)[0x5c0dd2]
> /usr/bin/traffic_server(HttpSM::main_handler(int, void*)+0xc8)[0x5c5e38]
> /usr/bin/traffic_server(UnixNetVConnection::mainEvent(int,
> Event*)+0x4ff)[0x78651f]
> /usr/bin/traffic_server(InactivityCop::check_inactivity(int,
> Event*)+0x28d)[0x7789ad]
> /usr/bin/traffic_server(EThread::process_event(Event*, int)+0x8a)[0x7bdf5a]
> /usr/bin/traffic_server(EThread::execute()+0xaa5)[0x7bf045]
> /usr/bin/traffic_server[0x7bda25]
> /lib64/libpthread.so.0(+0x7555)[0x2abaac559555]
> /lib64/libc.so.6(clone+0x6d)[0x2abaad67bb9d]
> Dec 05 21:00:12 localhost sendEmail[23289]: Email was sent successfully!
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TS-4058) Logging doesn't work when TS is compiled and run w/ --with-user
[ https://issues.apache.org/jira/browse/TS-4058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-4058: -- Fix Version/s: sometime > Logging doesn't work when TS is compiled and run w/ --with-user > --- > > Key: TS-4058 > URL: https://issues.apache.org/jira/browse/TS-4058 > Project: Traffic Server > Issue Type: Bug > Components: Logging >Reporter: Daniel Xu >Assignee: Daniel Xu > Fix For: sometime > > > ie. we run this _without_ sudo. > traffic_cop output seems to point to permission errors that occur within > traffic_manager -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-4064) Customizable congestion control algorithms
[ https://issues.apache.org/jira/browse/TS-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-4064: -- Fix Version/s: sometime > Customizable congestion control algorithms > -- > > Key: TS-4064 > URL: https://issues.apache.org/jira/browse/TS-4064 > Project: Traffic Server > Issue Type: Improvement > Components: Core, Network >Reporter: Brian Geffon >Assignee: Brian Geffon > Fix For: sometime > > > This ticket will track per-socket configurable congestion control algorithms > based on incoming or outgoing socket types / listen or connection types. > Given asymmetric routes (such as User -> PoP -> DC) it might make sense to > have different congestion control algorithms or listening sockets and > outgoing sockets. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TS-4068) Change default for server_ports to include IPv6
Leif Hedstrom created TS-4068:
-
Summary: Change default for server_ports to include IPv6
Key: TS-4068
URL: https://issues.apache.org/jira/browse/TS-4068
Project: Traffic Server
Issue Type: Improvement
Components: Configuration
Reporter: Leif Hedstrom
With the world finally moving towards universal IPv6 deployment, maybe for 7.0
we should change the default server ports? E.g.
{code}
CONFIG proxy.config.http.server_ports STRING 80 80:ipv6 443:ssl 443:ipv6:ssl
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TS-4068) Change default for server_ports to include IPv6
[
https://issues.apache.org/jira/browse/TS-4068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-4068:
--
Labels: compatibility (was: )
> Change default for server_ports to include IPv6
> ---
>
> Key: TS-4068
> URL: https://issues.apache.org/jira/browse/TS-4068
> Project: Traffic Server
> Issue Type: Improvement
> Components: Configuration
>Reporter: Leif Hedstrom
> Labels: compatibility
> Fix For: 7.0.0
>
>
> With the world finally moving towards universal IPv6 deployment, maybe for
> 7.0 we should change the default server ports? E.g.
> {code}
> CONFIG proxy.config.http.server_ports STRING 80 80:ipv6 443:ssl 443:ipv6:ssl
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TS-4055) Segmentation fault
[
https://issues.apache.org/jira/browse/TS-4055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15051443#comment-15051443
]
Susan Hinrichs commented on TS-4055:
Yes, assuming this commit fixes the issue.
> Segmentation fault
> ---
>
> Key: TS-4055
> URL: https://issues.apache.org/jira/browse/TS-4055
> Project: Traffic Server
> Issue Type: Bug
>Affects Versions: 6.0.1
>Reporter: bettydramit
>
> {code}
> c++filt traffic_server: Segmentation fault (Address not mapped to object [0x8])
> traffic_server - STACK TRACE:
> /usr/bin/traffic_server(crash_logger_invoke(int, siginfo_t*,
> void*)+0x8e)[0x4abf4e]
> /lib64/libpthread.so.0(+0x10430)[0x2abaac562430]
> /usr/bin/traffic_server(HttpSM::handle_server_setup_error(int,
> void*)+0x25b)[0x5b5d0b]
> /usr/bin/traffic_server(HttpSM::state_send_server_request_header(int,
> void*)+0x142)[0x5c0dd2]
> /usr/bin/traffic_server(HttpSM::main_handler(int, void*)+0xc8)[0x5c5e38]
> /usr/bin/traffic_server(UnixNetVConnection::mainEvent(int,
> Event*)+0x4ff)[0x78651f]
> /usr/bin/traffic_server(InactivityCop::check_inactivity(int,
> Event*)+0x28d)[0x7789ad]
> /usr/bin/traffic_server(EThread::process_event(Event*, int)+0x8a)[0x7bdf5a]
> /usr/bin/traffic_server(EThread::execute()+0xaa5)[0x7bf045]
> /usr/bin/traffic_server[0x7bda25]
> /lib64/libpthread.so.0(+0x7555)[0x2abaac559555]
> /lib64/libc.so.6(clone+0x6d)[0x2abaad67bb9d]
> Dec 05 21:00:12 localhost sendEmail[23289]: Email was sent successfully!
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (TS-4069) proxy.config.diags.show_location doesn't work for plugins
David Carlin created TS-4069: Summary: proxy.config.diags.show_location doesn't work for plugins Key: TS-4069 URL: https://issues.apache.org/jira/browse/TS-4069 Project: Traffic Server Issue Type: Bug Components: Plugins Reporter: David Carlin enabling proxy.config.diags.show_location doesn't provide any additional debug info for plugins. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-4069) proxy.config.diags.show_location doesn't work for plugins
[ https://issues.apache.org/jira/browse/TS-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Carlin updated TS-4069: - Affects Version/s: 5.3.0 > proxy.config.diags.show_location doesn't work for plugins > - > > Key: TS-4069 > URL: https://issues.apache.org/jira/browse/TS-4069 > Project: Traffic Server > Issue Type: Bug > Components: Plugins >Affects Versions: 5.3.0 >Reporter: David Carlin > Labels: 5.3.x, yahoo > > enabling proxy.config.diags.show_location doesn't provide any additional > debug info for plugins. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-4069) proxy.config.diags.show_location doesn't work for plugins
[ https://issues.apache.org/jira/browse/TS-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Carlin updated TS-4069: - Labels: 5.3.x yahoo (was: ) > proxy.config.diags.show_location doesn't work for plugins > - > > Key: TS-4069 > URL: https://issues.apache.org/jira/browse/TS-4069 > Project: Traffic Server > Issue Type: Bug > Components: Plugins >Reporter: David Carlin > Labels: 5.3.x, yahoo > > enabling proxy.config.diags.show_location doesn't provide any additional > debug info for plugins. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
