[jira] [Commented] (TS-1411) Seg fault when using %cquuc
[
https://issues.apache.org/jira/browse/TS-1411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13799832#comment-13799832
]
Zhao Yongming commented on TS-1411:
---
yeah, I mean TS-1988
Seg fault when using %cquuc
-
Key: TS-1411
URL: https://issues.apache.org/jira/browse/TS-1411
Project: Traffic Server
Issue Type: Bug
Components: Logging
Affects Versions: 3.2.0
Environment: RHEL 6.2 x86_64
Reporter: David Carlin
Assignee: Yunkai Zhang
Priority: Critical
Fix For: 4.2.0
Attachments: Log rotation segaults.txt, TS-1411 backtraces.txt
I've been experiencing some segfaults during log rotation. The sequence of
events is this.. log rotation occurs, then I get hundreds of dropping log
buffer error msgs, then the segfault.
This started occurring when I lengthened the default log format to include
the unmapped URL and the user agent string:
%cqtq %ttms %chi %crc/%pssc %psql %cqhm %cquc %caun
%phr/%pqsn %psct %xid %cquuc \%{User-Agent}cqh\
In terms of frequency, we have a number of boxes and I probably see one of
these crashed per day since the above change. Logs are rotated every 2 hours.
I've had other log related segfaults, reported in TS-1330 - these new ones
seem to have a different cause.
[Aug 14 21:07:20.002] Server {0x2ae3a8887700} STATUS: The rolled logfile,
/home/y/logs/trafficserver/error.log_l30.ycs.a4e.yahoo.com.20120814.17h59m50s-20120814.20h00m00s.old,
was auto-deleted; 3148252 bytes were reclaimed.
[Aug 14 21:07:42.859] Server {0x2ae3a8887700} STATUS: The rolled logfile,
/home/y/logs/trafficserver/squid.blog_l30.ycs.a4e.yahoo.com.20120814.18h00m00s-20120814.20h00m00s.old,
was auto-deleted; 14735520048 bytes were reclaimed.
[Aug 14 21:07:42.865] Server {0x2ae3a8887700} WARNING: Dropping log buffer,
can't keep up.
[Aug 14 21:07:42.865] Server {0x2ae3a8887700} WARNING: Dropping log buffer,
can't keep up.
[Aug 14 21:07:42.865] Server {0x2ae3a8887700} WARNING: Dropping log buffer,
can't keep up.
[Aug 14 21:07:42.865] Server {0x2ae3a8887700} WARNING: Dropping log buffer,
can't keep up.
[Aug 14 21:07:42.865] Server {0x2ae3a8887700} WARNING: Dropping log buffer,
can't keep up.
[...]
[Aug 14 21:07:42.876] Server {0x2ae3a8887700} WARNING: Dropping log buffer,
can't keep up.
[Aug 14 21:07:42.876] Server {0x2ae3a8887700} WARNING: Dropping log buffer,
can't keep up.
[Aug 14 21:07:42.876] Server {0x2ae3a8887700} WARNING: Dropping log buffer,
can't keep up.
[Aug 14 21:07:42.876] Server {0x2ae3a8887700} WARNING: Dropping log buffer,
can't keep up.
NOTE: Traffic Server received Sig 11: Segmentation fault
/home/y/bin/traffic_server - STACK TRACE:
/lib64/libpthread.so.0[0x383f00f500]
/home/y/bin/traffic_server(_ZN9LogAccess11marshal_memEPcPKcii+0x48)[0x58a118]
/home/y/bin/traffic_server(_ZN13LogAccessHttp28marshal_client_req_url_canonEPc+0x20)[0x58c3f0]
/home/y/bin/traffic_server(_ZN12LogFieldList7marshalEP9LogAccessPc+0x32)[0x59d5a2]
/home/y/bin/traffic_server(_ZN9LogObject3logEP9LogAccessPc+0x399)[0x5a7ed9]
/home/y/bin/traffic_server(_ZN3Log6accessEP9LogAccess+0x146)[0x58f506]
/home/y/bin/traffic_server(_ZN6HttpSM12update_statsEv+0x630)[0x526c50]
/home/y/bin/traffic_server(_ZN6HttpSM9kill_thisEv+0x928)[0x52b548]
/home/y/bin/traffic_server(_ZN6HttpSM12main_handlerEiPv+0x198)[0x52b868]
/home/y/bin/traffic_server(_ZN10HttpTunnel12main_handlerEiPv+0xde)[0x56c3ee]
/home/y/bin/traffic_server[0x673871]
/home/y/bin/traffic_server(_Z15write_to_net_ioP10NetHandlerP18UnixNetVConnectionP7EThread+0x847)[0x6756e7]
/home/y/bin/traffic_server(_ZN10NetHandler12mainNetEventEiP5Event+0x286)[0x66e076]
/home/y/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0xb4)[0x696ce4]
/home/y/bin/traffic_server(_ZN7EThread7executeEv+0x4c3)[0x697673]
/home/y/bin/traffic_server[0x695cb2]
/lib64/libpthread.so.0[0x383f007851]
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Created] (TS-2289) Only support AIO_MODE_THREAD and AIO_MODE_NATIVE
Leif Hedstrom created TS-2289: - Summary: Only support AIO_MODE_THREAD and AIO_MODE_NATIVE Key: TS-2289 URL: https://issues.apache.org/jira/browse/TS-2289 Project: Traffic Server Issue Type: Improvement Components: Core Reporter: Leif Hedstrom As discussed, we'd like to simplify this code, and only keep our own AIO and the linux native AIO implementations. That would leave AIO_MODE_THREAD and AIO_MODE_NATIVE. Also, I think it's pretty unfortunate that AIO_MODE_NATIVE has to escape encapsulation and have custom code in e.g. Cache.cc. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (TS-2280) C++ API build failure on OS X
[
https://issues.apache.org/jira/browse/TS-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-2280:
--
Fix Version/s: 4.1.0
C++ API build failure on OS X
-
Key: TS-2280
URL: https://issues.apache.org/jira/browse/TS-2280
Project: Traffic Server
Issue Type: Bug
Components: Portability, TS API
Reporter: James Peach
Assignee: Brian Geffon
Fix For: 4.1.0
The new C++ API fails to build on OS X. Looks like an include path issue.
FWIW, there is {{build/plugins.mk}} automake fragment that sets build
variables consistently for plugins. That might be helpful here.
{code}
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p...
/Users/jpeach/src/trafficserver.git/build/aux/install-sh -c -d
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether UID '9306' is supported by ustar format... yes
checking whether GID '20' is supported by ustar format... yes
checking how to create a ustar tar archive... gnutar
checking whether make supports nested variables... (cached) yes
checking for chosen layout... TrafficServer
checking build system type... x86_64-apple-darwin13.0.0
checking host system type... x86_64-apple-darwin13.0.0
checking whether to enable debugging... no
checking whether to enable -Werror... no
checking whether to enable fast SDK APIs... no
checking whether to enable diags... yes
checking whether to enable regression tests... yes
checking whether to enable micro-TS... no
checking whether to build a standalone iocore... no
checking whether to build some static libts (dev only)... no
checking whether to commit cov defects to remote host... localhost
checking whether to enable WCCP v2 support... no
checking whether to enable interim cache support... no
checking whether to enable profiler... no
checking whether to enable eventfd()... yes
checking whether to use POSIX capabilities... auto
checking whether to use hwloc library... yes
checking whether to enable ccache... no
checking whether to enable traffic_cop debugging... no
checking whether to enable TPROXY based transparency... auto
checking whether to disable freelist... yes
checking whether to enable reclaimable freelist...
checking whether to enable experimental plugins... no
checking whether to build c++ api... yes
checking for cc... cc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether cc accepts -g... yes
checking for cc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of cc... gcc3
checking for c++... c++
checking whether we are using the GNU C++ compiler... yes
checking whether c++ accepts -g... yes
checking dependency style of c++... gcc3
checking whether cc understands -c and -o together... yes
checking how to run the C preprocessor... cc -E
checking how to run the C++ preprocessor... c++ -E
checking dependency style of cc... gcc3
checking for C compiler vendor... clang
checking whether c++ supports C++11 features by default... no
checking whether c++ supports C++11 features with -std=c++11... yes
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking unordered_map usability... yes
checking unordered_map presence... yes
checking for unordered_map... yes
checking unordered_set usability... yes
checking unordered_set presence... yes
checking for unordered_set... yes
checking for ext/hash_map... yes
checking for ar... ar
checking the archiver (ar) interface... ar
checking for gawk... (cached) awk
checking for a sed that does not truncate output... /usr/bin/sed
checking whether ln -s works... yes
checking how to print strings... printf
checking for a sed that does not truncate output... (cached) /usr/bin/sed
checking for fgrep... /usr/bin/grep -F
checking for ld used by cc...
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld
checking if the linker
[jira] [Updated] (TS-2279) proxy.config.exec_thread.affinity's values
[
https://issues.apache.org/jira/browse/TS-2279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-2279:
--
Assignee: Igor Galić
proxy.config.exec_thread.affinity's values
--
Key: TS-2279
URL: https://issues.apache.org/jira/browse/TS-2279
Project: Traffic Server
Issue Type: Bug
Components: Configuration
Reporter: Igor Galić
Assignee: Igor Galić
Fix For: 4.1.0
The setting of {{proxy.config.exec_thread.affinity}} only has an affect when
traffic server was compiled with {{\-\-enable-hwloc}}. It has *no* affect at
all, not even a warning about its being ineffectual when setting that value
while trafficserver is *not* configured with {{--enable-hwloc}}.
Further, mgmt/RecordsConfig.cc defines a range of {{[0-1]}}:
{code}
{RECT_CONFIG, proxy.config.exec_thread.affinity, RECD_INT, 0,
RECU_RESTART_TS, RR_NULL, RECC_INT, [0-1], RECA_READ_ONLY}
{code}
but the code uses a range of [0-3]:
{code}
#if TS_USE_HWLOC
if (affinity != 0) {
int logical_ratio;
switch(affinity) {
case 3: // assign threads to logical cores
logical_ratio = 1;
break;
case 2: // assign threads to real cores
logical_ratio = pu / cu;
break;
case 1: // assign threads to sockets
default:
logical_ratio = pu / socket;
}
{code}
And finally, 1 is the default value, rather than issuing a warning about an
incorrect value.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (TS-2275) fix interim cache lossing data if the server process crash
[ https://issues.apache.org/jira/browse/TS-2275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2275: -- Fix Version/s: 4.2.0 fix interim cache lossing data if the server process crash -- Key: TS-2275 URL: https://issues.apache.org/jira/browse/TS-2275 Project: Traffic Server Issue Type: Improvement Components: Cache Reporter: Zhao Yongming Assignee: portl4t Fix For: 4.2.0 the current interim cache device is not permanent storage, it is cleared on each server restart, that is because we do not have a very good solution for the storage consistence. we have a patch under testing for that improvement. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (TS-2275) fix interim cache lossing data if the server process crash
[ https://issues.apache.org/jira/browse/TS-2275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2275: -- Fix Version/s: (was: 4.2.0) fix interim cache lossing data if the server process crash -- Key: TS-2275 URL: https://issues.apache.org/jira/browse/TS-2275 Project: Traffic Server Issue Type: Improvement Components: Cache Reporter: Zhao Yongming Assignee: portl4t the current interim cache device is not permanent storage, it is cleared on each server restart, that is because we do not have a very good solution for the storage consistence. we have a patch under testing for that improvement. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (TS-2139) Twice purge to refresh object form cache when enable-interim-cache
[ https://issues.apache.org/jira/browse/TS-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13799918#comment-13799918 ] Leif Hedstrom commented on TS-2139: --- Moving the open bugs on this issue to be under one ticket. Twice purge to refresh object form cache when enable-interim-cache -- Key: TS-2139 URL: https://issues.apache.org/jira/browse/TS-2139 Project: Traffic Server Issue Type: Bug Components: Cache Reporter: bettydramit Assignee: portl4t Fix For: 4.2.0 Attachments: 0001-fix-purge-twice.patch Centos x86_64 gitmaster and http://people.apache.org/~zwoop/rel-candidates/trafficserver-3.3.5-dev.tar.bz2 when enable enable-interim-cache It muse use twice purge to refresh object form cache my records.config LOCAL proxy.config.cache.interim.storage STRING /dev/vdb Test example: [root@localhost trafficserver]# wget -SO /dev/null -e http_proxy=127.0.0.1 http://www.test.com/ben.bf --2013-08-17 14:45:23-- http://www.test.com/ben.bf Connecting to 127.0.0.1:80... connected. Proxy request sent, awaiting response... HTTP/1.0 200 OK Date: Sat, 17 Aug 2013 06:38:13 GMT Server: ATS/3.3.5-dev Last-Modified: Mon, 08 Jul 2013 15:26:09 GMT ETag: 41d26-103-4e101a9fc2c93 Accept-Ranges: bytes Content-Length: 259 Content-Type: text/plain; charset=UTF-8 Age: 430 Length: 259 [text/plain] Saving to: “/dev/null” 100%[] 259 --.-K/s in 0s 2013-08-17 14:45:23 (38.5 MB/s) - “/dev/null” saved [259/259] [root@localhost trafficserver]# curl -X purge -x 127.0.0.1:80 -v http://www.test.com/ben.bf * About to connect() to proxy 127.0.0.1 port 80 (#0) * Trying 127.0.0.1... connected * Connected to 127.0.0.1 (127.0.0.1) port 80 (#0) purge http://www.test.com/ben.bf HTTP/1.1 User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.14.0.0 zlib/1.2.3 libidn/1.18 libssh2/1.4.2 Host: www.test.com Accept: */* Proxy-Connection: Keep-Alive HTTP/1.1 200 OK Date: Sat, 17 Aug 2013 06:45:28 GMT Proxy-Connection: keep-alive Server: ATS/3.3.5-dev Content-Length: 0 * Connection #0 to host 127.0.0.1 left intact * Closing connection #0 [root@localhost trafficserver]# curl -X purge -x 127.0.0.1:80 -v http://www.test.com/ben.bf * About to connect() to proxy 127.0.0.1 port 80 (#0) * Trying 127.0.0.1... connected * Connected to 127.0.0.1 (127.0.0.1) port 80 (#0) purge http://www.test.com/ben.bf HTTP/1.1 User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.14.0.0 zlib/1.2.3 libidn/1.18 libssh2/1.4.2 Host: www.test.com Accept: */* Proxy-Connection: Keep-Alive HTTP/1.1 200 OK Date: Sat, 17 Aug 2013 06:45:29 GMT Proxy-Connection: keep-alive Server: ATS/3.3.5-dev Content-Length: 0 * Connection #0 to host 127.0.0.1 left intact * Closing connection #0 [root@localhost trafficserver]# curl -X purge -x 127.0.0.1:80 -v http://www.test.com/ben.bf * About to connect() to proxy 127.0.0.1 port 80 (#0) * Trying 127.0.0.1... connected * Connected to 127.0.0.1 (127.0.0.1) port 80 (#0) purge http://www.test.com/ben.bf HTTP/1.1 User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.14.0.0 zlib/1.2.3 libidn/1.18 libssh2/1.4.2 Host: www.test.com Accept: */* Proxy-Connection: Keep-Alive HTTP/1.1 404 Not Found Date: Sat, 17 Aug 2013 06:45:33 GMT Proxy-Connection: keep-alive Server: ATS/3.3.5-dev Content-Length: 0 * Connection #0 to host 127.0.0.1 left intact * Closing connection #0 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (TS-2275) fix interim cache lossing data if the server process crash
[ https://issues.apache.org/jira/browse/TS-2275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom resolved TS-2275. --- Resolution: Duplicate fix interim cache lossing data if the server process crash -- Key: TS-2275 URL: https://issues.apache.org/jira/browse/TS-2275 Project: Traffic Server Issue Type: Improvement Components: Cache Reporter: Zhao Yongming Assignee: portl4t the current interim cache device is not permanent storage, it is cleared on each server restart, that is because we do not have a very good solution for the storage consistence. we have a patch under testing for that improvement. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (TS-2139) Twice purge to refresh object form cache when enable-interim-cache
[ https://issues.apache.org/jira/browse/TS-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2139: -- Fix Version/s: (was: 5.0.0) 4.2.0 Twice purge to refresh object form cache when enable-interim-cache -- Key: TS-2139 URL: https://issues.apache.org/jira/browse/TS-2139 Project: Traffic Server Issue Type: Bug Components: Cache Reporter: bettydramit Assignee: portl4t Fix For: 4.2.0 Attachments: 0001-fix-purge-twice.patch Centos x86_64 gitmaster and http://people.apache.org/~zwoop/rel-candidates/trafficserver-3.3.5-dev.tar.bz2 when enable enable-interim-cache It muse use twice purge to refresh object form cache my records.config LOCAL proxy.config.cache.interim.storage STRING /dev/vdb Test example: [root@localhost trafficserver]# wget -SO /dev/null -e http_proxy=127.0.0.1 http://www.test.com/ben.bf --2013-08-17 14:45:23-- http://www.test.com/ben.bf Connecting to 127.0.0.1:80... connected. Proxy request sent, awaiting response... HTTP/1.0 200 OK Date: Sat, 17 Aug 2013 06:38:13 GMT Server: ATS/3.3.5-dev Last-Modified: Mon, 08 Jul 2013 15:26:09 GMT ETag: 41d26-103-4e101a9fc2c93 Accept-Ranges: bytes Content-Length: 259 Content-Type: text/plain; charset=UTF-8 Age: 430 Length: 259 [text/plain] Saving to: “/dev/null” 100%[] 259 --.-K/s in 0s 2013-08-17 14:45:23 (38.5 MB/s) - “/dev/null” saved [259/259] [root@localhost trafficserver]# curl -X purge -x 127.0.0.1:80 -v http://www.test.com/ben.bf * About to connect() to proxy 127.0.0.1 port 80 (#0) * Trying 127.0.0.1... connected * Connected to 127.0.0.1 (127.0.0.1) port 80 (#0) purge http://www.test.com/ben.bf HTTP/1.1 User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.14.0.0 zlib/1.2.3 libidn/1.18 libssh2/1.4.2 Host: www.test.com Accept: */* Proxy-Connection: Keep-Alive HTTP/1.1 200 OK Date: Sat, 17 Aug 2013 06:45:28 GMT Proxy-Connection: keep-alive Server: ATS/3.3.5-dev Content-Length: 0 * Connection #0 to host 127.0.0.1 left intact * Closing connection #0 [root@localhost trafficserver]# curl -X purge -x 127.0.0.1:80 -v http://www.test.com/ben.bf * About to connect() to proxy 127.0.0.1 port 80 (#0) * Trying 127.0.0.1... connected * Connected to 127.0.0.1 (127.0.0.1) port 80 (#0) purge http://www.test.com/ben.bf HTTP/1.1 User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.14.0.0 zlib/1.2.3 libidn/1.18 libssh2/1.4.2 Host: www.test.com Accept: */* Proxy-Connection: Keep-Alive HTTP/1.1 200 OK Date: Sat, 17 Aug 2013 06:45:29 GMT Proxy-Connection: keep-alive Server: ATS/3.3.5-dev Content-Length: 0 * Connection #0 to host 127.0.0.1 left intact * Closing connection #0 [root@localhost trafficserver]# curl -X purge -x 127.0.0.1:80 -v http://www.test.com/ben.bf * About to connect() to proxy 127.0.0.1 port 80 (#0) * Trying 127.0.0.1... connected * Connected to 127.0.0.1 (127.0.0.1) port 80 (#0) purge http://www.test.com/ben.bf HTTP/1.1 User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.14.0.0 zlib/1.2.3 libidn/1.18 libssh2/1.4.2 Host: www.test.com Accept: */* Proxy-Connection: Keep-Alive HTTP/1.1 404 Not Found Date: Sat, 17 Aug 2013 06:45:33 GMT Proxy-Connection: keep-alive Server: ATS/3.3.5-dev Content-Length: 0 * Connection #0 to host 127.0.0.1 left intact * Closing connection #0 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (TS-2273) test_AIO fail with Linux native AIO
[
https://issues.apache.org/jira/browse/TS-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-2273:
--
Fix Version/s: 4.2.0
test_AIO fail with Linux native AIO
---
Key: TS-2273
URL: https://issues.apache.org/jira/browse/TS-2273
Project: Traffic Server
Issue Type: Bug
Reporter: Zhao Yongming
Fix For: 4.2.0
{code}
test_AIO-test_AIO.o: In function `main':
/var/jenkins/workspace/centos_6.4_x64-master-taobao-regression/iocore/aio/test_AIO.cc:494:
undefined reference to `cache_config_threads_per_disk'
collect2: ld returned 1 exit status
make[3]: *** [test_AIO] Error 1
make[3]: Leaving directory
`/var/jenkins/workspace/centos_6.4_x64-master-taobao-regression/build/centos_6.4_x64-master-taobao-regression.90/iocore/aio'
make[2]: *** [check-am] Error 2
make[2]: Leaving directory
`/var/jenkins/workspace/centos_6.4_x64-master-taobao-regression/build/centos_6.4_x64-master-taobao-regression.90/iocore/aio'
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory
`/var/jenkins/workspace/centos_6.4_x64-master-taobao-regression/build/centos_6.4_x64-master-taobao-regression.90/iocore'
make: *** [check-recursive] Error 1
Build step 'Execute shell' marked build as failure
Finished: FAILURE
{code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (TS-2274) Better initial default configs
[ https://issues.apache.org/jira/browse/TS-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2274: -- Fix Version/s: 4.2.0 Better initial default configs -- Key: TS-2274 URL: https://issues.apache.org/jira/browse/TS-2274 Project: Traffic Server Issue Type: Bug Reporter: Miles Libbey Fix For: 4.2.0 Seems like there are several config values that are not very smart for the newbie user: - cache size: storage.config: var/trafficserver 256M - max object size (though, perhaps this is now unlimited) - read-while-write settings? - 4-5 volumes for the volume config? - CONFIG proxy.config.cache.ram_cache_cutoff INT 4194304 ? Adam Dace in https://cwiki.apache.org/confluence/display/TS/WebProxyCacheSetup suggested several others, but, it looks to me like the settings are very machine specific (eg, specific IP addresses) Others? -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (TS-2289) Only support AIO_MODE_THREAD and AIO_MODE_NATIVE
[ https://issues.apache.org/jira/browse/TS-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2289: -- Fix Version/s: 4.2.0 Only support AIO_MODE_THREAD and AIO_MODE_NATIVE Key: TS-2289 URL: https://issues.apache.org/jira/browse/TS-2289 Project: Traffic Server Issue Type: Improvement Components: Core Reporter: Leif Hedstrom Fix For: 4.2.0 As discussed, we'd like to simplify this code, and only keep our own AIO and the linux native AIO implementations. That would leave AIO_MODE_THREAD and AIO_MODE_NATIVE. Also, I think it's pretty unfortunate that AIO_MODE_NATIVE has to escape encapsulation and have custom code in e.g. Cache.cc. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (TS-2286) Make config files pretty with comments
[ https://issues.apache.org/jira/browse/TS-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2286: -- Fix Version/s: 4.2.0 Make config files pretty with comments -- Key: TS-2286 URL: https://issues.apache.org/jira/browse/TS-2286 Project: Traffic Server Issue Type: Sub-task Reporter: Phil Sorber Assignee: Alan M. Carroll Fix For: 4.2.0 Basically what the summary says. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (TS-2284) Run with no configs
[ https://issues.apache.org/jira/browse/TS-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2284: -- Fix Version/s: 4.2.0 Run with no configs --- Key: TS-2284 URL: https://issues.apache.org/jira/browse/TS-2284 Project: Traffic Server Issue Type: Sub-task Reporter: Phil Sorber Fix For: 4.2.0 In addition to running with empty configs (TS-2282), we should be able to run with no configs and not write them out (TS-2283). -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (TS-2287) Create a Wiki page to document the design
[ https://issues.apache.org/jira/browse/TS-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2287: -- Fix Version/s: 4.2.0 Create a Wiki page to document the design - Key: TS-2287 URL: https://issues.apache.org/jira/browse/TS-2287 Project: Traffic Server Issue Type: Sub-task Reporter: Phil Sorber Fix For: 4.2.0 We need something a little more formal than the summit notes. It should go in the wiki. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (TS-2283) Make writing out configs optional
[ https://issues.apache.org/jira/browse/TS-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom resolved TS-2283. --- Resolution: Duplicate Make writing out configs optional - Key: TS-2283 URL: https://issues.apache.org/jira/browse/TS-2283 Project: Traffic Server Issue Type: Sub-task Reporter: Phil Sorber Many people find the automated config file writing bad. We should have an option to disable this. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (TS-2228) Allow header_rewrite to set overridable configurations
[
https://issues.apache.org/jira/browse/TS-2228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-2228:
--
Fix Version/s: (was: 5.0.0)
4.1.0
Allow header_rewrite to set overridable configurations
---
Key: TS-2228
URL: https://issues.apache.org/jira/browse/TS-2228
Project: Traffic Server
Issue Type: New Feature
Components: Plugins
Reporter: Leif Hedstrom
Assignee: Leif Hedstrom
Fix For: 4.1.0
It'd be swell to be able to do e.g.
cond %{READ_REQUEST_HDR_HOOK} [AND]
cond %{CLIENT-HEADER:Foo-bar} =1
set-config proxy.config.http.insert_response_via_str 1
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (TS-2226) header_rewrite ought to have a set-header operator
[ https://issues.apache.org/jira/browse/TS-2226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2226: -- Fix Version/s: (was: 5.0.0) 4.1.0 header_rewrite ought to have a set-header operator -- Key: TS-2226 URL: https://issues.apache.org/jira/browse/TS-2226 Project: Traffic Server Issue Type: Bug Components: Plugins Reporter: Leif Hedstrom Assignee: Leif Hedstrom Fix For: 4.1.0 Right now, the expectation is that if you really want to set a header, you have to do rm-header Foo-Header add-header Foo-Header bar Lame. The examples even has a set-header line, but there's no code for it. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (TS-2227) Make header_rewrite load all pparam's as config files
[
https://issues.apache.org/jira/browse/TS-2227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-2227:
--
Fix Version/s: (was: 5.0.0)
4.1.0
Make header_rewrite load all pparam's as config files
-
Key: TS-2227
URL: https://issues.apache.org/jira/browse/TS-2227
Project: Traffic Server
Issue Type: New Feature
Components: Plugins
Reporter: Leif Hedstrom
Assignee: Leif Hedstrom
Fix For: 4.1.0
Particularly in a remap rule, it'd be useful to do concatenation of config
files, e.g.
{code}
… @plugin=header_rewrite.so @pparam=set-cache-control.config
@pparam=set-id-tag.config ...
{code}
This allows certain portions of a config to be shared across multiple remap
rules for example.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (TS-2275) fix interim cache lossing data if the server process crash
[ https://issues.apache.org/jira/browse/TS-2275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13799936#comment-13799936 ] Zhao Yongming commented on TS-2275: --- that is not the same as TS-2139. we have disable the permanent storage on the interim cache device due to consistence. that is why I point out this is #1 problem of the current implement in https://blog.zymlinux.net/index.php/archives/555 TS-2139 is relate to the purge consistence, which is introduced during the forward porting to master, we have a patch there already, pending for review fix interim cache lossing data if the server process crash -- Key: TS-2275 URL: https://issues.apache.org/jira/browse/TS-2275 Project: Traffic Server Issue Type: Improvement Components: Cache Reporter: Zhao Yongming Assignee: portl4t the current interim cache device is not permanent storage, it is cleared on each server restart, that is because we do not have a very good solution for the storage consistence. we have a patch under testing for that improvement. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (TS-2281) Augment config system to use LUA
[ https://issues.apache.org/jira/browse/TS-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13799945#comment-13799945 ] Igor Galić commented on TS-2281: I understand that the final target is 6.0.0, but what can we do in 4.1.x? 4.2.x? 5.0.0? Augment config system to use LUA Key: TS-2281 URL: https://issues.apache.org/jira/browse/TS-2281 Project: Traffic Server Issue Type: Improvement Components: Configuration Reporter: Phil Sorber Assignee: Phil Sorber Fix For: 6.0.0 This is the main ticket for an upgrade of the config system to support LUA as discussed at the Fall 2013 Summit at Yahoo!. Notes from Summit: https://docs.google.com/document/d/1Gf3tfad1CbUEtd4n79MzgN4hRq-eu1hMh8FPW49NBe8/edit# -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (TS-2281) Augment config system to use LUA
[ https://issues.apache.org/jira/browse/TS-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13799953#comment-13799953 ] Leif Hedstrom commented on TS-2281: --- Maybe this should move, I just did a massive bulk change to get some more reasonable bug counts per each release. Augment config system to use LUA Key: TS-2281 URL: https://issues.apache.org/jira/browse/TS-2281 Project: Traffic Server Issue Type: Improvement Components: Configuration Reporter: Phil Sorber Assignee: Phil Sorber Fix For: 6.0.0 This is the main ticket for an upgrade of the config system to support LUA as discussed at the Fall 2013 Summit at Yahoo!. Notes from Summit: https://docs.google.com/document/d/1Gf3tfad1CbUEtd4n79MzgN4hRq-eu1hMh8FPW49NBe8/edit# -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (TS-2231) header_rewrite uses boost regexes, we should switch to PCRE
[ https://issues.apache.org/jira/browse/TS-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2231: -- Fix Version/s: (was: 6.0.0) 4.2.0 header_rewrite uses boost regexes, we should switch to PCRE --- Key: TS-2231 URL: https://issues.apache.org/jira/browse/TS-2231 Project: Traffic Server Issue Type: New Feature Components: Plugins Reporter: Leif Hedstrom Fix For: 4.2.0 It makes no sense to have another regex format, lets unify everything on PCRE. Also, while we're at it, lets get rid of BOOST entirely. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Assigned] (TS-2231) header_rewrite uses boost regexes, we should switch to PCRE
[ https://issues.apache.org/jira/browse/TS-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom reassigned TS-2231: - Assignee: Leif Hedstrom header_rewrite uses boost regexes, we should switch to PCRE --- Key: TS-2231 URL: https://issues.apache.org/jira/browse/TS-2231 Project: Traffic Server Issue Type: New Feature Components: Plugins Reporter: Leif Hedstrom Assignee: Leif Hedstrom Fix For: 4.2.0 It makes no sense to have another regex format, lets unify everything on PCRE. Also, while we're at it, lets get rid of BOOST entirely. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Assigned] (TS-2290) Eliminate X-ID header / log tag
[ https://issues.apache.org/jira/browse/TS-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom reassigned TS-2290: - Assignee: Leif Hedstrom Eliminate X-ID header / log tag --- Key: TS-2290 URL: https://issues.apache.org/jira/browse/TS-2290 Project: Traffic Server Issue Type: Improvement Components: Logging Reporter: Leif Hedstrom Assignee: Leif Hedstrom Fix For: 4.2.0 I think this is a legacy thing, that's pointless to support. This also includes a config proxy.config.log.xuid_logging_enabled . The thing is, all I can see this doing is to log a client header X-ID, which we can easily log using other mechanisms. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (TS-2290) Eliminate X-ID header / log tag
[ https://issues.apache.org/jira/browse/TS-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2290: -- Fix Version/s: 4.2.0 Eliminate X-ID header / log tag --- Key: TS-2290 URL: https://issues.apache.org/jira/browse/TS-2290 Project: Traffic Server Issue Type: Improvement Components: Logging Reporter: Leif Hedstrom Fix For: 4.2.0 I think this is a legacy thing, that's pointless to support. This also includes a config proxy.config.log.xuid_logging_enabled . The thing is, all I can see this doing is to log a client header X-ID, which we can easily log using other mechanisms. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (TS-2290) Eliminate X-ID header / log tag
Leif Hedstrom created TS-2290: - Summary: Eliminate X-ID header / log tag Key: TS-2290 URL: https://issues.apache.org/jira/browse/TS-2290 Project: Traffic Server Issue Type: Improvement Components: Logging Reporter: Leif Hedstrom I think this is a legacy thing, that's pointless to support. This also includes a config proxy.config.log.xuid_logging_enabled . The thing is, all I can see this doing is to log a client header X-ID, which we can easily log using other mechanisms. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (TS-2265) Remove unsupported log tags
[
https://issues.apache.org/jira/browse/TS-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-2265:
--
Description:
There are a number of log tags, which are no longer supporter (or possible to
support). They were used / defined only for various streaming protocols, which
our core no longer supports.
To avoid confusion, we should remove these. I'll post a full list here once
complete, but a few examples include
{code}
prob
prcb
{code}
was:
There are a number of log tags, which are no longer supporter (or possible to
support). They were used / defined only for various streaming protocols, which
our core no longer supports.
To avoid confusion, we should remove these. I'll post a full list here once
complete, but a few examples include
{code}
band
prob
prcb
{code}
Remove unsupported log tags
---
Key: TS-2265
URL: https://issues.apache.org/jira/browse/TS-2265
Project: Traffic Server
Issue Type: Bug
Components: Logging
Reporter: Leif Hedstrom
Assignee: Leif Hedstrom
Fix For: 4.1.0
There are a number of log tags, which are no longer supporter (or possible to
support). They were used / defined only for various streaming protocols,
which our core no longer supports.
To avoid confusion, we should remove these. I'll post a full list here once
complete, but a few examples include
{code}
prob
prcb
{code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
