[jira] [Created] (TS-1213) Crash report: update will crash at HttpTransact::process_quick_http_filter
Crash report: update will crash at HttpTransact::process_quick_http_filter
--
Key: TS-1213
URL: https://issues.apache.org/jira/browse/TS-1213
Project: Traffic Server
Issue Type: Bug
Environment: git master with update enabled.
Reporter: Zhao Yongming
the new ip_allow & quick filter may affect the scheduled update functions:
{code}
NOTE: Traffic Server received Sig 11: Segmentation fault
/opt/ats/bin/traffic_server - STACK TRACE:
/lib64/libpthread.so.0(+0x10bc0)[0x2ab9e4318bc0]
/opt/ats/bin/traffic_server(HttpTransact::process_quick_http_filter(HttpTransact::State*,
int)+0x3b)[0x5501db]
/opt/ats/bin/traffic_server(HttpTransact::EndRemapRequest(HttpTransact::State*)+0x3a1)[0x55ed91]
/opt/ats/bin/traffic_server(HttpSM::call_transact_and_set_next_state(void
(*)(HttpTransact::State*))+0x62)[0x530202]
/opt/ats/bin/traffic_server(HttpSM::set_next_state()+0x54a)[0x54031a]
/opt/ats/bin/traffic_server(HttpSM::set_next_state()+0x41c)[0x5401ec]
/opt/ats/bin/traffic_server(HttpSM::set_next_state()+0x41c)[0x5401ec]
/opt/ats/bin/traffic_server(HttpSM::state_add_to_list(int,
void*)+0x18f)[0x53b2df]
/opt/ats/bin/traffic_server(HttpSM::main_handler(int, void*)+0xe8)[0x53c288]
/opt/ats/bin/traffic_server(HttpUpdateSM::start_scheduled_update(Continuation*,
HTTPHdr*)+0x1c7)[0x576d97]
/opt/ats/bin/traffic_server(UpdateSM::http_scheme(UpdateSM*)+0x197)[0x4fbd77]
/opt/ats/bin/traffic_server(UpdateSM::HandleSMEvent(int,
Event*)+0x378)[0x4f7198]
/opt/ats/bin/traffic_server(EThread::process_event(Event*, int)+0x90)[0x6b0250]
/opt/ats/bin/traffic_server(EThread::execute()+0x5eb)[0x6b0e0b]
/opt/ats/bin/traffic_server[0x6af042]
/lib64/libpthread.so.0(+0x8e2c)[0x2ab9e4310e2c]
/lib64/libc.so.6(clone+0x6d)[0x2ab9e6beb35d]
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1212) can not limit ram cache
can not limit ram cache
---
Key: TS-1212
URL: https://issues.apache.org/jira/browse/TS-1212
Project: Traffic Server
Issue Type: Bug
Components: Cache
Affects Versions: 2.1.3
Environment: we are on v3.0.x but maybe affected v3.1 and later too.
Reporter: Zhao Yongming
ram cache limit is not activate at sometime:
{code}
[yonghao@cache177 ~]$ links -dump http://localhost:8080/stat/ | grep ram
proxy.config.cache.ram_cache.size=10737418240
proxy.config.cache.ram_cache_cutoff=131072
proxy.config.cache.ram_cache.algorithm=1
proxy.config.cache.ram_cache.compress=0
proxy.config.cache.ram_cache.ssd_percent=25
proxy.config.cache.ram_cache.compress_percent=90
proxy.process.cache.ram_cache.total_bytes=12884901886
proxy.process.cache.volume_0.ram_cache.total_bytes=-7301066
proxy.process.cache.ram_cache.bytes_used=11840122880
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1211) listen queue doesn't get modified for traffic_manager when setting configuration option in records.config
listen queue doesn't get modified for traffic_manager when setting configuration option in records.config - Key: TS-1211 URL: https://issues.apache.org/jira/browse/TS-1211 Project: Traffic Server Issue Type: Bug Affects Versions: 3.1.3 Reporter: Bryan Call listen queue only gets modified if you are running the traffic_server binary and not if you use traffic_cop or the startup scripts traffic_manager is hardcoded to have a listen backlog of 1024. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1210) remove 3.0.x deprecated APIs
remove 3.0.x deprecated APIs Key: TS-1210 URL: https://issues.apache.org/jira/browse/TS-1210 Project: Traffic Server Issue Type: Bug Components: TS API Reporter: James Peach Fix For: 3.1.4 We should remove the following APIs that were deprecated in 3.0: tsapi TSReturnCode TSUrlDestroy(TSMBuffer bufp, TSMLoc offset); tsapi TS_DEPRECATED unsigned int TSHttpTxnClientIPGet(TSHttpTxn txnp); tsapi TS_DEPRECATED TSReturnCode TSHttpTxnClientRemotePortGet(TSHttpTxn txnp, int* portp); tsapi TS_DEPRECATED int TSHttpTxnClientIncomingPortGet(TSHttpTxn txnp); tsapi TS_DEPRECATED unsigned int TSHttpTxnServerIPGet(TSHttpTxn txnp); tsapi TS_DEPRECATED unsigned int TSHttpTxnNextHopIPGet(TSHttpTxn txnp); tsapi TS_DEPRECATED int TSHttpTxnNextHopPortGet(TSHttpTxn txnp); tsapi TS_DEPRECATED int TSHttpTxnMaxArgCntGet(void); tsapi TS_DEPRECATED unsigned int TSNetVConnRemoteIPGet(TSVConn vc); tsapi TS_DEPRECATED int TSNetVConnRemotePortGet(TSVConn vc); tsapi TS_DEPRECATED unsigned int TSHostLookupResultIPGet(TSHostLookupResult lookup_result); tsapi TS_DEPRECATED void TSOSIpSet(TSHttpTxn txnp, unsigned int ip); tsapi TS_DEPRECATED void TSIOBufferAppend(TSIOBuffer bufp, TSIOBufferBlock blockp); tsapi TS_DEPRECATED TSIOBufferData TSIOBufferDataCreate(void* data, int size, TSIOBufferDataFlags flags); tsapi TS_DEPRECATED TSIOBufferBlock TSIOBufferBlockCreate(TSIOBufferData datap, int size, int offset); -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1209) background_fill values don't seem to be working
background_fill values don't seem to be working --- Key: TS-1209 URL: https://issues.apache.org/jira/browse/TS-1209 Project: Traffic Server Issue Type: Bug Components: Cache Affects Versions: 3.0.4 Reporter: Robert Logue Priority: Minor If I request a 57 MB file TS caches the fill no problem and on subsequent requests the file gets served from cache. If I cut the request early, about 40MB downloaded and I have proxy.config.http.background_fill_completed_threshold = 0.5 and proxy.config.http.background_fill_active_timeout is suitably high, the file is not cached. I am of the understanding that the background fill values should keep the OS connection open and allow the full item to be cached though this is not happening. I have tried various values for proxy.config.http.background_fill_completed_threshold ranging from 0.0 -> 0.5, none seem to work. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1208) check_memory() in traffic_cop never active on linux
check_memory() in traffic_cop never active on linux --- Key: TS-1208 URL: https://issues.apache.org/jira/browse/TS-1208 Project: Traffic Server Issue Type: Bug Components: Management Reporter: Zhao Yongming Assignee: Zhao Yongming check_memory() will check system memory usage to prevent OOM. and it is still on linux v2.2 codes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1207) request for plugin cacheurl move into master tree
request for plugin cacheurl move into master tree - Key: TS-1207 URL: https://issues.apache.org/jira/browse/TS-1207 Project: Traffic Server Issue Type: New Feature Components: Plugins Affects Versions: 3.1.3 Reporter: Zhao Yongming from my testing, the cacheurl plugin is stable and usable in any version of 2.x & 3.x, should we move into the meanline? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1206) stats snap file may crash during server crash
stats snap file may crash during server crash - Key: TS-1206 URL: https://issues.apache.org/jira/browse/TS-1206 Project: Traffic Server Issue Type: Bug Reporter: Zhao Yongming when sometimes traffic_server crashed, some or all of the stats counter are not updating anymore. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1205) Crash report: double free when RecDataSet in cluster mode
Crash report: double free when RecDataSet in cluster mode
-
Key: TS-1205
URL: https://issues.apache.org/jira/browse/TS-1205
Project: Traffic Server
Issue Type: Bug
Components: Clustering, Configuration
Affects Versions: 3.1.3
Environment: v3.0.x, with cluster mode 2
Reporter: Zhao Yongming
Fix For: 3.3.0
we have seen some config system syncing config files in cluster mode.
{code}
*** glibc detected *** /usr/bin/traffic_server: double free or corruption
(fasttop): 0x2b639c0009a0 ***
=== Backtrace: =
/lib64/libc.so.6[0x3f8f0750c6]
/usr/bin/traffic_server(RecDataSet(RecDataT, RecData*, RecData*)+0xb8)[0x65dd58]
/usr/bin/traffic_server(RecForceInsert(RecRecord*)+0x74)[0x6584b4]
/usr/bin/traffic_server[0x65cd62]
/usr/bin/traffic_server(RecMessageRecvThis(void*, char*, int)+0x16)[0x65ed46]
/usr/bin/traffic_server(BaseManager::executeMgmtCallback(int, char*,
int)+0x3d)[0x5b562d]
/usr/bin/traffic_server(ProcessManager::processEventQueue()+0x29)[0x5b5d49]
/usr/bin/traffic_server(startProcessManager(void*)+0x8d)[0x5b633d]
/lib64/libpthread.so.0[0x3f8f4077f1]
/lib64/libc.so.6(clone+0x6d)[0x3f8f0e570d]
=== Memory map:
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1204) Crash report: HttpSM::main_handler HttpSM.cc:2412: failed assert `magic == HTTP_SM_MAGIC_ALIVE`
Crash report: HttpSM::main_handler HttpSM.cc:2412: failed assert `magic ==
HTTP_SM_MAGIC_ALIVE`
---
Key: TS-1204
URL: https://issues.apache.org/jira/browse/TS-1204
Project: Traffic Server
Issue Type: Bug
Components: HTTP
Affects Versions: 3.1.3
Environment: git master Sat Apr 7 03:29:50 2012. forwarding proxy on
centos 6.2 x86_64, with cacheurl plugin
Reporter: Zhao Yongming
{code}
FATAL: HttpSM.cc:2412: failed assert `magic == HTTP_SM_MAGIC_ALIVE`
/usr/bin/traffic_server - STACK TRACE:
/usr/lib64/trafficserver/libtsutil.so.3(ink_fatal+0x88)[0x3ddba14368]
/usr/lib64/trafficserver/libtsutil.so.3(_ink_assert+0x1f)[0x3ddba12c6f]
/usr/bin/traffic_server(HttpSM::main_handler(int, void*)+0x2e)[0x5163fe]
/usr/bin/traffic_server[0x628b4b]
/usr/bin/traffic_server(write_to_net_io(NetHandler*, UnixNetVConnection*,
EThread*)+0x353)[0x62c7a3]
/usr/bin/traffic_server(NetHandler::mainNetEvent(int, Event*)+0x2fe)[0x624cce]
/usr/bin/traffic_server(EThread::process_event(Event*, int)+0xb4)[0x6494f4]
/usr/bin/traffic_server(EThread::execute()+0x4c3)[0x649e83]
/usr/bin/traffic_server[0x648832]
/lib64/libpthread.so.0[0x380dc077f1]
/lib64/libc.so.6(clone+0x6d)[0x380d0e592d]
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1203) Crash report: HdrHeap::duplicate_str, in host_set
Crash report: HdrHeap::duplicate_str, in host_set
-
Key: TS-1203
URL: https://issues.apache.org/jira/browse/TS-1203
Project: Traffic Server
Issue Type: Bug
Components: HTTP
Affects Versions: 3.1.3
Environment: 3.0.x, new crashes
Reporter: Zhao Yongming
we get some new crashes in the production:
{code}
warning: no loadable sections found in added symbol-file system-supplied DSO at
0x727fd000
Core was generated by `/usr/bin/traffic_server -M -A,12:X,13:X'.
Program terminated with signal 11, Segmentation fault.
#0 0x003e5b07c24e in memcpy () from /lib64/libc.so.6
(gdb) bt
#0 0x003e5b07c24e in memcpy () from /lib64/libc.so.6
#1 0x005aab68 in HdrHeap::duplicate_str (this=,
str=0x2aae474a6ec0 ,
nbytes=21) at HdrHeap.cc:344
#2 0x005b3ac3 in mime_str_u16_set (heap=0x2aaabd62be12,
s_str=0x2aae474a6ec0 , s_len=21,
d_str=0x2aae3656f348, d_len=0x2aae3656f322, must_copy=true) at MIME.cc:3034
#3 0x005aef28 in host_set (this=0x2aae268f8c18, url=) at URL.h:541
#4 HTTPHdr::set_url_target_from_host_field (this=0x2aae268f8c18, url=) at HTTP.cc:1484
#5 0x0055dc69 in RemapProcessor::setup_for_remap (this=, s=0x2aae268f83c8) at RemapProcessor.cc:130
#6 0x005165d9 in HttpSM::do_remap_request (this=0x2aae268f8360,
run_inline=true) at HttpSM.cc:3666
#7 0x00526cbb in HttpSM::set_next_state (this=0x2aaabd62be12) at
HttpSM.cc:6392
#8 0x005136f0 in HttpSM::call_transact_and_set_next_state
(this=0x2aae268f8360, f=) at HttpSM.cc:6345
#9 0x00526713 in HttpSM::set_next_state (this=0x2aae268f8360) at
HttpSM.cc:6553
#10 0x005136f0 in HttpSM::call_transact_and_set_next_state
(this=0x2aae268f8360, f=) at HttpSM.cc:6345
#11 0x00526713 in HttpSM::set_next_state (this=0x2aae268f8360) at
HttpSM.cc:6553
#12 0x005136f0 in HttpSM::call_transact_and_set_next_state
(this=0x2aae268f8360, f=) at HttpSM.cc:6345
#13 0x00520f21 in HttpSM::state_read_client_request_header
(this=0x2aae268f8360, event=100, data=)
at HttpSM.cc:783
#14 0x005259b9 in HttpSM::main_handler (this=0x2aae268f8360, event=100,
data=0x2aae68aee6e0) at HttpSM.cc:2456
#15 0x0066d1fb in handleEvent (nh=0x2b105668, vc=0x2aae68aee520,
thread=0x2b104010)
at ../../iocore/eventsystem/I_Continuation.h:146
#16 read_signal_and_update (nh=0x2b105668, vc=0x2aae68aee520,
thread=0x2b104010) at UnixNetVConnection.cc:138
#17 read_from_net (nh=0x2b105668, vc=0x2aae68aee520, thread=0x2b104010)
at UnixNetVConnection.cc:320
#18 0x00666579 in NetHandler::mainNetEvent (this=0x2b105668,
event=, e=0x2b8ed028) at UnixNet.cc:389
#19 0x00691c8f in EThread::process_event (this=0x2b104010,
e=0x35681c0, calling_code=5) at I_Continuation.h:146
#20 0x0069259c in EThread::execute (this=0x2b104010) at
UnixEThread.cc:263
#21 0x0069115e in spawn_thread_internal (a=0x35621b0) at Thread.cc:88
#22 0x003e5b80673d in start_thread () from /lib64/libpthread.so.0
#23 0x003e5b0d44bd in clone () from /lib64/libc.so.6
(gdb) f 1
#1 0x005aab68 in HdrHeap::duplicate_str (this=,
str=0x2aae474a6ec0 ,
nbytes=21) at HdrHeap.cc:344
344 memcpy(new_str, str, nbytes);
(gdb) p str
$1 = 0x2aae474a6ec0
(gdb) p nbytes
$2 = 21
(gdb) f 2
#2 0x005b3ac3 in mime_str_u16_set (heap=0x2aaabd62be12,
s_str=0x2aae474a6ec0 , s_len=21,
d_str=0x2aae3656f348, d_len=0x2aae3656f322, must_copy=true) at MIME.cc:3034
3034s_str = heap->duplicate_str(s_str, s_len);
(gdb) p s_str
$3 = 0x2aae474a6ec0
(gdb) f 3
#3 0x005aef28 in host_set (this=0x2aae268f8c18, url=) at URL.h:541
541 url_host_set(m_heap, m_url_impl, value, length, true);
(gdb) p value
$4 =
(gdb) p length
$5 =
(gdb) f 2
#2 0x005b3ac3 in mime_str_u16_set (heap=0x2aaabd62be12,
s_str=0x2aae474a6ec0 , s_len=21,
d_str=0x2aae3656f348, d_len=0x2aae3656f322, must_copy=true) at MIME.cc:3034
3034s_str = heap->duplicate_str(s_str, s_len);
(gdb) l
3029 //either NULL or be valid ptr for a string already
3030 //the string heaps
3031 heap->free_string(*d_str, *d_len);
3032
3033 if (must_copy && s_str) {
3034s_str = heap->duplicate_str(s_str, s_len);
3035 }
3036 *d_str = s_str;
3037 *d_len = s_len;
3038 return s_str;
(gdb) p d_str
$6 = (const char **) 0x2aae3656f348
(gdb) p s_str
$7 = 0x2aae474a6ec0
(gdb) p s_length
No symbol "s_length" in current context.
(gdb) p s_len
$8 = 21
(gdb) p d_len
$9 = (uint16_t *) 0x2aae3656f322
(gdb) p *d_len
$10 = 0
(gdb) p must_copy
$11 = true
(gdb) p heap
$12 = (HdrHeap *) 0x2aaabd62be12
(gdb) p *heap
$13 = {m_magic = 4244214959, m_free_start = 0xf1895c4222d0b96a ,
m_data_start = 0x285db46ea5b18c6a ,
m_size = 3748408139, m_writeable = 72,
m_next = 0x4b5d55
[jira] [Created] (TS-1202) install traffic_shell man/doc pages in a more appropriate location
install traffic_shell man/doc pages in a more appropriate location -- Key: TS-1202 URL: https://issues.apache.org/jira/browse/TS-1202 Project: Traffic Server Issue Type: Improvement Affects Versions: 3.1.4 Reporter: Igor Brezac Priority: Minor Fix For: 3.1.4 Attachments: doc.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1201) Crash report: hostdb multicache, double free
Crash report: hostdb multicache, double free
Key: TS-1201
URL: https://issues.apache.org/jira/browse/TS-1201
Project: Traffic Server
Issue Type: Bug
Reporter: Zhao Yongming
Assignee: weijin
{code}
*** glibc detected *** /usr/bin/traffic_server: corrupted double-linked list:
0x1fe10ef0 ***
=== Backtrace: =
/lib64/libc.so.6[0x3db2072555]
/lib64/libc.so.6(cfree+0x4b)[0x3db20728bb]
/usr/bin/traffic_server(_ZN14MultiCacheSync7mcEventEiP5Event+0xa4)[0x5dae04]
/usr/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x22f)[0x691c8f]
/usr/bin/traffic_server(_ZN7EThread7executeEv+0x6a1)[0x692681]
/usr/bin/traffic_server[0x69115e]
/lib64/libpthread.so.0[0x3db280673d]
/lib64/libc.so.6(clone+0x6d)[0x3db20d44bd]
=== Memory map:
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1200) DOAP file reference incorrect
DOAP file reference incorrect - Key: TS-1200 URL: https://issues.apache.org/jira/browse/TS-1200 Project: Traffic Server Issue Type: Bug Reporter: Sebb Priority: Critical The DOAP file for the project needs to be available for the projects.a.o website to function correctly. Currently the build is looking for http://svn.apache.org/repos/asf/trafficserver/traffic/trunk/doc/doap.rdf However this does not exist, so the build is reporting an error. Please update the file https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/files.xml with the new location ASAP. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1199) Out of memory: Kill process 1490 ([ET_NET 0]) score 963 or sacrifice child Killed process 1490, UID 99, ([ET_NET 0]) total-vm:10837656kB, anon-rss:7834172kB, file-rss:180kB
Out of memory: Kill process 1490 ([ET_NET 0]) score 963 or sacrifice child Killed process 1490, UID 99, ([ET_NET 0]) total-vm:10837656kB, anon-rss:7834172kB, file-rss:180kB - Key: TS-1199 URL: https://issues.apache.org/jira/browse/TS-1199 Project: Traffic Server Issue Type: Bug Components: Core Affects Versions: 3.0.3 Environment: centos 6 x86_64 Reporter: bettydramit Out of memory: Kill process 1490 ([ET_NET 0]) score 963 or sacrifice child Killed process 1490, UID 99, ([ET_NET 0]) total-vm:10837656kB, anon-rss:7834172kB, file-rss:180kB -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1198) ssl crash when certificates are missing
ssl crash when certificates are missing --- Key: TS-1198 URL: https://issues.apache.org/jira/browse/TS-1198 Project: Traffic Server Issue Type: Bug Components: SSL Affects Versions: 3.1.4 Reporter: James Peach Assignee: James Peach Fix For: 3.1.4 So, I made the mistake of upgrading ATS from trunk, without upgrading configs. And shit went to hell, with all the cores filling up my disk :). I know, it's my mistake, but perhaps there's something we can do to at least not segfault when someone has the old configs? Not a huge deal, but I'd hate for a prod box to run into this. The stack trace is below, if it makes any sense to you. -- Leif #0 0x4006e045 in SSL_CTX_callback_ctrl () from /home/server/lib/libssl.so.1.0.0 #1 0x001dc2c0 in _dl_runtime_resolve () from /lib/ld-linux.so.2 #2 0x0828c843 in SSLNetVConnection::sslStartHandShake (this=0xb52d230, event=0, err=@0x411f2e60) at SSLNetVConnection.cc:501 #3 0x0828e1b0 in SSLNetVConnection::net_read_io (this=0xb52d230, nh=0xac250d0, lthread=0xac22000) at SSLNetVConnection.cc:251 #4 0x0829589e in NetHandler::mainNetEvent (this=0xac250d0, event=5, e=0x9eb5980) at UnixNet.cc:372 #5 0x082c3774 in EThread::process_event (this=0xac22000, e=0x9eb5980, calling_code=5) at I_Continuation.h:146 #6 0x082c3f7e in EThread::execute (this=0xac22000) at UnixEThread.cc:264 #7 0x082c2b31 in spawn_thread_internal (a=0x9a6da80) at Thread.cc:88 #8 0x0037544b in start_thread () from /lib/libpthread.so.0 #9 0x002b880e in clone () from /lib/libc.so.6 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1197) Build fails when building outside the source tree
Build fails when building outside the source tree - Key: TS-1197 URL: https://issues.apache.org/jira/browse/TS-1197 Project: Traffic Server Issue Type: Bug Components: Build Affects Versions: 3.1.3 Reporter: Yossi Gottlieb Priority: Minor Fix For: 3.1.4 Currently some Makefiles assume $(builddir) == $(srcdir), which is an incorrect assumption. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1196) the via metrix in PURGE response should be documented
the via metrix in PURGE response should be documented
-
Key: TS-1196
URL: https://issues.apache.org/jira/browse/TS-1196
Project: Traffic Server
Issue Type: Task
Components: Documentation
Affects Versions: 3.1.3
Reporter: Zhao Yongming
Assignee: Zhao Yongming
Priority: Minor
{code}
[yonghao@cache161.cn50 trafficserver]$ echo -ne "PURGE
http://img01.taobaocdn.com/bao/uploaded/i1/000/160/T1RoNcXn5Qj0JX.jpg_60x60.jpg
HTTP/1.0\r\n\r\n" | nc -i 1 cache162.cn50 81
HTTP/1.0 200 Ok
Date: Tue, 10 Apr 2012 07:10:30 GMT
Via: http/1.1 cn50 (ApacheTrafficServer/3.0.2 [cRs f ])
Content-Length: 0
{code}
what does the cR mean? we should document it down!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1195) IPv6 address URLs are not parsed.
IPv6 address URLs are not parsed. - Key: TS-1195 URL: https://issues.apache.org/jira/browse/TS-1195 Project: Traffic Server Issue Type: Bug Components: HTTP Affects Versions: 3.1.3 Reporter: Alan M. Carroll Assignee: Alan M. Carroll Priority: Minor Fix For: 3.2.0 A URL with a raw IPv6 address is not parsed. It should be parsed with or without braces (per RFC). http://fe80:2710::1:1/some/path http://[fe80:2810::1:1]/some/path -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1194) Build problem with gcc 4.6 and OmniOS ("solaris")
Build problem with gcc 4.6 and OmniOS ("solaris")
-
Key: TS-1194
URL: https://issues.apache.org/jira/browse/TS-1194
Project: Traffic Server
Issue Type: Bug
Components: Core
Reporter: Leif Hedstrom
Assignee: Leif Hedstrom
Fix For: 3.1.4
Seems printf() is unhappy with a few of our type conversions on Solaris. Also
might be a problem on some plugin dependencies?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1193) Traffic Server building on OpenBSD
Traffic Server building on OpenBSD -- Key: TS-1193 URL: https://issues.apache.org/jira/browse/TS-1193 Project: Traffic Server Issue Type: Improvement Reporter: Brian Geffon Assignee: Brian Geffon This is a parent issue for the task of getting traffic server building on OpenBSD. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1192) Remove gethostbyname usage in test code
Remove gethostbyname usage in test code --- Key: TS-1192 URL: https://issues.apache.org/jira/browse/TS-1192 Project: Traffic Server Issue Type: Improvement Affects Versions: 3.1.3 Reporter: Brian Geffon NetTest-simple-proxy.cc and test_I_simple_proxy.cc directly use gethostbyname(). These will be changed to use getaddrinfo(). We're removing gethostbyname() and gethostbyaddr() in an effort to get traffic server building on more platforms. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1191) change the default for search domains for dns to 0
change the default for search domains for dns to 0 -- Key: TS-1191 URL: https://issues.apache.org/jira/browse/TS-1191 Project: Traffic Server Issue Type: Improvement Reporter: Bryan Call Assignee: Bryan Call Priority: Minor Fix For: 3.1.4 As part of TS-703. Making this change a separate bug that is easy to change. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1190) Change default for proxy.config.http.share_server_sessions
Change default for proxy.config.http.share_server_sessions -- Key: TS-1190 URL: https://issues.apache.org/jira/browse/TS-1190 Project: Traffic Server Issue Type: Improvement Components: HTTP Reporter: Leif Hedstrom Assignee: Leif Hedstrom Fix For: 3.1.4 We should enable session sharing with dedicated session pools per net-thread as the default. It has the best performance for a majority of our use cases. CONFIG proxy.config.http.share_server_sessions INT 2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1189) Build problem on CentOS5
Build problem on CentOS5
Key: TS-1189
URL: https://issues.apache.org/jira/browse/TS-1189
Project: Traffic Server
Issue Type: Bug
Components: SSL
Reporter: Leif Hedstrom
Assignee: Leif Hedstrom
Priority: Critical
Fix For: 3.1.4
{code}
diff --git a/iocore/net/SSLNetVConnection.cc b/iocore/net/SSLNetVConnection.cc
index 33ebe64..0a41a08 100644
--- a/iocore/net/SSLNetVConnection.cc
+++ b/iocore/net/SSLNetVConnection.cc
@@ -673,9 +673,9 @@ SSLNetVConnection::registerNextProtocolSet(const
SSLNextProtocolSet * s)
}
int
-SSLNetVConnection::advertise_next_protocol(
-SSL *ssl, const unsigned char **out, unsigned int *outlen, void *arg)
+SSLNetVConnection::advertise_next_protocol(SSL *ssl, const unsigned char
**out, unsigned int *outlen, void *arg)
{
+#if TS_USE_TLS_NPN
SSLNetVConnection * netvc = (SSLNetVConnection *)SSL_get_app_data(ssl);
ink_release_assert(netvc != NULL);
@@ -686,4 +686,7 @@ SSLNetVConnection::advertise_next_protocol(
}
return SSL_TLSEXT_ERR_NOACK;
+#else
+ return 0;
+#endif
}
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1188) http://trafficserver.apache.org/docs/trunk/admin/ts_admin_chinese.pdf is 404
http://trafficserver.apache.org/docs/trunk/admin/ts_admin_chinese.pdf is 404 Key: TS-1188 URL: https://issues.apache.org/jira/browse/TS-1188 Project: Traffic Server Issue Type: Bug Components: Web site Reporter: James Peach Assignee: Igor Galić Priority: Minor The main docs page tries to point to the Chinese admin docs at http://trafficserver.apache.org/docs/trunk/admin/ts_admin_chinese.pdf, but there's nothing there. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1187) TSMimeHdrFieldNameSet does not work for headers read from the client or origin server (but does work for headers added by traffic server)
TSMimeHdrFieldNameSet does not work for headers read from the client or origin server (but does work for headers added by traffic server) - Key: TS-1187 URL: https://issues.apache.org/jira/browse/TS-1187 Project: Traffic Server Issue Type: Bug Components: MIME Affects Versions: 3.0.2 Environment: Redhat linux with plugin that wants to rename a header read from the client. Reporter: Alistair Stevenson Fix For: 3.1.4 TSMimeHdrFieldNameSet does not work for headers read from the client or origin server (but does work for headers added by traffic server) The name appears set (and the function returns SUCCESS) but when the data is sent to the origin Server it is corrupted at the point where the header is set. i.e the header name is sent but the header is corrupted after this. I am having to create a new header and copy the values and then destroy the original header which is not as efficient. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1186) Problem with Perl stats API not parsing the stats as 64-bit int
Problem with Perl stats API not parsing the stats as 64-bit int --- Key: TS-1186 URL: https://issues.apache.org/jira/browse/TS-1186 Project: Traffic Server Issue Type: Bug Affects Versions: 3.1.3 Environment: RHEL 6.2 Reporter: Bryan Call Assignee: Bryan Call Priority: Minor Fix For: 3.1.4 Stats will rollover because they are parsed as 32-bit int instead of 64-bit int in the Apache::TS::AdminClient module. Change: -@resp = unpack( "slsl", $res ); +@resp = unpack( "slsq", $res ); -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1185) fails to build from source with gcc 4.7
fails to build from source with gcc 4.7
---
Key: TS-1185
URL: https://issues.apache.org/jira/browse/TS-1185
Project: Traffic Server
Issue Type: Bug
Affects Versions: 3.0.4, 3.1.3
Environment: Debian Unstable with gcc 4.7
Reporter: Arno Toell
Using gcc 4.7, ATS fails to build from source. See Debian bug 667396
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667396) for further
information. gcc 4.7 fails with
{code}
g++ -DHAVE_CONFIG_H -I. -I../../lib/ts -I../../iocore/eventsystem
-I../../iocore/net -I../../iocore/aio -I../../iocore/hostdb
-I../../iocore/cache -I../../iocore/cluster -I../../iocore/utils
-I../../iocore/dns -I../../proxy -I../../lib/records -I../../mgmt
-I../../mgmt/preparse -I../../mgmt/utils -I../../proxy/hdrs
-I../../proxy/http/remap -I../../proxy/logging -D_FORTIFY_SOURCE=2
-D_LARGEFILE64_SOURCE=1 -D_COMPILE64BIT_SOURCE=1 -D_GNU_SOURCE -D_REENTRANT
-Dlinux -I/usr/include/tcl8.5 -g -O2 -fstack-protector
--param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security
-pipe -Wall -Werror -feliminate-unused-debug-symbols -fno-strict-aliasing
-Wno-invalid-offsetof -MT HttpClientSession.o -MD -MP -MF
.deps/HttpClientSession.Tpo -c -o HttpClientSession.o HttpClientSession.cc
In file included from ../../lib/ts/libts.h:96:0,
from HttpClientSession.h:35,
from HttpClientSession.cc:35:
../../lib/ts/Map.h: In instantiation of 'C Map::get(K) [with K =
unsigned int; C = int; A = DefaultAlloc]':
HttpConnectionCount.h:51:34: required from here
../../lib/ts/Map.h:240:29: error: 'set_in' was not declared in this scope, and
no declarations were found by argument-dependent lookup at the point of
instantiation [-fpermissive]
../../lib/ts/Map.h:240:29: note: declarations in dependent base
'Vec, DefaultAlloc, 2>' are not found by unqualified
lookup
../../lib/ts/Map.h:240:29: note: use 'this->set_in' instead
../../lib/ts/Map.h: In instantiation of 'MapElem* Map::put(K, C)
[with K = unsigned int; C = int; A = DefaultAlloc]':
HttpConnectionCount.h:64:37: required from here
../../lib/ts/Map.h:258:29: error: 'set_in' was not declared in this scope, and
no declarations were found by argument-dependent lookup at the point of
instantiation [-fpermissive]
../../lib/ts/Map.h:258:29: note: declarations in dependent base
'Vec, DefaultAlloc, 2>' are not found by unqualified
lookup
../../lib/ts/Map.h:258:29: note: use 'this->set_in' instead
../../lib/ts/Map.h:263:21: error: 'set_add' was not declared in this scope, and
no declarations were found by argument-dependent lookup at the point of
instantiation [-fpermissive]
../../lib/ts/Map.h:263:21: note: declarations in dependent base
'Vec, DefaultAlloc, 2>' are not found by unqualified
lookup
../../lib/ts/Map.h:263:21: note: use 'this->set_add' instead
make[4]: *** [HttpClientSession.o] Error 1
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1184) Additional whitespace in proxy.config.admin.user_id value results in error
Additional whitespace in proxy.config.admin.user_id value results in error
--
Key: TS-1184
URL: https://issues.apache.org/jira/browse/TS-1184
Project: Traffic Server
Issue Type: Bug
Components: Configuration
Affects Versions: 3.0.4
Reporter: Kurt Payne
Priority: Minor
Config looked like this:
CONFIG proxy.config.alarm_email STRING nobody
The username had a trailing space. ATS fails to start, and the following
messages appear in /var/log/messages:
Apr 3 10:46:33 blitz traffic_cop[5498]: --- Cop Starting [Version: Apache
Traffic Server - traffic_cop - 3.0.4 - (build # 3310 on Apr 3 2012 at
10:16:46)] ---
Apr 3 10:46:33 blitz traffic_cop[5498]: can't get passwd entry for the admin
user
Apr 3 10:46:33 blitz traffic_cop[5498]: can't get passwd entry for the admin
user
Apr 3 10:46:33 blitz traffic_cop[5498]: traffic_manager not running, making
sure traffic_server is dead
Apr 3 10:46:33 blitz traffic_cop[5498]: spawning traffic_manager
Apr 3 10:46:33 blitz traffic_manager[5500]: NOTE: --- Manager Starting ---
Apr 3 10:46:33 blitz traffic_manager[5500]: NOTE: Manager Version: Apache
Traffic Server - traffic_manager - 3.0.4 - (build # 3310 on Apr 3 2012 at
10:16:03)
Apr 3 10:46:33 blitz traffic_manager[5500]: NOTE:
RLIMIT_NOFILE(7):cur(3),max(3)
Apr 3 10:46:33 blitz traffic_manager[5500]: {140630387636192} STATUS: opened
/usr/local/var/log/trafficserver/manager.log
Apr 3 10:46:35 blitz traffic_server[5509]: NOTE: --- Server Starting ---
Apr 3 10:46:35 blitz traffic_server[5509]: NOTE: Server Version: Apache
Traffic Server - traffic_server - 3.0.4 - (build # 3310 on Apr 3 2012 at
10:16:30)
Apr 3 10:46:35 blitz traffic_server[5509]: {47289782682464} STATUS: opened
/usr/local/var/log/trafficserver/diags.log
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1183) issue with videos on yahoo website
issue with videos on yahoo website -- Key: TS-1183 URL: https://issues.apache.org/jira/browse/TS-1183 Project: Traffic Server Issue Type: Bug Components: HTTP Affects Versions: 3.0.4 Reporter: Luca Can't view yahoo videos (tested in forwarding mode). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1182) Add a flag to LogBuffer's for endian used
Add a flag to LogBuffer's for endian used - Key: TS-1182 URL: https://issues.apache.org/jira/browse/TS-1182 Project: Traffic Server Issue Type: Improvement Components: Logging Reporter: Leif Hedstrom Fix For: 3.3.0 After discussions with amc: To support "reading" logs (either via logcat or log collation) on a box with a different endian from where it was generated, we need to know which endian we generated the log in. Either that, or go back and do the htonl / ntohl conversions always. I favor the "flag", since most sane platforms are little endian anyways (certainly all platforms we support are), so why take the cost of the conversions if they are rarely used. This would let us check the endian flag in e.g. the log collation server, and in logcat like tools, and do the conversions only when necessary. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1181) TSHttpTxnConfigInt* don't look right with MgmtByte fields in OverridableHttpConfigParams
TSHttpTxnConfigInt* don't look right with MgmtByte fields in OverridableHttpConfigParams Key: TS-1181 URL: https://issues.apache.org/jira/browse/TS-1181 Project: Traffic Server Issue Type: Bug Components: TS API Affects Versions: 3.0.4 Reporter: William Bardwell Priority: Minor TSHttpTxnConfigIntSet and Get use _conf_to_memberp to get a pointer to various fields, and then access it as a 32bit int. But many of the fields are now bytes. A fix would be to make _conf_to_memberp return the type properly, and make TSHttpTxnConfigInt* access the field as the proper size. I saw valgrind complaining about uninitialized data from the code (which is probably because of padding in the structure, since it is cleared a field at a time), but there are probably much worse effects around reading and writing unrelated fields. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1180) gzip plugin needs to be configurable for certain file/mime types
gzip plugin needs to be configurable for certain file/mime types Key: TS-1180 URL: https://issues.apache.org/jira/browse/TS-1180 Project: Traffic Server Issue Type: New Feature Components: Plugins Reporter: Igor Galić Most browsers don't take it very well when JavaScript is compressed - or rather, when AJAX requests are. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1179) libraries and plugins are installed with .la files
libraries and plugins are installed with .la files
--
Key: TS-1179
URL: https://issues.apache.org/jira/browse/TS-1179
Project: Traffic Server
Issue Type: Bug
Components: Build
Reporter: Igor Galić
Who needs or uses {{.la}} files?
We have {{tsxs}} which compiles stuff without {{libtool}}, and the plugins
definitely don't need {{.la}} files for loading.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1178) cop will kill manager & server, even cop it self
cop will kill manager & server, even cop it self
Key: TS-1178
URL: https://issues.apache.org/jira/browse/TS-1178
Project: Traffic Server
Issue Type: Bug
Components: Management
Affects Versions: 3.1.4
Environment: git master on RHEL6.1 x86_64
Reporter: Zhao Yongming
Assignee: Zhao Yongming
Fix For: 3.1.4
{code}
[root@test58 trafficserver]# cat /tmp/traffic_cop.trace
<1333239680.> [DEBUG]: Entering init()
<1333239680.> [DEBUG]: Entering init_signals()
<1333239680.> [DEBUG]: Entering set_alarm_death()
<1333239680.> [DEBUG]: Leaving set_alarm_death()
<1333239680.> [DEBUG]: Leaving init_signals()
<1333239680.> [DEBUG]: Entering init_config_dir()
<1333239680.> [DEBUG]: Leaving init_config_dir()
<1333239680.> [DEBUG]: Entering init_config_file()
<1333239680.> [DEBUG]: Leaving init_config_file()
<1333239680.> [DEBUG]: Entering init_lockfiles()
<1333239680.> [DEBUG]: Leaving init_lockfiles()
<1333239680.> [DEBUG]: Entering check_lockfile()
<1333239680.> [unknown]: --- Cop Starting [Version: Apache Traffic Server -
traffic_cop - 3.1.4-unstable - (build # 310 on Apr 1 2012 at 00:34:30)] ---
<1333239680.> [DEBUG]: Leaving check_lockfile()
<1333239680.> [DEBUG]: Leaving init()
<1333239680.> [DEBUG]: Entering check()
<1333239680.> [DEBUG]: Entering check_no_run()
<1333239680.> [DEBUG]: Entering transient_error(2, 500)
<1333239680.> [DEBUG]: Leaving transient_error(2, 500) --> false
<1333239680.> [DEBUG]: Leaving check_no_run() --> 0
<1333239680.> [DEBUG]: Entering read_config()
<1333239680.> [DEBUG]: Entering build_config_table(33932704)
<1333239680.> [DEBUG]: Leaving build_config_table(33932704)
<1333239680.> [DEBUG]: Entering process_syslog_config()
<1333239680.> [DEBUG]: Leaving process_syslog_config()
<1333239680.> [DEBUG]: Leaving read_config()
<1333239680.> [DEBUG]: Entering check_programs()
<1333239680.> [DEBUG]: Entering heartbeat_manager()
<1333239680.> [WARNING]: (cli test) unable to retrieve manager_binary
<1333239680.> [WARNING]: manager heartbeat [variable] failed [1]
<1333239680.> [DEBUG]: Leaving heartbeat_manager() --> -1
<1333239680.> [DEBUG]: Entering check_memory()
<1333239680.> [DEBUG]: Leaving check_memory()
<1333239680.> [DEBUG]: Entering millisleep(1)
<1333239680.> [DEBUG]: Leaving millisleep(1)
<1333239680.> [DEBUG]: Entering check_no_run()
<1333239680.> [DEBUG]: Entering transient_error(2, 500)
<1333239680.> [DEBUG]: Leaving transient_error(2, 500) --> false
<1333239680.> [DEBUG]: Leaving check_no_run() --> 0
<1333239680.> [DEBUG]: Entering read_config()
<1333239680.> [DEBUG]: Entering check_programs()
<1333239680.> [DEBUG]: Entering heartbeat_manager()
<1333239680.> [DEBUG]: Entering milliseconds()
<1333239680.> [DEBUG]: Leaving milliseconds()
<1333239680.> [DEBUG]: Entering open_socket(8088, (null), (null))
<1333239680.> [DEBUG]: Entering transient_error(115, 500)
<1333239680.> [DEBUG]: Leaving transient_error(115, 500) --> false
<1333239680.> [DEBUG]: Leaving open_socket(8088, 127.0.0.1, (null)) --> 8
<1333239680.> [DEBUG]: Entering milliseconds()
<1333239680.> [DEBUG]: Leaving milliseconds()
<1333239680.> [DEBUG]: Entering milliseconds()
<1333239680.> [DEBUG]: Leaving milliseconds()
<1333239680.> [DEBUG]: Entering milliseconds()
<1333239680.> [DEBUG]: Leaving milliseconds()
<1333239680.> [WARNING]: (manager test) bad response value
<1333239680.> [WARNING]: manager heartbeat [variable] failed [2]
<1333239680.> [WARNING]: killing manager
<1333239680.> [DEBUG]: Entering
safe_kill(/var/run/trafficserver/manager.lock, traffic_manager, 1)
<1333239680.> [DEBUG]: Entering set_alarm_warn()
<1333239680.> [DEBUG]: Leaving set_alarm_warn()
<1333239680.> [DEBUG]: Entering set_alarm_death()
<1333239680.> [DEBUG]: Leaving set_alarm_death()
<1333239680.> [DEBUG]: Leaving
safe_kill(/var/run/trafficserver/manager.lock, traffic_manager, 1)
<1333239680.> [DEBUG]: Leaving heartbeat_manager() --> -1
<1333239680.> [DEBUG]: Entering check_memory()
<1333239680.> [DEBUG]: Leaving check_memory()
<1333239680.> [DEBUG]: Entering millisleep(1)
<1333239680.> [DEBUG]: Leaving millisleep(1)
<1333239680.> [DEBUG]: Entering check_no_run()
<1333239680.> [DEBUG]: Entering transient_error(2, 500)
<1333239680.> [DEBUG]: Leaving transient_error(2, 500) --> false
<1333239680.> [DEBUG]: Leaving check_no_run() --> 0
<1333239680.> [DEBUG]: Entering read_config()
<1333239680.> [DEBUG]: Entering check_programs()
<1333239680.> [WARNING]: traffic_manager not running, making sure
traffic_server is dead
<1333239680.> [DEBUG]: Entering
safe_kill(/var/run/
[jira] [Created] (TS-1177) Download mirrors and cache hits
Download mirrors and cache hits --- Key: TS-1177 URL: https://issues.apache.org/jira/browse/TS-1177 Project: Traffic Server Issue Type: Improvement Reporter: Jack Bates I just applied to GSoC with a proposal to use RFC 6249 (Metalink/HTTP: Mirrors and Hashes) to discover requests for the same files from different mirrors and redirect clients to mirrors that are already cached I am filing this JIRA ticket describing my proposal to cause the Apache organization to process it [2]. Thanks for considering this proposal [1] http://www.google-melange.com/gsoc/proposal/review/google/gsoc2012/nottheoilrig/4001 [2] http://mail-archives.apache.org/mod_mbox/trafficserver-dev/201203.mbox/%3CF28ED27B-8224-4362-B98C-945530CADC7C%40me.com%3E -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1176) Eliminate the delayed delete of LogBuffer
Eliminate the delayed delete of LogBuffer - Key: TS-1176 URL: https://issues.apache.org/jira/browse/TS-1176 Project: Traffic Server Issue Type: Improvement Components: Logging Reporter: Leif Hedstrom Assignee: Leif Hedstrom Fix For: 3.1.4 There's a race condition in another place in the code, and it's obvious to me that this deferred delete was done to avoid this race condition. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1175) The LogBuffer object is allocated with new (and deallocated with delete)
The LogBuffer object is allocated with new (and deallocated with delete) Key: TS-1175 URL: https://issues.apache.org/jira/browse/TS-1175 Project: Traffic Server Issue Type: Improvement Components: Logging Reporter: Leif Hedstrom Fix For: 3.3.0 We should at least use a class allocator for LogBuffer itself, and perhaps even its internal buffer. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1174) Should we eliminate all ERR_* "status" message in squid logging?
Should we eliminate all ERR_* "status" message in squid logging?
Key: TS-1174
URL: https://issues.apache.org/jira/browse/TS-1174
Project: Traffic Server
Issue Type: Improvement
Components: Logging
Reporter: Leif Hedstrom
Fix For: 3.3.0
In more recent versions of Squid, ERR_* status messages have been merged into
the status code. E.g.
{code}
ERR_*
Errors are now contained in the status code.
{code}
Should we do likewise?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1173) remap.config comments are wrong
remap.config comments are wrong --- Key: TS-1173 URL: https://issues.apache.org/jira/browse/TS-1173 Project: Traffic Server Issue Type: Bug Components: Configuration Affects Versions: 3.1.3 Reporter: Alan M. Carroll Assignee: Leif Hedstrom Priority: Minor Fix For: 3.3.0 The comments in remap.config describe the configuration lines incorrectly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1172) Remove remap/StringHash.{cc,h}
Remove remap/StringHash.{cc,h}
--
Key: TS-1172
URL: https://issues.apache.org/jira/browse/TS-1172
Project: Traffic Server
Issue Type: Improvement
Components: HTTP
Reporter: Leif Hedstrom
Assignee: Leif Hedstrom
Fix For: 3.1.4
These files are not used, nuke.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1171) Crash report: http_ui cache lookup, double free
Crash report: http_ui cache lookup, double free
---
Key: TS-1171
URL: https://issues.apache.org/jira/browse/TS-1171
Project: Traffic Server
Issue Type: Bug
Components: Core
Affects Versions: 3.1.4
Reporter: Zhao Yongming
{code}
*** glibc detected *** /opt/ats/bin/traffic_server: double free or corruption
(!prev): 0x013e9a50 ***
=== Backtrace: =
/lib64/libc.so.6(+0x77856)[0x2b14ef973856]
/lib64/libc.so.6(cfree+0x6c)[0x2b14ef97774c]
/opt/ats/bin/traffic_server(ShowCache::~ShowCache()+0x20)[0x6428c0]
/opt/ats/bin/traffic_server(ShowCont::done(int, int, void*)+0x23)[0x5e1c63]
/opt/ats/bin/traffic_server(ShowCache::handleCacheEvent(int,
Event*)+0x15d7)[0x641ee7]
/opt/ats/bin/traffic_server(Cache::open_read(Continuation*, INK_MD5*,
CacheFragType, char*, int)+0x42c)[0x64e62c]
/opt/ats/bin/traffic_server(ShowCache::lookup_url(int, Event*)+0x1a5)[0x63f655]
/opt/ats/bin/traffic_server(EThread::process_event(Event*, int)+0x90)[0x6a6350]
/opt/ats/bin/traffic_server(EThread::execute()+0x31b)[0x6a6c3b]
/opt/ats/bin/traffic_server[0x6a5142]
/lib64/libpthread.so.0(+0x8e2c)[0x2b14ed0f5e2c]
/lib64/libc.so.6(clone+0x6d)[0x2b14ef9d63cd]
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1170) ats_ip_getbestaddrinfo should provide better options
ats_ip_getbestaddrinfo should provide better options Key: TS-1170 URL: https://issues.apache.org/jira/browse/TS-1170 Project: Traffic Server Issue Type: Improvement Components: Network Affects Versions: 3.1.3 Reporter: Alan M. Carroll Assignee: Alan M. Carroll Priority: Minor Fix For: sometime ats_ip_getaddrinfo should support better options about how it selects addresses. * Pick just one address that can be either family. * Force IPv4, IPv6 or be able to prefer if two are equivalent. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1169) in enable-debug and pristine_host_hdr=0 mode, TS will crash when purge a cached object which is after TSCacheUrlSet
in enable-debug and pristine_host_hdr=0 mode, TS will crash when purge a cached
object which is after TSCacheUrlSet
---
Key: TS-1169
URL: https://issues.apache.org/jira/browse/TS-1169
Project: Traffic Server
Issue Type: Bug
Affects Versions: 3.0.4, 3.1.3
Environment: configure --enable-debug
Reporter: Conan Wang
{code}
#6 0x000100d269af in _ink_assert (a=0x1003c6be0 "md5a == md5b ||
t_state.txn_conf->maintain_pristine_host_hdr", f=0x1003c514e "HttpSM.cc",
l=3921) at ink_assert.cc:44
#7 0x000100123e59 in HttpSM::do_cache_delete_all_alts (this=0x109d41190,
cont=0x0) at HttpSM.cc:3921
{code}
in HttpSM::do_cache_delete_all_alts debug code, if a object key is rewritten by
TSCacheUrlSet, md5a will not equal md5b, and it will crash because
maintain_pristine_host_hdr = 0 ( when disable pristine_host_hdr ).
Anyway, the cached object is purged successfully. Maybe it's just a wrong
assert which didn't consider TSCacheUrlSet case.
{code}
#ifdef DEBUG
INK_MD5 md5a;
INK_MD5 md5b;
t_state.hdr_info.client_request.url_get()->MD5_get(&md5a);
t_state.cache_info.lookup_url->MD5_get(&md5b);
ink_assert(md5a == md5b || t_state.txn_conf->maintain_pristine_host_hdr);
#endif
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1168) Remap blind tunnel handling is not IPv6 compliant
Remap blind tunnel handling is not IPv6 compliant - Key: TS-1168 URL: https://issues.apache.org/jira/browse/TS-1168 Project: Traffic Server Issue Type: Bug Components: Core Affects Versions: 3.1.3 Reporter: Alan M. Carroll Priority: Minor Fix For: 3.1.4 When a blind tunnel request is received, the hostname is set as the IP address. This is hardwired for IPv4. ink_gethostbyname should be replaced by getaddrinfo and the logic made IPv6 compliant. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1167) proxy/ParentSelection.cc is not IPv6 compliant.
proxy/ParentSelection.cc is not IPv6 compliant. --- Key: TS-1167 URL: https://issues.apache.org/jira/browse/TS-1167 Project: Traffic Server Issue Type: Bug Components: Clustering Affects Versions: 3.1.3 Reporter: Alan M. Carroll Priority: Minor Fix For: 3.1.4 setup_socks_servers is IPv4 only. It should be changed to use getaddrinfo() and handle IPv6 addresses. This may require changing ParentRecord. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1166) proxy/Stuffer.cc is not IPv6 compatible.
proxy/Stuffer.cc is not IPv6 compatible. Key: TS-1166 URL: https://issues.apache.org/jira/browse/TS-1166 Project: Traffic Server Issue Type: Bug Components: Clustering Affects Versions: 3.1.3 Reporter: Alan M. Carroll Priority: Minor Fix For: 3.1.4 Parent IP tracking in proxy/Stuff.cc is IPv4 only. Also the use of ink_gethostbyname should be removed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1165) Health checks not working
Health checks not working - Key: TS-1165 URL: https://issues.apache.org/jira/browse/TS-1165 Project: Traffic Server Issue Type: Bug Components: Core Affects Versions: 3.1.3 Reporter: Igor Brezac Fix For: 3.1.4 Health checks not working -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1164) a race condition in cache init
a race condition in cache init --- Key: TS-1164 URL: https://issues.apache.org/jira/browse/TS-1164 Project: Traffic Server Issue Type: Bug Components: Cache Affects Versions: 3.0.0, 3.1.1 Environment: all Reporter: weijin Assignee: weijin Fix For: 3.1.6 there is a race condition in CacheProcessor::diskInitialized, which may lead to cache can not be enabled. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1163) Raw disks with more than (2^32)-1 sectors (usually 2TB) are not supported on linux
Raw disks with more than (2^32)-1 sectors (usually 2TB) are not supported on linux -- Key: TS-1163 URL: https://issues.apache.org/jira/browse/TS-1163 Project: Traffic Server Issue Type: Bug Components: Cache Reporter: B Wyatt Assignee: B Wyatt Due to 32bit integers in both the trafficersever code and the ioctl used to determine raw disk size, the number of sectors reported to the cache storage system is bound to 0-0x. If a disk has 512 byte sectors and is larger than 2TB it will report (num_sectors % 0x) * 512 bytes avaliable. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1162) UnixNetVConnection.cc assertion when accepting a TLS connection
UnixNetVConnection.cc assertion when accepting a TLS connection
---
Key: TS-1162
URL: https://issues.apache.org/jira/browse/TS-1162
Project: Traffic Server
Issue Type: Bug
Components: Core
Affects Versions: 3.1.4
Reporter: James Peach
Trunk always crashes when accepting a TLS connection:
FATAL: UnixNetVConnection.cc:801: failed assert `vio->mutex->thread_holding ==
this_ethread()`
/opt/ats/bin/traffic_server - STACK TRACE:
0 libtsutil.3.dylib 0x00010c3e7ee7 ink_fatal + 359
1 libtsutil.3.dylib 0x00010c3e6e22 _ink_assert + 66
2 traffic_server 0x00010b9e6d9a
_ZN18UnixNetVConnection11set_enabledEP3VIO + 90
3 traffic_server 0x00010b9e681d
_ZN18UnixNetVConnection8reenableEP3VIO + 93
4 traffic_server 0x00010b7bfcd6 _ZN3VIO8reenableEv +
54
5 traffic_server 0x00010b9e5cd9
_ZN18UnixNetVConnection10do_io_readEP12ContinuationxP9MIOBuffer + 297
6 traffic_server 0x00010b792611
_ZN11VConnection5do_ioEiP12ContinuationxP9MIOBufferi + 129
7 traffic_server 0x00010b9d6da9
_ZN21SSLNextProtocolAccept9mainEventEiPv + 329
8 traffic_server 0x00010b792229
_ZN12Continuation11handleEventEiPv + 121
9 traffic_server 0x00010b9e89bd
_ZN18UnixNetVConnection11acceptEventEiP5Event + 829
10 traffic_server 0x00010b792229
_ZN12Continuation11handleEventEiPv + 121
11 traffic_server 0x00010ba0905d
_ZN7EThread13process_eventEP5Eventi + 349
12 traffic_server 0x00010ba09367
_ZN7EThread7executeEv + 215
13 traffic_server 0x00010ba080ed
_ZL21spawn_thread_internalPv + 109
14 libsystem_c.dylib 0x7fff8fcb78bf _pthread_start + 335
15 libsystem_c.dylib 0x7fff8fcbab75 thread_start + 13
[Mar 22 21:58:45.009] Manager {0x7fff79b01960} ERROR:
[LocalManager::pollMgmtProcessServer] Server Process terminated due to Sig 6:
Abort trap: 6
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1161) insafe raw device in storage.config
insafe raw device in storage.config --- Key: TS-1161 URL: https://issues.apache.org/jira/browse/TS-1161 Project: Traffic Server Issue Type: Bug Components: Core Reporter: Zhao Yongming if you system is on /dev/sda and you put /dev/sda into storage.config, TS will destroy the data on /dev/sda without any hesitate. this is proved to be true, please do not try, trust me. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1160) FATAL: ink_memalign: couldn't allocate 602439680 bytes at alignment 4096 - insufficient memory ts crash
FATAL: ink_memalign: couldn't allocate 602439680 bytes at alignment 4096 - insufficient memory ts crash - Key: TS-1160 URL: https://issues.apache.org/jira/browse/TS-1160 Project: Traffic Server Issue Type: Bug Components: Core Affects Versions: 3.0.3 Environment: centos 6.0 x86_64 Reporter: bettydramit FATAL: ink_memalign: couldn't allocate 602439680 bytes at alignment 4096 - insufficient memory /usr/bin/traffic_server - STACK TRACE: /usr/lib64/trafficserver/libtsutil.so.3(ink_fatal_va+0x9d)[0x2ab0905926dd] /usr/lib64/trafficserver/libtsutil.so.3(ink_fatal+0x88)[0x2ab090592838] /usr/lib64/trafficserver/libtsutil.so.3(ink_memalign+0x9c)[0x2ab09059414c] /usr/bin/traffic_server(_ZN9CacheSync9mainEventEiP5Event+0x2c8)[0x644ab8] /usr/bin/traffic_server(_ZN3Vol12aggWriteDoneEiP5Event+0x5d7)[0x668567] /usr/bin/traffic_server(_ZN13AIOThreadInfo5startEiP5Event+0x945)[0x6772d5] /usr/bin/traffic_server(_ZN7EThread7executeEv+0xb86)[0x6ac6a6] /usr/bin/traffic_server[0x6aa4a2] /lib64/libpthread.so.0(+0x77f1)[0x2ab0907bd7f1] /lib64/libc.so.6(clone+0x6d)[0x2ab092e4792d] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1159) add compiler hints to debug logging
add compiler hints to debug logging --- Key: TS-1159 URL: https://issues.apache.org/jira/browse/TS-1159 Project: Traffic Server Issue Type: Improvement Components: Logging Reporter: James Peach Assignee: James Peach Priority: Minor Fix For: 3.1.4 Add compiler hints to specify that we usually don't emit diagnostic logging. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1158) Race on mutex switching for NetVConnections in UnixNetVConnection::mainEvent
Race on mutex switching for NetVConnections in UnixNetVConnection::mainEvent Key: TS-1158 URL: https://issues.apache.org/jira/browse/TS-1158 Project: Traffic Server Issue Type: Bug Components: Core Affects Versions: 3.0.3 Environment: ALL Reporter: John Plevyak Assignee: John Plevyak Fix For: 3.1.4 Because of the way session management works, the vio.mutex must be re-verified to be identical to the one the lock was taken on after the lock is acquired. Otherwise there is a race when the mutex is switched allowing such that the old lock is held while the new lock is in not held. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1157) freelist for TSAPI's and plugin "structs"
freelist for TSAPI's and plugin "structs" - Key: TS-1157 URL: https://issues.apache.org/jira/browse/TS-1157 Project: Traffic Server Issue Type: New Feature Components: TS API Reporter: Leif Hedstrom Fix For: 3.3.0 It could be useful to expose a simple "freelist" APIs, which lets plugins "allocate" and "free" simple C structs on a freelist, instead of having to call TSmalloc / TSfree. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1156) Multiple "time" tags in a log format gets bad results
Multiple "time" tags in a log format gets bad results
-
Key: TS-1156
URL: https://issues.apache.org/jira/browse/TS-1156
Project: Traffic Server
Issue Type: Bug
Components: Logging
Reporter: Leif Hedstrom
Fix For: 3.1.4
It seems putting two (or more) "date time" tags in a custom log generates bad
results. For example, with one such tag, I see:
{code}
[%]
[19/Mar/2012:14:30:51 -0600]
{code}
vs
{code}
[% %]
[183876 07/Apr/2028:19:26:39 -0600]
{code}
This is obviously not the correct date now for either tags (the first is not
correct either). I'm guessing something in the marshalling code might be
corrupting the timestamp?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1155) POST requests that are chunked encoding hang when going forward to origin over SSL
POST requests that are chunked encoding hang when going forward to origin over SSL -- Key: TS-1155 URL: https://issues.apache.org/jira/browse/TS-1155 Project: Traffic Server Issue Type: Bug Components: HTTP Affects Versions: 3.0.2 Reporter: William Bardwell If you make a chunked encoded POST request, e.g.: curl -H "Transfer-Encoding: chunked" -d@/etc/ca-certificates.conf http://example.com/cgi-bin/cgi.pl Where ATS is going forward to the origin over SSL, it junk hangs for a little while and ends up returning a 502 response. The problem seems to be code at proxy/http/HttpTransact.cc:5273 which only checks for chunked encoding when the scheme is http. Just removing the extra scheme check makes it work for me. I don't know why it has that check, especially since it is checking for http or https right before that. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1154) quick_filter on HEAD does not work
quick_filter on HEAD does not work -- Key: TS-1154 URL: https://issues.apache.org/jira/browse/TS-1154 Project: Traffic Server Issue Type: Bug Components: HTTP Reporter: Zhao Yongming Assignee: weijin we take quick filter as a good solution for some security concern, but when I set it to 0x0733, it does not allow HEAD in, but setting as 0x0723 does that. Weijin have the patch in our tree: https://gitorious.org/trafficserver/taobao/commit/cb23b87d167da4074e047fabc94786003ee94e9a/diffs/db7d0e5be69988b531e8d1e4eea717e6d46df5cd I will commit if no one complain in 2 days. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1153) On Solaris, link with libumem by default
On Solaris, link with libumem by default Key: TS-1153 URL: https://issues.apache.org/jira/browse/TS-1153 Project: Traffic Server Issue Type: Improvement Components: Performance Environment: Solaris Reporter: Igor Galić http://developers.sun.com/solaris/articles/multiproc/multiproc.html Maybe we should make use of that and link to libumem by default. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1152) http_ui error,when i get http://localhost/cache/
http_ui error,when i get http://localhost/cache/
Key: TS-1152
URL: https://issues.apache.org/jira/browse/TS-1152
Project: Traffic Server
Issue Type: Bug
Components: Web UI
Affects Versions: 3.0.4
Environment: centos 6 x86_64
Reporter: bettydramit
When i enable http_ui ，I got follow error (get http://xxx.xxx.xxx.xxx/cache/)
[Mar 19 16:46:17.778] Manager {13989191624} ERROR:
[WebHttpHandleConnection] /favicon.ico not valid autoconf file
[Mar 19 16:46:17.778] Manager {13989191624} ERROR: (last system error 11:
Resource temporarily unavailable)
[Mar 19 16:46:19.089] Manager {13989191624} ERROR:
[WebHttpHandleConnection] /favicon.ico not valid autoconf file
[Mar 19 16:46:19.090] Manager {13989191624} ERROR: (last system error 11:
Resource temporarily unavailable)
[Mar 19 16:46:20.763] Manager {13989191624} ERROR:
[WebHttpHandleConnection] /favicon.ico not valid autoconf file
[Mar 19 16:46:20.763] Manager {13989191624} ERROR: (last system error 11:
Resource temporarily unavailable)
[Mar 19 16:58:21.906] Manager {13989191624} ERROR:
[WebHttpHandleConnection] /robots.txt not valid autoconf file
[Mar 19 16:58:21.906] Manager {13989191624} ERROR: (last system error 11:
Resource temporarily unavailable)
[Mar 19 17:01:43.703] Manager {13989191624} ERROR:
[WebHttpHandleConnection] /favicon.ico not valid autoconf file
[Mar 19 17:01:43.703] Manager {13989191624} ERROR: (last system error 11:
Resource temporarily unavailable)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1151) in some strange situation, cop will crash
in some strange situation, cop will crash
-
Key: TS-1151
URL: https://issues.apache.org/jira/browse/TS-1151
Project: Traffic Server
Issue Type: Bug
Reporter: Zhao Yongming
Assignee: Zhao Yongming
we get some strange crash, the manager & cop may die, we are not sure what that
is, but I'd like to start one Issue here if we have other same issue.
here is the log in /var/log/messages
{code}
Mar 19 10:11:06 cache162.cn77 kernel:: [2510081.212455] [ET_NET 3][319]:
segfault at 2aaae6e986bc ip 003f7f27bdbe sp 40be2188 error 4 in
libc-2.5.so[3f7f20+14d000]
Mar 19 10:11:09 cache162.cn77 traffic_manager[305]: {0x7fd3a665c720} FATAL:
[LocalManager::pollMgmtProcessServer] Error in read (errno: 104)
Mar 19 10:11:09 cache162.cn77 traffic_manager[305]: {0x7fd3a665c720} FATAL:
(last system error 104: Connection reset by peer)
Mar 19 10:11:09 cache162.cn77 traffic_manager[305]: {0x7fd3a665c720} ERROR:
[LocalManager::sendMgmtMsgToProcesses] Error writing message
Mar 19 10:11:09 cache162.cn77 traffic_manager[305]: {0x7fd3a665c720} ERROR:
(last system error 32: Broken pipe)
Mar 19 10:11:09 cache162.cn77 traffic_cop[303]: cop received child status
signal [305 2816]
Mar 19 10:11:09 cache162.cn77 traffic_cop[303]: traffic_manager not running,
making sure traffic_server is dead
Mar 19 10:11:09 cache162.cn77 traffic_cop[303]: spawning traffic_manager
Mar 19 10:11:16 cache162.cn77 traffic_manager[1227]: NOTE: --- Manager Starting
---
Mar 19 10:11:16 cache162.cn77 traffic_manager[1227]: NOTE: Manager Version:
Apache Traffic Server - traffic_manager - 3.0.2 - (build # 299 on Mar 9 2012
at 09:55:44)
Mar 19 10:11:16 cache162.cn77 traffic_manager[1227]: {0x7f8ae2f48720} STATUS:
opened /var/log/trafficserver/manager.log
Mar 19 10:11:23 cache162.cn77 traffic_cop[303]: (cli test) unable to retrieve
manager_binary
Mar 19 10:11:39 cache162.cn77 traffic_server[1260]: NOTE: --- Server Starting
---
Mar 19 10:11:39 cache162.cn77 traffic_server[1260]: NOTE: Server Version:
Apache Traffic Server - traffic_server - 3.0.2 - (build # 299 on Mar 9 2012 at
09:56:00)
Mar 19 10:11:46 cache162.cn77 traffic_server[1260]: {0x2ad4afd3d970} STATUS:
opened /var/log/trafficserver/diags.log
Mar 19 10:15:06 cache162.cn77 kernel:: [2510320.713808] [ET_NET 3][1277]:
segfault at 2aab1cfa6a03 ip 003f7f27bdbe sp 4141c188 error 4 in
libc-2.5.so[3f7f20+14d000]
Mar 19 10:15:06 cache162.cn77 traffic_manager[1227]: {0x7f8ae2f48720} ERROR:
[LocalManager::pollMgmtProcessServer] Server Process terminated due to Sig 11:
Segmentation fault
Mar 19 10:15:06 cache162.cn77 traffic_manager[1227]: {0x7f8ae2f48720} ERROR:
(last system error 2: No such file or directory)
Mar 19 10:15:06 cache162.cn77 traffic_manager[1227]: {0x7f8ae2f48720} ERROR:
[Alarms::signalAlarm] Server Process was reset
Mar 19 10:15:06 cache162.cn77 traffic_manager[1227]: {0x7f8ae2f48720} ERROR:
(last system error 2: No such file or directory)
Mar 19 10:15:08 cache162.cn77 traffic_server[2412]: NOTE: --- Server Starting
---
Mar 19 10:15:08 cache162.cn77 traffic_server[2412]: NOTE: Server Version:
Apache Traffic Server - traffic_server - 3.0.2 - (build # 299 on Mar 9 2012 at
09:56:00)
Mar 19 10:15:08 cache162.cn77 traffic_server[2412]: {0x2af4c2ad5970} STATUS:
opened /var/log/trafficserver/diags.log
Mar 19 10:54:53 cache162.cn77 ops.hdmon.power: [ OK ] Power Unit PSU 1:
OK;Power Unit PSU 2: OK.
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1150) Improve on some header handling functionality
Improve on some header handling functionality - Key: TS-1150 URL: https://issues.apache.org/jira/browse/TS-1150 Project: Traffic Server Issue Type: Bug Components: Core Reporter: Leif Hedstrom Assignee: Leif Hedstrom Fix For: 3.1.4 There are a few performance and functionality improvements we can do around header handling. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1149) pretty up automate output
pretty up automate output - Key: TS-1149 URL: https://issues.apache.org/jira/browse/TS-1149 Project: Traffic Server Issue Type: Improvement Components: Build Reporter: James Peach Assignee: James Peach Priority: Trivial automake is super ugly by default. Make it pretty. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1148) support systemd init system
support systemd init system --- Key: TS-1148 URL: https://issues.apache.org/jira/browse/TS-1148 Project: Traffic Server Issue Type: Improvement Components: Packaging Reporter: Jan-Frode Myklebust Fix For: 3.0.3 ATS should support systemd init system for managing the trafficserver service. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1147) deprecate records.config SSL configuration
deprecate records.config SSL configuration -- Key: TS-1147 URL: https://issues.apache.org/jira/browse/TS-1147 Project: Traffic Server Issue Type: Improvement Components: SSL Reporter: James Peach Priority: Minor Since ssl_multicert.config is a strict superset of the SSL certificate configuration in records.config, we should deprecate configuring SSL certificates in records.config and make ssl_multicert.config the One True Way. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1146) RFC 5077 TLS Session tickets
RFC 5077 TLS Session tickets Key: TS-1146 URL: https://issues.apache.org/jira/browse/TS-1146 Project: Traffic Server Issue Type: Improvement Components: SSL Reporter: James Peach For supporting RFC 5077 TLS Session tickets across a ATS cluster, all the machines need to have the same server ticket. See https://github.com/apache/httpd rev 967d943b93498233f0ec81a5b48706fdb6892dfd -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1145) clang build fixes
clang build fixes - Key: TS-1145 URL: https://issues.apache.org/jira/browse/TS-1145 Project: Traffic Server Issue Type: Bug Components: Build Reporter: James Peach Assignee: James Peach Priority: Minor A handful of build fixes for svn versions of clang++. It's strict in slightly different ways than the current release version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1144) fox out of tree builds
fox out of tree builds -- Key: TS-1144 URL: https://issues.apache.org/jira/browse/TS-1144 Project: Traffic Server Issue Type: Bug Components: Build Reporter: James Peach Assignee: James Peach Fixes some minor issues in the build system when building sources in separate directory than the obj files. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1143) IpMap::fill fails to handle some edge cases.
IpMap::fill fails to handle some edge cases. Key: TS-1143 URL: https://issues.apache.org/jira/browse/TS-1143 Project: Traffic Server Issue Type: Bug Affects Versions: 3.1.2 Reporter: Alan M. Carroll Assignee: Alan M. Carroll Priority: Minor Fix For: 3.1.3 Three related issues: 1) Input ranges with a min value of zero can be mishandled due to wrap. 2) Input ranges with a maximum value can be mishandled due to wrap. 3) Fill sometimes fails to insert ranges between two existing ranges. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1142) we need to record ram hit in ram cache hit
we need to record ram hit in ram cache hit -- Key: TS-1142 URL: https://issues.apache.org/jira/browse/TS-1142 Project: Traffic Server Issue Type: Improvement Components: Cache, Stats Affects Versions: 3.1.4 Reporter: Zhao Yongming Assignee: kuotai we need to record the ram & mem hites in stats -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1141) Server intercerpt performance problems.
Server intercerpt performance problems. --- Key: TS-1141 URL: https://issues.apache.org/jira/browse/TS-1141 Project: Traffic Server Issue Type: Improvement Components: Core Reporter: Leif Hedstrom Fix For: 3.3.0 It seems server intercept plugins are fairly expensive. A very simple one, serving a few bytes out of RAM, can only do in the order of 20K QPS, whereas the same server serving out of RAM cache do wo 175k QPS. I know there will be overhead in plugin APIs, but almost 10x seems quite high. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1140) Implement HTTP method filtering in ip_allow.config
Implement HTTP method filtering in ip_allow.config -- Key: TS-1140 URL: https://issues.apache.org/jira/browse/TS-1140 Project: Traffic Server Issue Type: New Feature Components: HTTP Affects Versions: 3.1.2, 3.1.3 Reporter: Igor Brezac Priority: Critical Fix For: 3.1.3 Implement HTTP method filtering in ip_allow.config (and deprecate proxy.config.http.quick_filter.mask) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1139) Expose API such that plugins can easily be written in a glue-language such as Lua.
Expose API such that plugins can easily be written in a glue-language such as Lua. -- Key: TS-1139 URL: https://issues.apache.org/jira/browse/TS-1139 Project: Traffic Server Issue Type: New Feature Reporter: Igor Galić Let's be honest here: our plugin API is great. But woulnd't it be great if we didn't just expose it to C/C++ but also to a script language, like Lua? I think it would be cool if an admin (I think they are be our main target group here) could hack up a couple of lines of Lua script and already have a great (prototype of a) plugin. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1138) IpMap::fill does not handle singleton, then range correctly.
IpMap::fill does not handle singleton, then range correctly. Key: TS-1138 URL: https://issues.apache.org/jira/browse/TS-1138 Project: Traffic Server Issue Type: Bug Components: Core Affects Versions: 3.1.2 Reporter: Alan M. Carroll Assignee: Alan M. Carroll Priority: Minor Fix For: 3.1.3 If you use IpMap::fill on a singleton, and then a range, the resulting ranges can overlap the singleton. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1137) Expose API such that tests can easily be written in a glue-language such as Lua.
Expose API such that tests can easily be written in a glue-language such as Lua. Key: TS-1137 URL: https://issues.apache.org/jira/browse/TS-1137 Project: Traffic Server Issue Type: New Feature Components: TS API Reporter: Igor Galić To unify and simplify our tests it would be great to have them in a script language. Lua is an ideal candidate as it is easy to embed. Imagine what it would be like if users experiencing a bug could file a report with a test case attached that reproduces it? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1136) Expose Configuration API such that config files can be written (or scripted) in a glue-language such as Lua
Expose Configuration API such that config files can be written (or scripted) in a glue-language such as Lua --- Key: TS-1136 URL: https://issues.apache.org/jira/browse/TS-1136 Project: Traffic Server Issue Type: New Feature Components: Configuration Reporter: Igor Galić To unify and simplify our configuration it would be great to have them in a script language. Lua is an ideal candidate as it is easy to embed and it would make for a wonderful - and powerful DSL. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1135) support wildcard certificates for ServerNameIndication (SNI)
support wildcard certificates for ServerNameIndication (SNI) Key: TS-1135 URL: https://issues.apache.org/jira/browse/TS-1135 Project: Traffic Server Issue Type: Improvement Components: SSL Reporter: James Peach The ServerNameIndication support added in TS-472 doesn't handle wildcard certificates. We need to add certificate parsing support to detect wildcard certificates and then (if there is not an exact match) choose the certificate with the longest wildcard match. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1134) TSNetAcceptNamedProtocol should fail if NPN is not supported
TSNetAcceptNamedProtocol should fail if NPN is not supported Key: TS-1134 URL: https://issues.apache.org/jira/browse/TS-1134 Project: Traffic Server Issue Type: Bug Components: TS API Reporter: James Peach Assignee: James Peach Priority: Minor Fix For: 3.2.0 If NPN is not supported by the OpenSSL version, TSNetAcceptNamedProtocol() should always fail so that plugins don't' get the wrong idea. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1133) Make remap max-host length configure.ac configurable
Make remap max-host length configure.ac configurable Key: TS-1133 URL: https://issues.apache.org/jira/browse/TS-1133 Project: Traffic Server Issue Type: Improvement Components: Remap API Reporter: Leif Hedstrom Assignee: Leif Hedstrom Fix For: 3.1.3 Right now, we have a hardcoded limit of 256 bytes on the Host matching. We should make this configurable. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1132) Clean up usage of HDR_BUF_RONLY_HEAPS
Clean up usage of HDR_BUF_RONLY_HEAPS - Key: TS-1132 URL: https://issues.apache.org/jira/browse/TS-1132 Project: Traffic Server Issue Type: Improvement Components: Core Reporter: Leif Hedstrom Fix For: 3.1.4 We should clean up the usage of HDR_BUF_RONLY_HEAPS, and not assume it's always "3". In addition, we should consider making this configurable, via either records.config, or at least configure.ac. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1131) fails to build on RHEL6 ppc64
fails to build on RHEL6 ppc64 - Key: TS-1131 URL: https://issues.apache.org/jira/browse/TS-1131 Project: Traffic Server Issue Type: Bug Components: Build Affects Versions: 3.0.3 Environment: RHEL6 ppc64 Reporter: Jan-Frode Myklebust I fail to build ats 3.0.3 on RHEL6/ppc64. It fails with the message: #error "unsupported processor" from lib/ts/ink_queue.h:119. Ref: http://koji.fedoraproject.org/koji/getfile?taskID=3884843&name=build.log -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1130) ink_time_t is 64bit on x86_64
ink_time_t is 64bit on x86_64 - Key: TS-1130 URL: https://issues.apache.org/jira/browse/TS-1130 Project: Traffic Server Issue Type: Sub-task Reporter: Zhao Yongming Assignee: weijin Fix For: 3.1.3 Weijin: paste your patch here, :D -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1129) gzip (or deflate) plugin // the return
gzip (or deflate) plugin // the return -- Key: TS-1129 URL: https://issues.apache.org/jira/browse/TS-1129 Project: Traffic Server Issue Type: Improvement Components: Plugins Affects Versions: 3.0.2 Reporter: Otto van der Schaaf Attachments: gzip.c this is a more battle hardened version of the deflate compressor plugin we use in production for a few months now // WHAT THIS PLUGIN DOES: // in spite of its name, it compresses responses to the raw deflate format. // it also normalizes the accept-encoding header from user agent requests // to either deflate or nothing. it compresses responses from origins only, // though it can be modified easily to also compress contents from cache. // // MAJOR ISSUES: // - there is an issue with *some* origins that send connection:close. // the plugin will not execute in that situation as a temporary fix. // - the workings of this plugin support our use case, but probably is not // on size fits all. it shouldnt be too hard to adjust it to your own needs though. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1128) gcc don't like break strict-aliasing in I_ProxyAllocator.h
gcc don't like break strict-aliasing in I_ProxyAllocator.h
--
Key: TS-1128
URL: https://issues.apache.org/jira/browse/TS-1128
Project: Traffic Server
Issue Type: Improvement
Components: Cleanup
Affects Versions: 3.1.4
Reporter: Zhao Yongming
Priority: Minor
{code}
cc1plus: warnings being treated as errors
../../iocore/eventsystem/I_ProxyAllocator.h: In member function 'virtual
UnixNetVConnection* SSLNetAccept::allocateThread(EThread*)':
../../iocore/eventsystem/I_ProxyAllocator.h:54: error: dereferencing pointer
'' does break strict-aliasing rules
../../iocore/eventsystem/I_ProxyAllocator.h:54: note: initialized from here
cc1plus: warnings being treated as errors
../../iocore/eventsystem/I_ProxyAllocator.h: In member function 'virtual
UnixNetVConnection* UnixNetProcessor::allocateThread(EThread*)':
../../iocore/eventsystem/I_ProxyAllocator.h:54: error: dereferencing pointer
'' does break strict-aliasing rules
../../iocore/eventsystem/I_ProxyAllocator.h:54: note: initialized from here
../../iocore/eventsystem/I_ProxyAllocator.h: In member function 'virtual
UnixNetVConnection* SSLNetProcessor::allocateThread(EThread*)':
../../iocore/eventsystem/I_ProxyAllocator.h:54: error: dereferencing pointer
'' does break strict-aliasing rules
../../iocore/eventsystem/I_ProxyAllocator.h:54: note: initialized from here
cc1plus: warnings being treated as errors
../../iocore/eventsystem/I_ProxyAllocator.h: In member function 'virtual
UnixNetVConnection* NetAccept::allocateThread(EThread*)':
../../iocore/eventsystem/I_ProxyAllocator.h:54: error: dereferencing pointer
'' does break strict-aliasing rules
../../iocore/eventsystem/I_ProxyAllocator.h:54: note: initialized from here
make[2]: *** [SSLUnixNet.o] Error 1
make[2]: *** Waiting for unfinished jobs
make[2]: *** [UnixNetProcessor.o] Error 1
mv -f .deps/NetVConnection.Tpo .deps/NetVConnection.Po
mv -f .deps/Net.Tpo .deps/Net.Po
mv -f .deps/UDPIOEvent.Tpo .deps/UDPIOEvent.Po
make[2]: *** [UnixNetAccept.o] Error 1
mv -f .deps/Connection.Tpo .deps/Connection.Po
mv -f .deps/SSLCertLookup.Tpo .deps/SSLCertLookup.Po
mv -f .deps/UnixConnection.Tpo .deps/UnixConnection.Po
mv -f .deps/SSLConfig.Tpo .deps/SSLConfig.Po
mv -f .deps/SSLNet.Tpo .deps/SSLNet.Po
mv -f .deps/UnixNet.Tpo .deps/UnixNet.Po
mv -f .deps/UnixNetPages.Tpo .deps/UnixNetPages.Po
mv -f .deps/Socks.Tpo .deps/Socks.Po
mv -f .deps/SSLNetVConnection.Tpo .deps/SSLNetVConnection.Po
mv -f .deps/UnixNetVConnection.Tpo .deps/UnixNetVConnection.Po
make[2]: Leaving directory `/root/rpmbuild/BUILD/trafficserver-3.0.2/iocore/net'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/rpmbuild/BUILD/trafficserver-3.0.2/iocore'
make: *** [all-recursive] Error 1
error: Bad exit status from /var/tmp/rpm-tmp.VFqSxi (%build)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1127) Wrong assignment of incoming address
Wrong assignment of incoming address Key: TS-1127 URL: https://issues.apache.org/jira/browse/TS-1127 Project: Traffic Server Issue Type: Bug Components: HTTP Affects Versions: 3.1.2 Reporter: Yakov Kopel Fix For: 3.1.4 In HttpSM.cc file (attach_client_session) there are two lines: ink_inet_copy(&t_state.client_info.addr, netvc->get_remote_addr()); t_state.client_info.port = netvc->get_local_port(); instead of: ink_inet_copy(&t_state.client_info.addr, netvc->get_local_addr()); t_state.client_info.port = netvc->get_local_port(); -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1126) traffic_server is unable to bind 127.0.0.1:8084 (the default mgmt port) on OSX
traffic_server is unable to bind 127.0.0.1:8084 (the default mgmt port) on OSX
--
Key: TS-1126
URL: https://issues.apache.org/jira/browse/TS-1126
Project: Traffic Server
Issue Type: Bug
Components: Management API
Affects Versions: 3.1.2
Reporter: Leif Hedstrom
Priority: Critical
Fix For: 3.1.3
When we start up, it errors out binding 8084:
[Mar 1 16:40:33.937] Server {0x7fff74cdb960} ERROR: Could not bind or listen
to port 8084 (error: -1)
[Mar 1 16:40:33.937] Server {0x7fff74cdb960} WARNING: unable to listen on port
8084: -1 49, Can't assign requested address
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1125) POST's with Expect: 100-continue are slowed by delayed 100 response.
POST's with Expect: 100-continue are slowed by delayed 100 response. Key: TS-1125 URL: https://issues.apache.org/jira/browse/TS-1125 Project: Traffic Server Issue Type: Bug Components: HTTP Affects Versions: 3.0.2 Environment: TS 3.0.2 going to Apache 2.2 web server Reporter: William Bardwell Priority: Minor Sending a post like: POST / HTTP/1.1 Host: www.example.com Content-Length: 10 Expect: 100-continue directly to the web server immediately sends back: HTTP/1.1 100 Continue And then when the post data is sent, a status 200 response comes back. But when going through ATS the "HTTP/1.1 100 Continue" is not sent immediately, and instead is sent after the POST data has been received. This is legal, but it makes clients that are hoping for a 100 continue to wait a little while hoping to get that, ATS should forward that response through immediately. Note: I see curl using "Expect: 100-continue" with > 1024 bytes of post data, but web searching indicates that some Microsoft products also use it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1124) Move a few plugins into main repo.
Move a few plugins into main repo. -- Key: TS-1124 URL: https://issues.apache.org/jira/browse/TS-1124 Project: Traffic Server Issue Type: New Feature Components: Plugins Reporter: Leif Hedstrom Assignee: Leif Hedstrom Fix For: 3.1.3 Moving regex_remap, header_filter and stats_over_http into main git repo (in plugins). I've tried to preserve history, but it gets a little wonky due to the change in directory structure. But the history is there :). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1123) Problems building with editline/readline on OSX
Problems building with editline/readline on OSX --- Key: TS-1123 URL: https://issues.apache.org/jira/browse/TS-1123 Project: Traffic Server Issue Type: Bug Components: Build Reporter: Leif Hedstrom Assignee: Leif Hedstrom Fix For: 3.1.3 There seems to be a conflict between editline and readline/history.h. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1122) Make regex_remap plugin understand redirect directives
Make regex_remap plugin understand redirect directives -- Key: TS-1122 URL: https://issues.apache.org/jira/browse/TS-1122 Project: Traffic Server Issue Type: Improvement Components: Plugins Reporter: Leif Hedstrom Assignee: Leif Hedstrom Fix For: 3.1.3 Fix the code to support the new APIs, for dealing with redirects. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1121) --disable-diags configuration option does not do anything
--disable-diags configuration option does not do anything - Key: TS-1121 URL: https://issues.apache.org/jira/browse/TS-1121 Project: Traffic Server Issue Type: Bug Components: Build, Core Affects Versions: 3.0.3 Environment: any Reporter: Uri Shachar Priority: Minor The --disable-diags flag sets TS_USE_DIAGS to 0 but Diags.h tests if it is defined or not -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1120) Use ink_zero / ats_zero instead of calling memset when zeroing a variable or member.
Use ink_zero / ats_zero instead of calling memset when zeroing a variable or member. Key: TS-1120 URL: https://issues.apache.org/jira/browse/TS-1120 Project: Traffic Server Issue Type: Improvement Components: Cleanup Affects Versions: 3.1.2 Reporter: Alan M. Carroll Priority: Minor Fix For: sometime We have an inline template, ink_zero(foo) which does "memset(&foo, 0, sizeof(foo))". Because this is easy to mess up with a typo, the inline template should be used for safety and clarity. Also, the template should be renamed "ats_zero" to be consistent. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1119) fatal error when uploading gzip-transform plugin
fatal error when uploading gzip-transform plugin
Key: TS-1119
URL: https://issues.apache.org/jira/browse/TS-1119
Project: Traffic Server
Issue Type: Bug
Components: Plugins
Affects Versions: 3.0.2
Reporter: angela asher
getting the following error on traffic.out when running the traffic server with
gzip-transform plugin:
[Feb 23 16:28:15.509] Server {47392853811680} DEBUG: (http) [13] calling plugin
on hook TS_HTTP_READ_RESPONSE_HDR_HOOK at hook 0x35BBEE0
FATAL: InkAPI.cc:3036: failed assert `sdk_sanity_check_null_ptr((void*)
value_len_ptr) == TS_SUCCESS`
/usr/local/bin/traffic_server - STACK TRACE:
/usr/local/lib/libtsutil.so.3(ink_fatal_va+0x9d)[0x2b1a7ecca37d]
/usr/local/lib/libtsutil.so.3(ink_fatal+0x88)[0x2b1a7ecca4d8]
/usr/local/lib/libtsutil.so.3(_ink_assert+0x85)[0x2b1a7ecc8af5]
/usr/local/bin/traffic_server(TSMimeHdrFieldValueStringGet+0x124)[0x4a9144]
/usr/local/libexec/trafficserver/gzip-transform.so(+0x1bde)[0x2b1a8b3c7bde]
/usr/local/libexec/trafficserver/gzip-transform.so(+0x27c4)[0x2b1a8b3c87c4]
/usr/local/bin/traffic_server(_ZN6HttpSM17state_api_calloutEiPv+0x525)[0x52cfa5]
/usr/local/bin/traffic_server(_ZN6HttpSM33state_read_server_response_headerEiPv+0x420)[0x52f1c0]
/usr/local/bin/traffic_server(_ZN6HttpSM12main_handlerEiPv+0xe8)[0x530568]
/usr/local/bin/traffic_server[0x681dcb]
/usr/local/bin/traffic_server[0x6848f1]
/usr/local/bin/traffic_server(_ZN10NetHandler12mainNetEventEiP5Event+0x2e2)[0x67d402]
/usr/local/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0xb4)[0x6a9ce4]
/usr/local/bin/traffic_server(_ZN7EThread7executeEv+0x4c3)[0x6aa673]
/usr/local/bin/traffic_server(main+0x1128)[0x4c07e8]
/lib64/libc.so.6(__libc_start_main+0xfd)[0x2b1a81092c5d]
/usr/local/bin/traffic_server[0x47e0e9]
[Feb 23 16:28:15.512] Manager {140400187066336} ERROR:
[LocalManager::pollMgmtProcessServer] Server Process terminated due to Sig 6:
Aborted
[Feb 23 16:28:15.512] Manager {140400187066336} ERROR: (last system error 2:
No such file or directory)
[Feb 23 16:28:15.512] Manager {140400187066336} ERROR: [Alarms::signalAlarm]
Server Process was reset
[Feb 23 16:28:15.512] Manager {140400187066336} ERROR: (last system error 2:
No such file or directory)
[Feb 23 16:28:16.522] Manager {140400187066336} NOTE:
[LocalManager::startProxy] Launching ts process
[TrafficServer] using root directory '/usr/local'
[Feb 23 16:28:16.527] Manager {140400187066336} NOTE:
[LocalManager::pollMgmtProcessServer] New process connecting fd '11'
[Feb 23 16:28:16.527] Manager {140400187066336} NOTE: [Alarms::signalAlarm]
Server Process born
[Feb 23 16:28:17.539] {47668265021920} STATUS: opened
/usr/local/var/log/trafficserver/diags.log
[Feb 23 16:28:17.539] {47668265021920} NOTE: updated diags config
[Feb 23 16:28:17.541] Server {47668265021920} DEBUG: (http_aeua)
[HttpConfig::init_aeua_filter] - Config:
"/usr/local/etc/trafficserver/ae_ua.config"
[Feb 23 16:28:17.541] Server {47668265021920} DEBUG: (http_aeua)
[HttpConfig::init_aeua_filter] - Opening config
"/usr/local/etc/trafficserver/ae_ua.config"
[Feb 23 16:28:17.541] Server {47668265021920} DEBUG: (http_aeua)
[HttpConfig::init_aeua_filter] - Added 0 REGEXP filters
[Feb 23 16:28:17.541] Server {47668265021920} DEBUG: (http_aeua)
[init_http_aeua_filter] - Total loaded 0 REGEXP for Accept-Enconding/User-Agent
filtering
[Feb 23 16:28:17.542] Server {47668265021920} NOTE: cache clustering disabled
[Feb 23 16:28:17.543] Server {47668265021920} DEBUG: (dns) ink_dns_init: called
with init_called = 0
[Feb 23 16:28:17.546] Server {47668265021920} DEBUG: (dns) localhost=isk-vsrv227
[Feb 23 16:28:17.546] Server {47668265021920} DEBUG: (dns) Round-robin
nameservers = 0
[Feb 23 16:28:17.547] Server {47668265021920} NOTE: cache clustering disabled
[Feb 23 16:28:17.568] Server {47668265021920} NOTE: logging initialized[7],
logging_mode = 3
[Feb 23 16:28:17.569] Server {47668265021920} NOTE: loading plugin
'/usr/local/libexec/trafficserver/gzip-transform.so'
[Feb 23 16:28:17.570] Server {47668265021920} DEBUG: (http_init)
proxy.config.http.redirection_enabled = 0
[Feb 23 16:28:17.570] Server {47668265021920} DEBUG: (http_init)
proxy.config.http.number_of_redirections = 1
[Feb 23 16:28:17.570] Server {47668265021920} DEBUG: (http_init)
proxy.config.http.post_copy_size = 2048
[Feb 23 16:28:17.570] Server {47668265021920} DEBUG: (http_tproxy) Primary
listen socket transparency is off
[Feb 23 16:28:17.573] Server {47668424926976} DEBUG: (http_tproxy) Marking
accepted connect on 39e0f80 as not outbound transparent.
[Feb 23 16:28:17.573] Server {47668265021920} NOTE: traffic server running
[Feb 23 16:28:17.573] Server {47668265021920} DEBUG: (dns)
DNSHandler::startEvent: on thread 0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://iss
[jira] [Created] (TS-1118) Modify how we manage the cache key / MD5 / lookup_url in the CacheSM / HttpSM.
Modify how we manage the cache key / MD5 / lookup_url in the CacheSM / HttpSM. -- Key: TS-1118 URL: https://issues.apache.org/jira/browse/TS-1118 Project: Traffic Server Issue Type: New Feature Components: Core Reporter: Leif Hedstrom Assignee: Leif Hedstrom Fix For: 3.1.3 I'd like to make the core simpler, and more efficient, dealing with the cache keys. We have APIs today to modify the cache URL (lookup_url), but it's incredibly inefficient. I'll post more details on my ideas here when I have it all written down. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1117) Remove TS_HAS_PURIFY macro
Remove TS_HAS_PURIFY macro -- Key: TS-1117 URL: https://issues.apache.org/jira/browse/TS-1117 Project: Traffic Server Issue Type: Bug Affects Versions: 3.0.3, 3.1.2 Reporter: Brian Geffon Assignee: Brian Geffon Fix For: 3.1.3 The TS_HAS_PURIFY stuff is confusing and should be removed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1116) Fix build issues with clang (particularly on OSX)
Fix build issues with clang (particularly on OSX) - Key: TS-1116 URL: https://issues.apache.org/jira/browse/TS-1116 Project: Traffic Server Issue Type: Improvement Reporter: Leif Hedstrom Assignee: Leif Hedstrom Fix For: 3.1.3 We should get it to compile with clang again, specially since on OSX, clang is the 'future'. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1115) Fix build issues with Intel ICC
Fix build issues with Intel ICC --- Key: TS-1115 URL: https://issues.apache.org/jira/browse/TS-1115 Project: Traffic Server Issue Type: Bug Reporter: Leif Hedstrom Assignee: Leif Hedstrom Fix For: 3.1.3 Get it to compile cleanly, and run, with Intel ICC again. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1114) Crash report: HttpTransactCache::SelectFromAlternates
Crash report: HttpTransactCache::SelectFromAlternates
-
Key: TS-1114
URL: https://issues.apache.org/jira/browse/TS-1114
Project: Traffic Server
Issue Type: Bug
Reporter: Zhao Yongming
it may or may not be the upstream issue, let us open it for tracking.
{code}
#0 0x0053075e in HttpTransactCache::SelectFromAlternates
(cache_vector=0x2aaab80ff500, client_request=0x2aaab80ff4c0,
http_config_params=0x2aaab547b800) at ../../proxy/hdrs/HTTP.h:1375
1375 ((int32_t *) & val)[0] = m_alt->m_object_key[0];
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
