[jira] [Updated] (TS-2447) Cache fails to load / initialize, seems stuck on directory entry cleanup
[ https://issues.apache.org/jira/browse/TS-2447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Carlin updated TS-2447: - Labels: yahoo (was: ) Cache fails to load / initialize, seems stuck on directory entry cleanup Key: TS-2447 URL: https://issues.apache.org/jira/browse/TS-2447 Project: Traffic Server Issue Type: Bug Components: Cache Reporter: Leif Hedstrom Assignee: Alan M. Carroll Labels: yahoo Fix For: sometime We had an issue where a number of machines would not startup properly. They get stuck on reading / initializing the cache. It initializes the caches with {code} [Dec 20 16:45:40.195] Server {0x7f3f2f4ef7e0} DEBUG: (cache_hosting) Disk: 0: Vol Blocks: 1: Free space: 0 [Dec 20 16:45:40.195] Server {0x7f3f2f4ef7e0} DEBUG: (cache_hosting)Vol: 0 Size: 62509342 [Dec 20 16:45:40.195] Server {0x7f3f2f4ef7e0} DEBUG: (cache_hosting)Block No: 0 Size: 62509342 Free: 0 [Dec 20 16:45:40.195] Server {0x7f3f2f4ef7e0} DEBUG: (cache_hosting) Disk: 1: Vol Blocks: 1: Free space: 0 [Dec 20 16:45:40.195] Server {0x7f3f2f4ef7e0} DEBUG: (cache_hosting)Vol: 0 Size: 62509342 [Dec 20 16:45:40.195] Server {0x7f3f2f4ef7e0} DEBUG: (cache_hosting)Block No: 0 Size: 62509342 Free: 0 [Dec 20 16:45:40.195] Server {0x7f3f2f4ef7e0} DEBUG: (cache_hosting) Disk: 2: Vol Blocks: 1: Free space: 0 [Dec 20 16:45:40.195] Server {0x7f3f2f4ef7e0} DEBUG: (cache_hosting)Vol: 0 Size: 62509342 [Dec 20 16:45:40.195] Server {0x7f3f2f4ef7e0} DEBUG: (cache_hosting)Block No: 0 Size: 62509342 Free: 0 [Dec 20 16:45:40.195] Server {0x7f3f2f4ef7e0} DEBUG: (cache_hosting) Disk: 3: Vol Blocks: 1: Free space: 0 [Dec 20 16:45:40.195] Server {0x7f3f2f4ef7e0} DEBUG: (cache_hosting)Vol: 0 Size: 62509342 [Dec 20 16:45:40.195] Server {0x7f3f2f4ef7e0} DEBUG: (cache_hosting)Block No: 0 Size: 62509342 Free: 0 [Dec 20 16:45:40.195] Server {0x7f3f2f4ef7e0} DEBUG: (cache_hosting) Disk: 4: Vol Blocks: 1: Free space: 0 [Dec 20 16:45:40.195] Server {0x7f3f2f4ef7e0} DEBUG: (cache_hosting)Vol: 0 Size: 62509342 [Dec 20 16:45:40.195] Server {0x7f3f2f4ef7e0} DEBUG: (cache_hosting)Block No: 0 Size: 62509342 Free: 0 [Dec 20 16:45:40.195] Server {0x7f3f2f4ef7e0} DEBUG: (cache_hosting) Disk: 5: Vol Blocks: 1: Free space: 0 [Dec 20 16:45:40.195] Server {0x7f3f2f4ef7e0} DEBUG: (cache_hosting)Vol: 0 Size: 62509342 [Dec 20 16:45:40.195] Server {0x7f3f2f4ef7e0} DEBUG: (cache_hosting)Block No: 0 Size: 62509342 Free: 0 [Dec 20 16:45:40.195] Server {0x7f3f2f4ef7e0} DEBUG: (cache_hosting) Disk: 6: Vol Blocks: 1: Free space: 0 [Dec 20 16:45:40.195] Server {0x7f3f2f4ef7e0} DEBUG: (cache_hosting)Vol: 0 Size: 62509342 [Dec 20 16:45:40.195] Server {0x7f3f2f4ef7e0} DEBUG: (cache_hosting)Block No: 0 Size: 62509342 Free: 0 [Dec 20 16:45:40.195] Server {0x7f3f2f4ef7e0} DEBUG: (cache_init) Cache::open - proxy.config.cache.min_average_object_size = 65536 [Dec 20 16:45:40.198] Server {0x7f3f2f4ef7e0} DEBUG: (cache_init) allocating 78135296 directory bytes for a 512076529664 byte volume (0.015259%) [Dec 20 16:45:40.201] Server {0x7f3f2f4ef7e0} DEBUG: (cache_init) allocating 78135296 directory bytes for a 512076529664 byte volume (0.015259%) [Dec 20 16:45:40.204] Server {0x7f3f2f4ef7e0} DEBUG: (cache_init) allocating 78135296 directory bytes for a 512076529664 byte volume (0.015259%) [Dec 20 16:45:40.208] Server {0x7f3f2f4ef7e0} DEBUG: (cache_init) allocating 78135296 directory bytes for a 512076529664 byte volume (0.015259%) [Dec 20 16:45:40.213] Server {0x7f3f2f4ef7e0} DEBUG: (cache_init) allocating 78135296 directory bytes for a 512076529664 byte volume (0.015259%) [Dec 20 16:45:40.219] Server {0x7f3f2f4ef7e0} DEBUG: (cache_init) allocating 78135296 directory bytes for a 512076529664 byte volume (0.015259%) [Dec 20 16:45:40.224] Server {0x7f3f2f4ef7e0} DEBUG: (cache_init) allocating 78135296 directory bytes for a 512076529664 byte volume (0.015259%) {code} After this, it enters a stage where it’s doing a *lot* of dir_clean events: {code} [Dec 20 16:45:40.314] Server {0x7f3f26f91700} DEBUG: (dir_clean) cleaning 0x7f3edcd6f028 tag 0 boffset 0 b 0x7f3edcd6f028 p (nil) l 1 [Dec 20 16:45:40.314] Server {0x7f3f26f91700} DEBUG: (dir_clean) cleaning 0x7f3edcd6f050 tag 0 boffset 0 b 0x7f3edcd6f050 p (nil) l 1 [Dec 20 16:45:40.314] Server {0x7f3f26f91700} DEBUG: (dir_clean) cleaning 0x7f3edcd6f078 tag 0 boffset 0 b 0x7f3edcd6f078 p (nil) l 1 [Dec 20 16:45:40.314] Server {0x7f3f26f91700} DEBUG: (dir_clean) cleaning 0x7f3edcd6f0a0 tag 0 boffset 0 b 0x7f3edcd6f0a0 p (nil) l 1 [Dec 20 16:45:40.314] Server {0x7f3f26f91700} DEBUG: (dir_clean) cleaning 0x7f3edcd6f0c8 tag 0 boffset 0 b
[jira] [Commented] (TS-2447) Cache fails to load / initialize, seems stuck on directory entry cleanup
[ https://issues.apache.org/jira/browse/TS-2447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14647659#comment-14647659 ] David Carlin commented on TS-2447: -- I am seeing this on almost every box I enable debugging. Possibly related to 5.0.1 - 5.3.0 migration. traffic_server -Cclear fixes the issue. Cache fails to load / initialize, seems stuck on directory entry cleanup Key: TS-2447 URL: https://issues.apache.org/jira/browse/TS-2447 Project: Traffic Server Issue Type: Bug Components: Cache Reporter: Leif Hedstrom Assignee: Alan M. Carroll Labels: yahoo Fix For: sometime We had an issue where a number of machines would not startup properly. They get stuck on reading / initializing the cache. It initializes the caches with {code} [Dec 20 16:45:40.195] Server {0x7f3f2f4ef7e0} DEBUG: (cache_hosting) Disk: 0: Vol Blocks: 1: Free space: 0 [Dec 20 16:45:40.195] Server {0x7f3f2f4ef7e0} DEBUG: (cache_hosting)Vol: 0 Size: 62509342 [Dec 20 16:45:40.195] Server {0x7f3f2f4ef7e0} DEBUG: (cache_hosting)Block No: 0 Size: 62509342 Free: 0 [Dec 20 16:45:40.195] Server {0x7f3f2f4ef7e0} DEBUG: (cache_hosting) Disk: 1: Vol Blocks: 1: Free space: 0 [Dec 20 16:45:40.195] Server {0x7f3f2f4ef7e0} DEBUG: (cache_hosting)Vol: 0 Size: 62509342 [Dec 20 16:45:40.195] Server {0x7f3f2f4ef7e0} DEBUG: (cache_hosting)Block No: 0 Size: 62509342 Free: 0 [Dec 20 16:45:40.195] Server {0x7f3f2f4ef7e0} DEBUG: (cache_hosting) Disk: 2: Vol Blocks: 1: Free space: 0 [Dec 20 16:45:40.195] Server {0x7f3f2f4ef7e0} DEBUG: (cache_hosting)Vol: 0 Size: 62509342 [Dec 20 16:45:40.195] Server {0x7f3f2f4ef7e0} DEBUG: (cache_hosting)Block No: 0 Size: 62509342 Free: 0 [Dec 20 16:45:40.195] Server {0x7f3f2f4ef7e0} DEBUG: (cache_hosting) Disk: 3: Vol Blocks: 1: Free space: 0 [Dec 20 16:45:40.195] Server {0x7f3f2f4ef7e0} DEBUG: (cache_hosting)Vol: 0 Size: 62509342 [Dec 20 16:45:40.195] Server {0x7f3f2f4ef7e0} DEBUG: (cache_hosting)Block No: 0 Size: 62509342 Free: 0 [Dec 20 16:45:40.195] Server {0x7f3f2f4ef7e0} DEBUG: (cache_hosting) Disk: 4: Vol Blocks: 1: Free space: 0 [Dec 20 16:45:40.195] Server {0x7f3f2f4ef7e0} DEBUG: (cache_hosting)Vol: 0 Size: 62509342 [Dec 20 16:45:40.195] Server {0x7f3f2f4ef7e0} DEBUG: (cache_hosting)Block No: 0 Size: 62509342 Free: 0 [Dec 20 16:45:40.195] Server {0x7f3f2f4ef7e0} DEBUG: (cache_hosting) Disk: 5: Vol Blocks: 1: Free space: 0 [Dec 20 16:45:40.195] Server {0x7f3f2f4ef7e0} DEBUG: (cache_hosting)Vol: 0 Size: 62509342 [Dec 20 16:45:40.195] Server {0x7f3f2f4ef7e0} DEBUG: (cache_hosting)Block No: 0 Size: 62509342 Free: 0 [Dec 20 16:45:40.195] Server {0x7f3f2f4ef7e0} DEBUG: (cache_hosting) Disk: 6: Vol Blocks: 1: Free space: 0 [Dec 20 16:45:40.195] Server {0x7f3f2f4ef7e0} DEBUG: (cache_hosting)Vol: 0 Size: 62509342 [Dec 20 16:45:40.195] Server {0x7f3f2f4ef7e0} DEBUG: (cache_hosting)Block No: 0 Size: 62509342 Free: 0 [Dec 20 16:45:40.195] Server {0x7f3f2f4ef7e0} DEBUG: (cache_init) Cache::open - proxy.config.cache.min_average_object_size = 65536 [Dec 20 16:45:40.198] Server {0x7f3f2f4ef7e0} DEBUG: (cache_init) allocating 78135296 directory bytes for a 512076529664 byte volume (0.015259%) [Dec 20 16:45:40.201] Server {0x7f3f2f4ef7e0} DEBUG: (cache_init) allocating 78135296 directory bytes for a 512076529664 byte volume (0.015259%) [Dec 20 16:45:40.204] Server {0x7f3f2f4ef7e0} DEBUG: (cache_init) allocating 78135296 directory bytes for a 512076529664 byte volume (0.015259%) [Dec 20 16:45:40.208] Server {0x7f3f2f4ef7e0} DEBUG: (cache_init) allocating 78135296 directory bytes for a 512076529664 byte volume (0.015259%) [Dec 20 16:45:40.213] Server {0x7f3f2f4ef7e0} DEBUG: (cache_init) allocating 78135296 directory bytes for a 512076529664 byte volume (0.015259%) [Dec 20 16:45:40.219] Server {0x7f3f2f4ef7e0} DEBUG: (cache_init) allocating 78135296 directory bytes for a 512076529664 byte volume (0.015259%) [Dec 20 16:45:40.224] Server {0x7f3f2f4ef7e0} DEBUG: (cache_init) allocating 78135296 directory bytes for a 512076529664 byte volume (0.015259%) {code} After this, it enters a stage where it’s doing a *lot* of dir_clean events: {code} [Dec 20 16:45:40.314] Server {0x7f3f26f91700} DEBUG: (dir_clean) cleaning 0x7f3edcd6f028 tag 0 boffset 0 b 0x7f3edcd6f028 p (nil) l 1 [Dec 20 16:45:40.314] Server {0x7f3f26f91700} DEBUG: (dir_clean) cleaning 0x7f3edcd6f050 tag 0 boffset 0 b 0x7f3edcd6f050 p (nil) l 1 [Dec 20 16:45:40.314] Server {0x7f3f26f91700} DEBUG: (dir_clean) cleaning 0x7f3edcd6f078 tag 0 boffset 0 b 0x7f3edcd6f078 p (nil) l 1 [Dec 20 16:45:40.314] Server {0x7f3f26f91700} DEBUG: (dir_clean) cleaning
[jira] [Commented] (TS-3476) Add a log tag for application protocol
[ https://issues.apache.org/jira/browse/TS-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14647766#comment-14647766 ] ASF GitHub Bot commented on TS-3476: Github user asfgit closed the pull request at: https://github.com/apache/trafficserver/pull/250 Add a log tag for application protocol -- Key: TS-3476 URL: https://issues.apache.org/jira/browse/TS-3476 Project: Traffic Server Issue Type: New Feature Components: Logging, SSL Reporter: Leif Hedstrom Assignee: Eric Schwartz Fix For: 6.0.0 It seems crucial to be able to log which protocol handler was negotiated with ALPN (and perhaps NPN as long as we support it). This could simple be the string that was negotiated by the client/server in the TLS handshake. For example, with HTTP/2, it would be h2 (or h2-14 with some browsers). A suggested log tag name would be %alpn which seems clear enough to me and easy to remember :). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-3476) Add a log tag for application protocol
[ https://issues.apache.org/jira/browse/TS-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14647765#comment-14647765 ] ASF subversion and git services commented on TS-3476: - Commit 0749fd89cf64f24542c851e14e58db178442e18d in trafficserver's branch refs/heads/master from ericcarlschwartz [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=0749fd8 ] [TS-3476] Add a log tag for application protocol (add docs) This closes #250 Add a log tag for application protocol -- Key: TS-3476 URL: https://issues.apache.org/jira/browse/TS-3476 Project: Traffic Server Issue Type: New Feature Components: Logging, SSL Reporter: Leif Hedstrom Assignee: Eric Schwartz Fix For: 6.0.0 It seems crucial to be able to log which protocol handler was negotiated with ALPN (and perhaps NPN as long as we support it). This could simple be the string that was negotiated by the client/server in the TLS handshake. For example, with HTTP/2, it would be h2 (or h2-14 with some browsers). A suggested log tag name would be %alpn which seems clear enough to me and easy to remember :). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TS-3476) Add a log tag for application protocol
[ https://issues.apache.org/jira/browse/TS-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom resolved TS-3476. --- Resolution: Fixed Add a log tag for application protocol -- Key: TS-3476 URL: https://issues.apache.org/jira/browse/TS-3476 Project: Traffic Server Issue Type: New Feature Components: Logging, SSL Reporter: Leif Hedstrom Assignee: Eric Schwartz Fix For: 6.0.0 It seems crucial to be able to log which protocol handler was negotiated with ALPN (and perhaps NPN as long as we support it). This could simple be the string that was negotiated by the client/server in the TLS handshake. For example, with HTTP/2, it would be h2 (or h2-14 with some browsers). A suggested log tag name would be %alpn which seems clear enough to me and easy to remember :). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-3794) Enhance post SSL handshake read race condition for SPDY and H2 scenarios.
[ https://issues.apache.org/jira/browse/TS-3794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3794: -- Fix Version/s: (was: 6.1.0) 6.0.0 Enhance post SSL handshake read race condition for SPDY and H2 scenarios. - Key: TS-3794 URL: https://issues.apache.org/jira/browse/TS-3794 Project: Traffic Server Issue Type: Bug Components: Core Affects Versions: 5.3.0 Reporter: Sudheer Vinukonda Assignee: Sudheer Vinukonda Fix For: 6.0.0 This is a follow up for TS-3714 to extend the SSL post handshake read to SPDY and H2 scenarios. An example slow log showing very high *ua_first_read*. {code} ERROR: [8624075] Slow Request: client_ip: xx.xx.xx.xxx url: http://xx status: 200 unique id: bytes: 86 fd: 0 client state: 0 serv er state: 9 ua_begin: 0.000 ua_first_read: 42.224 ua_read_header_done: 42.224 cache_open_rea d_begin: 42.224 cache_open_read_end: 42.224 dns_lookup_begin: 42.224 dns_lookup_end: 42.224 server_connect: 42.224 server_first_read: 42.229 server_read_header_done: 42.229 server_clos e: 42.229 ua_begin_write: 42.229 ua_close: 42.229 sm_finish: 42.229 {code} Initially, I suspected that it might be caused by browser's connecting early before sending any bytes to TS. However, this seems to be happening too frequently and with unrealistically high delay between *ua_begin* and *ua_first_read*. I suspect it's caused due to the code that disables the read temporarily before calling *TXN_START* hook and re-enables it after the API call out. The read disable is done via a 0-byte *do_io_read* on the client vc, but, the problem is that a valid *mbuf* is still passed. Based on what I am seeing, it's possible this results in actually enabling the *read_vio* all the way uptil *ssl_read_from_net* for instance (if there's a race condition and there were bytes already from the client resulting in an epoll read event), which would finally disable the read since, the *ntodo* (nbytes) is 0. However, this may result in the epoll event being lost until a new i/o happens from the client. I'm trying out further experiments to confirm the theory. In most cases, the read buffer already has some bytes by the time the http session and http sm is created, which makes it just work. But, if there's a slight delay in the receiving bytes after making a connection, the epoll mechanism should read it, but, due to the way the temporary read disable is being done, the event may be lost (this is coz, ATS uses the epoll edge triggered mode). Some history on this issue - This issue has been a problem for a long time and affects both http and https requests. When this issue was first reported, our router operations team eventually closed it indicating that disabling *accept* threads resolved it ([~yzlai] also reported similar observations and conclusions). It's possible that the race condition window may be slightly reduced by disabling accept threads, but, to the overall performance and through put, accept threads are very important. I now notice that the issue still exists (regardless of whether or not accept threads are enabled/disabled) and am testing further to confirm the issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TS-3805) ASAN heap-use-after-free in ProxyClientSession::ssn_hook_get
Leif Hedstrom created TS-3805: - Summary: ASAN heap-use-after-free in ProxyClientSession::ssn_hook_get Key: TS-3805 URL: https://issues.apache.org/jira/browse/TS-3805 Project: Traffic Server Issue Type: Bug Components: Core Reporter: Leif Hedstrom {code} [E. Mgmt] log == [TrafficManager] using root directory '/opt/ats' [Jul 30 11:02:22.124] Manager {0x7f1366c0e8c0} WARNING: Be aware that access control checks for HTTP/2 connections are not active! [Jul 30 11:02:22.124] Manager {0x7f1366c0e8c0} WARNING: Be aware that access control checks for HTTP/2 connections are not active! traffic_server: using root directory '/opt/ats' = ==11239==ERROR: AddressSanitizer: heap-use-after-free on address 0x6179a170 at pc 0x52e50d bp 0x2b9d1a56a6b0 sp 0x2b9d1a56a6a8 READ of size 8 at 0x6179a170 thread T3 ([ET_NET 2]) #0 0x52e50c in APIHooks::get() const /usr/local/src/trafficserver/proxy/InkAPI.cc:1258 #1 0x66bb1e in FeatureAPIHooksTSHttpHookID, (TSHttpHookID)19::get(TSHttpHookID) const ../../proxy/InkAPIInternal.h:256 #2 0x66bb1e in ProxyClientSession::ssn_hook_get(TSHttpHookID) const ../../proxy/ProxyClientSession.h:64 #3 0x66bb1e in HttpSM::state_api_callout(int, void*) /usr/local/src/trafficserver/proxy/http/HttpSM.cc:1328 #4 0x67c586 in HttpSM::kill_this() /usr/local/src/trafficserver/proxy/http/HttpSM.cc:6552 #5 0x67f817 in HttpSM::main_handler(int, void*) /usr/local/src/trafficserver/proxy/http/HttpSM.cc:2558 #6 0xbb82d0 in Continuation::handleEvent(int, void*) ../../iocore/eventsystem/I_Continuation.h:146 #7 0xbb82d0 in read_signal_and_update /usr/local/src/trafficserver/iocore/net/UnixNetVConnection.cc:145 #8 0xbb82d0 in UnixNetVConnection::mainEvent(int, Event*) /usr/local/src/trafficserver/iocore/net/UnixNetVConnection.cc:1175 #9 0xb8d622 in Continuation::handleEvent(int, void*) ../../iocore/eventsystem/I_Continuation.h:146 #10 0xb8d622 in InactivityCop::check_inactivity(int, Event*) /usr/local/src/trafficserver/iocore/net/UnixNet.cc:102 #11 0xc336de in Continuation::handleEvent(int, void*) /usr/local/src/trafficserver/iocore/eventsystem/I_Continuation.h:146 #12 0xc336de in EThread::process_event(Event*, int) /usr/local/src/trafficserver/iocore/eventsystem/UnixEThread.cc:128 #13 0xc35947 in EThread::execute() /usr/local/src/trafficserver/iocore/eventsystem/UnixEThread.cc:207 #14 0xc322e8 in spawn_thread_internal /usr/local/src/trafficserver/iocore/eventsystem/Thread.cc:86 #15 0x2b9d1363bdf4 in start_thread (/lib64/libpthread.so.0+0x7df4) #16 0x2b9d14ea41ac in __clone (/lib64/libc.so.6+0xf61ac) 0x6179a170 is located 240 bytes inside of 688-byte region [0x6179a080,0x6179a330) freed by thread T3 ([ET_NET 2]) here: #0 0x2b9d1123a1c7 in __interceptor_free ../../.././libsanitizer/asan/asan_malloc_linux.cc:62 #1 0x62f74e in HttpVCTable::cleanup_entry(HttpVCTableEntry*) /usr/local/src/trafficserver/proxy/http/HttpSM.cc:216 #2 0x65047a in HttpSM::state_read_client_request_header(int, void*) /usr/local/src/trafficserver/proxy/http/HttpSM.cc:606 #3 0x67f4f0 in HttpSM::main_handler(int, void*) /usr/local/src/trafficserver/proxy/http/HttpSM.cc:2545 #4 0xbb82d0 in Continuation::handleEvent(int, void*) ../../iocore/eventsystem/I_Continuation.h:146 #5 0xbb82d0 in read_signal_and_update /usr/local/src/trafficserver/iocore/net/UnixNetVConnection.cc:145 #6 0xbb82d0 in UnixNetVConnection::mainEvent(int, Event*) /usr/local/src/trafficserver/iocore/net/UnixNetVConnection.cc:1175 #7 0xb8d622 in Continuation::handleEvent(int, void*) ../../iocore/eventsystem/I_Continuation.h:146 #8 0xb8d622 in InactivityCop::check_inactivity(int, Event*) /usr/local/src/trafficserver/iocore/net/UnixNet.cc:102 #9 0xc336de in Continuation::handleEvent(int, void*) /usr/local/src/trafficserver/iocore/eventsystem/I_Continuation.h:146 #10 0xc336de in EThread::process_event(Event*, int) /usr/local/src/trafficserver/iocore/eventsystem/UnixEThread.cc:128 #11 0xc35947 in EThread::execute() /usr/local/src/trafficserver/iocore/eventsystem/UnixEThread.cc:207 #12 0xc322e8 in spawn_thread_internal /usr/local/src/trafficserver/iocore/eventsystem/Thread.cc:86 #13 0x2b9d1363bdf4 in start_thread (/lib64/libpthread.so.0+0x7df4) previously allocated by thread T3 ([ET_NET 2]) here: #0 0x2b9d1123a93b in __interceptor_posix_memalign ../../.././libsanitizer/asan/asan_malloc_linux.cc:130 #1 0x2b9d12123849 in ats_memalign /usr/local/src/trafficserver/lib/ts/ink_memory.cc:100 #2 0x2b9d121241b0 in ink_freelist_new /usr/local/src/trafficserver/lib/ts/ink_queue.cc:239 #3 0x5ffe94 in ClassAllocatorHttpClientSession::alloc() ../../lib/ts/Allocator.h:120 #4 0x5ffe94 in
[jira] [Updated] (TS-3805) ASAN heap-use-after-free in ProxyClientSession::ssn_hook_get
[ https://issues.apache.org/jira/browse/TS-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3805: -- Fix Version/s: 6.0.0 ASAN heap-use-after-free in ProxyClientSession::ssn_hook_get Key: TS-3805 URL: https://issues.apache.org/jira/browse/TS-3805 Project: Traffic Server Issue Type: Bug Components: Core Reporter: Leif Hedstrom Priority: Blocker Labels: asan, crash Fix For: 6.0.0 {code} [E. Mgmt] log == [TrafficManager] using root directory '/opt/ats' [Jul 30 11:02:22.124] Manager {0x7f1366c0e8c0} WARNING: Be aware that access control checks for HTTP/2 connections are not active! [Jul 30 11:02:22.124] Manager {0x7f1366c0e8c0} WARNING: Be aware that access control checks for HTTP/2 connections are not active! traffic_server: using root directory '/opt/ats' = ==11239==ERROR: AddressSanitizer: heap-use-after-free on address 0x6179a170 at pc 0x52e50d bp 0x2b9d1a56a6b0 sp 0x2b9d1a56a6a8 READ of size 8 at 0x6179a170 thread T3 ([ET_NET 2]) #0 0x52e50c in APIHooks::get() const /usr/local/src/trafficserver/proxy/InkAPI.cc:1258 #1 0x66bb1e in FeatureAPIHooksTSHttpHookID, (TSHttpHookID)19::get(TSHttpHookID) const ../../proxy/InkAPIInternal.h:256 #2 0x66bb1e in ProxyClientSession::ssn_hook_get(TSHttpHookID) const ../../proxy/ProxyClientSession.h:64 #3 0x66bb1e in HttpSM::state_api_callout(int, void*) /usr/local/src/trafficserver/proxy/http/HttpSM.cc:1328 #4 0x67c586 in HttpSM::kill_this() /usr/local/src/trafficserver/proxy/http/HttpSM.cc:6552 #5 0x67f817 in HttpSM::main_handler(int, void*) /usr/local/src/trafficserver/proxy/http/HttpSM.cc:2558 #6 0xbb82d0 in Continuation::handleEvent(int, void*) ../../iocore/eventsystem/I_Continuation.h:146 #7 0xbb82d0 in read_signal_and_update /usr/local/src/trafficserver/iocore/net/UnixNetVConnection.cc:145 #8 0xbb82d0 in UnixNetVConnection::mainEvent(int, Event*) /usr/local/src/trafficserver/iocore/net/UnixNetVConnection.cc:1175 #9 0xb8d622 in Continuation::handleEvent(int, void*) ../../iocore/eventsystem/I_Continuation.h:146 #10 0xb8d622 in InactivityCop::check_inactivity(int, Event*) /usr/local/src/trafficserver/iocore/net/UnixNet.cc:102 #11 0xc336de in Continuation::handleEvent(int, void*) /usr/local/src/trafficserver/iocore/eventsystem/I_Continuation.h:146 #12 0xc336de in EThread::process_event(Event*, int) /usr/local/src/trafficserver/iocore/eventsystem/UnixEThread.cc:128 #13 0xc35947 in EThread::execute() /usr/local/src/trafficserver/iocore/eventsystem/UnixEThread.cc:207 #14 0xc322e8 in spawn_thread_internal /usr/local/src/trafficserver/iocore/eventsystem/Thread.cc:86 #15 0x2b9d1363bdf4 in start_thread (/lib64/libpthread.so.0+0x7df4) #16 0x2b9d14ea41ac in __clone (/lib64/libc.so.6+0xf61ac) 0x6179a170 is located 240 bytes inside of 688-byte region [0x6179a080,0x6179a330) freed by thread T3 ([ET_NET 2]) here: #0 0x2b9d1123a1c7 in __interceptor_free ../../.././libsanitizer/asan/asan_malloc_linux.cc:62 #1 0x62f74e in HttpVCTable::cleanup_entry(HttpVCTableEntry*) /usr/local/src/trafficserver/proxy/http/HttpSM.cc:216 #2 0x65047a in HttpSM::state_read_client_request_header(int, void*) /usr/local/src/trafficserver/proxy/http/HttpSM.cc:606 #3 0x67f4f0 in HttpSM::main_handler(int, void*) /usr/local/src/trafficserver/proxy/http/HttpSM.cc:2545 #4 0xbb82d0 in Continuation::handleEvent(int, void*) ../../iocore/eventsystem/I_Continuation.h:146 #5 0xbb82d0 in read_signal_and_update /usr/local/src/trafficserver/iocore/net/UnixNetVConnection.cc:145 #6 0xbb82d0 in UnixNetVConnection::mainEvent(int, Event*) /usr/local/src/trafficserver/iocore/net/UnixNetVConnection.cc:1175 #7 0xb8d622 in Continuation::handleEvent(int, void*) ../../iocore/eventsystem/I_Continuation.h:146 #8 0xb8d622 in InactivityCop::check_inactivity(int, Event*) /usr/local/src/trafficserver/iocore/net/UnixNet.cc:102 #9 0xc336de in Continuation::handleEvent(int, void*) /usr/local/src/trafficserver/iocore/eventsystem/I_Continuation.h:146 #10 0xc336de in EThread::process_event(Event*, int) /usr/local/src/trafficserver/iocore/eventsystem/UnixEThread.cc:128 #11 0xc35947 in EThread::execute() /usr/local/src/trafficserver/iocore/eventsystem/UnixEThread.cc:207 #12 0xc322e8 in spawn_thread_internal /usr/local/src/trafficserver/iocore/eventsystem/Thread.cc:86 #13 0x2b9d1363bdf4 in start_thread (/lib64/libpthread.so.0+0x7df4) previously allocated by thread T3 ([ET_NET 2]) here: #0 0x2b9d1123a93b in __interceptor_posix_memalign
[jira] [Updated] (TS-3803) CID 1313321 CID 1313322: HostDB memory issues
[ https://issues.apache.org/jira/browse/TS-3803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3803: -- Fix Version/s: (was: 6.1.0) 6.0.0 CID 1313321 CID 1313322: HostDB memory issues - Key: TS-3803 URL: https://issues.apache.org/jira/browse/TS-3803 Project: Traffic Server Issue Type: Bug Components: HostDB Reporter: Leif Hedstrom Assignee: Brian Geffon Fix For: 6.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-3646) chm log field and TCP_MEM_HIT are the same feature
[ https://issues.apache.org/jira/browse/TS-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3646: -- Component/s: (was: Logging) Docs chm log field and TCP_MEM_HIT are the same feature Key: TS-3646 URL: https://issues.apache.org/jira/browse/TS-3646 Project: Traffic Server Issue Type: Improvement Components: Docs Affects Versions: 5.3.0 Reporter: Stephane Bagneris Assignee: Jon Sime Fix For: Docs The documented chm log field feature which will differentiate between RAM_HIT and DISK_HIT as already been implemented with the addition of TCP_MEM_HIT in the crc filed. Having both feature is redundant and confusing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-3476) Add a log tag for application protocol
[ https://issues.apache.org/jira/browse/TS-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3476: -- Fix Version/s: (was: 6.1.0) 6.0.0 Add a log tag for application protocol -- Key: TS-3476 URL: https://issues.apache.org/jira/browse/TS-3476 Project: Traffic Server Issue Type: New Feature Components: Logging, SSL Reporter: Leif Hedstrom Assignee: Eric Schwartz Fix For: 6.0.0 It seems crucial to be able to log which protocol handler was negotiated with ALPN (and perhaps NPN as long as we support it). This could simple be the string that was negotiated by the client/server in the TLS handshake. For example, with HTTP/2, it would be h2 (or h2-14 with some browsers). A suggested log tag name would be %alpn which seems clear enough to me and easy to remember :). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TS-3794) Enhance post SSL handshake read race condition for SPDY and H2 scenarios.
[ https://issues.apache.org/jira/browse/TS-3794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudheer Vinukonda resolved TS-3794. --- Resolution: Fixed Enhance post SSL handshake read race condition for SPDY and H2 scenarios. - Key: TS-3794 URL: https://issues.apache.org/jira/browse/TS-3794 Project: Traffic Server Issue Type: Bug Components: Core Affects Versions: 5.3.0 Reporter: Sudheer Vinukonda Assignee: Sudheer Vinukonda Fix For: 6.1.0 This is a follow up for TS-3714 to extend the SSL post handshake read to SPDY and H2 scenarios. An example slow log showing very high *ua_first_read*. {code} ERROR: [8624075] Slow Request: client_ip: xx.xx.xx.xxx url: http://xx status: 200 unique id: bytes: 86 fd: 0 client state: 0 serv er state: 9 ua_begin: 0.000 ua_first_read: 42.224 ua_read_header_done: 42.224 cache_open_rea d_begin: 42.224 cache_open_read_end: 42.224 dns_lookup_begin: 42.224 dns_lookup_end: 42.224 server_connect: 42.224 server_first_read: 42.229 server_read_header_done: 42.229 server_clos e: 42.229 ua_begin_write: 42.229 ua_close: 42.229 sm_finish: 42.229 {code} Initially, I suspected that it might be caused by browser's connecting early before sending any bytes to TS. However, this seems to be happening too frequently and with unrealistically high delay between *ua_begin* and *ua_first_read*. I suspect it's caused due to the code that disables the read temporarily before calling *TXN_START* hook and re-enables it after the API call out. The read disable is done via a 0-byte *do_io_read* on the client vc, but, the problem is that a valid *mbuf* is still passed. Based on what I am seeing, it's possible this results in actually enabling the *read_vio* all the way uptil *ssl_read_from_net* for instance (if there's a race condition and there were bytes already from the client resulting in an epoll read event), which would finally disable the read since, the *ntodo* (nbytes) is 0. However, this may result in the epoll event being lost until a new i/o happens from the client. I'm trying out further experiments to confirm the theory. In most cases, the read buffer already has some bytes by the time the http session and http sm is created, which makes it just work. But, if there's a slight delay in the receiving bytes after making a connection, the epoll mechanism should read it, but, due to the way the temporary read disable is being done, the event may be lost (this is coz, ATS uses the epoll edge triggered mode). Some history on this issue - This issue has been a problem for a long time and affects both http and https requests. When this issue was first reported, our router operations team eventually closed it indicating that disabling *accept* threads resolved it ([~yzlai] also reported similar observations and conclusions). It's possible that the race condition window may be slightly reduced by disabling accept threads, but, to the overall performance and through put, accept threads are very important. I now notice that the issue still exists (regardless of whether or not accept threads are enabled/disabled) and am testing further to confirm the issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Build failed in Jenkins: tsqa-master #746
See https://ci.trafficserver.apache.org/job/tsqa-master/746/changes Changes: [Leif Hedstrom] TS-3766 Ignore unknown frame in debugging [Leif Hedstrom] TS-3492 Only send SETTINGS which are different than protocol defaults -- [...truncated 540 lines...] ERROR INFO 2015-07-30 20:39:07,886 - Environment prefix is /tmp/tsqa.env.ayNq02 test_default_404 (test_example.TestBootstrap) ... ok Test that traffic_line works, and verify that the values for proxy.config ... ok INFO 2015-07-30 20:39:37,772 - Starting build (1b6c9541459e058351cd39ec55dcb772): configure {'enable-spdy': None, 'enable-ccache': None, 'enable-experimental-plugins': None, 'enable-example-plugins': None, 'enable-test-tools': None, 'disable-dependency-tracking': None} INFO 2015-07-30 20:40:35,289 - Build completed (1b6c9541459e058351cd39ec55dcb772): configure {'enable-spdy': None, 'enable-ccache': None, 'enable-experimental-plugins': None, 'enable-example-plugins': None, 'enable-test-tools': None, 'disable-dependency-tracking': None} INFO 2015-07-30 20:40:35,357 - Environment prefix is /tmp/tsqa.env.mGEZmY test_spdy (test_example.TestConfigureFlags) ... ok INFO 2015-07-30 20:40:38,776 - Environment prefix is /tmp/tsqa.env._Y3hOB test_basic_proxy (test_example.TestDynamicHTTPEndpointCase) ... 127.0.0.1 - - [30/Jul/2015 20:40:42] GET /test HTTP/1.1 404 0 ok INFO 2015-07-30 20:40:42,188 - Environment prefix is /tmp/tsqa.env.iOAWiu test_logs_exist (test_example.TestLogRefCounting) ... 127.0.0.1 - - [30/Jul/2015 20:40:45] GET / HTTP/1.1 404 0 127.0.0.1 - - [30/Jul/2015 20:40:45] GET / HTTP/1.1 404 0 127.0.0.1 - - [30/Jul/2015 20:40:45] GET / HTTP/1.1 404 0 127.0.0.1 - - [30/Jul/2015 20:40:45] GET / HTTP/1.1 404 0 127.0.0.1 - - [30/Jul/2015 20:40:45] GET / HTTP/1.1 404 0 127.0.0.1 - - [30/Jul/2015 20:40:45] GET / HTTP/1.1 404 0 127.0.0.1 - - [30/Jul/2015 20:40:45] GET / HTTP/1.1 404 0 127.0.0.1 - - [30/Jul/2015 20:40:45] GET / HTTP/1.1 404 0 127.0.0.1 - - [30/Jul/2015 20:40:45] GET / HTTP/1.1 404 0 127.0.0.1 - - [30/Jul/2015 20:40:45] GET / HTTP/1.1 404 0 FAIL INFO 2015-07-30 20:40:55,670 - Environment prefix is /tmp/tsqa.env.1I2_mD test_logs_exist (test_example.TestLogs) ... FAIL SKIP: Skip the entire class INFO 2015-07-30 20:41:09,127 - Environment prefix is /tmp/tsqa.env.zaqiKT test_basic_intercept (test_example.TestServerIntercept) ... 127.0.0.1 - - [30/Jul/2015 20:41:12] GET / HTTP/1.1 200 5 127.0.0.1 - - [30/Jul/2015 20:41:12] GET / HTTP/1.1 200 5 127.0.0.1 - - [30/Jul/2015 20:41:12] GET / HTTP/1.1 200 5 127.0.0.1 - - [30/Jul/2015 20:41:12] GET / HTTP/1.1 200 5 127.0.0.1 - - [30/Jul/2015 20:41:12] GET / HTTP/1.1 200 5 127.0.0.1 - - [30/Jul/2015 20:41:12] GET / HTTP/1.1 200 5 127.0.0.1 - - [30/Jul/2015 20:41:12] GET / HTTP/1.1 200 5 127.0.0.1 - - [30/Jul/2015 20:41:12] GET / HTTP/1.1 200 5 127.0.0.1 - - [30/Jul/2015 20:41:12] GET / HTTP/1.1 200 5 127.0.0.1 - - [30/Jul/2015 20:41:12] GET / HTTP/1.1 200 5 ok INFO 2015-07-30 20:41:12,590 - Environment prefix is /tmp/tsqa.env.5ymS3w test_lookup_timeout (test_hostdb.TestHostDBFailedDNS) ... ok INFO 2015-07-30 20:41:18,014 - Environment prefix is /tmp/tsqa.env.zTSRDy Test basic fnctionality of hosts files ... ok Test that changes to hosts file get loaded within host_file.interval ... ok INFO 2015-07-30 20:41:27,496 - Environment prefix is /tmp/tsqa.env.WUlUBP SKIP: begin captured logging root: INFO: Environment prefix is /tmp/tsqa.env.WUlUBP - end captured logging - INFO 2015-07-30 20:41:28,523 - Environment prefix is /tmp/tsqa.env.wEtbY6 test_ecdsa (test_https.TestECDSA) ... ok test_intermediate_ca_ecdsa (test_https.TestECDSA) ... ok test_intermediate_ca_rsa (test_https.TestECDSA) ... ok We should be served the first match, since we aren't sending SNI headers ... ok Make sure we get the certificate we asked for if we pass in SNI headers ... ok test_rsa (test_https.TestECDSA) ... ok We should be served the first match, since we aren't sending SNI headers ... ok Make sure we get the certificate we asked for if we pass in SNI headers ... ok INFO 2015-07-30 20:41:32,056 - Environment prefix is /tmp/tsqa.env.Yi65jt test_ecdsa (test_https.TestMix) ... ok test_intermediate_ca_ecdsa (test_https.TestMix) ... ok test_intermediate_ca_rsa (test_https.TestMix) ... ok We should be served the first match, since we aren't sending SNI headers ... ok Make sure we get the certificate we asked for if we pass in SNI headers ... ok test_rsa (test_https.TestMix) ... ok We should be served the first match, since we aren't sending SNI headers ... ok Make sure we get the certificate we asked for if we pass in SNI headers ... ok INFO 2015-07-30 20:41:35,607 - Environment prefix is /tmp/tsqa.env.8Kxxzi test_ecdsa (test_https.TestRSA) ... ok test_intermediate_ca_ecdsa (test_https.TestRSA) ... ok test_intermediate_ca_rsa (test_https.TestRSA) ... ok We should be served the first match, since
Jenkins build is still unstable: tsqa-lint #378
See https://ci.trafficserver.apache.org/job/tsqa-lint/changes
Jenkins build is still unstable: tsqa-lint #377
See https://ci.trafficserver.apache.org/job/tsqa-lint/changes
[jira] [Resolved] (TS-3724) ATS doesn't properly check last_failure time for most RR methods
[ https://issues.apache.org/jira/browse/TS-3724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom resolved TS-3724. --- Resolution: Fixed Going to close this now, it's been a month. ATS doesn't properly check last_failure time for most RR methods Key: TS-3724 URL: https://issues.apache.org/jira/browse/TS-3724 Project: Traffic Server Issue Type: Bug Reporter: Thomas Jackson Assignee: Thomas Jackson Fix For: 6.0.0 Right now strict and timed RR don't check the last_failure time of the real. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-3625) Some statistics not being gathered
[ https://issues.apache.org/jira/browse/TS-3625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3625: -- Fix Version/s: (was: 6.0.0) 7.0.0 Some statistics not being gathered -- Key: TS-3625 URL: https://issues.apache.org/jira/browse/TS-3625 Project: Traffic Server Issue Type: Bug Components: Metrics Reporter: Jon Sime Assignee: Leif Hedstrom Labels: compatibility Fix For: 7.0.0 The following statistics appear to not have any data collected for them in recent versions of TS, instead only emitting a zero value. The list was put together by examining the stats_over_http output on a production instance which receives enough varied traffic that it should, in theory at least, cause most implemented statistics to go non-zero. proxy.node.cache.contents.num_docs proxy.node.cache_hit_mem_ratio_avg_10s_int_pct proxy.node.cache_hit_mem_ratio_int_pct proxy.node.current_cache_connections proxy.node.dns.lookup_avg_time_ms proxy.node.dns.lookups_per_second proxy.node.dns.total_dns_lookups proxy.node.http.transaction_frac_avg_10s.errors.aborts_int_pct proxy.node.http.transaction_frac_avg_10s.errors.connect_failed_int_pct proxy.node.http.transaction_frac_avg_10s.errors.early_hangups_int_pct proxy.node.http.transaction_frac_avg_10s.errors.empty_hangups_int_pct proxy.node.http.transaction_frac_avg_10s.errors.other_int_pct proxy.node.http.transaction_frac_avg_10s.errors.possible_aborts_int_pct proxy.node.http.transaction_frac_avg_10s.errors.pre_accept_hangups_int_pct proxy.node.http.transaction_frac_avg_10s.hit_fresh_int_pct proxy.node.http.transaction_frac_avg_10s.hit_revalidated_int_pct proxy.node.http.transaction_frac_avg_10s.miss_changed_int_pct proxy.node.http.transaction_frac_avg_10s.miss_client_no_cache_int_pct proxy.node.http.transaction_frac_avg_10s.miss_cold_int_pct proxy.node.http.transaction_frac_avg_10s.miss_not_cacheable_int_pct proxy.node.http.transaction_frac_avg_10s.other.unclassified_int_pct proxy.node.log.bytes_flush_to_disk proxy.node.log.bytes_lost_before_flush_to_disk proxy.node.log.bytes_lost_before_preproc proxy.node.log.bytes_lost_before_sent_to_network proxy.node.log.bytes_lost_before_written_to_disk proxy.node.log.bytes_received_from_network proxy.node.log.bytes_received_from_network_avg_10s proxy.node.log.bytes_sent_to_network proxy.node.log.bytes_sent_to_network_avg_10s proxy.node.log.bytes_written_to_disk proxy.node.log.event_log_access_aggr proxy.node.log.event_log_access_fail proxy.node.log.event_log_access_full proxy.node.log.event_log_access_ok proxy.node.log.event_log_access_skip proxy.node.log.event_log_error_aggr proxy.node.log.event_log_error_fail proxy.node.log.event_log_error_full proxy.node.log.event_log_error_ok proxy.node.log.event_log_error_skip proxy.node.log.num_flush_to_disk proxy.node.log.num_lost_before_flush_to_disk proxy.node.log.num_lost_before_sent_to_network proxy.node.log.num_received_from_network proxy.node.log.num_sent_to_network proxy.process.cache.directory_collision proxy.process.cache.evacuate.active proxy.process.cache.evacuate.failure proxy.process.cache.evacuate.success proxy.process.cache.frags_per_doc.1 proxy.process.cache.frags_per_doc.2 proxy.process.cache.frags_per_doc.3+ proxy.process.cache.gc_bytes_evacuated proxy.process.cache.gc_frags_evacuated proxy.process.cache.hdr_marshal_bytes proxy.process.cache.hdr_marshals proxy.process.cache.lookup.active proxy.process.cache.lookup.failure proxy.process.cache.lookup.success proxy.process.cache.percent_full proxy.process.cache.pread_count proxy.process.cache.read_busy.failure proxy.process.cache.read_busy.success proxy.process.cache.remove.active proxy.process.cache.remove.failure proxy.process.cache.remove.success proxy.process.cache.scan.active proxy.process.cache.scan.failure proxy.process.cache.scan.success proxy.process.cache.volume_0.directory_collision proxy.process.cache.volume_0.evacuate.active proxy.process.cache.volume_0.evacuate.failure proxy.process.cache.volume_0.evacuate.success proxy.process.cache.volume_0.frags_per_doc.1 proxy.process.cache.volume_0.frags_per_doc.2 proxy.process.cache.volume_0.frags_per_doc.3+ proxy.process.cache.volume_0.gc_bytes_evacuated proxy.process.cache.volume_0.gc_frags_evacuated proxy.process.cache.volume_0.hdr_marshal_bytes proxy.process.cache.volume_0.hdr_marshals proxy.process.cache.volume_0.lookup.active proxy.process.cache.volume_0.lookup.failure proxy.process.cache.volume_0.lookup.success proxy.process.cache.volume_0.pread_count proxy.process.cache.volume_0.remove.active proxy.process.cache.volume_0.remove.failure proxy.process.cache.volume_0.remove.success proxy.process.cache.volume_0.scan.active
[jira] [Resolved] (TS-3492) Only send SETTINGS which are different than protocol defaults
[ https://issues.apache.org/jira/browse/TS-3492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom resolved TS-3492. --- Resolution: Fixed I had to make an additional cast for it to work :). Only send SETTINGS which are different than protocol defaults - Key: TS-3492 URL: https://issues.apache.org/jira/browse/TS-3492 Project: Traffic Server Issue Type: Improvement Components: HTTP/2 Reporter: Leif Hedstrom Assignee: Leif Hedstrom Labels: newbie, review Fix For: 6.0.0 Attachments: settings.patch I'm thinking, why bother sending SETTINGS for values which are at the protocol defaults? Also, should we make our default configs match the protocol defaults consistently? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-3766) Ignore unknown frame in debugging
[ https://issues.apache.org/jira/browse/TS-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14648266#comment-14648266 ] ASF subversion and git services commented on TS-3766: - Commit 8a2b2413399d4fb11a69431146db8d7ebee7219f in trafficserver's branch refs/heads/master from [~masaori] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=8a2b241 ] TS-3766 Ignore unknown frame in debugging Ignore unknown frame in debugging - Key: TS-3766 URL: https://issues.apache.org/jira/browse/TS-3766 Project: Traffic Server Issue Type: Bug Components: HTTP/2 Reporter: Masaori Koshiba Assignee: Leif Hedstrom Labels: review Fix For: 6.0.0 Attachments: ts-3766.patch When ATS with {{--enable-debug}} recieve a frame which has unknown frame type in HTTP/2 stream, ATS aborts. ATS should just discard unknown frame. {noformat} FATAL: Http2ConnectionState.cc:643: failed assert `frame-header().type HTTP2_FRAME_TYPE_MAX` traffic_server: Aborted (Signal sent by tkill() 1 99)traffic_server - STACK TRACE: /opt/ats/bin/traffic_server(_Z19crash_logger_invokeiP7siginfoPv+0xc3)[0x4fc831] /lib64/libpthread.so.0(+0xf710)[0x7f00d1762710] /lib64/libc.so.6(gsignal+0x35)[0x7f00cfe79625] /lib64/libc.so.6(abort+0x175)[0x7f00cfe7ae05] /opt/ats/lib/libtsutil.so.6(_Z12ink_fatal_vaPKcP13__va_list_tag+0x0)[0x7f00d253e839] /opt/ats/lib/libtsutil.so.6(_Z9ink_fatalPKcz+0x0)[0x7f00d253e8f0] /opt/ats/lib/libtsutil.so.6(_Z10ink_pfatalPKcz+0x0)[0x7f00d253e9b5] /opt/ats/lib/libtsutil.so.6(+0x3a54a)[0x7f00d253c54a] /opt/ats/bin/traffic_server(_ZN20Http2ConnectionState18main_event_handlerEiPv+0x2f2)[0x5d8a18] /opt/ats/bin/traffic_server(_ZN12Continuation11handleEventEiPv+0x6c)[0x4ffaae] {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-3492) Only send SETTINGS which are different than protocol defaults
[ https://issues.apache.org/jira/browse/TS-3492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14648267#comment-14648267 ] ASF subversion and git services commented on TS-3492: - Commit 213a70036ccbf39d5298674bdaa70d31f4fe1fca in trafficserver's branch refs/heads/master from [~masaori] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=213a700 ] TS-3492 Only send SETTINGS which are different than protocol defaults Only send SETTINGS which are different than protocol defaults - Key: TS-3492 URL: https://issues.apache.org/jira/browse/TS-3492 Project: Traffic Server Issue Type: Improvement Components: HTTP/2 Reporter: Leif Hedstrom Assignee: Leif Hedstrom Labels: newbie, review Fix For: 6.0.0 Attachments: settings.patch I'm thinking, why bother sending SETTINGS for values which are at the protocol defaults? Also, should we make our default configs match the protocol defaults consistently? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-3806) In cmd/traffic_manager: libwccp.a(WccpMsg.o): undefined reference to symbol MD5_Final
[ https://issues.apache.org/jira/browse/TS-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14648506#comment-14648506 ] ASF GitHub Bot commented on TS-3806: GitHub user sodabrew opened a pull request: https://github.com/apache/trafficserver/pull/266 TS-3806 Resolve undefined reference to symbol MD5_Final This is similar to TS-3632. It should also be cherry-pick to the 5.3.x branch. You can merge this pull request into a Git repository by running: $ git pull https://github.com/sodabrew/trafficserver patch-1 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/trafficserver/pull/266.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 #266 commit dc2e60b105f4cd88b55349d219bd64abbbf58d52 Author: Aaron Stone aa...@serendipity.cx Date: 2015-07-30T23:43:35Z TS-3806 Resolve undefined reference to symbol MD5_Final This is similar to TS-3632 In cmd/traffic_manager: libwccp.a(WccpMsg.o): undefined reference to symbol MD5_Final - Key: TS-3806 URL: https://issues.apache.org/jira/browse/TS-3806 Project: Traffic Server Issue Type: Bug Components: Build Affects Versions: 5.3.0 Reporter: Aaron Stone Assignee: Jean Baptiste Favre Fix For: 5.3.1, 6.0.0 When building ATS 5.3.0 on Ubuntu 11.04[1,2] a linking failure occurs because of the ordering of the libraries: {code} libtool: link: c++ -g -O2 -fPIE -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -pipe -Wall -feliminate-unused-debug-symbols -fno-strict-aliasing -Wno-invalid-offsetof -mcx16 -rdynamic -Wl,-Bsymbolic-functions -fPIE -pie -Wl,-z -Wl,relro -Wl,-z -Wl,now -o .libs/traffic_manager AddConfigFilesHere.o traffic_manager.o StatProcessor.o StatType.o StatXML.o ../../mgmt/web2/libweb.a ../../mgmt/api/.libs/libmgmtapilocal.a /«PKGBUILDDIR»/lib/ts/.libs/libtsutil.so -lssl -lcrypto -L/usr/lib ../../mgmt/.libs/libmgmt_lm.a ../../proxy/hdrs/libhdrs.a ../../lib/records/librecords_lm.a ../../lib/ts/.libs/libtsutil.so ../../iocore/eventsystem/libinkevent.a ../../proxy/shared/liberror.a ../../proxy/shared/libdiagsconfig.a -lresolv -ltcl8.5 -lhwloc -lm ../../lib/wccp/libwccp.a ../../lib/tsconfig/.libs/libtsconfig.so -lcap -lpcre -lz -lcrypt -lpthread -lrt -ldl /usr/lib/x86_64-linux-gnu/libxml2.so -Wl,-rpath -Wl,/usr/lib/trafficserver /usr/bin/ld: ../../lib/wccp/libwccp.a(WccpMsg.o): undefined reference to symbol 'MD5_Final@@OPENSSL_1.0.0' /usr/bin/ld: note: 'MD5_Final@@OPENSSL_1.0.0' is defined in DSO /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libcrypto.so so try adding it to the linker command line /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libcrypto.so: could not read symbols: Invalid operation collect2: ld returned 1 exit status make[3]: *** [traffic_manager] Error 1 make[3]: Leaving directory `/«PKGBUILDDIR»/cmd/traffic_manager' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/«PKGBUILDDIR»/cmd' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/«PKGBUILDDIR»' dh_auto_build: make -j1 returned exit code 2 make: *** [binary-arch] Error 2 {code} [1] https://wiki.debian.org/ToolChain/DSOLinking#Only_link_with_needed_libraries [2] https://wiki.ubuntu.com/NattyNarwhal/ToolchainTransition -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Jenkins build is still unstable: tsqa-lint #381
See https://ci.trafficserver.apache.org/job/tsqa-lint/changes
[jira] [Created] (TS-3807) Remove legacy log splitting code and docs
Phil Sorber created TS-3807: --- Summary: Remove legacy log splitting code and docs Key: TS-3807 URL: https://issues.apache.org/jira/browse/TS-3807 Project: Traffic Server Issue Type: Improvement Reporter: Phil Sorber -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (TS-3807) Remove legacy log splitting code and docs
[ https://issues.apache.org/jira/browse/TS-3807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber reassigned TS-3807: --- Assignee: Phil Sorber Remove legacy log splitting code and docs - Key: TS-3807 URL: https://issues.apache.org/jira/browse/TS-3807 Project: Traffic Server Issue Type: Improvement Reporter: Phil Sorber Assignee: Phil Sorber -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Build failed in Jenkins: tsqa-master #748
See https://ci.trafficserver.apache.org/job/tsqa-master/748/changes Changes: [Phil Sorber] TS-3807: Remove legacy log splitting code and docs. -- [...truncated 509 lines...] Test that incrementing the cache generation acts like a cache clear ... ok INFO 2015-07-31 01:31:41,358 - Environment prefix is /tmp/tsqa.env.523NIF test_chunked_bad_close (test_chunked.TestChunked) ... INFO 2015-07-31 01:31:44,613 - sending data back to the client ok test_chunked_basic (test_chunked.TestChunked) ... INFO 2015-07-31 01:31:47,122 - Client disconnected INFO 2015-07-31 01:31:47,124 - sending data back to the client ok test_chunked_keepalive_client (test_chunked.TestChunked) ... INFO 2015-07-31 01:31:50,129 - sending data back to the client INFO 2015-07-31 01:31:53,134 - sending data back to the client INFO 2015-07-31 01:31:56,138 - sending data back to the client INFO 2015-07-31 01:31:58,541 - sending data back to the client INFO 2015-07-31 01:32:00,943 - sending data back to the client INFO 2015-07-31 01:32:04,948 - sending data back to the client ok test_chunked_keepalive_server (test_chunked.TestChunked) ... INFO 2015-07-31 01:32:08,954 - sending data back to the client INFO 2015-07-31 01:32:11,959 - sending data back to the client ok Test that the origin does in fact support keepalive ... INFO 2015-07-31 01:32:12,964 - sending data back to the client INFO 2015-07-31 01:32:15,968 - sending data back to the client INFO 2015-07-31 01:32:16,972 - sending data back to the client INFO 2015-07-31 01:32:18,973 - Client disconnected INFO 2015-07-31 01:32:19,375 - sending data back to the client INFO 2015-07-31 01:32:19,777 - sending data back to the client INFO 2015-07-31 01:32:21,779 - Client disconnected INFO 2015-07-31 01:32:23,783 - sending data back to the client ok INFO 2015-07-31 01:32:25,795 - Client disconnected INFO 2015-07-31 01:32:25,985 - Environment prefix is /tmp/tsqa.env.PlVR6a INFO 2015-07-31 01:32:27,788 - Client disconnected Verify that we get 502s from an origin which just did a bind ... ok Verify that we get 200s from origins that delayed_accept_after_connect ... ok Verify that we get 504s from origins that die_on_connect ... ok Verify that we get 502s from origins that bind + listen ... ok Verify that we get 504s from origins that return a partial_response ... FAIL Verify that we get 200s from origins that reset_after_accept ... FAIL INFO 2015-07-31 01:32:36,305 - Environment prefix is /tmp/tsqa.env.jIjOro test_log_field (test_custom_log.TestCustomLogField) ... ok INFO 2015-07-31 01:34:19,847 - Environment prefix is /tmp/tsqa.env.iUiqcr test_default_404 (test_example.TestBootstrap) ... ok Test that traffic_line works, and verify that the values for proxy.config ... ok INFO 2015-07-31 01:34:51,260 - Starting build (1b6c9541459e058351cd39ec55dcb772): configure {'enable-spdy': None, 'enable-ccache': None, 'enable-experimental-plugins': None, 'enable-example-plugins': None, 'enable-test-tools': None, 'disable-dependency-tracking': None} INFO 2015-07-31 01:36:36,684 - Build completed (1b6c9541459e058351cd39ec55dcb772): configure {'enable-spdy': None, 'enable-ccache': None, 'enable-experimental-plugins': None, 'enable-example-plugins': None, 'enable-test-tools': None, 'disable-dependency-tracking': None} INFO 2015-07-31 01:36:36,752 - Environment prefix is /tmp/tsqa.env.2Og11X test_spdy (test_example.TestConfigureFlags) ... ok INFO 2015-07-31 01:36:40,158 - Environment prefix is /tmp/tsqa.env.A3dtqY test_basic_proxy (test_example.TestDynamicHTTPEndpointCase) ... 127.0.0.1 - - [31/Jul/2015 01:36:43] GET /test HTTP/1.1 404 0 ok INFO 2015-07-31 01:36:43,798 - Environment prefix is /tmp/tsqa.env.qjfV4Z test_logs_exist (test_example.TestLogRefCounting) ... 127.0.0.1 - - [31/Jul/2015 01:36:47] GET / HTTP/1.1 404 0 127.0.0.1 - - [31/Jul/2015 01:36:47] GET / HTTP/1.1 404 0 127.0.0.1 - - [31/Jul/2015 01:36:47] GET / HTTP/1.1 404 0 127.0.0.1 - - [31/Jul/2015 01:36:47] GET / HTTP/1.1 404 0 127.0.0.1 - - [31/Jul/2015 01:36:47] GET / HTTP/1.1 404 0 127.0.0.1 - - [31/Jul/2015 01:36:47] GET / HTTP/1.1 404 0 127.0.0.1 - - [31/Jul/2015 01:36:47] GET / HTTP/1.1 404 0 127.0.0.1 - - [31/Jul/2015 01:36:47] GET / HTTP/1.1 404 0 127.0.0.1 - - [31/Jul/2015 01:36:47] GET / HTTP/1.1 404 0 127.0.0.1 - - [31/Jul/2015 01:36:47] GET / HTTP/1.1 404 0 FAIL INFO 2015-07-31 01:36:57,354 - Environment prefix is /tmp/tsqa.env.Wtm9Mh test_logs_exist (test_example.TestLogs) ... ok SKIP: Skip the entire class INFO 2015-07-31 01:37:10,823 - Environment prefix is /tmp/tsqa.env.qVRj9p test_basic_intercept (test_example.TestServerIntercept) ... 127.0.0.1 - - [31/Jul/2015 01:37:14] GET / HTTP/1.1 200 5 127.0.0.1 - - [31/Jul/2015 01:37:14] GET / HTTP/1.1 200 5 127.0.0.1 - - [31/Jul/2015 01:37:14] GET / HTTP/1.1 200 5 127.0.0.1 - - [31/Jul/2015 01:37:14] GET / HTTP/1.1 200 5 127.0.0.1 - - [31/Jul/2015 01:37:14] GET / HTTP/1.1 200 5 127.0.0.1 - - [31/Jul/2015 01:37:14] GET / HTTP/1.1 200 5
[jira] [Resolved] (TS-3749) Error log isn't recorded
[ https://issues.apache.org/jira/browse/TS-3749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber resolved TS-3749. - Resolution: Fixed Error log isn't recorded Key: TS-3749 URL: https://issues.apache.org/jira/browse/TS-3749 Project: Traffic Server Issue Type: Bug Components: Logging Reporter: Ryo Okubo Assignee: Crystal Qian Priority: Blocker Fix For: 6.0.0 error.log has not been recorded after TS-1985. Enabling error logging and specifying a format of error.log depended on pre-defined log format but this logic was eliminated on the issue. Error logging works fine when I tried to revert [5c2b032fb9f8f05ae7be1794a3103140ffe7d07e|https://github.com/apache/trafficserver/commit/5c2b032fb9f8f05ae7be1794a3103140ffe7d07e]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-3632) libwccp.a(WccpMsg.o): undefined reference to symbol MD5_Final
[ https://issues.apache.org/jira/browse/TS-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14648427#comment-14648427 ] ASF GitHub Bot commented on TS-3632: Github user sodabrew commented on the pull request: https://github.com/apache/trafficserver/pull/203#issuecomment-126513201 As noted by @igalic in https://issues.apache.org/jira/browse/TS-3632?focusedCommentId=14648395 I am still able to reproduce a similar problem when building a 5.3.1 package on Ubuntu Trusty - but this time with traffic_manager instead of traffic_wccp. I solved it as below: ``` diff --- traffic_manager/Makefile.am.org 2015-07-30 22:46:21.074881421 + +++ traffic_manager/Makefile.am 2015-07-30 22:44:41.535809481 + @@ -67,5 +67,6 @@ if BUILD_WCCP traffic_manager_LDADD += \ $(top_builddir)/lib/wccp/libwccp.a \ - $(top_builddir)/lib/tsconfig/libtsconfig.la + $(top_builddir)/lib/tsconfig/libtsconfig.la \ + @OPENSSL_LIBS@ endif ``` I can submit this as a new PR if it looks like the right approach. libwccp.a(WccpMsg.o): undefined reference to symbol MD5_Final - Key: TS-3632 URL: https://issues.apache.org/jira/browse/TS-3632 Project: Traffic Server Issue Type: Bug Components: Build Affects Versions: 5.3.0 Reporter: Igor Galić Assignee: Jean Baptiste Favre Fix For: 5.3.1, 6.0.0 When building ATS 5.3.0 on Ubuntu 11.04[1,2] a linking failure occurs because of the ordering of the libraries: {code} libtool: link: c++ -g -O2 -fPIE -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -pipe -Wall -feliminate-unused-debug-symbols -fno-strict-aliasing -Wno-invalid-offsetof -mcx16 -rdynamic -Wl,-Bsymbolic-functions -fPIE -pie -Wl,-z -Wl,relro -Wl,-z -Wl,now -o .libs/traffic_manager AddConfigFilesHere.o traffic_manager.o StatProcessor.o StatType.o StatXML.o ../../mgmt/web2/libweb.a ../../mgmt/api/.libs/libmgmtapilocal.a /«PKGBUILDDIR»/lib/ts/.libs/libtsutil.so -lssl -lcrypto -L/usr/lib ../../mgmt/.libs/libmgmt_lm.a ../../proxy/hdrs/libhdrs.a ../../lib/records/librecords_lm.a ../../lib/ts/.libs/libtsutil.so ../../iocore/eventsystem/libinkevent.a ../../proxy/shared/liberror.a ../../proxy/shared/libdiagsconfig.a -lresolv -ltcl8.5 -lhwloc -lm ../../lib/wccp/libwccp.a ../../lib/tsconfig/.libs/libtsconfig.so -lcap -lpcre -lz -lcrypt -lpthread -lrt -ldl /usr/lib/x86_64-linux-gnu/libxml2.so -Wl,-rpath -Wl,/usr/lib/trafficserver /usr/bin/ld: ../../lib/wccp/libwccp.a(WccpMsg.o): undefined reference to symbol 'MD5_Final@@OPENSSL_1.0.0' /usr/bin/ld: note: 'MD5_Final@@OPENSSL_1.0.0' is defined in DSO /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libcrypto.so so try adding it to the linker command line /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libcrypto.so: could not read symbols: Invalid operation collect2: ld returned 1 exit status make[3]: *** [traffic_manager] Error 1 make[3]: Leaving directory `/«PKGBUILDDIR»/cmd/traffic_manager' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/«PKGBUILDDIR»/cmd' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/«PKGBUILDDIR»' dh_auto_build: make -j1 returned exit code 2 make: *** [binary-arch] Error 2 {code} [1] https://wiki.debian.org/ToolChain/DSOLinking#Only_link_with_needed_libraries [2] https://wiki.ubuntu.com/NattyNarwhal/ToolchainTransition -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TS-3806) In cmd/traffic_manager: libwccp.a(WccpMsg.o): undefined reference to symbol MD5_Final
Aaron Stone created TS-3806: --- Summary: In cmd/traffic_manager: libwccp.a(WccpMsg.o): undefined reference to symbol MD5_Final Key: TS-3806 URL: https://issues.apache.org/jira/browse/TS-3806 Project: Traffic Server Issue Type: Bug Components: Build Affects Versions: 5.3.0 Reporter: Aaron Stone Assignee: Jean Baptiste Favre Fix For: 5.3.1, 6.0.0 When building ATS 5.3.0 on Ubuntu 11.04[1,2] a linking failure occurs because of the ordering of the libraries: {code} libtool: link: c++ -g -O2 -fPIE -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -pipe -Wall -feliminate-unused-debug-symbols -fno-strict-aliasing -Wno-invalid-offsetof -mcx16 -rdynamic -Wl,-Bsymbolic-functions -fPIE -pie -Wl,-z -Wl,relro -Wl,-z -Wl,now -o .libs/traffic_manager AddConfigFilesHere.o traffic_manager.o StatProcessor.o StatType.o StatXML.o ../../mgmt/web2/libweb.a ../../mgmt/api/.libs/libmgmtapilocal.a /«PKGBUILDDIR»/lib/ts/.libs/libtsutil.so -lssl -lcrypto -L/usr/lib ../../mgmt/.libs/libmgmt_lm.a ../../proxy/hdrs/libhdrs.a ../../lib/records/librecords_lm.a ../../lib/ts/.libs/libtsutil.so ../../iocore/eventsystem/libinkevent.a ../../proxy/shared/liberror.a ../../proxy/shared/libdiagsconfig.a -lresolv -ltcl8.5 -lhwloc -lm ../../lib/wccp/libwccp.a ../../lib/tsconfig/.libs/libtsconfig.so -lcap -lpcre -lz -lcrypt -lpthread -lrt -ldl /usr/lib/x86_64-linux-gnu/libxml2.so -Wl,-rpath -Wl,/usr/lib/trafficserver /usr/bin/ld: ../../lib/wccp/libwccp.a(WccpMsg.o): undefined reference to symbol 'MD5_Final@@OPENSSL_1.0.0' /usr/bin/ld: note: 'MD5_Final@@OPENSSL_1.0.0' is defined in DSO /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libcrypto.so so try adding it to the linker command line /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libcrypto.so: could not read symbols: Invalid operation collect2: ld returned 1 exit status make[3]: *** [traffic_manager] Error 1 make[3]: Leaving directory `/«PKGBUILDDIR»/cmd/traffic_manager' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/«PKGBUILDDIR»/cmd' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/«PKGBUILDDIR»' dh_auto_build: make -j1 returned exit code 2 make: *** [binary-arch] Error 2 {code} [1] https://wiki.debian.org/ToolChain/DSOLinking#Only_link_with_needed_libraries [2] https://wiki.ubuntu.com/NattyNarwhal/ToolchainTransition -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Jenkins build is still unstable: tsqa-lint #380
See https://ci.trafficserver.apache.org/job/tsqa-lint/changes
[jira] [Commented] (TS-3749) Error log isn't recorded
[ https://issues.apache.org/jira/browse/TS-3749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14648417#comment-14648417 ] Leif Hedstrom commented on TS-3749: --- Almost :) With a few modifications, it works again: {code} diff --git a/proxy/logging/LogConfig.cc b/proxy/logging/LogConfig.cc index aa5d160..ee4273d 100644 --- a/proxy/logging/LogConfig.cc +++ b/proxy/logging/LogConfig.cc @@ -446,7 +446,24 @@ LogConfig::init(LogConfig *prev_config) } // -- - Log::error_log = NULL; + // Construct a new error log object candidate. + if (Log::error_logging_enabled()) { +LogFormat *fmt; + +Debug(log, creating predefined error log object); + +fmt = MakeTextLogFormat(error); +this-global_format_list.add(fmt, false); +errlog = new LogObject(fmt, logfile_dir, error.log, LOG_FILE_ASCII, NULL, (Log::RollingEnabledValues)rolling_enabled, + collation_preproc_threads, rolling_interval_sec, rolling_offset_hr, rolling_size_mb); +errlog-set_fmt_timestamps(); +if (log_object_manager.manage_object(errlog) != LogObjectManager::NO_FILENAME_CONFLICTS) { + delete errlog; + errlog = NULL; +} + } else { +Log::error_log = NULL; + } if (prev_config) { // Transfer objects from previous configuration. {code} Error log isn't recorded Key: TS-3749 URL: https://issues.apache.org/jira/browse/TS-3749 Project: Traffic Server Issue Type: Bug Components: Logging Reporter: Ryo Okubo Assignee: Crystal Qian Priority: Blocker Fix For: 6.0.0 error.log has not been recorded after TS-1985. Enabling error logging and specifying a format of error.log depended on pre-defined log format but this logic was eliminated on the issue. Error logging works fine when I tried to revert [5c2b032fb9f8f05ae7be1794a3103140ffe7d07e|https://github.com/apache/trafficserver/commit/5c2b032fb9f8f05ae7be1794a3103140ffe7d07e]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-3806) In cmd/traffic_manager: libwccp.a(WccpMsg.o): undefined reference to symbol MD5_Final
[ https://issues.apache.org/jira/browse/TS-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14648502#comment-14648502 ] Aaron Stone commented on TS-3806: - I am still able to reproduce this error when building Traffic Server 5.3.1 on Ubuntu Trusty. I found the following change resolved the problem: {code} --- cmd/traffic_manager/Makefile.am.org 2015-07-30 22:46:21.074881421 + +++ cmd/traffic_manager/Makefile.am 2015-07-30 22:44:41.535809481 + @@ -67,5 +67,6 @@ if BUILD_WCCP traffic_manager_LDADD += \ $(top_builddir)/lib/wccp/libwccp.a \ - $(top_builddir)/lib/tsconfig/libtsconfig.la + $(top_builddir)/lib/tsconfig/libtsconfig.la \ + @OPENSSL_LIBS@ endif {code} In cmd/traffic_manager: libwccp.a(WccpMsg.o): undefined reference to symbol MD5_Final - Key: TS-3806 URL: https://issues.apache.org/jira/browse/TS-3806 Project: Traffic Server Issue Type: Bug Components: Build Affects Versions: 5.3.0 Reporter: Aaron Stone Assignee: Jean Baptiste Favre Fix For: 5.3.1, 6.0.0 When building ATS 5.3.0 on Ubuntu 11.04[1,2] a linking failure occurs because of the ordering of the libraries: {code} libtool: link: c++ -g -O2 -fPIE -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -pipe -Wall -feliminate-unused-debug-symbols -fno-strict-aliasing -Wno-invalid-offsetof -mcx16 -rdynamic -Wl,-Bsymbolic-functions -fPIE -pie -Wl,-z -Wl,relro -Wl,-z -Wl,now -o .libs/traffic_manager AddConfigFilesHere.o traffic_manager.o StatProcessor.o StatType.o StatXML.o ../../mgmt/web2/libweb.a ../../mgmt/api/.libs/libmgmtapilocal.a /«PKGBUILDDIR»/lib/ts/.libs/libtsutil.so -lssl -lcrypto -L/usr/lib ../../mgmt/.libs/libmgmt_lm.a ../../proxy/hdrs/libhdrs.a ../../lib/records/librecords_lm.a ../../lib/ts/.libs/libtsutil.so ../../iocore/eventsystem/libinkevent.a ../../proxy/shared/liberror.a ../../proxy/shared/libdiagsconfig.a -lresolv -ltcl8.5 -lhwloc -lm ../../lib/wccp/libwccp.a ../../lib/tsconfig/.libs/libtsconfig.so -lcap -lpcre -lz -lcrypt -lpthread -lrt -ldl /usr/lib/x86_64-linux-gnu/libxml2.so -Wl,-rpath -Wl,/usr/lib/trafficserver /usr/bin/ld: ../../lib/wccp/libwccp.a(WccpMsg.o): undefined reference to symbol 'MD5_Final@@OPENSSL_1.0.0' /usr/bin/ld: note: 'MD5_Final@@OPENSSL_1.0.0' is defined in DSO /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libcrypto.so so try adding it to the linker command line /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libcrypto.so: could not read symbols: Invalid operation collect2: ld returned 1 exit status make[3]: *** [traffic_manager] Error 1 make[3]: Leaving directory `/«PKGBUILDDIR»/cmd/traffic_manager' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/«PKGBUILDDIR»/cmd' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/«PKGBUILDDIR»' dh_auto_build: make -j1 returned exit code 2 make: *** [binary-arch] Error 2 {code} [1] https://wiki.debian.org/ToolChain/DSOLinking#Only_link_with_needed_libraries [2] https://wiki.ubuntu.com/NattyNarwhal/ToolchainTransition -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Jenkins build is still unstable: tsqa-lint #379
See https://ci.trafficserver.apache.org/job/tsqa-lint/changes
[jira] [Commented] (TS-3632) libwccp.a(WccpMsg.o): undefined reference to symbol MD5_Final
[ https://issues.apache.org/jira/browse/TS-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14648430#comment-14648430 ] ASF GitHub Bot commented on TS-3632: Github user zwoop commented on the pull request: https://github.com/apache/trafficserver/pull/203#issuecomment-126513769 Also, since we closed TS-3632, please open a new Jira for this as well. libwccp.a(WccpMsg.o): undefined reference to symbol MD5_Final - Key: TS-3632 URL: https://issues.apache.org/jira/browse/TS-3632 Project: Traffic Server Issue Type: Bug Components: Build Affects Versions: 5.3.0 Reporter: Igor Galić Assignee: Jean Baptiste Favre Fix For: 5.3.1, 6.0.0 When building ATS 5.3.0 on Ubuntu 11.04[1,2] a linking failure occurs because of the ordering of the libraries: {code} libtool: link: c++ -g -O2 -fPIE -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -pipe -Wall -feliminate-unused-debug-symbols -fno-strict-aliasing -Wno-invalid-offsetof -mcx16 -rdynamic -Wl,-Bsymbolic-functions -fPIE -pie -Wl,-z -Wl,relro -Wl,-z -Wl,now -o .libs/traffic_manager AddConfigFilesHere.o traffic_manager.o StatProcessor.o StatType.o StatXML.o ../../mgmt/web2/libweb.a ../../mgmt/api/.libs/libmgmtapilocal.a /«PKGBUILDDIR»/lib/ts/.libs/libtsutil.so -lssl -lcrypto -L/usr/lib ../../mgmt/.libs/libmgmt_lm.a ../../proxy/hdrs/libhdrs.a ../../lib/records/librecords_lm.a ../../lib/ts/.libs/libtsutil.so ../../iocore/eventsystem/libinkevent.a ../../proxy/shared/liberror.a ../../proxy/shared/libdiagsconfig.a -lresolv -ltcl8.5 -lhwloc -lm ../../lib/wccp/libwccp.a ../../lib/tsconfig/.libs/libtsconfig.so -lcap -lpcre -lz -lcrypt -lpthread -lrt -ldl /usr/lib/x86_64-linux-gnu/libxml2.so -Wl,-rpath -Wl,/usr/lib/trafficserver /usr/bin/ld: ../../lib/wccp/libwccp.a(WccpMsg.o): undefined reference to symbol 'MD5_Final@@OPENSSL_1.0.0' /usr/bin/ld: note: 'MD5_Final@@OPENSSL_1.0.0' is defined in DSO /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libcrypto.so so try adding it to the linker command line /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libcrypto.so: could not read symbols: Invalid operation collect2: ld returned 1 exit status make[3]: *** [traffic_manager] Error 1 make[3]: Leaving directory `/«PKGBUILDDIR»/cmd/traffic_manager' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/«PKGBUILDDIR»/cmd' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/«PKGBUILDDIR»' dh_auto_build: make -j1 returned exit code 2 make: *** [binary-arch] Error 2 {code} [1] https://wiki.debian.org/ToolChain/DSOLinking#Only_link_with_needed_libraries [2] https://wiki.ubuntu.com/NattyNarwhal/ToolchainTransition -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-3141) Port number in host header breaks ATS remap
[ https://issues.apache.org/jira/browse/TS-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14648473#comment-14648473 ] Brian Geffon commented on TS-3141: -- Let's keep this ticket open for a bit and just wait and see if anyone else chimes in... Port number in host header breaks ATS remap --- Key: TS-3141 URL: https://issues.apache.org/jira/browse/TS-3141 Project: Traffic Server Issue Type: Bug Reporter: Thomas Jackson Assignee: Brian Geffon Labels: newbie Fix For: 6.1.0 If someone adds port 80 (lets say) to the host header of a request, ATS remap fails {code} [thjackso@thjackso-ld ~]$ curl -I -4k -H 'Host: www.ogre.com:80' https://www.ogre.com HTTP/1.1 404 Not Found on Accelerator Date: Thu, 16 Oct 2014 21:14:02 GMT Connection: keep-alive Via: https/1.1 cosmo.ogre.com (ApacheTrafficServer/5.2.0 [c s f ]) Server: ATS/5.2.0 Cache-Control: no-store Content-Type: text/html Content-Language: en Content-Length: 297 {code} Although if you set the port to 443 it seems to work fine {code} [thjackso@thjackso-ld ~]$ curl -I -4k -H 'Host: www.ogre.com:443' https://www.ogre.com HTTP/1.1 200 OK Date: Thu, 16 Oct 2014 21:15:09 GMT Server: ATS/5.2.0 X-Drupal-Cache: MISS Expires: Sun, 19 Nov 1978 05:00:00 GMT Last-Modified: Thu, 16 Oct 2014 21:15:09 + Cache-Control: public, max-age=300 Content-Language: en X-Generator: Drupal 7 (http://drupal.org) Vary: Cookie Content-Type: text/html; charset=utf-8 Age: 0 Connection: keep-alive Via: http/1.1 cosmo.ogre.com (ApacheTrafficServer/5.2.0 [cMsSf ]) {code} In addition I can send a host header with 443 on the http port and I'll get similar behavior. This leads me to believe that if you set the port to anything that isn't the default for the schema you are connecting on it fails remap (url looks like https:/// in the logs). I would think that the port in the host header would be completely ignored right? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-3806) In cmd/traffic_manager: libwccp.a(WccpMsg.o): undefined reference to symbol MD5_Final
[ https://issues.apache.org/jira/browse/TS-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14648510#comment-14648510 ] ASF GitHub Bot commented on TS-3806: Github user sodabrew commented on the pull request: https://github.com/apache/trafficserver/pull/266#issuecomment-126522684 See also #203 In cmd/traffic_manager: libwccp.a(WccpMsg.o): undefined reference to symbol MD5_Final - Key: TS-3806 URL: https://issues.apache.org/jira/browse/TS-3806 Project: Traffic Server Issue Type: Bug Components: Build Affects Versions: 5.3.1 Reporter: Aaron Stone Assignee: Jean Baptiste Favre When building ATS 5.3.0 on Ubuntu 11.04[1,2] a linking failure occurs because of the ordering of the libraries: {code} libtool: link: c++ -g -O2 -fPIE -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -pipe -Wall -feliminate-unused-debug-symbols -fno-strict-aliasing -Wno-invalid-offsetof -mcx16 -rdynamic -Wl,-Bsymbolic-functions -fPIE -pie -Wl,-z -Wl,relro -Wl,-z -Wl,now -o .libs/traffic_manager AddConfigFilesHere.o traffic_manager.o StatProcessor.o StatType.o StatXML.o ../../mgmt/web2/libweb.a ../../mgmt/api/.libs/libmgmtapilocal.a /«PKGBUILDDIR»/lib/ts/.libs/libtsutil.so -lssl -lcrypto -L/usr/lib ../../mgmt/.libs/libmgmt_lm.a ../../proxy/hdrs/libhdrs.a ../../lib/records/librecords_lm.a ../../lib/ts/.libs/libtsutil.so ../../iocore/eventsystem/libinkevent.a ../../proxy/shared/liberror.a ../../proxy/shared/libdiagsconfig.a -lresolv -ltcl8.5 -lhwloc -lm ../../lib/wccp/libwccp.a ../../lib/tsconfig/.libs/libtsconfig.so -lcap -lpcre -lz -lcrypt -lpthread -lrt -ldl /usr/lib/x86_64-linux-gnu/libxml2.so -Wl,-rpath -Wl,/usr/lib/trafficserver /usr/bin/ld: ../../lib/wccp/libwccp.a(WccpMsg.o): undefined reference to symbol 'MD5_Final@@OPENSSL_1.0.0' /usr/bin/ld: note: 'MD5_Final@@OPENSSL_1.0.0' is defined in DSO /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libcrypto.so so try adding it to the linker command line /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libcrypto.so: could not read symbols: Invalid operation collect2: ld returned 1 exit status make[3]: *** [traffic_manager] Error 1 make[3]: Leaving directory `/«PKGBUILDDIR»/cmd/traffic_manager' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/«PKGBUILDDIR»/cmd' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/«PKGBUILDDIR»' dh_auto_build: make -j1 returned exit code 2 make: *** [binary-arch] Error 2 {code} [1] https://wiki.debian.org/ToolChain/DSOLinking#Only_link_with_needed_libraries [2] https://wiki.ubuntu.com/NattyNarwhal/ToolchainTransition -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-3806) In cmd/traffic_manager: libwccp.a(WccpMsg.o): undefined reference to symbol MD5_Final
[ https://issues.apache.org/jira/browse/TS-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14648508#comment-14648508 ] Aaron Stone commented on TS-3806: - Oh cool, JIRA connected to the GitHub PR. In cmd/traffic_manager: libwccp.a(WccpMsg.o): undefined reference to symbol MD5_Final - Key: TS-3806 URL: https://issues.apache.org/jira/browse/TS-3806 Project: Traffic Server Issue Type: Bug Components: Build Affects Versions: 5.3.1 Reporter: Aaron Stone Assignee: Jean Baptiste Favre When building ATS 5.3.0 on Ubuntu 11.04[1,2] a linking failure occurs because of the ordering of the libraries: {code} libtool: link: c++ -g -O2 -fPIE -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -pipe -Wall -feliminate-unused-debug-symbols -fno-strict-aliasing -Wno-invalid-offsetof -mcx16 -rdynamic -Wl,-Bsymbolic-functions -fPIE -pie -Wl,-z -Wl,relro -Wl,-z -Wl,now -o .libs/traffic_manager AddConfigFilesHere.o traffic_manager.o StatProcessor.o StatType.o StatXML.o ../../mgmt/web2/libweb.a ../../mgmt/api/.libs/libmgmtapilocal.a /«PKGBUILDDIR»/lib/ts/.libs/libtsutil.so -lssl -lcrypto -L/usr/lib ../../mgmt/.libs/libmgmt_lm.a ../../proxy/hdrs/libhdrs.a ../../lib/records/librecords_lm.a ../../lib/ts/.libs/libtsutil.so ../../iocore/eventsystem/libinkevent.a ../../proxy/shared/liberror.a ../../proxy/shared/libdiagsconfig.a -lresolv -ltcl8.5 -lhwloc -lm ../../lib/wccp/libwccp.a ../../lib/tsconfig/.libs/libtsconfig.so -lcap -lpcre -lz -lcrypt -lpthread -lrt -ldl /usr/lib/x86_64-linux-gnu/libxml2.so -Wl,-rpath -Wl,/usr/lib/trafficserver /usr/bin/ld: ../../lib/wccp/libwccp.a(WccpMsg.o): undefined reference to symbol 'MD5_Final@@OPENSSL_1.0.0' /usr/bin/ld: note: 'MD5_Final@@OPENSSL_1.0.0' is defined in DSO /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libcrypto.so so try adding it to the linker command line /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libcrypto.so: could not read symbols: Invalid operation collect2: ld returned 1 exit status make[3]: *** [traffic_manager] Error 1 make[3]: Leaving directory `/«PKGBUILDDIR»/cmd/traffic_manager' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/«PKGBUILDDIR»/cmd' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/«PKGBUILDDIR»' dh_auto_build: make -j1 returned exit code 2 make: *** [binary-arch] Error 2 {code} [1] https://wiki.debian.org/ToolChain/DSOLinking#Only_link_with_needed_libraries [2] https://wiki.ubuntu.com/NattyNarwhal/ToolchainTransition -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-3806) In cmd/traffic_manager: libwccp.a(WccpMsg.o): undefined reference to symbol MD5_Final
[ https://issues.apache.org/jira/browse/TS-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3806: -- Fix Version/s: 6.0.0 In cmd/traffic_manager: libwccp.a(WccpMsg.o): undefined reference to symbol MD5_Final - Key: TS-3806 URL: https://issues.apache.org/jira/browse/TS-3806 Project: Traffic Server Issue Type: Bug Components: Build Affects Versions: 5.3.1 Reporter: Aaron Stone Assignee: Jean Baptiste Favre Fix For: 6.0.0 When building ATS 5.3.0 on Ubuntu 11.04[1,2] a linking failure occurs because of the ordering of the libraries: {code} libtool: link: c++ -g -O2 -fPIE -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -pipe -Wall -feliminate-unused-debug-symbols -fno-strict-aliasing -Wno-invalid-offsetof -mcx16 -rdynamic -Wl,-Bsymbolic-functions -fPIE -pie -Wl,-z -Wl,relro -Wl,-z -Wl,now -o .libs/traffic_manager AddConfigFilesHere.o traffic_manager.o StatProcessor.o StatType.o StatXML.o ../../mgmt/web2/libweb.a ../../mgmt/api/.libs/libmgmtapilocal.a /«PKGBUILDDIR»/lib/ts/.libs/libtsutil.so -lssl -lcrypto -L/usr/lib ../../mgmt/.libs/libmgmt_lm.a ../../proxy/hdrs/libhdrs.a ../../lib/records/librecords_lm.a ../../lib/ts/.libs/libtsutil.so ../../iocore/eventsystem/libinkevent.a ../../proxy/shared/liberror.a ../../proxy/shared/libdiagsconfig.a -lresolv -ltcl8.5 -lhwloc -lm ../../lib/wccp/libwccp.a ../../lib/tsconfig/.libs/libtsconfig.so -lcap -lpcre -lz -lcrypt -lpthread -lrt -ldl /usr/lib/x86_64-linux-gnu/libxml2.so -Wl,-rpath -Wl,/usr/lib/trafficserver /usr/bin/ld: ../../lib/wccp/libwccp.a(WccpMsg.o): undefined reference to symbol 'MD5_Final@@OPENSSL_1.0.0' /usr/bin/ld: note: 'MD5_Final@@OPENSSL_1.0.0' is defined in DSO /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libcrypto.so so try adding it to the linker command line /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libcrypto.so: could not read symbols: Invalid operation collect2: ld returned 1 exit status make[3]: *** [traffic_manager] Error 1 make[3]: Leaving directory `/«PKGBUILDDIR»/cmd/traffic_manager' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/«PKGBUILDDIR»/cmd' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/«PKGBUILDDIR»' dh_auto_build: make -j1 returned exit code 2 make: *** [binary-arch] Error 2 {code} [1] https://wiki.debian.org/ToolChain/DSOLinking#Only_link_with_needed_libraries [2] https://wiki.ubuntu.com/NattyNarwhal/ToolchainTransition -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Build failed in Jenkins: tsqa-master #747
See https://ci.trafficserver.apache.org/job/tsqa-master/747/changes Changes: [Phil Sorber] TS-3749: Re-enable error log. -- [...truncated 504 lines...] Test that incrementing the cache generation acts like a cache clear ... ok INFO 2015-07-31 01:15:29,663 - Environment prefix is /tmp/tsqa.env.6wOEza test_chunked_bad_close (test_chunked.TestChunked) ... INFO 2015-07-31 01:15:32,895 - sending data back to the client ok test_chunked_basic (test_chunked.TestChunked) ... INFO 2015-07-31 01:15:35,400 - Client disconnected INFO 2015-07-31 01:15:35,402 - sending data back to the client ok test_chunked_keepalive_client (test_chunked.TestChunked) ... INFO 2015-07-31 01:15:38,407 - sending data back to the client INFO 2015-07-31 01:15:41,411 - sending data back to the client INFO 2015-07-31 01:15:44,414 - sending data back to the client INFO 2015-07-31 01:15:46,818 - sending data back to the client INFO 2015-07-31 01:15:49,221 - sending data back to the client INFO 2015-07-31 01:15:53,226 - sending data back to the client ok test_chunked_keepalive_server (test_chunked.TestChunked) ... INFO 2015-07-31 01:15:57,230 - sending data back to the client INFO 2015-07-31 01:16:00,234 - sending data back to the client ok Test that the origin does in fact support keepalive ... INFO 2015-07-31 01:16:01,238 - sending data back to the client INFO 2015-07-31 01:16:04,243 - sending data back to the client INFO 2015-07-31 01:16:05,246 - sending data back to the client INFO 2015-07-31 01:16:07,247 - Client disconnected INFO 2015-07-31 01:16:07,649 - sending data back to the client INFO 2015-07-31 01:16:08,051 - sending data back to the client INFO 2015-07-31 01:16:10,052 - Client disconnected INFO 2015-07-31 01:16:12,056 - sending data back to the client ok INFO 2015-07-31 01:16:14,066 - Client disconnected INFO 2015-07-31 01:16:14,262 - Environment prefix is /tmp/tsqa.env.dKEKYX INFO 2015-07-31 01:16:16,060 - Client disconnected Verify that we get 502s from an origin which just did a bind ... ok Verify that we get 200s from origins that delayed_accept_after_connect ... ok Verify that we get 504s from origins that die_on_connect ... ok Verify that we get 502s from origins that bind + listen ... ok Verify that we get 504s from origins that return a partial_response ... FAIL Verify that we get 200s from origins that reset_after_accept ... FAIL INFO 2015-07-31 01:16:26,541 - Environment prefix is /tmp/tsqa.env.Sa6eyw test_log_field (test_custom_log.TestCustomLogField) ... ok INFO 2015-07-31 01:18:10,072 - Environment prefix is /tmp/tsqa.env.pZ07mE test_default_404 (test_example.TestBootstrap) ... ok Test that traffic_line works, and verify that the values for proxy.config ... ok INFO 2015-07-31 01:18:39,849 - Starting build (1b6c9541459e058351cd39ec55dcb772): configure {'enable-spdy': None, 'enable-ccache': None, 'enable-experimental-plugins': None, 'enable-example-plugins': None, 'enable-test-tools': None, 'disable-dependency-tracking': None} INFO 2015-07-31 01:19:31,964 - Build completed (1b6c9541459e058351cd39ec55dcb772): configure {'enable-spdy': None, 'enable-ccache': None, 'enable-experimental-plugins': None, 'enable-example-plugins': None, 'enable-test-tools': None, 'disable-dependency-tracking': None} INFO 2015-07-31 01:19:32,030 - Environment prefix is /tmp/tsqa.env.lUUSlA test_spdy (test_example.TestConfigureFlags) ... ok INFO 2015-07-31 01:19:35,437 - Environment prefix is /tmp/tsqa.env.0Upb5L test_basic_proxy (test_example.TestDynamicHTTPEndpointCase) ... 127.0.0.1 - - [31/Jul/2015 01:19:38] GET /test HTTP/1.1 404 0 ok INFO 2015-07-31 01:19:38,855 - Environment prefix is /tmp/tsqa.env.oPzIou test_logs_exist (test_example.TestLogRefCounting) ... 127.0.0.1 - - [31/Jul/2015 01:19:42] GET / HTTP/1.1 404 0 127.0.0.1 - - [31/Jul/2015 01:19:42] GET / HTTP/1.1 404 0 127.0.0.1 - - [31/Jul/2015 01:19:42] GET / HTTP/1.1 404 0 127.0.0.1 - - [31/Jul/2015 01:19:42] GET / HTTP/1.1 404 0 127.0.0.1 - - [31/Jul/2015 01:19:42] GET / HTTP/1.1 404 0 127.0.0.1 - - [31/Jul/2015 01:19:42] GET / HTTP/1.1 404 0 127.0.0.1 - - [31/Jul/2015 01:19:42] GET / HTTP/1.1 404 0 127.0.0.1 - - [31/Jul/2015 01:19:42] GET / HTTP/1.1 404 0 127.0.0.1 - - [31/Jul/2015 01:19:42] GET / HTTP/1.1 404 0 127.0.0.1 - - [31/Jul/2015 01:19:42] GET / HTTP/1.1 404 0 FAIL INFO 2015-07-31 01:19:52,343 - Environment prefix is /tmp/tsqa.env.MH9vEX test_logs_exist (test_example.TestLogs) ... ok SKIP: Skip the entire class INFO 2015-07-31 01:20:05,788 - Environment prefix is /tmp/tsqa.env.dNq1az test_basic_intercept (test_example.TestServerIntercept) ... 127.0.0.1 - - [31/Jul/2015 01:20:09] GET / HTTP/1.1 200 5 127.0.0.1 - - [31/Jul/2015 01:20:09] GET / HTTP/1.1 200 5 127.0.0.1 - - [31/Jul/2015 01:20:09] GET / HTTP/1.1 200 5 127.0.0.1 - - [31/Jul/2015 01:20:09] GET / HTTP/1.1 200 5 127.0.0.1 - - [31/Jul/2015 01:20:09] GET / HTTP/1.1 200 5 127.0.0.1 - - [31/Jul/2015 01:20:09] GET / HTTP/1.1 200 5 127.0.0.1 - - [31/Jul/2015
[jira] [Updated] (TS-3806) In cmd/traffic_manager: libwccp.a(WccpMsg.o): undefined reference to symbol MD5_Final
[ https://issues.apache.org/jira/browse/TS-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron Stone updated TS-3806: Fix Version/s: (was: 5.3.1) (was: 6.0.0) In cmd/traffic_manager: libwccp.a(WccpMsg.o): undefined reference to symbol MD5_Final - Key: TS-3806 URL: https://issues.apache.org/jira/browse/TS-3806 Project: Traffic Server Issue Type: Bug Components: Build Affects Versions: 5.3.1 Reporter: Aaron Stone Assignee: Jean Baptiste Favre When building ATS 5.3.0 on Ubuntu 11.04[1,2] a linking failure occurs because of the ordering of the libraries: {code} libtool: link: c++ -g -O2 -fPIE -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -pipe -Wall -feliminate-unused-debug-symbols -fno-strict-aliasing -Wno-invalid-offsetof -mcx16 -rdynamic -Wl,-Bsymbolic-functions -fPIE -pie -Wl,-z -Wl,relro -Wl,-z -Wl,now -o .libs/traffic_manager AddConfigFilesHere.o traffic_manager.o StatProcessor.o StatType.o StatXML.o ../../mgmt/web2/libweb.a ../../mgmt/api/.libs/libmgmtapilocal.a /«PKGBUILDDIR»/lib/ts/.libs/libtsutil.so -lssl -lcrypto -L/usr/lib ../../mgmt/.libs/libmgmt_lm.a ../../proxy/hdrs/libhdrs.a ../../lib/records/librecords_lm.a ../../lib/ts/.libs/libtsutil.so ../../iocore/eventsystem/libinkevent.a ../../proxy/shared/liberror.a ../../proxy/shared/libdiagsconfig.a -lresolv -ltcl8.5 -lhwloc -lm ../../lib/wccp/libwccp.a ../../lib/tsconfig/.libs/libtsconfig.so -lcap -lpcre -lz -lcrypt -lpthread -lrt -ldl /usr/lib/x86_64-linux-gnu/libxml2.so -Wl,-rpath -Wl,/usr/lib/trafficserver /usr/bin/ld: ../../lib/wccp/libwccp.a(WccpMsg.o): undefined reference to symbol 'MD5_Final@@OPENSSL_1.0.0' /usr/bin/ld: note: 'MD5_Final@@OPENSSL_1.0.0' is defined in DSO /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libcrypto.so so try adding it to the linker command line /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libcrypto.so: could not read symbols: Invalid operation collect2: ld returned 1 exit status make[3]: *** [traffic_manager] Error 1 make[3]: Leaving directory `/«PKGBUILDDIR»/cmd/traffic_manager' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/«PKGBUILDDIR»/cmd' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/«PKGBUILDDIR»' dh_auto_build: make -j1 returned exit code 2 make: *** [binary-arch] Error 2 {code} [1] https://wiki.debian.org/ToolChain/DSOLinking#Only_link_with_needed_libraries [2] https://wiki.ubuntu.com/NattyNarwhal/ToolchainTransition -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-3806) In cmd/traffic_manager: libwccp.a(WccpMsg.o): undefined reference to symbol MD5_Final
[ https://issues.apache.org/jira/browse/TS-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron Stone updated TS-3806: Affects Version/s: (was: 5.3.0) 5.3.1 In cmd/traffic_manager: libwccp.a(WccpMsg.o): undefined reference to symbol MD5_Final - Key: TS-3806 URL: https://issues.apache.org/jira/browse/TS-3806 Project: Traffic Server Issue Type: Bug Components: Build Affects Versions: 5.3.1 Reporter: Aaron Stone Assignee: Jean Baptiste Favre When building ATS 5.3.0 on Ubuntu 11.04[1,2] a linking failure occurs because of the ordering of the libraries: {code} libtool: link: c++ -g -O2 -fPIE -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -pipe -Wall -feliminate-unused-debug-symbols -fno-strict-aliasing -Wno-invalid-offsetof -mcx16 -rdynamic -Wl,-Bsymbolic-functions -fPIE -pie -Wl,-z -Wl,relro -Wl,-z -Wl,now -o .libs/traffic_manager AddConfigFilesHere.o traffic_manager.o StatProcessor.o StatType.o StatXML.o ../../mgmt/web2/libweb.a ../../mgmt/api/.libs/libmgmtapilocal.a /«PKGBUILDDIR»/lib/ts/.libs/libtsutil.so -lssl -lcrypto -L/usr/lib ../../mgmt/.libs/libmgmt_lm.a ../../proxy/hdrs/libhdrs.a ../../lib/records/librecords_lm.a ../../lib/ts/.libs/libtsutil.so ../../iocore/eventsystem/libinkevent.a ../../proxy/shared/liberror.a ../../proxy/shared/libdiagsconfig.a -lresolv -ltcl8.5 -lhwloc -lm ../../lib/wccp/libwccp.a ../../lib/tsconfig/.libs/libtsconfig.so -lcap -lpcre -lz -lcrypt -lpthread -lrt -ldl /usr/lib/x86_64-linux-gnu/libxml2.so -Wl,-rpath -Wl,/usr/lib/trafficserver /usr/bin/ld: ../../lib/wccp/libwccp.a(WccpMsg.o): undefined reference to symbol 'MD5_Final@@OPENSSL_1.0.0' /usr/bin/ld: note: 'MD5_Final@@OPENSSL_1.0.0' is defined in DSO /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libcrypto.so so try adding it to the linker command line /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libcrypto.so: could not read symbols: Invalid operation collect2: ld returned 1 exit status make[3]: *** [traffic_manager] Error 1 make[3]: Leaving directory `/«PKGBUILDDIR»/cmd/traffic_manager' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/«PKGBUILDDIR»/cmd' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/«PKGBUILDDIR»' dh_auto_build: make -j1 returned exit code 2 make: *** [binary-arch] Error 2 {code} [1] https://wiki.debian.org/ToolChain/DSOLinking#Only_link_with_needed_libraries [2] https://wiki.ubuntu.com/NattyNarwhal/ToolchainTransition -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-3749) Error log isn't recorded
[ https://issues.apache.org/jira/browse/TS-3749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14648579#comment-14648579 ] ASF subversion and git services commented on TS-3749: - Commit 792a75b1aa348b0d51256635a54f6ff534a8dcf8 in trafficserver's branch refs/heads/master from [~psudaemon] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=792a75b ] TS-3749: Re-enable error log. Error log isn't recorded Key: TS-3749 URL: https://issues.apache.org/jira/browse/TS-3749 Project: Traffic Server Issue Type: Bug Components: Logging Reporter: Ryo Okubo Assignee: Crystal Qian Priority: Blocker Fix For: 6.0.0 error.log has not been recorded after TS-1985. Enabling error logging and specifying a format of error.log depended on pre-defined log format but this logic was eliminated on the issue. Error logging works fine when I tried to revert [5c2b032fb9f8f05ae7be1794a3103140ffe7d07e|https://github.com/apache/trafficserver/commit/5c2b032fb9f8f05ae7be1794a3103140ffe7d07e]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-3807) Remove legacy log splitting code and docs
[ https://issues.apache.org/jira/browse/TS-3807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber updated TS-3807: Fix Version/s: 6.0.0 Remove legacy log splitting code and docs - Key: TS-3807 URL: https://issues.apache.org/jira/browse/TS-3807 Project: Traffic Server Issue Type: Improvement Affects Versions: 6.0.0 Reporter: Phil Sorber Assignee: Phil Sorber Fix For: 6.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-3807) Remove legacy log splitting code and docs
[ https://issues.apache.org/jira/browse/TS-3807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14648589#comment-14648589 ] ASF subversion and git services commented on TS-3807: - Commit 6d37b7c888eae4290c605729783ef1f8d4a384bb in trafficserver's branch refs/heads/master from [~psudaemon] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=6d37b7c ] TS-3807: Remove legacy log splitting code and docs. Remove legacy log splitting code and docs - Key: TS-3807 URL: https://issues.apache.org/jira/browse/TS-3807 Project: Traffic Server Issue Type: Improvement Affects Versions: 6.0.0 Reporter: Phil Sorber Assignee: Phil Sorber Fix For: 6.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TS-3807) Remove legacy log splitting code and docs
[ https://issues.apache.org/jira/browse/TS-3807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber resolved TS-3807. - Resolution: Fixed Remove legacy log splitting code and docs - Key: TS-3807 URL: https://issues.apache.org/jira/browse/TS-3807 Project: Traffic Server Issue Type: Improvement Affects Versions: 6.0.0 Reporter: Phil Sorber Assignee: Phil Sorber Fix For: 6.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-3807) Remove legacy log splitting code and docs
[ https://issues.apache.org/jira/browse/TS-3807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber updated TS-3807: Affects Version/s: 6.0.0 Remove legacy log splitting code and docs - Key: TS-3807 URL: https://issues.apache.org/jira/browse/TS-3807 Project: Traffic Server Issue Type: Improvement Affects Versions: 6.0.0 Reporter: Phil Sorber Assignee: Phil Sorber Fix For: 6.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-3806) In cmd/traffic_manager: libwccp.a(WccpMsg.o): undefined reference to symbol MD5_Final
[ https://issues.apache.org/jira/browse/TS-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3806: -- Backport to Version: 5.3.2 In cmd/traffic_manager: libwccp.a(WccpMsg.o): undefined reference to symbol MD5_Final - Key: TS-3806 URL: https://issues.apache.org/jira/browse/TS-3806 Project: Traffic Server Issue Type: Bug Components: Build Affects Versions: 5.3.1 Reporter: Aaron Stone Assignee: Jean Baptiste Favre Fix For: 6.0.0 When building ATS 5.3.0 on Ubuntu 11.04[1,2] a linking failure occurs because of the ordering of the libraries: {code} libtool: link: c++ -g -O2 -fPIE -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -pipe -Wall -feliminate-unused-debug-symbols -fno-strict-aliasing -Wno-invalid-offsetof -mcx16 -rdynamic -Wl,-Bsymbolic-functions -fPIE -pie -Wl,-z -Wl,relro -Wl,-z -Wl,now -o .libs/traffic_manager AddConfigFilesHere.o traffic_manager.o StatProcessor.o StatType.o StatXML.o ../../mgmt/web2/libweb.a ../../mgmt/api/.libs/libmgmtapilocal.a /«PKGBUILDDIR»/lib/ts/.libs/libtsutil.so -lssl -lcrypto -L/usr/lib ../../mgmt/.libs/libmgmt_lm.a ../../proxy/hdrs/libhdrs.a ../../lib/records/librecords_lm.a ../../lib/ts/.libs/libtsutil.so ../../iocore/eventsystem/libinkevent.a ../../proxy/shared/liberror.a ../../proxy/shared/libdiagsconfig.a -lresolv -ltcl8.5 -lhwloc -lm ../../lib/wccp/libwccp.a ../../lib/tsconfig/.libs/libtsconfig.so -lcap -lpcre -lz -lcrypt -lpthread -lrt -ldl /usr/lib/x86_64-linux-gnu/libxml2.so -Wl,-rpath -Wl,/usr/lib/trafficserver /usr/bin/ld: ../../lib/wccp/libwccp.a(WccpMsg.o): undefined reference to symbol 'MD5_Final@@OPENSSL_1.0.0' /usr/bin/ld: note: 'MD5_Final@@OPENSSL_1.0.0' is defined in DSO /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libcrypto.so so try adding it to the linker command line /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libcrypto.so: could not read symbols: Invalid operation collect2: ld returned 1 exit status make[3]: *** [traffic_manager] Error 1 make[3]: Leaving directory `/«PKGBUILDDIR»/cmd/traffic_manager' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/«PKGBUILDDIR»/cmd' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/«PKGBUILDDIR»' dh_auto_build: make -j1 returned exit code 2 make: *** [binary-arch] Error 2 {code} [1] https://wiki.debian.org/ToolChain/DSOLinking#Only_link_with_needed_libraries [2] https://wiki.ubuntu.com/NattyNarwhal/ToolchainTransition -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-3718) Unused members in LogFile.h
[ https://issues.apache.org/jira/browse/TS-3718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3718: -- Fix Version/s: (was: 6.1.0) 6.0.0 Unused members in LogFile.h --- Key: TS-3718 URL: https://issues.apache.org/jira/browse/TS-3718 Project: Traffic Server Issue Type: Improvement Components: Logging Reporter: Daniel Xu Assignee: Daniel Xu Priority: Trivial Labels: review Fix For: 6.0.0 read_metadata() is declared in LogFile.h, but not defined anywhere in the code base. It is also not referenced anywhere else. m_size_bytes is a public variable initialized to 0 in the default LogFile constructor, however, it is not used or referenced anywhere in the code base. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TS-3786) Use a consensus algorithm to elect the cluster master
[ https://issues.apache.org/jira/browse/TS-3786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom resolved TS-3786. --- Resolution: Fixed Use a consensus algorithm to elect the cluster master - Key: TS-3786 URL: https://issues.apache.org/jira/browse/TS-3786 Project: Traffic Server Issue Type: Improvement Components: Manager Reporter: John Plevyak Assignee: John Plevyak Fix For: 6.0.0 We should use a consensus algorithm to elect the cluster master and to update the configurations so that there is no single point of failure and machines entering or restarting can be brought to a consistent state. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-3718) Unused members in LogFile.h
[ https://issues.apache.org/jira/browse/TS-3718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3718: -- Assignee: Daniel Xu Unused members in LogFile.h --- Key: TS-3718 URL: https://issues.apache.org/jira/browse/TS-3718 Project: Traffic Server Issue Type: Improvement Components: Logging Reporter: Daniel Xu Assignee: Daniel Xu Priority: Trivial Labels: review Fix For: 6.0.0 read_metadata() is declared in LogFile.h, but not defined anywhere in the code base. It is also not referenced anywhere else. m_size_bytes is a public variable initialized to 0 in the default LogFile constructor, however, it is not used or referenced anywhere in the code base. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-3786) Use a consensus algorithm to elect the cluster master
[ https://issues.apache.org/jira/browse/TS-3786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3786: -- Fix Version/s: (was: 6.1.0) 6.0.0 Use a consensus algorithm to elect the cluster master - Key: TS-3786 URL: https://issues.apache.org/jira/browse/TS-3786 Project: Traffic Server Issue Type: Improvement Components: Manager Reporter: John Plevyak Assignee: John Plevyak Fix For: 6.0.0 We should use a consensus algorithm to elect the cluster master and to update the configurations so that there is no single point of failure and machines entering or restarting can be brought to a consistent state. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-3534) Wiretracing for SSL connections
[ https://issues.apache.org/jira/browse/TS-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3534: -- Fix Version/s: (was: 6.1.0) 6.0.0 Wiretracing for SSL connections --- Key: TS-3534 URL: https://issues.apache.org/jira/browse/TS-3534 Project: Traffic Server Issue Type: New Feature Components: Logging, Tools Reporter: Eric Schwartz Assignee: Eric Schwartz Fix For: 6.0.0 Opening a ticket for discussion of the wiretracing change I made on our internal version of ATS. The change allows for tracing requests through ATS for: a small percentage of traffic, traffic from a certain IP and/or traffic to a specific origin. These settings can be combined. The main updates are to SSLNetVConnection and UnixNetVConnection (adding the trace logic) and to the Logging APIs (to add the special trace logs). One change is made to HttpSM to allow client and server traces to be associated with one another. [~dcarlin] has some notes from the summit on the initial discussion. I'll add a pull request with actual code for people to look at shortly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TS-3575) Make an option for traffic_layout to reproduce the configure invocation
[ https://issues.apache.org/jira/browse/TS-3575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom resolved TS-3575. --- Resolution: Fixed Make an option for traffic_layout to reproduce the configure invocation --- Key: TS-3575 URL: https://issues.apache.org/jira/browse/TS-3575 Project: Traffic Server Issue Type: Improvement Components: CI, Tools Reporter: Leif Hedstrom Assignee: Leif Hedstrom Fix For: 6.0.0 Basically have it echo out the equivalent of what is in config.nice. This will be useful not only for someone to check the build, but our tsqa tool can then use that to decide what tests are suitable for the run. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-3478) Indexing header representations on HPACK encoder
[ https://issues.apache.org/jira/browse/TS-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryo Okubo updated TS-3478: -- Summary: Indexing header representations on HPACK encoder (was: Support some header representations on HPACK encoder) Indexing header representations on HPACK encoder Key: TS-3478 URL: https://issues.apache.org/jira/browse/TS-3478 Project: Traffic Server Issue Type: Improvement Components: HTTP/2 Reporter: Ryo Okubo Assignee: Leif Hedstrom Labels: review Fix For: 6.0.0 Attachments: indexing.patch Support other header field representations on HPACK encoder. http://tools.ietf.org/html/draft-ietf-httpbis-header-compression-12#section-6 Currently the encoder supports only [Literal Header Field never Indexed|http://tools.ietf.org/html/draft-ietf-httpbis-header-compression-12#section-6.2.3]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Jenkins build is still unstable: tsqa-lint #382
See https://ci.trafficserver.apache.org/job/tsqa-lint/changes
[jira] [Commented] (TS-3801) Correct responses when CLOSED stream receive frames.
[ https://issues.apache.org/jira/browse/TS-3801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14648683#comment-14648683 ] Masaori Koshiba commented on TS-3801: - Patches to fix this is on github. - https://github.com/apache/trafficserver/pull/264 Correct responses when CLOSED stream receive frames. Key: TS-3801 URL: https://issues.apache.org/jira/browse/TS-3801 Project: Traffic Server Issue Type: Bug Components: HTTP/2 Reporter: Masaori Koshiba RFC 7540 says below in 5.1. Stream States. {quote} Similarly, an endpoint that receives any frames after receiving a frame with the END_STREAM flag set MUST treat that as a connection error (Section 5.4.1) of type STREAM_CLOSED, unless the frame is permitted as described below. WINDOW_UPDATE or RST_STREAM frames can be received in this state for a short period after a DATA or HEADERS frame containing an END_STREAM flag is sent. {quote} But ATS dosen't return {{STREAM_CLOSED}} when ATS receives {{DATA}}, {{HEADERS}} and {{CONTINUATION}} frames. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Build failed in Jenkins: tsqa-master #749
See https://ci.trafficserver.apache.org/job/tsqa-master/749/changes Changes: [Leif Hedstrom] TS-3806 Resolve undefined reference to symbol MD5_Final -- [...truncated 504 lines...] Test that incrementing the cache generation acts like a cache clear ... ok INFO 2015-07-31 03:03:50,965 - Environment prefix is /tmp/tsqa.env.5OdXM7 test_chunked_bad_close (test_chunked.TestChunked) ... INFO 2015-07-31 03:03:54,195 - sending data back to the client INFO 2015-07-31 03:03:56,699 - Client disconnected ok test_chunked_basic (test_chunked.TestChunked) ... INFO 2015-07-31 03:03:56,703 - sending data back to the client ok test_chunked_keepalive_client (test_chunked.TestChunked) ... INFO 2015-07-31 03:03:59,707 - sending data back to the client INFO 2015-07-31 03:04:02,712 - sending data back to the client INFO 2015-07-31 03:04:05,717 - sending data back to the client INFO 2015-07-31 03:04:08,120 - sending data back to the client INFO 2015-07-31 03:04:10,523 - sending data back to the client INFO 2015-07-31 03:04:14,528 - sending data back to the client ok test_chunked_keepalive_server (test_chunked.TestChunked) ... INFO 2015-07-31 03:04:18,533 - sending data back to the client INFO 2015-07-31 03:04:21,537 - sending data back to the client ok Test that the origin does in fact support keepalive ... INFO 2015-07-31 03:04:22,541 - sending data back to the client INFO 2015-07-31 03:04:25,545 - sending data back to the client INFO 2015-07-31 03:04:26,549 - sending data back to the client INFO 2015-07-31 03:04:28,548 - Client disconnected INFO 2015-07-31 03:04:28,952 - sending data back to the client INFO 2015-07-31 03:04:29,354 - sending data back to the client INFO 2015-07-31 03:04:31,355 - Client disconnected INFO 2015-07-31 03:04:33,359 - sending data back to the client ok INFO 2015-07-31 03:04:35,369 - Client disconnected INFO 2015-07-31 03:04:35,566 - Environment prefix is /tmp/tsqa.env.HRSEM7 INFO 2015-07-31 03:04:37,364 - Client disconnected Verify that we get 502s from an origin which just did a bind ... ok Verify that we get 200s from origins that delayed_accept_after_connect ... ok Verify that we get 504s from origins that die_on_connect ... ok Verify that we get 502s from origins that bind + listen ... ok Verify that we get 504s from origins that return a partial_response ... FAIL Verify that we get 200s from origins that reset_after_accept ... FAIL INFO 2015-07-31 03:04:46,862 - Environment prefix is /tmp/tsqa.env.KotrMs test_log_field (test_custom_log.TestCustomLogField) ... ok INFO 2015-07-31 03:06:30,394 - Environment prefix is /tmp/tsqa.env.opck_5 test_default_404 (test_example.TestBootstrap) ... ok Test that traffic_line works, and verify that the values for proxy.config ... ok INFO 2015-07-31 03:07:00,327 - Starting build (1b6c9541459e058351cd39ec55dcb772): configure {'enable-spdy': None, 'enable-ccache': None, 'enable-experimental-plugins': None, 'enable-example-plugins': None, 'enable-test-tools': None, 'disable-dependency-tracking': None} INFO 2015-07-31 03:07:58,655 - Build completed (1b6c9541459e058351cd39ec55dcb772): configure {'enable-spdy': None, 'enable-ccache': None, 'enable-experimental-plugins': None, 'enable-example-plugins': None, 'enable-test-tools': None, 'disable-dependency-tracking': None} INFO 2015-07-31 03:07:58,721 - Environment prefix is /tmp/tsqa.env.12GThQ test_spdy (test_example.TestConfigureFlags) ... ok INFO 2015-07-31 03:08:02,131 - Environment prefix is /tmp/tsqa.env.8H0J18 test_basic_proxy (test_example.TestDynamicHTTPEndpointCase) ... 127.0.0.1 - - [31/Jul/2015 03:08:05] GET /test HTTP/1.1 404 0 ok INFO 2015-07-31 03:08:05,544 - Environment prefix is /tmp/tsqa.env.PR6kHt test_logs_exist (test_example.TestLogRefCounting) ... 127.0.0.1 - - [31/Jul/2015 03:08:08] GET / HTTP/1.1 404 0 127.0.0.1 - - [31/Jul/2015 03:08:08] GET / HTTP/1.1 404 0 127.0.0.1 - - [31/Jul/2015 03:08:08] GET / HTTP/1.1 404 0 127.0.0.1 - - [31/Jul/2015 03:08:08] GET / HTTP/1.1 404 0 127.0.0.1 - - [31/Jul/2015 03:08:08] GET / HTTP/1.1 404 0 127.0.0.1 - - [31/Jul/2015 03:08:08] GET / HTTP/1.1 404 0 127.0.0.1 - - [31/Jul/2015 03:08:08] GET / HTTP/1.1 404 0 127.0.0.1 - - [31/Jul/2015 03:08:08] GET / HTTP/1.1 404 0 127.0.0.1 - - [31/Jul/2015 03:08:08] GET / HTTP/1.1 404 0 127.0.0.1 - - [31/Jul/2015 03:08:08] GET / HTTP/1.1 404 0 FAIL INFO 2015-07-31 03:08:19,018 - Environment prefix is /tmp/tsqa.env.YtB4Qw test_logs_exist (test_example.TestLogs) ... ok SKIP: Skip the entire class INFO 2015-07-31 03:08:32,481 - Environment prefix is /tmp/tsqa.env.i43RAy test_basic_intercept (test_example.TestServerIntercept) ... 127.0.0.1 - - [31/Jul/2015 03:08:35] GET / HTTP/1.1 200 5 127.0.0.1 - - [31/Jul/2015 03:08:35] GET / HTTP/1.1 200 5 127.0.0.1 - - [31/Jul/2015 03:08:35] GET / HTTP/1.1 200 5 127.0.0.1 - - [31/Jul/2015 03:08:35] GET / HTTP/1.1 200 5 127.0.0.1 - - [31/Jul/2015 03:08:35] GET / HTTP/1.1 200 5 127.0.0.1 - - [31/Jul/2015 03:08:35] GET / HTTP/1.1 200 5
[jira] [Commented] (TS-3801) Correct responses when CLOSED stream receive frames.
[ https://issues.apache.org/jira/browse/TS-3801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14648691#comment-14648691 ] Leif Hedstrom commented on TS-3801: --- [~masaori] What's your confidence here, should we land this for 6.0.0 ? Correct responses when CLOSED stream receive frames. Key: TS-3801 URL: https://issues.apache.org/jira/browse/TS-3801 Project: Traffic Server Issue Type: Bug Components: HTTP/2 Reporter: Masaori Koshiba RFC 7540 says below in 5.1. Stream States. {quote} Similarly, an endpoint that receives any frames after receiving a frame with the END_STREAM flag set MUST treat that as a connection error (Section 5.4.1) of type STREAM_CLOSED, unless the frame is permitted as described below. WINDOW_UPDATE or RST_STREAM frames can be received in this state for a short period after a DATA or HEADERS frame containing an END_STREAM flag is sent. {quote} But ATS dosen't return {{STREAM_CLOSED}} when ATS receives {{DATA}}, {{HEADERS}} and {{CONTINUATION}} frames. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-3801) Correct responses when CLOSED stream receive frames.
[ https://issues.apache.org/jira/browse/TS-3801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3801: -- Assignee: Masaori Koshiba Correct responses when CLOSED stream receive frames. Key: TS-3801 URL: https://issues.apache.org/jira/browse/TS-3801 Project: Traffic Server Issue Type: Bug Components: HTTP/2 Reporter: Masaori Koshiba Assignee: Masaori Koshiba RFC 7540 says below in 5.1. Stream States. {quote} Similarly, an endpoint that receives any frames after receiving a frame with the END_STREAM flag set MUST treat that as a connection error (Section 5.4.1) of type STREAM_CLOSED, unless the frame is permitted as described below. WINDOW_UPDATE or RST_STREAM frames can be received in this state for a short period after a DATA or HEADERS frame containing an END_STREAM flag is sent. {quote} But ATS dosen't return {{STREAM_CLOSED}} when ATS receives {{DATA}}, {{HEADERS}} and {{CONTINUATION}} frames. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-3478) Indexing header representations on HPACK encoder
[ https://issues.apache.org/jira/browse/TS-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14648735#comment-14648735 ] Leif Hedstrom commented on TS-3478: --- Cool, moving it out for 6.1.0, I'll land this after we're done with the master - 6.0.x cleanup. Indexing header representations on HPACK encoder Key: TS-3478 URL: https://issues.apache.org/jira/browse/TS-3478 Project: Traffic Server Issue Type: Improvement Components: HTTP/2 Reporter: Ryo Okubo Assignee: Leif Hedstrom Labels: review Fix For: 6.1.0 Attachments: indexing.patch Support other header field representations on HPACK encoder. http://tools.ietf.org/html/draft-ietf-httpbis-header-compression-12#section-6 Currently the encoder supports only [Literal Header Field never Indexed|http://tools.ietf.org/html/draft-ietf-httpbis-header-compression-12#section-6.2.3]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-3478) Indexing header representations on HPACK encoder
[ https://issues.apache.org/jira/browse/TS-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3478: -- Fix Version/s: (was: 6.0.0) 6.1.0 Indexing header representations on HPACK encoder Key: TS-3478 URL: https://issues.apache.org/jira/browse/TS-3478 Project: Traffic Server Issue Type: Improvement Components: HTTP/2 Reporter: Ryo Okubo Assignee: Leif Hedstrom Labels: review Fix For: 6.1.0 Attachments: indexing.patch Support other header field representations on HPACK encoder. http://tools.ietf.org/html/draft-ietf-httpbis-header-compression-12#section-6 Currently the encoder supports only [Literal Header Field never Indexed|http://tools.ietf.org/html/draft-ietf-httpbis-header-compression-12#section-6.2.3]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-3766) Ignore unknown frame in debugging
[ https://issues.apache.org/jira/browse/TS-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14648637#comment-14648637 ] ASF subversion and git services commented on TS-3766: - Commit f0e395f598ee6f4bc5c69db5ac9186a9c2f77787 in trafficserver's branch refs/heads/6.0.x from [~zwoop] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=f0e395f ] Merge branch 'master' into 6.0.x * master: TS-3807: Remove legacy log splitting code and docs. TS-3749: Re-enable error log. TS-3492 Only send SETTINGS which are different than protocol defaults TS-3766 Ignore unknown frame in debugging [TS-3476] Add a log tag for application protocol (add docs) Revert TS-3752: Problem with larger headers and HTTP/2 TS-3800: Fix bug in hostdb ui related to missing query TS-3803: CID 1313322 CID 1313322: HostDB memory issues (introduced in TS-3800) Ignore unknown frame in debugging - Key: TS-3766 URL: https://issues.apache.org/jira/browse/TS-3766 Project: Traffic Server Issue Type: Bug Components: HTTP/2 Reporter: Masaori Koshiba Assignee: Leif Hedstrom Labels: review Fix For: 6.0.0 Attachments: ts-3766.patch When ATS with {{--enable-debug}} recieve a frame which has unknown frame type in HTTP/2 stream, ATS aborts. ATS should just discard unknown frame. {noformat} FATAL: Http2ConnectionState.cc:643: failed assert `frame-header().type HTTP2_FRAME_TYPE_MAX` traffic_server: Aborted (Signal sent by tkill() 1 99)traffic_server - STACK TRACE: /opt/ats/bin/traffic_server(_Z19crash_logger_invokeiP7siginfoPv+0xc3)[0x4fc831] /lib64/libpthread.so.0(+0xf710)[0x7f00d1762710] /lib64/libc.so.6(gsignal+0x35)[0x7f00cfe79625] /lib64/libc.so.6(abort+0x175)[0x7f00cfe7ae05] /opt/ats/lib/libtsutil.so.6(_Z12ink_fatal_vaPKcP13__va_list_tag+0x0)[0x7f00d253e839] /opt/ats/lib/libtsutil.so.6(_Z9ink_fatalPKcz+0x0)[0x7f00d253e8f0] /opt/ats/lib/libtsutil.so.6(_Z10ink_pfatalPKcz+0x0)[0x7f00d253e9b5] /opt/ats/lib/libtsutil.so.6(+0x3a54a)[0x7f00d253c54a] /opt/ats/bin/traffic_server(_ZN20Http2ConnectionState18main_event_handlerEiPv+0x2f2)[0x5d8a18] /opt/ats/bin/traffic_server(_ZN12Continuation11handleEventEiPv+0x6c)[0x4ffaae] {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-3492) Only send SETTINGS which are different than protocol defaults
[ https://issues.apache.org/jira/browse/TS-3492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14648636#comment-14648636 ] ASF subversion and git services commented on TS-3492: - Commit f0e395f598ee6f4bc5c69db5ac9186a9c2f77787 in trafficserver's branch refs/heads/6.0.x from [~zwoop] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=f0e395f ] Merge branch 'master' into 6.0.x * master: TS-3807: Remove legacy log splitting code and docs. TS-3749: Re-enable error log. TS-3492 Only send SETTINGS which are different than protocol defaults TS-3766 Ignore unknown frame in debugging [TS-3476] Add a log tag for application protocol (add docs) Revert TS-3752: Problem with larger headers and HTTP/2 TS-3800: Fix bug in hostdb ui related to missing query TS-3803: CID 1313322 CID 1313322: HostDB memory issues (introduced in TS-3800) Only send SETTINGS which are different than protocol defaults - Key: TS-3492 URL: https://issues.apache.org/jira/browse/TS-3492 Project: Traffic Server Issue Type: Improvement Components: HTTP/2 Reporter: Leif Hedstrom Assignee: Leif Hedstrom Labels: newbie, review Fix For: 6.0.0 Attachments: settings.patch I'm thinking, why bother sending SETTINGS for values which are at the protocol defaults? Also, should we make our default configs match the protocol defaults consistently? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-3807) Remove legacy log splitting code and docs
[ https://issues.apache.org/jira/browse/TS-3807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14648634#comment-14648634 ] ASF subversion and git services commented on TS-3807: - Commit f0e395f598ee6f4bc5c69db5ac9186a9c2f77787 in trafficserver's branch refs/heads/6.0.x from [~zwoop] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=f0e395f ] Merge branch 'master' into 6.0.x * master: TS-3807: Remove legacy log splitting code and docs. TS-3749: Re-enable error log. TS-3492 Only send SETTINGS which are different than protocol defaults TS-3766 Ignore unknown frame in debugging [TS-3476] Add a log tag for application protocol (add docs) Revert TS-3752: Problem with larger headers and HTTP/2 TS-3800: Fix bug in hostdb ui related to missing query TS-3803: CID 1313322 CID 1313322: HostDB memory issues (introduced in TS-3800) Remove legacy log splitting code and docs - Key: TS-3807 URL: https://issues.apache.org/jira/browse/TS-3807 Project: Traffic Server Issue Type: Improvement Affects Versions: 6.0.0 Reporter: Phil Sorber Assignee: Phil Sorber Fix For: 6.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-3807) Remove legacy log splitting code and docs
[ https://issues.apache.org/jira/browse/TS-3807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14648632#comment-14648632 ] ASF subversion and git services commented on TS-3807: - Commit 6d37b7c888eae4290c605729783ef1f8d4a384bb in trafficserver's branch refs/heads/6.0.x from [~psudaemon] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=6d37b7c ] TS-3807: Remove legacy log splitting code and docs. Remove legacy log splitting code and docs - Key: TS-3807 URL: https://issues.apache.org/jira/browse/TS-3807 Project: Traffic Server Issue Type: Improvement Affects Versions: 6.0.0 Reporter: Phil Sorber Assignee: Phil Sorber Fix For: 6.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-3476) Add a log tag for application protocol
[ https://issues.apache.org/jira/browse/TS-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14648638#comment-14648638 ] ASF subversion and git services commented on TS-3476: - Commit f0e395f598ee6f4bc5c69db5ac9186a9c2f77787 in trafficserver's branch refs/heads/6.0.x from [~zwoop] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=f0e395f ] Merge branch 'master' into 6.0.x * master: TS-3807: Remove legacy log splitting code and docs. TS-3749: Re-enable error log. TS-3492 Only send SETTINGS which are different than protocol defaults TS-3766 Ignore unknown frame in debugging [TS-3476] Add a log tag for application protocol (add docs) Revert TS-3752: Problem with larger headers and HTTP/2 TS-3800: Fix bug in hostdb ui related to missing query TS-3803: CID 1313322 CID 1313322: HostDB memory issues (introduced in TS-3800) Add a log tag for application protocol -- Key: TS-3476 URL: https://issues.apache.org/jira/browse/TS-3476 Project: Traffic Server Issue Type: New Feature Components: Logging, SSL Reporter: Leif Hedstrom Assignee: Eric Schwartz Fix For: 6.0.0 It seems crucial to be able to log which protocol handler was negotiated with ALPN (and perhaps NPN as long as we support it). This could simple be the string that was negotiated by the client/server in the TLS handshake. For example, with HTTP/2, it would be h2 (or h2-14 with some browsers). A suggested log tag name would be %alpn which seems clear enough to me and easy to remember :). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-3749) Error log isn't recorded
[ https://issues.apache.org/jira/browse/TS-3749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14648633#comment-14648633 ] Ryo Okubo commented on TS-3749: --- Both patches work correctly. Thanks :) {noformat} $ tail /var/log/trafficserver/error.log 20150731.10h56m49s RESPONSE: sent 127.0.0.1 status 502 (Cannot find server.) for 'http://nonexistent.yahoo.co.jp/' {noformat} Error log isn't recorded Key: TS-3749 URL: https://issues.apache.org/jira/browse/TS-3749 Project: Traffic Server Issue Type: Bug Components: Logging Reporter: Ryo Okubo Assignee: Phil Sorber Priority: Blocker Fix For: 6.0.0 error.log has not been recorded after TS-1985. Enabling error logging and specifying a format of error.log depended on pre-defined log format but this logic was eliminated on the issue. Error logging works fine when I tried to revert [5c2b032fb9f8f05ae7be1794a3103140ffe7d07e|https://github.com/apache/trafficserver/commit/5c2b032fb9f8f05ae7be1794a3103140ffe7d07e]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-3752) Problem with larger headers and HTTP/2
[ https://issues.apache.org/jira/browse/TS-3752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14648639#comment-14648639 ] ASF subversion and git services commented on TS-3752: - Commit f0e395f598ee6f4bc5c69db5ac9186a9c2f77787 in trafficserver's branch refs/heads/6.0.x from [~zwoop] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=f0e395f ] Merge branch 'master' into 6.0.x * master: TS-3807: Remove legacy log splitting code and docs. TS-3749: Re-enable error log. TS-3492 Only send SETTINGS which are different than protocol defaults TS-3766 Ignore unknown frame in debugging [TS-3476] Add a log tag for application protocol (add docs) Revert TS-3752: Problem with larger headers and HTTP/2 TS-3800: Fix bug in hostdb ui related to missing query TS-3803: CID 1313322 CID 1313322: HostDB memory issues (introduced in TS-3800) Problem with larger headers and HTTP/2 -- Key: TS-3752 URL: https://issues.apache.org/jira/browse/TS-3752 Project: Traffic Server Issue Type: Bug Components: HTTP/2 Reporter: Bryan Call Assignee: Masaori Koshiba Labels: yahoo Fix For: 6.1.0 There is a problem when ATS receives a HEADERS or CONTINUATION frame on the HEADERS frame and there is no end of header to be decoded. If there is 1 small header at the beginning of the frame it will work, but if a large header either starts at the beginning of the frame or started on the previous frame and don't end until the next frame then the decoded_bytes will be 0. This will cause a COMPRESSION_ERROR to be send to the client with a GOAWAY frame. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-3749) Error log isn't recorded
[ https://issues.apache.org/jira/browse/TS-3749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14648631#comment-14648631 ] ASF subversion and git services commented on TS-3749: - Commit 792a75b1aa348b0d51256635a54f6ff534a8dcf8 in trafficserver's branch refs/heads/6.0.x from [~psudaemon] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=792a75b ] TS-3749: Re-enable error log. Error log isn't recorded Key: TS-3749 URL: https://issues.apache.org/jira/browse/TS-3749 Project: Traffic Server Issue Type: Bug Components: Logging Reporter: Ryo Okubo Assignee: Phil Sorber Priority: Blocker Fix For: 6.0.0 error.log has not been recorded after TS-1985. Enabling error logging and specifying a format of error.log depended on pre-defined log format but this logic was eliminated on the issue. Error logging works fine when I tried to revert [5c2b032fb9f8f05ae7be1794a3103140ffe7d07e|https://github.com/apache/trafficserver/commit/5c2b032fb9f8f05ae7be1794a3103140ffe7d07e]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-3749) Error log isn't recorded
[ https://issues.apache.org/jira/browse/TS-3749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14648635#comment-14648635 ] ASF subversion and git services commented on TS-3749: - Commit f0e395f598ee6f4bc5c69db5ac9186a9c2f77787 in trafficserver's branch refs/heads/6.0.x from [~zwoop] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=f0e395f ] Merge branch 'master' into 6.0.x * master: TS-3807: Remove legacy log splitting code and docs. TS-3749: Re-enable error log. TS-3492 Only send SETTINGS which are different than protocol defaults TS-3766 Ignore unknown frame in debugging [TS-3476] Add a log tag for application protocol (add docs) Revert TS-3752: Problem with larger headers and HTTP/2 TS-3800: Fix bug in hostdb ui related to missing query TS-3803: CID 1313322 CID 1313322: HostDB memory issues (introduced in TS-3800) Error log isn't recorded Key: TS-3749 URL: https://issues.apache.org/jira/browse/TS-3749 Project: Traffic Server Issue Type: Bug Components: Logging Reporter: Ryo Okubo Assignee: Phil Sorber Priority: Blocker Fix For: 6.0.0 error.log has not been recorded after TS-1985. Enabling error logging and specifying a format of error.log depended on pre-defined log format but this logic was eliminated on the issue. Error logging works fine when I tried to revert [5c2b032fb9f8f05ae7be1794a3103140ffe7d07e|https://github.com/apache/trafficserver/commit/5c2b032fb9f8f05ae7be1794a3103140ffe7d07e]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-3766) Ignore unknown frame in debugging
[ https://issues.apache.org/jira/browse/TS-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14648629#comment-14648629 ] ASF subversion and git services commented on TS-3766: - Commit 8a2b2413399d4fb11a69431146db8d7ebee7219f in trafficserver's branch refs/heads/6.0.x from [~masaori] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=8a2b241 ] TS-3766 Ignore unknown frame in debugging Ignore unknown frame in debugging - Key: TS-3766 URL: https://issues.apache.org/jira/browse/TS-3766 Project: Traffic Server Issue Type: Bug Components: HTTP/2 Reporter: Masaori Koshiba Assignee: Leif Hedstrom Labels: review Fix For: 6.0.0 Attachments: ts-3766.patch When ATS with {{--enable-debug}} recieve a frame which has unknown frame type in HTTP/2 stream, ATS aborts. ATS should just discard unknown frame. {noformat} FATAL: Http2ConnectionState.cc:643: failed assert `frame-header().type HTTP2_FRAME_TYPE_MAX` traffic_server: Aborted (Signal sent by tkill() 1 99)traffic_server - STACK TRACE: /opt/ats/bin/traffic_server(_Z19crash_logger_invokeiP7siginfoPv+0xc3)[0x4fc831] /lib64/libpthread.so.0(+0xf710)[0x7f00d1762710] /lib64/libc.so.6(gsignal+0x35)[0x7f00cfe79625] /lib64/libc.so.6(abort+0x175)[0x7f00cfe7ae05] /opt/ats/lib/libtsutil.so.6(_Z12ink_fatal_vaPKcP13__va_list_tag+0x0)[0x7f00d253e839] /opt/ats/lib/libtsutil.so.6(_Z9ink_fatalPKcz+0x0)[0x7f00d253e8f0] /opt/ats/lib/libtsutil.so.6(_Z10ink_pfatalPKcz+0x0)[0x7f00d253e9b5] /opt/ats/lib/libtsutil.so.6(+0x3a54a)[0x7f00d253c54a] /opt/ats/bin/traffic_server(_ZN20Http2ConnectionState18main_event_handlerEiPv+0x2f2)[0x5d8a18] /opt/ats/bin/traffic_server(_ZN12Continuation11handleEventEiPv+0x6c)[0x4ffaae] {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-3800) Improve HostDB UI output
[ https://issues.apache.org/jira/browse/TS-3800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14648640#comment-14648640 ] ASF subversion and git services commented on TS-3800: - Commit f0e395f598ee6f4bc5c69db5ac9186a9c2f77787 in trafficserver's branch refs/heads/6.0.x from [~zwoop] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=f0e395f ] Merge branch 'master' into 6.0.x * master: TS-3807: Remove legacy log splitting code and docs. TS-3749: Re-enable error log. TS-3492 Only send SETTINGS which are different than protocol defaults TS-3766 Ignore unknown frame in debugging [TS-3476] Add a log tag for application protocol (add docs) Revert TS-3752: Problem with larger headers and HTTP/2 TS-3800: Fix bug in hostdb ui related to missing query TS-3803: CID 1313322 CID 1313322: HostDB memory issues (introduced in TS-3800) Improve HostDB UI output Key: TS-3800 URL: https://issues.apache.org/jira/browse/TS-3800 Project: Traffic Server Issue Type: Improvement Components: Core, HostDB Reporter: Brian Geffon Assignee: Brian Geffon Fix For: 6.0.0 This ticket will track a few changes to HostDB UI which will improve the output including: - better viewall output - better srv record output - ability to output data in json format. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-3492) Only send SETTINGS which are different than protocol defaults
[ https://issues.apache.org/jira/browse/TS-3492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14648630#comment-14648630 ] ASF subversion and git services commented on TS-3492: - Commit 213a70036ccbf39d5298674bdaa70d31f4fe1fca in trafficserver's branch refs/heads/6.0.x from [~masaori] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=213a700 ] TS-3492 Only send SETTINGS which are different than protocol defaults Only send SETTINGS which are different than protocol defaults - Key: TS-3492 URL: https://issues.apache.org/jira/browse/TS-3492 Project: Traffic Server Issue Type: Improvement Components: HTTP/2 Reporter: Leif Hedstrom Assignee: Leif Hedstrom Labels: newbie, review Fix For: 6.0.0 Attachments: settings.patch I'm thinking, why bother sending SETTINGS for values which are at the protocol defaults? Also, should we make our default configs match the protocol defaults consistently? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TS-3808) Testing HTTP/2 features by h2spec
Masaori Koshiba created TS-3808: --- Summary: Testing HTTP/2 features by h2spec Key: TS-3808 URL: https://issues.apache.org/jira/browse/TS-3808 Project: Traffic Server Issue Type: Bug Components: HTTP/2 Reporter: Masaori Koshiba This is an umbrella ticket for testing HTTP/2 features of ATS by [h2spec|https://github.com/summerwind/h2spec]. Our goal : passing all tests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-3808) Testing HTTP/2 features by h2spec
[ https://issues.apache.org/jira/browse/TS-3808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masaori Koshiba updated TS-3808: Issue Type: Test (was: Bug) Testing HTTP/2 features by h2spec - Key: TS-3808 URL: https://issues.apache.org/jira/browse/TS-3808 Project: Traffic Server Issue Type: Test Components: HTTP/2 Reporter: Masaori Koshiba Labels: Umbrella This is an umbrella ticket for testing HTTP/2 features of ATS by [h2spec|https://github.com/summerwind/h2spec]. Our goal : passing all tests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-3808) Testing HTTP/2 features by h2spec
[ https://issues.apache.org/jira/browse/TS-3808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masaori Koshiba updated TS-3808: Labels: Umbrella (was: ) Testing HTTP/2 features by h2spec - Key: TS-3808 URL: https://issues.apache.org/jira/browse/TS-3808 Project: Traffic Server Issue Type: Bug Components: HTTP/2 Reporter: Masaori Koshiba Labels: Umbrella This is an umbrella ticket for testing HTTP/2 features of ATS by [h2spec|https://github.com/summerwind/h2spec]. Our goal : passing all tests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Jenkins build is still unstable: tsqa-lint #383
See https://ci.trafficserver.apache.org/job/tsqa-lint/changes
[jira] [Commented] (TS-3806) In cmd/traffic_manager: libwccp.a(WccpMsg.o): undefined reference to symbol MD5_Final
[ https://issues.apache.org/jira/browse/TS-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14648672#comment-14648672 ] Phil Sorber commented on TS-3806: - Will you be marking this for backport? In cmd/traffic_manager: libwccp.a(WccpMsg.o): undefined reference to symbol MD5_Final - Key: TS-3806 URL: https://issues.apache.org/jira/browse/TS-3806 Project: Traffic Server Issue Type: Bug Components: Build Affects Versions: 5.3.1 Reporter: Aaron Stone Assignee: Jean Baptiste Favre Fix For: 6.0.0 When building ATS 5.3.0 on Ubuntu 11.04[1,2] a linking failure occurs because of the ordering of the libraries: {code} libtool: link: c++ -g -O2 -fPIE -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -pipe -Wall -feliminate-unused-debug-symbols -fno-strict-aliasing -Wno-invalid-offsetof -mcx16 -rdynamic -Wl,-Bsymbolic-functions -fPIE -pie -Wl,-z -Wl,relro -Wl,-z -Wl,now -o .libs/traffic_manager AddConfigFilesHere.o traffic_manager.o StatProcessor.o StatType.o StatXML.o ../../mgmt/web2/libweb.a ../../mgmt/api/.libs/libmgmtapilocal.a /«PKGBUILDDIR»/lib/ts/.libs/libtsutil.so -lssl -lcrypto -L/usr/lib ../../mgmt/.libs/libmgmt_lm.a ../../proxy/hdrs/libhdrs.a ../../lib/records/librecords_lm.a ../../lib/ts/.libs/libtsutil.so ../../iocore/eventsystem/libinkevent.a ../../proxy/shared/liberror.a ../../proxy/shared/libdiagsconfig.a -lresolv -ltcl8.5 -lhwloc -lm ../../lib/wccp/libwccp.a ../../lib/tsconfig/.libs/libtsconfig.so -lcap -lpcre -lz -lcrypt -lpthread -lrt -ldl /usr/lib/x86_64-linux-gnu/libxml2.so -Wl,-rpath -Wl,/usr/lib/trafficserver /usr/bin/ld: ../../lib/wccp/libwccp.a(WccpMsg.o): undefined reference to symbol 'MD5_Final@@OPENSSL_1.0.0' /usr/bin/ld: note: 'MD5_Final@@OPENSSL_1.0.0' is defined in DSO /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libcrypto.so so try adding it to the linker command line /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libcrypto.so: could not read symbols: Invalid operation collect2: ld returned 1 exit status make[3]: *** [traffic_manager] Error 1 make[3]: Leaving directory `/«PKGBUILDDIR»/cmd/traffic_manager' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/«PKGBUILDDIR»/cmd' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/«PKGBUILDDIR»' dh_auto_build: make -j1 returned exit code 2 make: *** [binary-arch] Error 2 {code} [1] https://wiki.debian.org/ToolChain/DSOLinking#Only_link_with_needed_libraries [2] https://wiki.ubuntu.com/NattyNarwhal/ToolchainTransition -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (TS-1007) SSN Close called before TXN Close
[ https://issues.apache.org/jira/browse/TS-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom reopened TS-1007: --- SSN Close called before TXN Close - Key: TS-1007 URL: https://issues.apache.org/jira/browse/TS-1007 Project: Traffic Server Issue Type: Bug Components: TS API Affects Versions: 3.0.1 Reporter: Nick Kew Assignee: Susan Hinrichs Labels: incompatible Fix For: 6.0.0 Where a plugin implements both SSN_CLOSE_HOOK and TXN_CLOSE_HOOK, the SSN_CLOSE_HOOK is called first of the two. This messes up normal cleanups! Details: Register a SSN_START event globally In the SSN START, add a TXN_START and a SSN_CLOSE In the TXN START, add a TXN_CLOSE Stepping through, I see the order of events actually called, for the simple case of a one-off HTTP request with no keepalive: SSN_START TXN_START SSN_END TXN_END Whoops, SSN_END cleaned up the SSN context, leaving dangling pointers in the TXN! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-3728) Socket option are not being set on new incoming socket connections
[ https://issues.apache.org/jira/browse/TS-3728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3728: -- Fix Version/s: (was: 6.0.0) 6.1.0 Socket option are not being set on new incoming socket connections -- Key: TS-3728 URL: https://issues.apache.org/jira/browse/TS-3728 Project: Traffic Server Issue Type: Bug Components: Network Reporter: Bryan Call Assignee: Bryan Call Labels: yahoo Fix For: 6.1.0 Socket option configuration value is not set in the code and the Connection is not being set to SOCK_STREAM. Both of these need to be done for new incoming socket connection to have their options set. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-3161) traffic_top shows some values incorrectly
[ https://issues.apache.org/jira/browse/TS-3161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3161: -- Fix Version/s: (was: 6.0.0) 6.1.0 traffic_top shows some values incorrectly - Key: TS-3161 URL: https://issues.apache.org/jira/browse/TS-3161 Project: Traffic Server Issue Type: Bug Components: Utilities Reporter: Feifei Cai Assignee: Bryan Call Fix For: 6.1.0 Attachments: traffic_top-1.png, traffic_top-2.png The average time values in Cache Information do not show correctly, such as Fresh (ms), Reval (ms)... We use TSRecordGetInt to get all statistics. Some statistics are float value, we need to use TSRecordGetFloat. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-2150) Add Milestone log tags
[ https://issues.apache.org/jira/browse/TS-2150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2150: -- Fix Version/s: (was: 6.1.0) 6.0.0 Add Milestone log tags -- Key: TS-2150 URL: https://issues.apache.org/jira/browse/TS-2150 Project: Traffic Server Issue Type: New Feature Components: Logging Reporter: Leif Hedstrom Assignee: François Pesce Labels: yahoo Fix For: 6.0.0 We have a notion of milestones in the core, and plugin APIs (TSHttpTxnMilestoneGet() ). It'd be useful to expose these milestone timers as a log tag, something like: {code} %{UA_BEGIN}mtms {code} mtms is just an example / suggestion, MilestoneTimeMilliSecond, we can make it whatever we like. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-3808) ☂ Testing HTTP/2 features by h2spec
[ https://issues.apache.org/jira/browse/TS-3808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masaori Koshiba updated TS-3808: Description: This is an umbrella ticket for testing HTTP/2 features of ATS by [h2spec|https://github.com/summerwind/h2spec]. Our goal : passing all tests. h3. Status - 3.5. HTTP/2 Connection Preface - ✓ Sends invalid connection preface - 4.2. Frame Size - ✓ Sends large size frame that exceeds the SETTINGS_MAX_FRAME_SIZE - 4.3. Header Compression and Decompression - ✓ Sends invalid header block fragment - 5.1. Stream States - ✓ idle: Sends a DATA frame - × idle: Sends a RST_STREAM frame - × idle: Sends a WINDOW_UPDATE frame - ✓ idle: Sends a CONTINUATION frame - ✓ half closed (remote): Sends a DATA frame - × half closed (remote): Sends a HEADERS frame - ✓ half closed (remote): Sends a CONTINUATION frame - × closed: Sends a CONTINUATION frame - 5.1.1. Stream Identifiers - ✓ Sends even-numbered stream identifier - 5.1.2. Stream Concurrency - ✓ Sends HEADERS frames that causes their advertised concurrent stream limit to be exceeded - 5.3. Stream Priority - 5.3.1. Stream Dependencies - × Sends HEADERS frame that depend on itself - ✓ Sends PRIORITY frame that depend on itself - 5.4. Error Handling - 5.4.1. Connection Error Handling - × Receives a GOAWAY frame - 5.5. Extending HTTP/2 - ✓ Sends an unknown extension frame - × Sends an unknown extension frame in the middle of a header block - 6.1. DATA - ✓ Sends a DATA frame with 0x0 stream identifier - ✓ Sends a DATA frame on the stream that is not opend - ✓ Sends a DATA frame with invalid pad length - 6.2. HEADERS - ✓ Sends a HEADERS frame followed by any frame other than CONTINUATION - ✓ Sends a HEADERS frame followed by a frame on a different stream - ✓ Sends a HEADERS frame with 0x0 stream identifier - ✓ Sends a HEADERS frame with invalid pad length - 6.3. PRIORITY - ✓ Sends a PRIORITY frame with 0x0 stream identifier - ✓ Sends a PRIORITY frame with a length other than 5 octets - 6.4. RST_STREAM - ✓ Sends a RST_STREAM frame with 0x0 stream identifier - × Sends a RST_STREAM frame on a idle stream - ✓ Sends a RST_STREAM frame with a length other than 4 octets - 6.5. SETTINGS - ✓ Sends a SETTINGS frame - ✓ Sends a SETTINGS frame that is not a zero-length with ACK flag - ✓ Sends a SETTINGS frame with the stream identifier that is not 0x0 - × Sends a SETTINGS frame with a length other than a multiple of 6 octets - 6.5.2. Defined SETTINGS Parameters - ✓ SETTINGS_ENABLE_PUSH (0x2): Sends the value other than 0 or 1 - ✓ SETTINGS_INITIAL_WINDOW_SIZE (0x4): Sends the value above the maximum flow control window size - ✓ SETTINGS_MAX_FRAME_SIZE (0x5): Sends the value below the initial value - ✓ SETTINGS_MAX_FRAME_SIZE (0x5): Sends the value above the maximum allowed frame size - 6.7. PING - ✓ Sends a PING frame - ✓ Sends a PING frame with the stream identifier that is not 0x0 - ✓ Sends a PING frame with a length field value other than 8 - 6.8. GOAWAY - ✓ Sends a GOAWAY frame with the stream identifier that is not 0x0 - 6.9. WINDOW_UPDATE - ✓ Sends a WINDOW_UPDATE frame - ✓ Sends a WINDOW_UPDATE frame with an flow control window increment of 0 - ✓ Sends a WINDOW_UPDATE frame with an flow control window increment of 0 on a stream - ✓ Sends a WINDOW_UPDATE frame with a length other than a multiple of 4 octets - 6.10. CONTINUATION - × Sends a CONTINUATION frame - × Sends multiple CONTINUATION frames - × Sends a CONTINUATION frame followed by any frame other than CONTINUATION - × Sends a CONTINUATION frame followed by a frame on a different stream - × Sends a CONTINUATION frame with the stream identifier that is 0x0 - ✓ Sends a CONTINUATION frame after the frame other than HEADERS, PUSH_PROMISE or CONTINUATION - 8.1. HTTP Request/Response Exchange - ✓ Sends a HEADERS frame as HEAD request - × Sends a HEADERS frame containing trailer part - 8.1.2. HTTP Header Fields - ✓ Sends a HEADERS frame that contains the header field name in uppercase letters - 8.1.2.2. Connection-Specific Header Fields - × Sends a HEADERS frame that contains the connection-specific header field - ✓ Sends a HEADERS frame that contains the TE header field that contain any value other than trailers - 8.1.2.3. Request Pseudo-Header Fields - ✓ Sends a HEADERS frame that omits mandatory pseudo-header fields - ✓ Sends a HEADERS frame containing more than one pseudo-header fields with the same name - 8.1.2.6. Malformed Requests and Responses - ✓ Sends a HEADERS frame that contains the content-length header field which does not equal the sum of the DATA frame payload lengths - ✓ Sends a HEADERS frame that contains the content-length header field which does not equal the sum of the multiple DATA frame payload lengths -
[jira] [Updated] (TS-3808) ☂ Testing HTTP/2 features by h2spec
[ https://issues.apache.org/jira/browse/TS-3808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masaori Koshiba updated TS-3808: Description: This is an umbrella ticket for testing HTTP/2 features of ATS by [h2spec|https://github.com/summerwind/h2spec]. Our goal : passing all tests. h3. Status * 3.5. HTTP/2 Connection Preface ** ✓ Sends invalid connection preface * 4.2. Frame Size ** ✓ Sends large size frame that exceeds the SETTINGS_MAX_FRAME_SIZE * 4.3. Header Compression and Decompression ** ✓ Sends invalid header block fragment * 5.1. Stream States ** ✓ idle: Sends a DATA frame ** × idle: Sends a RST_STREAM frame ** × idle: Sends a WINDOW_UPDATE frame ** ✓ idle: Sends a CONTINUATION frame ** ✓ half closed (remote): Sends a DATA frame ** × half closed (remote): Sends a HEADERS frame ** ✓ half closed (remote): Sends a CONTINUATION frame ** × closed: Sends a CONTINUATION frame ** 5.1.1. Stream Identifiers *** ✓ Sends even-numbered stream identifier ** 5.1.2. Stream Concurrency *** ✓ Sends HEADERS frames that causes their advertised concurrent stream limit to be exceeded * 5.3. Stream Priority ** 5.3.1. Stream Dependencies *** × Sends HEADERS frame that depend on itself *** ✓ Sends PRIORITY frame that depend on itself * 5.4. Error Handling ** 5.4.1. Connection Error Handling *** × Receives a GOAWAY frame * 5.5. Extending HTTP/2 ** ✓ Sends an unknown extension frame ** × Sends an unknown extension frame in the middle of a header block * 6.1. DATA ** ✓ Sends a DATA frame with 0x0 stream identifier ** ✓ Sends a DATA frame on the stream that is not opend ** ✓ Sends a DATA frame with invalid pad length * 6.2. HEADERS ** ✓ Sends a HEADERS frame followed by any frame other than CONTINUATION ** ✓ Sends a HEADERS frame followed by a frame on a different stream ** ✓ Sends a HEADERS frame with 0x0 stream identifier ** ✓ Sends a HEADERS frame with invalid pad length * 6.3. PRIORITY ** ✓ Sends a PRIORITY frame with 0x0 stream identifier ** ✓ Sends a PRIORITY frame with a length other than 5 octets * 6.4. RST_STREAM ** ✓ Sends a RST_STREAM frame with 0x0 stream identifier ** × Sends a RST_STREAM frame on a idle stream ** ✓ Sends a RST_STREAM frame with a length other than 4 octets * 6.5. SETTINGS ** ✓ Sends a SETTINGS frame ** ✓ Sends a SETTINGS frame that is not a zero-length with ACK flag ** ✓ Sends a SETTINGS frame with the stream identifier that is not 0x0 ** × Sends a SETTINGS frame with a length other than a multiple of 6 octets ** 6.5.2. Defined SETTINGS Parameters *** ✓ SETTINGS_ENABLE_PUSH (0x2): Sends the value other than 0 or 1 *** ✓ SETTINGS_INITIAL_WINDOW_SIZE (0x4): Sends the value above the maximum flow control window size *** ✓ SETTINGS_MAX_FRAME_SIZE (0x5): Sends the value below the initial value *** ✓ SETTINGS_MAX_FRAME_SIZE (0x5): Sends the value above the maximum allowed frame size * 6.7. PING ** ✓ Sends a PING frame ** ✓ Sends a PING frame with the stream identifier that is not 0x0 ** ✓ Sends a PING frame with a length field value other than 8 * 6.8. GOAWAY ** ✓ Sends a GOAWAY frame with the stream identifier that is not 0x0 * 6.9. WINDOW_UPDATE ** ✓ Sends a WINDOW_UPDATE frame ** ✓ Sends a WINDOW_UPDATE frame with an flow control window increment of 0 ** ✓ Sends a WINDOW_UPDATE frame with an flow control window increment of 0 on a stream ** ✓ Sends a WINDOW_UPDATE frame with a length other than a multiple of 4 octets * 6.10. CONTINUATION ** × Sends a CONTINUATION frame ** × Sends multiple CONTINUATION frames ** × Sends a CONTINUATION frame followed by any frame other than CONTINUATION ** × Sends a CONTINUATION frame followed by a frame on a different stream ** × Sends a CONTINUATION frame with the stream identifier that is 0x0 ** ✓ Sends a CONTINUATION frame after the frame other than HEADERS, PUSH_PROMISE or CONTINUATION * 8.1. HTTP Request/Response Exchange ** ✓ Sends a HEADERS frame as HEAD request ** × Sends a HEADERS frame containing trailer part ** 8.1.2. HTTP Header Fields *** ✓ Sends a HEADERS frame that contains the header field name in uppercase letters *** 8.1.2.2. Connection-Specific Header Fields × Sends a HEADERS frame that contains the connection-specific header field ✓ Sends a HEADERS frame that contains the TE header field that contain any value other than trailers *** 8.1.2.3. Request Pseudo-Header Fields ✓ Sends a HEADERS frame that omits mandatory pseudo-header fields ✓ Sends a HEADERS frame containing more than one pseudo-header fields with the same name *** 8.1.2.6. Malformed Requests and Responses ✓ Sends a HEADERS frame that contains the content-length header field which does not equal the sum of the DATA frame payload lengths ✓ Sends a HEADERS frame that contains the content-length header field which does not equal the sum of the multiple DATA frame payload lengths * 8.2. Server Push ** ✓ Sends a PUSH_PROMISE frame was: This is an umbrella ticket for testing
[jira] [Commented] (TS-3478) Support some header representations on HPACK encoder
[ https://issues.apache.org/jira/browse/TS-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14648732#comment-14648732 ] Ryo Okubo commented on TS-3478: --- [~zwoop] I think 6.1.0 is better. This is a optional feature so H2 clients maybe don't require it. Support some header representations on HPACK encoder Key: TS-3478 URL: https://issues.apache.org/jira/browse/TS-3478 Project: Traffic Server Issue Type: Improvement Components: HTTP/2 Reporter: Ryo Okubo Assignee: Leif Hedstrom Labels: review Fix For: 6.0.0 Attachments: indexing.patch Support other header field representations on HPACK encoder. http://tools.ietf.org/html/draft-ietf-httpbis-header-compression-12#section-6 Currently the encoder supports only [Literal Header Field never Indexed|http://tools.ietf.org/html/draft-ietf-httpbis-header-compression-12#section-6.2.3]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-3808) ☂ Testing HTTP/2 features by h2spec
[ https://issues.apache.org/jira/browse/TS-3808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masaori Koshiba updated TS-3808: Description: This is an umbrella ticket for testing HTTP/2 features of ATS by [h2spec|https://github.com/summerwind/h2spec]. Goal : pass all tests. h3. Status * ATS : {{35f11dd5aab06364547d423e26b3d5bc31c4b1e1}} * h2spec : {{v1.1.1}} * 68 tests, 48 passed, 1 skipped, 19 failed h4. Details * 3.5. HTTP/2 Connection Preface ** ✓ Sends invalid connection preface * 4.2. Frame Size ** ✓ Sends large size frame that exceeds the SETTINGS_MAX_FRAME_SIZE * 4.3. Header Compression and Decompression ** ✓ Sends invalid header block fragment * 5.1. Stream States ** ✓ idle: Sends a DATA frame ** × idle: Sends a RST_STREAM frame ** × idle: Sends a WINDOW_UPDATE frame ** ✓ idle: Sends a CONTINUATION frame ** ✓ half closed (remote): Sends a DATA frame ** × half closed (remote): Sends a HEADERS frame ** ✓ half closed (remote): Sends a CONTINUATION frame ** × closed: Sends a CONTINUATION frame ** 5.1.1. Stream Identifiers *** ✓ Sends even-numbered stream identifier ** 5.1.2. Stream Concurrency *** Skipped: SETTINGS_MAX_CONCURRENT_STREAMS is unlimited * 5.3. Stream Priority ** 5.3.1. Stream Dependencies *** × Sends HEADERS frame that depend on itself *** ✓ Sends PRIORITY frame that depend on itself * 5.4. Error Handling ** 5.4.1. Connection Error Handling *** × Receives a GOAWAY frame * 5.5. Extending HTTP/2 ** ✓ Sends an unknown extension frame ** × Sends an unknown extension frame in the middle of a header block * 6.1. DATA ** ✓ Sends a DATA frame with 0x0 stream identifier ** ✓ Sends a DATA frame on the stream that is not opend ** ✓ Sends a DATA frame with invalid pad length * 6.2. HEADERS ** ✓ Sends a HEADERS frame followed by any frame other than CONTINUATION ** ✓ Sends a HEADERS frame followed by a frame on a different stream ** ✓ Sends a HEADERS frame with 0x0 stream identifier ** ✓ Sends a HEADERS frame with invalid pad length * 6.3. PRIORITY ** ✓ Sends a PRIORITY frame with 0x0 stream identifier ** ✓ Sends a PRIORITY frame with a length other than 5 octets * 6.4. RST_STREAM ** ✓ Sends a RST_STREAM frame with 0x0 stream identifier ** × Sends a RST_STREAM frame on a idle stream ** ✓ Sends a RST_STREAM frame with a length other than 4 octets * 6.5. SETTINGS ** ✓ Sends a SETTINGS frame ** ✓ Sends a SETTINGS frame that is not a zero-length with ACK flag ** ✓ Sends a SETTINGS frame with the stream identifier that is not 0x0 ** × Sends a SETTINGS frame with a length other than a multiple of 6 octets ** 6.5.2. Defined SETTINGS Parameters *** ✓ SETTINGS_ENABLE_PUSH (0x2): Sends the value other than 0 or 1 *** ✓ SETTINGS_INITIAL_WINDOW_SIZE (0x4): Sends the value above the maximum flow control window size *** ✓ SETTINGS_MAX_FRAME_SIZE (0x5): Sends the value below the initial value *** ✓ SETTINGS_MAX_FRAME_SIZE (0x5): Sends the value above the maximum allowed frame size * 6.7. PING ** ✓ Sends a PING frame ** ✓ Sends a PING frame with the stream identifier that is not 0x0 ** ✓ Sends a PING frame with a length field value other than 8 * 6.8. GOAWAY ** ✓ Sends a GOAWAY frame with the stream identifier that is not 0x0 * 6.9. WINDOW_UPDATE ** ✓ Sends a WINDOW_UPDATE frame ** ✓ Sends a WINDOW_UPDATE frame with an flow control window increment of 0 ** ✓ Sends a WINDOW_UPDATE frame with an flow control window increment of 0 on a stream ** ✓ Sends a WINDOW_UPDATE frame with a length other than a multiple of 4 octets ** 6.9.1. The Flow Control Window *** × Sends multiple WINDOW_UPDATE frames on a connection increasing the flow control window to above 2^31-1 *** × Sends multiple WINDOW_UPDATE frames on a stream increasing the flow control window to above 2^31-1 ** 6.9.2. Initial Flow Control Window Size *** ✓ Sends a SETTINGS_INITIAL_WINDOW_SIZE settings with an exceeded maximum window size value * 6.10. CONTINUATION ** × Sends a CONTINUATION frame ** × Sends multiple CONTINUATION frames ** × Sends a CONTINUATION frame followed by any frame other than CONTINUATION ** × Sends a CONTINUATION frame followed by a frame on a different stream ** × Sends a CONTINUATION frame with the stream identifier that is 0x0 * 8.1. HTTP Request/Response Exchange ** × Sends a HEADERS frame containing trailer part ** 8.1.2. HTTP Header Fields *** 8.1.2.2. Connection-Specific Header Fields × Sends a HEADERS frame that contains the connection-specific header field was: This is an umbrella ticket for testing HTTP/2 features of ATS by [h2spec|https://github.com/summerwind/h2spec]. Our goal : passing all tests. h3. Status * 3.5. HTTP/2 Connection Preface ** ✓ Sends invalid connection preface * 4.2. Frame Size ** ✓ Sends large size frame that exceeds the SETTINGS_MAX_FRAME_SIZE * 4.3. Header Compression and Decompression ** ✓ Sends invalid header block fragment * 5.1. Stream States ** ✓ idle: Sends a DATA frame ** × idle: Sends a RST_STREAM frame ** ×
[jira] [Updated] (TS-3575) Make an option for traffic_layout to reproduce the configure invocation
[ https://issues.apache.org/jira/browse/TS-3575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3575: -- Fix Version/s: (was: 6.1.0) 6.0.0 Make an option for traffic_layout to reproduce the configure invocation --- Key: TS-3575 URL: https://issues.apache.org/jira/browse/TS-3575 Project: Traffic Server Issue Type: Improvement Components: CI, Tools Reporter: Leif Hedstrom Assignee: Leif Hedstrom Fix For: 6.0.0 Basically have it echo out the equivalent of what is in config.nice. This will be useful not only for someone to check the build, but our tsqa tool can then use that to decide what tests are suitable for the run. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-3801) Correct responses when CLOSED stream receive frames.
[ https://issues.apache.org/jira/browse/TS-3801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14648784#comment-14648784 ] ASF GitHub Bot commented on TS-3801: Github user masaori335 closed the pull request at: https://github.com/apache/trafficserver/pull/264 Correct responses when CLOSED stream receive frames. Key: TS-3801 URL: https://issues.apache.org/jira/browse/TS-3801 Project: Traffic Server Issue Type: Bug Components: HTTP/2 Reporter: Masaori Koshiba Assignee: Masaori Koshiba RFC 7540 says below in 5.1. Stream States. {quote} Similarly, an endpoint that receives any frames after receiving a frame with the END_STREAM flag set MUST treat that as a connection error (Section 5.4.1) of type STREAM_CLOSED, unless the frame is permitted as described below. WINDOW_UPDATE or RST_STREAM frames can be received in this state for a short period after a DATA or HEADERS frame containing an END_STREAM flag is sent. {quote} But ATS dosen't return {{STREAM_CLOSED}} when ATS receives {{DATA}}, {{HEADERS}} and {{CONTINUATION}} frames. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-3801) Correct responses when CLOSED stream receive frames.
[ https://issues.apache.org/jira/browse/TS-3801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14648782#comment-14648782 ] Masaori Koshiba commented on TS-3801: - [~zwoop] yes we should land for 6.0.0. After rebased latest master branch, I got SEGV with my patch. I'm going to fix it and reopen the Pull-Request. Correct responses when CLOSED stream receive frames. Key: TS-3801 URL: https://issues.apache.org/jira/browse/TS-3801 Project: Traffic Server Issue Type: Bug Components: HTTP/2 Reporter: Masaori Koshiba Assignee: Masaori Koshiba RFC 7540 says below in 5.1. Stream States. {quote} Similarly, an endpoint that receives any frames after receiving a frame with the END_STREAM flag set MUST treat that as a connection error (Section 5.4.1) of type STREAM_CLOSED, unless the frame is permitted as described below. WINDOW_UPDATE or RST_STREAM frames can be received in this state for a short period after a DATA or HEADERS frame containing an END_STREAM flag is sent. {quote} But ATS dosen't return {{STREAM_CLOSED}} when ATS receives {{DATA}}, {{HEADERS}} and {{CONTINUATION}} frames. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-3141) Port number in host header breaks ATS remap
[ https://issues.apache.org/jira/browse/TS-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14647906#comment-14647906 ] Thomas Jackson commented on TS-3141: Well, even in that case (with the VIP) the reals now have to configure everything as real-ACTUAL_DOMAIN. I wonder if it'd be better for us to just make some option to strip out the ports from the host header :/ I can see that doing it generally might be problematic, but for our particular case (which I imagine isn't unique) is a bit odd to say the least ;) Port number in host header breaks ATS remap --- Key: TS-3141 URL: https://issues.apache.org/jira/browse/TS-3141 Project: Traffic Server Issue Type: Bug Reporter: Thomas Jackson Assignee: Brian Geffon Labels: newbie Fix For: 6.1.0 If someone adds port 80 (lets say) to the host header of a request, ATS remap fails {code} [thjackso@thjackso-ld ~]$ curl -I -4k -H 'Host: www.ogre.com:80' https://www.ogre.com HTTP/1.1 404 Not Found on Accelerator Date: Thu, 16 Oct 2014 21:14:02 GMT Connection: keep-alive Via: https/1.1 cosmo.ogre.com (ApacheTrafficServer/5.2.0 [c s f ]) Server: ATS/5.2.0 Cache-Control: no-store Content-Type: text/html Content-Language: en Content-Length: 297 {code} Although if you set the port to 443 it seems to work fine {code} [thjackso@thjackso-ld ~]$ curl -I -4k -H 'Host: www.ogre.com:443' https://www.ogre.com HTTP/1.1 200 OK Date: Thu, 16 Oct 2014 21:15:09 GMT Server: ATS/5.2.0 X-Drupal-Cache: MISS Expires: Sun, 19 Nov 1978 05:00:00 GMT Last-Modified: Thu, 16 Oct 2014 21:15:09 + Cache-Control: public, max-age=300 Content-Language: en X-Generator: Drupal 7 (http://drupal.org) Vary: Cookie Content-Type: text/html; charset=utf-8 Age: 0 Connection: keep-alive Via: http/1.1 cosmo.ogre.com (ApacheTrafficServer/5.2.0 [cMsSf ]) {code} In addition I can send a host header with 443 on the http port and I'll get similar behavior. This leads me to believe that if you set the port to anything that isn't the default for the schema you are connecting on it fails remap (url looks like https:/// in the logs). I would think that the port in the host header would be completely ignored right? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Build failed in Jenkins: tsqa-master #745
See https://ci.trafficserver.apache.org/job/tsqa-master/745/changes Changes: [Leif Hedstrom] [TS-3476] Add a log tag for application protocol (add docs) -- [...truncated 514 lines...] INFO 2015-07-30 17:23:23,258 - sending data back to the client INFO 2015-07-30 17:23:27,263 - sending data back to the client ok test_chunked_keepalive_server (test_chunked.TestChunked) ... INFO 2015-07-30 17:23:31,268 - sending data back to the client INFO 2015-07-30 17:23:34,273 - sending data back to the client ok Test that the origin does in fact support keepalive ... INFO 2015-07-30 17:23:35,277 - sending data back to the client INFO 2015-07-30 17:23:38,282 - sending data back to the client INFO 2015-07-30 17:23:39,285 - sending data back to the client INFO 2015-07-30 17:23:41,286 - Client disconnected INFO 2015-07-30 17:23:41,686 - sending data back to the client INFO 2015-07-30 17:23:42,088 - sending data back to the client INFO 2015-07-30 17:23:44,089 - Client disconnected INFO 2015-07-30 17:23:46,091 - sending data back to the client ok INFO 2015-07-30 17:23:48,101 - Client disconnected INFO 2015-07-30 17:23:48,296 - Environment prefix is /tmp/tsqa.env.XzED0W INFO 2015-07-30 17:23:50,096 - Client disconnected Verify that we get 502s from an origin which just did a bind ... ok Verify that we get 200s from origins that delayed_accept_after_connect ... ok Verify that we get 504s from origins that die_on_connect ... ok Verify that we get 502s from origins that bind + listen ... ok Verify that we get 504s from origins that return a partial_response ... FAIL Verify that we get 200s from origins that reset_after_accept ... FAIL INFO 2015-07-30 17:23:58,594 - Environment prefix is /tmp/tsqa.env.WOATAp test_log_field (test_custom_log.TestCustomLogField) ... ok INFO 2015-07-30 17:25:42,107 - Environment prefix is /tmp/tsqa.env.ueXFyE test_default_404 (test_example.TestBootstrap) ... ok Test that traffic_line works, and verify that the values for proxy.config ... ok INFO 2015-07-30 17:26:11,935 - Starting build (1b6c9541459e058351cd39ec55dcb772): configure {'enable-spdy': None, 'enable-ccache': None, 'enable-experimental-plugins': None, 'enable-example-plugins': None, 'enable-test-tools': None, 'disable-dependency-tracking': None} INFO 2015-07-30 17:27:05,672 - Build completed (1b6c9541459e058351cd39ec55dcb772): configure {'enable-spdy': None, 'enable-ccache': None, 'enable-experimental-plugins': None, 'enable-example-plugins': None, 'enable-test-tools': None, 'disable-dependency-tracking': None} INFO 2015-07-30 17:27:05,737 - Environment prefix is /tmp/tsqa.env.IKLa0A test_spdy (test_example.TestConfigureFlags) ... ok INFO 2015-07-30 17:27:09,144 - Environment prefix is /tmp/tsqa.env.8Hj0L7 test_basic_proxy (test_example.TestDynamicHTTPEndpointCase) ... 127.0.0.1 - - [30/Jul/2015 17:27:12] GET /test HTTP/1.1 404 0 ok INFO 2015-07-30 17:27:12,559 - Environment prefix is /tmp/tsqa.env.DzuWG9 test_logs_exist (test_example.TestLogRefCounting) ... 127.0.0.1 - - [30/Jul/2015 17:27:15] GET / HTTP/1.1 404 0 127.0.0.1 - - [30/Jul/2015 17:27:15] GET / HTTP/1.1 404 0 127.0.0.1 - - [30/Jul/2015 17:27:15] GET / HTTP/1.1 404 0 127.0.0.1 - - [30/Jul/2015 17:27:15] GET / HTTP/1.1 404 0 127.0.0.1 - - [30/Jul/2015 17:27:15] GET / HTTP/1.1 404 0 127.0.0.1 - - [30/Jul/2015 17:27:15] GET / HTTP/1.1 404 0 127.0.0.1 - - [30/Jul/2015 17:27:15] GET / HTTP/1.1 404 0 127.0.0.1 - - [30/Jul/2015 17:27:15] GET / HTTP/1.1 404 0 127.0.0.1 - - [30/Jul/2015 17:27:15] GET / HTTP/1.1 404 0 127.0.0.1 - - [30/Jul/2015 17:27:15] GET / HTTP/1.1 404 0 FAIL INFO 2015-07-30 17:27:26,045 - Environment prefix is /tmp/tsqa.env.UV7yoW test_logs_exist (test_example.TestLogs) ... FAIL SKIP: Skip the entire class INFO 2015-07-30 17:27:39,480 - Environment prefix is /tmp/tsqa.env.rnetE5 test_basic_intercept (test_example.TestServerIntercept) ... 127.0.0.1 - - [30/Jul/2015 17:27:42] GET / HTTP/1.1 200 5 127.0.0.1 - - [30/Jul/2015 17:27:42] GET / HTTP/1.1 200 5 127.0.0.1 - - [30/Jul/2015 17:27:42] GET / HTTP/1.1 200 5 127.0.0.1 - - [30/Jul/2015 17:27:42] GET / HTTP/1.1 200 5 127.0.0.1 - - [30/Jul/2015 17:27:42] GET / HTTP/1.1 200 5 127.0.0.1 - - [30/Jul/2015 17:27:42] GET / HTTP/1.1 200 5 127.0.0.1 - - [30/Jul/2015 17:27:42] GET / HTTP/1.1 200 5 127.0.0.1 - - [30/Jul/2015 17:27:42] GET / HTTP/1.1 200 5 127.0.0.1 - - [30/Jul/2015 17:27:42] GET / HTTP/1.1 200 5 127.0.0.1 - - [30/Jul/2015 17:27:42] GET / HTTP/1.1 200 5 ok INFO 2015-07-30 17:27:42,952 - Environment prefix is /tmp/tsqa.env.Neis7I test_lookup_timeout (test_hostdb.TestHostDBFailedDNS) ... ok INFO 2015-07-30 17:27:48,378 - Environment prefix is /tmp/tsqa.env.PAhjKX Test basic fnctionality of hosts files ... ok Test that changes to hosts file get loaded within host_file.interval ... ok INFO 2015-07-30 17:27:57,850 - Environment prefix is /tmp/tsqa.env.F6YzXT SKIP: begin captured logging root: INFO: Environment prefix is
[jira] [Commented] (TS-3806) In cmd/traffic_manager: libwccp.a(WccpMsg.o): undefined reference to symbol MD5_Final
[ https://issues.apache.org/jira/browse/TS-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14648667#comment-14648667 ] ASF subversion and git services commented on TS-3806: - Commit 35f11dd5aab06364547d423e26b3d5bc31c4b1e1 in trafficserver's branch refs/heads/master from [~sodabrew] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=35f11dd ] TS-3806 Resolve undefined reference to symbol MD5_Final This is similar to TS-3632 This closes #266 In cmd/traffic_manager: libwccp.a(WccpMsg.o): undefined reference to symbol MD5_Final - Key: TS-3806 URL: https://issues.apache.org/jira/browse/TS-3806 Project: Traffic Server Issue Type: Bug Components: Build Affects Versions: 5.3.1 Reporter: Aaron Stone Assignee: Jean Baptiste Favre Fix For: 6.0.0 When building ATS 5.3.0 on Ubuntu 11.04[1,2] a linking failure occurs because of the ordering of the libraries: {code} libtool: link: c++ -g -O2 -fPIE -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -pipe -Wall -feliminate-unused-debug-symbols -fno-strict-aliasing -Wno-invalid-offsetof -mcx16 -rdynamic -Wl,-Bsymbolic-functions -fPIE -pie -Wl,-z -Wl,relro -Wl,-z -Wl,now -o .libs/traffic_manager AddConfigFilesHere.o traffic_manager.o StatProcessor.o StatType.o StatXML.o ../../mgmt/web2/libweb.a ../../mgmt/api/.libs/libmgmtapilocal.a /«PKGBUILDDIR»/lib/ts/.libs/libtsutil.so -lssl -lcrypto -L/usr/lib ../../mgmt/.libs/libmgmt_lm.a ../../proxy/hdrs/libhdrs.a ../../lib/records/librecords_lm.a ../../lib/ts/.libs/libtsutil.so ../../iocore/eventsystem/libinkevent.a ../../proxy/shared/liberror.a ../../proxy/shared/libdiagsconfig.a -lresolv -ltcl8.5 -lhwloc -lm ../../lib/wccp/libwccp.a ../../lib/tsconfig/.libs/libtsconfig.so -lcap -lpcre -lz -lcrypt -lpthread -lrt -ldl /usr/lib/x86_64-linux-gnu/libxml2.so -Wl,-rpath -Wl,/usr/lib/trafficserver /usr/bin/ld: ../../lib/wccp/libwccp.a(WccpMsg.o): undefined reference to symbol 'MD5_Final@@OPENSSL_1.0.0' /usr/bin/ld: note: 'MD5_Final@@OPENSSL_1.0.0' is defined in DSO /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libcrypto.so so try adding it to the linker command line /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libcrypto.so: could not read symbols: Invalid operation collect2: ld returned 1 exit status make[3]: *** [traffic_manager] Error 1 make[3]: Leaving directory `/«PKGBUILDDIR»/cmd/traffic_manager' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/«PKGBUILDDIR»/cmd' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/«PKGBUILDDIR»' dh_auto_build: make -j1 returned exit code 2 make: *** [binary-arch] Error 2 {code} [1] https://wiki.debian.org/ToolChain/DSOLinking#Only_link_with_needed_libraries [2] https://wiki.ubuntu.com/NattyNarwhal/ToolchainTransition -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-3806) In cmd/traffic_manager: libwccp.a(WccpMsg.o): undefined reference to symbol MD5_Final
[ https://issues.apache.org/jira/browse/TS-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14648669#comment-14648669 ] ASF GitHub Bot commented on TS-3806: Github user asfgit closed the pull request at: https://github.com/apache/trafficserver/pull/266 In cmd/traffic_manager: libwccp.a(WccpMsg.o): undefined reference to symbol MD5_Final - Key: TS-3806 URL: https://issues.apache.org/jira/browse/TS-3806 Project: Traffic Server Issue Type: Bug Components: Build Affects Versions: 5.3.1 Reporter: Aaron Stone Assignee: Jean Baptiste Favre Fix For: 6.0.0 When building ATS 5.3.0 on Ubuntu 11.04[1,2] a linking failure occurs because of the ordering of the libraries: {code} libtool: link: c++ -g -O2 -fPIE -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -pipe -Wall -feliminate-unused-debug-symbols -fno-strict-aliasing -Wno-invalid-offsetof -mcx16 -rdynamic -Wl,-Bsymbolic-functions -fPIE -pie -Wl,-z -Wl,relro -Wl,-z -Wl,now -o .libs/traffic_manager AddConfigFilesHere.o traffic_manager.o StatProcessor.o StatType.o StatXML.o ../../mgmt/web2/libweb.a ../../mgmt/api/.libs/libmgmtapilocal.a /«PKGBUILDDIR»/lib/ts/.libs/libtsutil.so -lssl -lcrypto -L/usr/lib ../../mgmt/.libs/libmgmt_lm.a ../../proxy/hdrs/libhdrs.a ../../lib/records/librecords_lm.a ../../lib/ts/.libs/libtsutil.so ../../iocore/eventsystem/libinkevent.a ../../proxy/shared/liberror.a ../../proxy/shared/libdiagsconfig.a -lresolv -ltcl8.5 -lhwloc -lm ../../lib/wccp/libwccp.a ../../lib/tsconfig/.libs/libtsconfig.so -lcap -lpcre -lz -lcrypt -lpthread -lrt -ldl /usr/lib/x86_64-linux-gnu/libxml2.so -Wl,-rpath -Wl,/usr/lib/trafficserver /usr/bin/ld: ../../lib/wccp/libwccp.a(WccpMsg.o): undefined reference to symbol 'MD5_Final@@OPENSSL_1.0.0' /usr/bin/ld: note: 'MD5_Final@@OPENSSL_1.0.0' is defined in DSO /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libcrypto.so so try adding it to the linker command line /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libcrypto.so: could not read symbols: Invalid operation collect2: ld returned 1 exit status make[3]: *** [traffic_manager] Error 1 make[3]: Leaving directory `/«PKGBUILDDIR»/cmd/traffic_manager' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/«PKGBUILDDIR»/cmd' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/«PKGBUILDDIR»' dh_auto_build: make -j1 returned exit code 2 make: *** [binary-arch] Error 2 {code} [1] https://wiki.debian.org/ToolChain/DSOLinking#Only_link_with_needed_libraries [2] https://wiki.ubuntu.com/NattyNarwhal/ToolchainTransition -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-3632) libwccp.a(WccpMsg.o): undefined reference to symbol MD5_Final
[ https://issues.apache.org/jira/browse/TS-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14648668#comment-14648668 ] ASF subversion and git services commented on TS-3632: - Commit 35f11dd5aab06364547d423e26b3d5bc31c4b1e1 in trafficserver's branch refs/heads/master from [~sodabrew] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=35f11dd ] TS-3806 Resolve undefined reference to symbol MD5_Final This is similar to TS-3632 This closes #266 libwccp.a(WccpMsg.o): undefined reference to symbol MD5_Final - Key: TS-3632 URL: https://issues.apache.org/jira/browse/TS-3632 Project: Traffic Server Issue Type: Bug Components: Build Affects Versions: 5.3.0 Reporter: Igor Galić Assignee: Jean Baptiste Favre Fix For: 5.3.1, 6.0.0 When building ATS 5.3.0 on Ubuntu 11.04[1,2] a linking failure occurs because of the ordering of the libraries: {code} libtool: link: c++ -g -O2 -fPIE -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -pipe -Wall -feliminate-unused-debug-symbols -fno-strict-aliasing -Wno-invalid-offsetof -mcx16 -rdynamic -Wl,-Bsymbolic-functions -fPIE -pie -Wl,-z -Wl,relro -Wl,-z -Wl,now -o .libs/traffic_manager AddConfigFilesHere.o traffic_manager.o StatProcessor.o StatType.o StatXML.o ../../mgmt/web2/libweb.a ../../mgmt/api/.libs/libmgmtapilocal.a /«PKGBUILDDIR»/lib/ts/.libs/libtsutil.so -lssl -lcrypto -L/usr/lib ../../mgmt/.libs/libmgmt_lm.a ../../proxy/hdrs/libhdrs.a ../../lib/records/librecords_lm.a ../../lib/ts/.libs/libtsutil.so ../../iocore/eventsystem/libinkevent.a ../../proxy/shared/liberror.a ../../proxy/shared/libdiagsconfig.a -lresolv -ltcl8.5 -lhwloc -lm ../../lib/wccp/libwccp.a ../../lib/tsconfig/.libs/libtsconfig.so -lcap -lpcre -lz -lcrypt -lpthread -lrt -ldl /usr/lib/x86_64-linux-gnu/libxml2.so -Wl,-rpath -Wl,/usr/lib/trafficserver /usr/bin/ld: ../../lib/wccp/libwccp.a(WccpMsg.o): undefined reference to symbol 'MD5_Final@@OPENSSL_1.0.0' /usr/bin/ld: note: 'MD5_Final@@OPENSSL_1.0.0' is defined in DSO /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libcrypto.so so try adding it to the linker command line /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libcrypto.so: could not read symbols: Invalid operation collect2: ld returned 1 exit status make[3]: *** [traffic_manager] Error 1 make[3]: Leaving directory `/«PKGBUILDDIR»/cmd/traffic_manager' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/«PKGBUILDDIR»/cmd' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/«PKGBUILDDIR»' dh_auto_build: make -j1 returned exit code 2 make: *** [binary-arch] Error 2 {code} [1] https://wiki.debian.org/ToolChain/DSOLinking#Only_link_with_needed_libraries [2] https://wiki.ubuntu.com/NattyNarwhal/ToolchainTransition -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-3808) ☂Testing HTTP/2 features by h2spec
[ https://issues.apache.org/jira/browse/TS-3808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masaori Koshiba updated TS-3808: Summary: ☂Testing HTTP/2 features by h2spec (was: Testing HTTP/2 features by h2spec) ☂Testing HTTP/2 features by h2spec --- Key: TS-3808 URL: https://issues.apache.org/jira/browse/TS-3808 Project: Traffic Server Issue Type: Test Components: HTTP/2 Reporter: Masaori Koshiba Labels: Umbrella This is an umbrella ticket for testing HTTP/2 features of ATS by [h2spec|https://github.com/summerwind/h2spec]. Our goal : passing all tests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-3803) CID 1313321 CID 1313322: HostDB memory issues
[ https://issues.apache.org/jira/browse/TS-3803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14648641#comment-14648641 ] ASF subversion and git services commented on TS-3803: - Commit f0e395f598ee6f4bc5c69db5ac9186a9c2f77787 in trafficserver's branch refs/heads/6.0.x from [~zwoop] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=f0e395f ] Merge branch 'master' into 6.0.x * master: TS-3807: Remove legacy log splitting code and docs. TS-3749: Re-enable error log. TS-3492 Only send SETTINGS which are different than protocol defaults TS-3766 Ignore unknown frame in debugging [TS-3476] Add a log tag for application protocol (add docs) Revert TS-3752: Problem with larger headers and HTTP/2 TS-3800: Fix bug in hostdb ui related to missing query TS-3803: CID 1313322 CID 1313322: HostDB memory issues (introduced in TS-3800) CID 1313321 CID 1313322: HostDB memory issues - Key: TS-3803 URL: https://issues.apache.org/jira/browse/TS-3803 Project: Traffic Server Issue Type: Bug Components: HostDB Reporter: Leif Hedstrom Assignee: Brian Geffon Fix For: 6.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-3800) Improve HostDB UI output
[ https://issues.apache.org/jira/browse/TS-3800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14648642#comment-14648642 ] ASF subversion and git services commented on TS-3800: - Commit f0e395f598ee6f4bc5c69db5ac9186a9c2f77787 in trafficserver's branch refs/heads/6.0.x from [~zwoop] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=f0e395f ] Merge branch 'master' into 6.0.x * master: TS-3807: Remove legacy log splitting code and docs. TS-3749: Re-enable error log. TS-3492 Only send SETTINGS which are different than protocol defaults TS-3766 Ignore unknown frame in debugging [TS-3476] Add a log tag for application protocol (add docs) Revert TS-3752: Problem with larger headers and HTTP/2 TS-3800: Fix bug in hostdb ui related to missing query TS-3803: CID 1313322 CID 1313322: HostDB memory issues (introduced in TS-3800) Improve HostDB UI output Key: TS-3800 URL: https://issues.apache.org/jira/browse/TS-3800 Project: Traffic Server Issue Type: Improvement Components: Core, HostDB Reporter: Brian Geffon Assignee: Brian Geffon Fix For: 6.0.0 This ticket will track a few changes to HostDB UI which will improve the output including: - better viewall output - better srv record output - ability to output data in json format. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-3808) ☂ Testing HTTP/2 features by h2spec
[ https://issues.apache.org/jira/browse/TS-3808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masaori Koshiba updated TS-3808: Summary: ☂ Testing HTTP/2 features by h2spec (was: ☂Testing HTTP/2 features by h2spec) ☂ Testing HTTP/2 features by h2spec Key: TS-3808 URL: https://issues.apache.org/jira/browse/TS-3808 Project: Traffic Server Issue Type: Test Components: HTTP/2 Reporter: Masaori Koshiba Labels: Umbrella This is an umbrella ticket for testing HTTP/2 features of ATS by [h2spec|https://github.com/summerwind/h2spec]. Our goal : passing all tests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)