[jira] [Created] (TS-2190) need a way to turn off cacheurl.log for cacheurl plugin
esmq2092 created TS-2190: Summary: need a way to turn off cacheurl.log for cacheurl plugin Key: TS-2190 URL: https://issues.apache.org/jira/browse/TS-2190 Project: Traffic Server Issue Type: Improvement Components: Plugins Reporter: esmq2092 the cacheurl.log may useful for debug only, need a way to turn it off -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-2190) need a way to turn off cacheurl.log for cacheurl plugin
[ https://issues.apache.org/jira/browse/TS-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] esmq2092 updated TS-2190: - Affects Version/s: 4.0.1 need a way to turn off cacheurl.log for cacheurl plugin Key: TS-2190 URL: https://issues.apache.org/jira/browse/TS-2190 Project: Traffic Server Issue Type: Improvement Components: Plugins Affects Versions: 4.0.1 Reporter: esmq2092 Priority: Minor the cacheurl.log may useful for debug only, need a way to turn it off -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-2190) need a way to turn off cacheurl.log for cacheurl plugin
[ https://issues.apache.org/jira/browse/TS-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] esmq2092 updated TS-2190: - Priority: Minor (was: Major) need a way to turn off cacheurl.log for cacheurl plugin Key: TS-2190 URL: https://issues.apache.org/jira/browse/TS-2190 Project: Traffic Server Issue Type: Improvement Components: Plugins Reporter: esmq2092 Priority: Minor the cacheurl.log may useful for debug only, need a way to turn it off -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-2191) when http_info enabled, the http_sm may be deleted but a event associated it not cancelled.
weijin created TS-2191: -- Summary: when http_info enabled, the http_sm may be deleted but a event associated it not cancelled. Key: TS-2191 URL: https://issues.apache.org/jira/browse/TS-2191 Project: Traffic Server Issue Type: Bug Components: HTTP Reporter: weijin if the http_info enabled, when the sm_list`s lock not acquired but the client_vc`s timeout event triggered, the race may lead ts crash. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-2191) when http_info enabled, the http_sm may be deleted but a event associated it not cancelled.
[ https://issues.apache.org/jira/browse/TS-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] weijin updated TS-2191: --- Attachment: TS-2191.wj.diff when http_info enabled, the http_sm may be deleted but a event associated it not cancelled. Key: TS-2191 URL: https://issues.apache.org/jira/browse/TS-2191 Project: Traffic Server Issue Type: Bug Components: HTTP Reporter: weijin Attachments: TS-2191.wj.diff if the http_info enabled, when the sm_list`s lock not acquired but the client_vc`s timeout event triggered, the race may lead ts crash. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1086) Returning 304 response to unconditional request
[ https://issues.apache.org/jira/browse/TS-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohamad Khateeb updated TS-1086: Attachment: TS-1086.diff Returning 304 response to unconditional request --- Key: TS-1086 URL: https://issues.apache.org/jira/browse/TS-1086 Project: Traffic Server Issue Type: Bug Components: HTTP Affects Versions: 3.0.1 Environment: Observed on Amazon/ec2 build, which is 3.0.1 on redhat-like linux. Reporter: Nick Kew Fix For: 4.2.0 Attachments: TS-1086.diff ab is reporting HTTP 304 responses to a small number of unconditional requests in a test run: GET /testfile.html HTTP/1.0^M Host: localhost^M User-Agent: ApacheBench/2.3^M Accept: */*^M ^M HTTP/1.0 304 Not Modified^M Date: Mon, 21 Nov 2011 14:23:48 GMT^M Server: ATS/3.0.1^M ETag: 5e24-24cd-4b23b69f6e89c^M Cache-Control: max-age=60^M Age: 2^M ^M I presume what's happening is that trafficserver is sending a conditional request with If-Modified-Since to the origin server, and then returning the origin's 304 response to the client's unconditional request. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1086) Returning 304 response to unconditional request
[ https://issues.apache.org/jira/browse/TS-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13761893#comment-13761893 ] Mohamad Khateeb commented on TS-1086: - I have attached a patch for this issue . the problem was , when ATS fails to get the cache write lock it changes to proxy mode , so when the object is stale and ATS has already made a conditional get to the server , ATS now must remove the conditional request headers that have been added by it . the ATS just removes If-Modified-Since header from the request , but a conditional get made by ATS can also have If-None-Match header , if etag header is found in the cached response. The patch that I have attached is just checking if the If-None-Match header is added by ATS . If so remove it , if it's not in the original client request. Returning 304 response to unconditional request --- Key: TS-1086 URL: https://issues.apache.org/jira/browse/TS-1086 Project: Traffic Server Issue Type: Bug Components: HTTP Affects Versions: 3.0.1 Environment: Observed on Amazon/ec2 build, which is 3.0.1 on redhat-like linux. Reporter: Nick Kew Fix For: 4.2.0 Attachments: TS-1086.diff ab is reporting HTTP 304 responses to a small number of unconditional requests in a test run: GET /testfile.html HTTP/1.0^M Host: localhost^M User-Agent: ApacheBench/2.3^M Accept: */*^M ^M HTTP/1.0 304 Not Modified^M Date: Mon, 21 Nov 2011 14:23:48 GMT^M Server: ATS/3.0.1^M ETag: 5e24-24cd-4b23b69f6e89c^M Cache-Control: max-age=60^M Age: 2^M ^M I presume what's happening is that trafficserver is sending a conditional request with If-Modified-Since to the origin server, and then returning the origin's 304 response to the client's unconditional request. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-2192) sm_list may miss some http_sms if it is lock contention
weijin created TS-2192: -- Summary: sm_list may miss some http_sms if it is lock contention Key: TS-2192 URL: https://issues.apache.org/jira/browse/TS-2192 Project: Traffic Server Issue Type: Improvement Components: HTTP Reporter: weijin it is a sub task of TS-2191. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1086) Returning 304 response to unconditional request
[ https://issues.apache.org/jira/browse/TS-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13761928#comment-13761928 ] Nick Kew commented on TS-1086: -- Mohamad, I'm not sure if it's the same as my original issue, but your diagnosis and patch make sense to me, and pass make test. Committing to trunk - thanks! Returning 304 response to unconditional request --- Key: TS-1086 URL: https://issues.apache.org/jira/browse/TS-1086 Project: Traffic Server Issue Type: Bug Components: HTTP Affects Versions: 3.0.1 Environment: Observed on Amazon/ec2 build, which is 3.0.1 on redhat-like linux. Reporter: Nick Kew Fix For: 4.2.0 Attachments: TS-1086.diff ab is reporting HTTP 304 responses to a small number of unconditional requests in a test run: GET /testfile.html HTTP/1.0^M Host: localhost^M User-Agent: ApacheBench/2.3^M Accept: */*^M ^M HTTP/1.0 304 Not Modified^M Date: Mon, 21 Nov 2011 14:23:48 GMT^M Server: ATS/3.0.1^M ETag: 5e24-24cd-4b23b69f6e89c^M Cache-Control: max-age=60^M Age: 2^M ^M I presume what's happening is that trafficserver is sending a conditional request with If-Modified-Since to the origin server, and then returning the origin's 304 response to the client's unconditional request. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1086) Returning 304 response to unconditional request
[ https://issues.apache.org/jira/browse/TS-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-1086: -- Fix Version/s: (was: 4.2.0) 4.1.0 Assignee: Nick Kew Nick: We've started following best practices of committing other people's patches with the --author option to git. I know you haven't committed this yet, it's just a friendly reminder :-). Returning 304 response to unconditional request --- Key: TS-1086 URL: https://issues.apache.org/jira/browse/TS-1086 Project: Traffic Server Issue Type: Bug Components: HTTP Affects Versions: 3.0.1 Environment: Observed on Amazon/ec2 build, which is 3.0.1 on redhat-like linux. Reporter: Nick Kew Assignee: Nick Kew Fix For: 4.1.0 Attachments: TS-1086.diff ab is reporting HTTP 304 responses to a small number of unconditional requests in a test run: GET /testfile.html HTTP/1.0^M Host: localhost^M User-Agent: ApacheBench/2.3^M Accept: */*^M ^M HTTP/1.0 304 Not Modified^M Date: Mon, 21 Nov 2011 14:23:48 GMT^M Server: ATS/3.0.1^M ETag: 5e24-24cd-4b23b69f6e89c^M Cache-Control: max-age=60^M Age: 2^M ^M I presume what's happening is that trafficserver is sending a conditional request with If-Modified-Since to the origin server, and then returning the origin's 304 response to the client's unconditional request. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1086) Returning 304 response to unconditional request
[ https://issues.apache.org/jira/browse/TS-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13761939#comment-13761939 ] ASF subversion and git services commented on TS-1086: - Commit e8672a8934f468a4bf3fd34b3d573c783a5398cf in branch refs/heads/master from [~n...@webthing.com] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=e8672a8 ] TS-1086: Avoid returning 304 to an unconditional request. Diagnosis and patch by Mohamad Khateeb. Returning 304 response to unconditional request --- Key: TS-1086 URL: https://issues.apache.org/jira/browse/TS-1086 Project: Traffic Server Issue Type: Bug Components: HTTP Affects Versions: 3.0.1 Environment: Observed on Amazon/ec2 build, which is 3.0.1 on redhat-like linux. Reporter: Nick Kew Assignee: Nick Kew Fix For: 4.1.0 Attachments: TS-1086.diff ab is reporting HTTP 304 responses to a small number of unconditional requests in a test run: GET /testfile.html HTTP/1.0^M Host: localhost^M User-Agent: ApacheBench/2.3^M Accept: */*^M ^M HTTP/1.0 304 Not Modified^M Date: Mon, 21 Nov 2011 14:23:48 GMT^M Server: ATS/3.0.1^M ETag: 5e24-24cd-4b23b69f6e89c^M Cache-Control: max-age=60^M Age: 2^M ^M I presume what's happening is that trafficserver is sending a conditional request with If-Modified-Since to the origin server, and then returning the origin's 304 response to the client's unconditional request. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-2192) sm_list may miss some http_sms if it is lock contention
[ https://issues.apache.org/jira/browse/TS-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13761951#comment-13761951 ] ASF subversion and git services commented on TS-2192: - Commit a27b9e73a5e113a0231d56817e86fbad27583180 in branch refs/heads/master from [~taorui] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=a27b9e7 ] TS-2191 we should not simply reschdule the http_sm if the sm_list`s mutex is not acquired, because the client_vc`s timeout events maybe triggered. The race may lead http_sm received a event after it is deleted. Sub task (TS-2192) sm_list may miss some http_sms if it is lock contention --- Key: TS-2192 URL: https://issues.apache.org/jira/browse/TS-2192 Project: Traffic Server Issue Type: Improvement Components: HTTP Reporter: weijin it is a sub task of TS-2191. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-2191) when http_info enabled, the http_sm may be deleted but a event associated it not cancelled.
[ https://issues.apache.org/jira/browse/TS-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13761950#comment-13761950 ] ASF subversion and git services commented on TS-2191: - Commit a27b9e73a5e113a0231d56817e86fbad27583180 in branch refs/heads/master from [~taorui] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=a27b9e7 ] TS-2191 we should not simply reschdule the http_sm if the sm_list`s mutex is not acquired, because the client_vc`s timeout events maybe triggered. The race may lead http_sm received a event after it is deleted. Sub task (TS-2192) when http_info enabled, the http_sm may be deleted but a event associated it not cancelled. Key: TS-2191 URL: https://issues.apache.org/jira/browse/TS-2191 Project: Traffic Server Issue Type: Bug Components: HTTP Reporter: weijin Attachments: TS-2191.wj.diff if the http_info enabled, when the sm_list`s lock not acquired but the client_vc`s timeout event triggered, the race may lead ts crash. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-2188) healthcheck plugin seg faulting
[ https://issues.apache.org/jira/browse/TS-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762100#comment-13762100 ] Leif Hedstrom commented on TS-2188: --- This is actually a bug in the config parser. The patch you proposed is a nice optimization too, but I'll fix the real problem as well. Thanks! healthcheck plugin seg faulting --- Key: TS-2188 URL: https://issues.apache.org/jira/browse/TS-2188 Project: Traffic Server Issue Type: Bug Components: Plugins Reporter: Scott Harris Assignee: Leif Hedstrom Fix For: 4.1.0 When using the experimental healthcheck plugin any request received with a uri of / or null results in a seg fault. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-2193) Trafficserver 4.1 Crash with proxy.config.dns.dedicated_thread = 1
Tommy Lee created TS-2193: - Summary: Trafficserver 4.1 Crash with proxy.config.dns.dedicated_thread = 1 Key: TS-2193 URL: https://issues.apache.org/jira/browse/TS-2193 Project: Traffic Server Issue Type: Bug Components: DNS Reporter: Tommy Lee Hi all, I've tried to enable DNS Thread without luck. When i set proxy.config.dns.dedicated_thread to 1, it crashes with the information below. The ATS is working in Forward Proxy mode. Thanks in advance. -- traffic.out NOTE: Traffic Server received Sig 11: Segmentation fault /usr/local/cache-4.1/bin/traffic_server - STACK TRACE: /lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x2af714875cb0] /usr/local/cache-4.1/bin/traffic_server(_Z16_acquire_sessionP13SessionBucketPK8sockaddrR7INK_MD5P6HttpSM+0x52)[0x51dac2] /usr/local/cache-4.1/bin/traffic_server(_ZN18HttpSessionManager15acquire_sessionEP12ContinuationPK8sockaddrPKcP17HttpClientSessionP6HttpSM+0x3d1)[0x51e0f1] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM19do_http_server_openEb+0x30c)[0x53644c] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x6a0)[0x537560] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x57e)[0x53743e] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x57e)[0x53743e] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM27state_hostdb_reverse_lookupEiPv+0xb9)[0x526b99] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM12main_handlerEiPv+0xd8)[0x531be8] /usr/local/cache-4.1/bin/traffic_server[0x5d7c8a] /usr/local/cache-4.1/bin/traffic_server(_ZN18HostDBContinuation8dnsEventEiP7HostEnt+0x821)[0x5decd1] /usr/local/cache-4.1/bin/traffic_server(_ZN8DNSEntry9postEventEiP5Event+0x44)[0x5f7a94] /usr/local/cache-4.1/bin/traffic_server[0x5fd382] /usr/local/cache-4.1/bin/traffic_server(_ZN10DNSHandler8recv_dnsEiP5Event+0x852)[0x5fee72] /usr/local/cache-4.1/bin/traffic_server(_ZN10DNSHandler9mainEventEiP5Event+0x14)[0x5ffd94] /usr/local/cache-4.1/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x91)[0x6b2a41] /usr/local/cache-4.1/bin/traffic_server(_ZN7EThread7executeEv+0x514)[0x6b3534] /usr/local/cache-4.1/bin/traffic_server[0x6b17ea] /lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x2af71486de9a] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x2af71558dccd] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-2193) Trafficserver 4.1 Crash with proxy.config.dns.dedicated_thread = 1
[ https://issues.apache.org/jira/browse/TS-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommy Lee updated TS-2193: -- Affects Version/s: 4.1.0 More infos: This Crash only occurs if i have cache.config options enabled. No matter what kind of rules i have. This simple rule in cache.config, makes things happen. dest_host=200.143.26.216 action=never-cache Trafficserver 4.1 Crash with proxy.config.dns.dedicated_thread = 1 -- Key: TS-2193 URL: https://issues.apache.org/jira/browse/TS-2193 Project: Traffic Server Issue Type: Bug Components: DNS Affects Versions: 4.1.0 Reporter: Tommy Lee Hi all, I've tried to enable DNS Thread without luck. When i set proxy.config.dns.dedicated_thread to 1, it crashes with the information below. The ATS is working in Forward Proxy mode. Thanks in advance. -- traffic.out NOTE: Traffic Server received Sig 11: Segmentation fault /usr/local/cache-4.1/bin/traffic_server - STACK TRACE: /lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x2af714875cb0] /usr/local/cache-4.1/bin/traffic_server(_Z16_acquire_sessionP13SessionBucketPK8sockaddrR7INK_MD5P6HttpSM+0x52)[0x51dac2] /usr/local/cache-4.1/bin/traffic_server(_ZN18HttpSessionManager15acquire_sessionEP12ContinuationPK8sockaddrPKcP17HttpClientSessionP6HttpSM+0x3d1)[0x51e0f1] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM19do_http_server_openEb+0x30c)[0x53644c] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x6a0)[0x537560] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x57e)[0x53743e] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x57e)[0x53743e] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM27state_hostdb_reverse_lookupEiPv+0xb9)[0x526b99] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM12main_handlerEiPv+0xd8)[0x531be8] /usr/local/cache-4.1/bin/traffic_server[0x5d7c8a] /usr/local/cache-4.1/bin/traffic_server(_ZN18HostDBContinuation8dnsEventEiP7HostEnt+0x821)[0x5decd1] /usr/local/cache-4.1/bin/traffic_server(_ZN8DNSEntry9postEventEiP5Event+0x44)[0x5f7a94] /usr/local/cache-4.1/bin/traffic_server[0x5fd382] /usr/local/cache-4.1/bin/traffic_server(_ZN10DNSHandler8recv_dnsEiP5Event+0x852)[0x5fee72] /usr/local/cache-4.1/bin/traffic_server(_ZN10DNSHandler9mainEventEiP5Event+0x14)[0x5ffd94] /usr/local/cache-4.1/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x91)[0x6b2a41] /usr/local/cache-4.1/bin/traffic_server(_ZN7EThread7executeEv+0x514)[0x6b3534] /usr/local/cache-4.1/bin/traffic_server[0x6b17ea] /lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x2af71486de9a] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x2af71558dccd] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-2188) healthcheck plugin seg faulting
[ https://issues.apache.org/jira/browse/TS-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762196#comment-13762196 ] ASF subversion and git services commented on TS-2188: - Commit 9e82415fc2c40a628589f4053ad1103c5730bdb8 in branch refs/heads/master from [~scottharrisnet] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=9e82415 ] TS-2188 Never consider a simple / path as a healthcheck This is an optimization, and a safety net, such that a simple / path can never be considered for a healthcheck. healthcheck plugin seg faulting --- Key: TS-2188 URL: https://issues.apache.org/jira/browse/TS-2188 Project: Traffic Server Issue Type: Bug Components: Plugins Reporter: Scott Harris Assignee: Leif Hedstrom Fix For: 4.1.0 When using the experimental healthcheck plugin any request received with a uri of / or null results in a seg fault. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-2188) healthcheck plugin seg faulting
[ https://issues.apache.org/jira/browse/TS-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762197#comment-13762197 ] ASF subversion and git services commented on TS-2188: - Commit 49d00ff1fe2d8097952aa857d1b4d79103825043 in branch refs/heads/master from [~zwoop] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=49d00ff ] TS-2188 healthcheck plugin doesn't parse config files properly This is part of the fixes to the healthcheck plugins, such that we don't segfault. This part of the fix actually makes sure we properly parse the configuration file as was expected. healthcheck plugin seg faulting --- Key: TS-2188 URL: https://issues.apache.org/jira/browse/TS-2188 Project: Traffic Server Issue Type: Bug Components: Plugins Reporter: Scott Harris Assignee: Leif Hedstrom Fix For: 4.1.0 When using the experimental healthcheck plugin any request received with a uri of / or null results in a seg fault. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-2193) Trafficserver 4.1 Crash with proxy.config.dns.dedicated_thread = 1
[ https://issues.apache.org/jira/browse/TS-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2193: -- Fix Version/s: 4.1.0 Trafficserver 4.1 Crash with proxy.config.dns.dedicated_thread = 1 -- Key: TS-2193 URL: https://issues.apache.org/jira/browse/TS-2193 Project: Traffic Server Issue Type: Bug Components: DNS Affects Versions: 4.1.0 Reporter: Tommy Lee Fix For: 4.1.0 Hi all, I've tried to enable DNS Thread without luck. When i set proxy.config.dns.dedicated_thread to 1, it crashes with the information below. The ATS is working in Forward Proxy mode. Thanks in advance. -- traffic.out NOTE: Traffic Server received Sig 11: Segmentation fault /usr/local/cache-4.1/bin/traffic_server - STACK TRACE: /lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x2af714875cb0] /usr/local/cache-4.1/bin/traffic_server(_Z16_acquire_sessionP13SessionBucketPK8sockaddrR7INK_MD5P6HttpSM+0x52)[0x51dac2] /usr/local/cache-4.1/bin/traffic_server(_ZN18HttpSessionManager15acquire_sessionEP12ContinuationPK8sockaddrPKcP17HttpClientSessionP6HttpSM+0x3d1)[0x51e0f1] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM19do_http_server_openEb+0x30c)[0x53644c] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x6a0)[0x537560] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x57e)[0x53743e] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x57e)[0x53743e] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM27state_hostdb_reverse_lookupEiPv+0xb9)[0x526b99] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM12main_handlerEiPv+0xd8)[0x531be8] /usr/local/cache-4.1/bin/traffic_server[0x5d7c8a] /usr/local/cache-4.1/bin/traffic_server(_ZN18HostDBContinuation8dnsEventEiP7HostEnt+0x821)[0x5decd1] /usr/local/cache-4.1/bin/traffic_server(_ZN8DNSEntry9postEventEiP5Event+0x44)[0x5f7a94] /usr/local/cache-4.1/bin/traffic_server[0x5fd382] /usr/local/cache-4.1/bin/traffic_server(_ZN10DNSHandler8recv_dnsEiP5Event+0x852)[0x5fee72] /usr/local/cache-4.1/bin/traffic_server(_ZN10DNSHandler9mainEventEiP5Event+0x14)[0x5ffd94] /usr/local/cache-4.1/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x91)[0x6b2a41] /usr/local/cache-4.1/bin/traffic_server(_ZN7EThread7executeEv+0x514)[0x6b3534] /usr/local/cache-4.1/bin/traffic_server[0x6b17ea] /lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x2af71486de9a] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x2af71558dccd] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-2193) Trafficserver 4.1 Crash with proxy.config.dns.dedicated_thread = 1
[ https://issues.apache.org/jira/browse/TS-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762260#comment-13762260 ] Leif Hedstrom commented on TS-2193: --- The only thing I can think of is related to the share_server_sessions, curious at to how that is effected by the CDN thread. *Maybe* it ends up trying to allocate server sessions on the DNS thread, but that's a serious bug, it shouldn't do that (it's supposed to kick it back to an ET_NET t head). Trafficserver 4.1 Crash with proxy.config.dns.dedicated_thread = 1 -- Key: TS-2193 URL: https://issues.apache.org/jira/browse/TS-2193 Project: Traffic Server Issue Type: Bug Components: DNS Affects Versions: 4.1.0 Reporter: Tommy Lee Fix For: 4.1.0 Hi all, I've tried to enable DNS Thread without luck. When i set proxy.config.dns.dedicated_thread to 1, it crashes with the information below. The ATS is working in Forward Proxy mode. Thanks in advance. -- traffic.out NOTE: Traffic Server received Sig 11: Segmentation fault /usr/local/cache-4.1/bin/traffic_server - STACK TRACE: /lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x2af714875cb0] /usr/local/cache-4.1/bin/traffic_server(_Z16_acquire_sessionP13SessionBucketPK8sockaddrR7INK_MD5P6HttpSM+0x52)[0x51dac2] /usr/local/cache-4.1/bin/traffic_server(_ZN18HttpSessionManager15acquire_sessionEP12ContinuationPK8sockaddrPKcP17HttpClientSessionP6HttpSM+0x3d1)[0x51e0f1] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM19do_http_server_openEb+0x30c)[0x53644c] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x6a0)[0x537560] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x57e)[0x53743e] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x57e)[0x53743e] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM27state_hostdb_reverse_lookupEiPv+0xb9)[0x526b99] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM12main_handlerEiPv+0xd8)[0x531be8] /usr/local/cache-4.1/bin/traffic_server[0x5d7c8a] /usr/local/cache-4.1/bin/traffic_server(_ZN18HostDBContinuation8dnsEventEiP7HostEnt+0x821)[0x5decd1] /usr/local/cache-4.1/bin/traffic_server(_ZN8DNSEntry9postEventEiP5Event+0x44)[0x5f7a94] /usr/local/cache-4.1/bin/traffic_server[0x5fd382] /usr/local/cache-4.1/bin/traffic_server(_ZN10DNSHandler8recv_dnsEiP5Event+0x852)[0x5fee72] /usr/local/cache-4.1/bin/traffic_server(_ZN10DNSHandler9mainEventEiP5Event+0x14)[0x5ffd94] /usr/local/cache-4.1/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x91)[0x6b2a41] /usr/local/cache-4.1/bin/traffic_server(_ZN7EThread7executeEv+0x514)[0x6b3534] /usr/local/cache-4.1/bin/traffic_server[0x6b17ea] /lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x2af71486de9a] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x2af71558dccd] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1666) Plugins, clustering and core crashes when share_server_sessions=2
[
https://issues.apache.org/jira/browse/TS-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762262#comment-13762262
]
Leif Hedstrom commented on TS-1666:
---
Out of curiosity, I'm wondering if any of these use cases where running with
either remap threads, dedicated DNS thread or the generic thread pool ?
Plugins, clustering and core crashes when share_server_sessions=2
-
Key: TS-1666
URL: https://issues.apache.org/jira/browse/TS-1666
Project: Traffic Server
Issue Type: Bug
Components: MIME, Plugins
Reporter: Otto van der Schaaf
Priority: Critical
Labels: crash
Fix For: 4.1.0
ibrezac dumped this trace on irc:
{noformat}
[Jan 22 21:25:34.555] Server {0x2ac1f8a78300} NOTE: logging initialized[15],
logging_mode = 3
[Jan 22 21:25:34.610] Server {0x2ac1f8a78300} NOTE: loading plugin
'/usr/lib/trafficserver/modules/gzip.so'
[Jan 22 21:25:34.683] Server {0x2ac1f8a78300} NOTE: traffic server running
[Jan 22 21:25:34.705] Server {0x2ac1f8a78300} NOTE: cache enabled
NOTE: Traffic Server received Sig 11: Segmentation fault
/usr/bin/traffic_server - STACK TRACE:
/lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x2ac1f68bccb0]
/usr/bin/traffic_server(_Z19mime_hdr_field_findP11MIMEHdrImplPKci+0x152)[0x5c27f2]
/usr/bin/traffic_server(_ZN12HttpTransact27set_headers_for_cache_writeEPNS_5StateEP8HTTPInfoP7HTTPHdrS5_+0xe1)[0x545571]
/usr/bin/traffic_server(_ZN12HttpTransact22handle_transform_readyEPNS_5StateE+0x122)[0x553112]
/usr/bin/traffic_server(_ZN6HttpSM32call_transact_and_set_next_stateEPFvPN12HttpTransact5StateEE+0x28)[0x526df8]
/usr/bin/traffic_server(_ZN6HttpSM38state_response_wait_for_transform_readEiPv+0xed)[0x52ba2d]
/usr/bin/traffic_server(_ZN6HttpSM12main_handlerEiPv+0xe8)[0x533888]
/usr/bin/traffic_server(_ZN17TransformTerminus12handle_eventEiPv+0x272)[0x4e7402]
/usr/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x90)[0x6ab490]
/usr/bin/traffic_server(_ZN7EThread7executeEv+0x5fe)[0x6ac05e]
/usr/bin/traffic_server(main+0x160f)[0x48022f]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed)[0x2ac1f86da76d]
/usr/bin/traffic_server[0x4855fd]
[Jan 22 21:25:41.933] Manager {0x7fa2b126c740} ERROR:
[LocalManager::pollMgmtProcessServer] Server Process terminated due to Sig
11: Segmentation fault
[Jan 22 21:25:41.934] Manager {0x7fa2b126c740} ERROR: (last system error 2:
No such file or directory)
[Jan 22 21:25:41.934] Manager {0x7fa2b126c740} ERROR: [Alarms::signalAlarm]
Server Process was reset
[Jan 22 21:25:41.934] Manager {0x7fa2b126c740} ERROR: (last system error 2:
No such file or directory)
[Jan 22 21:25:42.946] Manager {0x7fa2b126c740} NOTE:
[LocalManager::startProxy] Launching ts process
[TrafficServer] using root directory '/usr'
{noformat}
configuration used:
{noformat}
cache true
enabled true
remove-accept-encoding false
compressible-content-type text/*
compressible-content-type *javascript*
{noformat}
=== misc info
TS Version 3.2.4
Running at around 50 qps
crashes every 10 seconds
== c++filt stack trace
{noformat}
/usr/bin/traffic_server - STACK TRACE:
/lib/x86_64-linux-gnu/libpthread.so.0( 0xfcb0)[0x2ac1f68bccb0]
/usr/bin/traffic_server(mime_hdr_field_find(MIMEHdrImpl*, char const*, int)
0x152)[0x5c27f2]
/usr/bin/traffic_server(ZN12HttpTransact27set_headers_for_cache_writeEPNS_5StateEP8HTTPInfoP7HTTPHdrS5
0xe1)[0x545571]
/usr/bin/traffic_server(HttpTransact::handle_transform_ready(HttpTransact::State*)
0x122)[0x553112]
/usr/bin/traffic_server(HttpSM::call_transact_and_set_next_state(void
(*)(HttpTransact::State*)) 0x28)[0x526df8]
/usr/bin/traffic_server(HttpSM::state_response_wait_for_transform_read(int,
void*) 0xed)[0x52ba2d]
/usr/bin/traffic_server(HttpSM::main_handler(int, void*) 0xe8)[0x533888]
/usr/bin/traffic_server(TransformTerminus::handle_event(int, void*)
0x272)[0x4e7402]
/usr/bin/traffic_server(EThread::process_event(Event*, int) 0x90)[0x6ab490]
/usr/bin/traffic_server(EThread::execute() 0x5fe)[0x6ac05e]
/usr/bin/traffic_server(main 0x160f)[0x48022f]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main 0xed)[0x2ac1f86da76d]
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-2193) Trafficserver 4.1 Crash with proxy.config.dns.dedicated_thread = 1
[ https://issues.apache.org/jira/browse/TS-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762261#comment-13762261 ] Tommy Lee commented on TS-2193: --- Leif, Yes. Current GIT Master. And you're right. With share_server_sessions=1, it doesn't occurs. Do you think that on a busy forward proxy, it's safe to go with share_server_sessions=1 ? Do you need a bt with share_server_sessions=2 ? Thanks in advance. Trafficserver 4.1 Crash with proxy.config.dns.dedicated_thread = 1 -- Key: TS-2193 URL: https://issues.apache.org/jira/browse/TS-2193 Project: Traffic Server Issue Type: Bug Components: DNS Affects Versions: 4.1.0 Reporter: Tommy Lee Fix For: 4.1.0 Hi all, I've tried to enable DNS Thread without luck. When i set proxy.config.dns.dedicated_thread to 1, it crashes with the information below. The ATS is working in Forward Proxy mode. Thanks in advance. -- traffic.out NOTE: Traffic Server received Sig 11: Segmentation fault /usr/local/cache-4.1/bin/traffic_server - STACK TRACE: /lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x2af714875cb0] /usr/local/cache-4.1/bin/traffic_server(_Z16_acquire_sessionP13SessionBucketPK8sockaddrR7INK_MD5P6HttpSM+0x52)[0x51dac2] /usr/local/cache-4.1/bin/traffic_server(_ZN18HttpSessionManager15acquire_sessionEP12ContinuationPK8sockaddrPKcP17HttpClientSessionP6HttpSM+0x3d1)[0x51e0f1] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM19do_http_server_openEb+0x30c)[0x53644c] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x6a0)[0x537560] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x57e)[0x53743e] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x57e)[0x53743e] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM27state_hostdb_reverse_lookupEiPv+0xb9)[0x526b99] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM12main_handlerEiPv+0xd8)[0x531be8] /usr/local/cache-4.1/bin/traffic_server[0x5d7c8a] /usr/local/cache-4.1/bin/traffic_server(_ZN18HostDBContinuation8dnsEventEiP7HostEnt+0x821)[0x5decd1] /usr/local/cache-4.1/bin/traffic_server(_ZN8DNSEntry9postEventEiP5Event+0x44)[0x5f7a94] /usr/local/cache-4.1/bin/traffic_server[0x5fd382] /usr/local/cache-4.1/bin/traffic_server(_ZN10DNSHandler8recv_dnsEiP5Event+0x852)[0x5fee72] /usr/local/cache-4.1/bin/traffic_server(_ZN10DNSHandler9mainEventEiP5Event+0x14)[0x5ffd94] /usr/local/cache-4.1/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x91)[0x6b2a41] /usr/local/cache-4.1/bin/traffic_server(_ZN7EThread7executeEv+0x514)[0x6b3534] /usr/local/cache-4.1/bin/traffic_server[0x6b17ea] /lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x2af71486de9a] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x2af71558dccd] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-2193) Trafficserver 4.1 Crash with proxy.config.dns.dedicated_thread = 1
[ https://issues.apache.org/jira/browse/TS-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762274#comment-13762274 ] Leif Hedstrom commented on TS-2193: --- To Clarify: Without dedicated DNS thread, all DNS happens on ET_NET[0]. Trafficserver 4.1 Crash with proxy.config.dns.dedicated_thread = 1 -- Key: TS-2193 URL: https://issues.apache.org/jira/browse/TS-2193 Project: Traffic Server Issue Type: Bug Components: DNS Affects Versions: 4.1.0 Reporter: Tommy Lee Fix For: 4.1.0 Hi all, I've tried to enable DNS Thread without luck. When i set proxy.config.dns.dedicated_thread to 1, it crashes with the information below. The ATS is working in Forward Proxy mode. Thanks in advance. -- traffic.out NOTE: Traffic Server received Sig 11: Segmentation fault /usr/local/cache-4.1/bin/traffic_server - STACK TRACE: /lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x2af714875cb0] /usr/local/cache-4.1/bin/traffic_server(_Z16_acquire_sessionP13SessionBucketPK8sockaddrR7INK_MD5P6HttpSM+0x52)[0x51dac2] /usr/local/cache-4.1/bin/traffic_server(_ZN18HttpSessionManager15acquire_sessionEP12ContinuationPK8sockaddrPKcP17HttpClientSessionP6HttpSM+0x3d1)[0x51e0f1] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM19do_http_server_openEb+0x30c)[0x53644c] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x6a0)[0x537560] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x57e)[0x53743e] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x57e)[0x53743e] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM27state_hostdb_reverse_lookupEiPv+0xb9)[0x526b99] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM12main_handlerEiPv+0xd8)[0x531be8] /usr/local/cache-4.1/bin/traffic_server[0x5d7c8a] /usr/local/cache-4.1/bin/traffic_server(_ZN18HostDBContinuation8dnsEventEiP7HostEnt+0x821)[0x5decd1] /usr/local/cache-4.1/bin/traffic_server(_ZN8DNSEntry9postEventEiP5Event+0x44)[0x5f7a94] /usr/local/cache-4.1/bin/traffic_server[0x5fd382] /usr/local/cache-4.1/bin/traffic_server(_ZN10DNSHandler8recv_dnsEiP5Event+0x852)[0x5fee72] /usr/local/cache-4.1/bin/traffic_server(_ZN10DNSHandler9mainEventEiP5Event+0x14)[0x5ffd94] /usr/local/cache-4.1/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x91)[0x6b2a41] /usr/local/cache-4.1/bin/traffic_server(_ZN7EThread7executeEv+0x514)[0x6b3534] /usr/local/cache-4.1/bin/traffic_server[0x6b17ea] /lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x2af71486de9a] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x2af71558dccd] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-2193) Trafficserver 4.1 Crash with proxy.config.dns.dedicated_thread = 1
[ https://issues.apache.org/jira/browse/TS-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762278#comment-13762278 ] Tommy Lee commented on TS-2193: --- Leif, Thanks for the explanation. I'll keep share_server_sessions untouched (=2), and disable dns dedicated thread. If you need a bt with these settings, please let me know. Trafficserver 4.1 Crash with proxy.config.dns.dedicated_thread = 1 -- Key: TS-2193 URL: https://issues.apache.org/jira/browse/TS-2193 Project: Traffic Server Issue Type: Bug Components: DNS Affects Versions: 4.1.0 Reporter: Tommy Lee Fix For: 4.1.0 Hi all, I've tried to enable DNS Thread without luck. When i set proxy.config.dns.dedicated_thread to 1, it crashes with the information below. The ATS is working in Forward Proxy mode. Thanks in advance. -- traffic.out NOTE: Traffic Server received Sig 11: Segmentation fault /usr/local/cache-4.1/bin/traffic_server - STACK TRACE: /lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x2af714875cb0] /usr/local/cache-4.1/bin/traffic_server(_Z16_acquire_sessionP13SessionBucketPK8sockaddrR7INK_MD5P6HttpSM+0x52)[0x51dac2] /usr/local/cache-4.1/bin/traffic_server(_ZN18HttpSessionManager15acquire_sessionEP12ContinuationPK8sockaddrPKcP17HttpClientSessionP6HttpSM+0x3d1)[0x51e0f1] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM19do_http_server_openEb+0x30c)[0x53644c] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x6a0)[0x537560] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x57e)[0x53743e] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x57e)[0x53743e] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM27state_hostdb_reverse_lookupEiPv+0xb9)[0x526b99] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM12main_handlerEiPv+0xd8)[0x531be8] /usr/local/cache-4.1/bin/traffic_server[0x5d7c8a] /usr/local/cache-4.1/bin/traffic_server(_ZN18HostDBContinuation8dnsEventEiP7HostEnt+0x821)[0x5decd1] /usr/local/cache-4.1/bin/traffic_server(_ZN8DNSEntry9postEventEiP5Event+0x44)[0x5f7a94] /usr/local/cache-4.1/bin/traffic_server[0x5fd382] /usr/local/cache-4.1/bin/traffic_server(_ZN10DNSHandler8recv_dnsEiP5Event+0x852)[0x5fee72] /usr/local/cache-4.1/bin/traffic_server(_ZN10DNSHandler9mainEventEiP5Event+0x14)[0x5ffd94] /usr/local/cache-4.1/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x91)[0x6b2a41] /usr/local/cache-4.1/bin/traffic_server(_ZN7EThread7executeEv+0x514)[0x6b3534] /usr/local/cache-4.1/bin/traffic_server[0x6b17ea] /lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x2af71486de9a] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x2af71558dccd] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-2193) Trafficserver 4.1 Crash with proxy.config.dns.dedicated_thread = 1
[ https://issues.apache.org/jira/browse/TS-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762271#comment-13762271 ] Leif Hedstrom commented on TS-2193: --- share_server_sessions=2 is definitely advantageous to performance. That probably has a bigger performance boost than the dedicated DNS thread. But, you should watch the CPU on your CPU running the ET_NET[0] thread (use e.g. top and hit the H key to see individual threads). It's real bad though that the DNS thread would try to acquire server sessions, we should investigate that. Trafficserver 4.1 Crash with proxy.config.dns.dedicated_thread = 1 -- Key: TS-2193 URL: https://issues.apache.org/jira/browse/TS-2193 Project: Traffic Server Issue Type: Bug Components: DNS Affects Versions: 4.1.0 Reporter: Tommy Lee Fix For: 4.1.0 Hi all, I've tried to enable DNS Thread without luck. When i set proxy.config.dns.dedicated_thread to 1, it crashes with the information below. The ATS is working in Forward Proxy mode. Thanks in advance. -- traffic.out NOTE: Traffic Server received Sig 11: Segmentation fault /usr/local/cache-4.1/bin/traffic_server - STACK TRACE: /lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x2af714875cb0] /usr/local/cache-4.1/bin/traffic_server(_Z16_acquire_sessionP13SessionBucketPK8sockaddrR7INK_MD5P6HttpSM+0x52)[0x51dac2] /usr/local/cache-4.1/bin/traffic_server(_ZN18HttpSessionManager15acquire_sessionEP12ContinuationPK8sockaddrPKcP17HttpClientSessionP6HttpSM+0x3d1)[0x51e0f1] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM19do_http_server_openEb+0x30c)[0x53644c] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x6a0)[0x537560] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x57e)[0x53743e] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x57e)[0x53743e] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM27state_hostdb_reverse_lookupEiPv+0xb9)[0x526b99] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM12main_handlerEiPv+0xd8)[0x531be8] /usr/local/cache-4.1/bin/traffic_server[0x5d7c8a] /usr/local/cache-4.1/bin/traffic_server(_ZN18HostDBContinuation8dnsEventEiP7HostEnt+0x821)[0x5decd1] /usr/local/cache-4.1/bin/traffic_server(_ZN8DNSEntry9postEventEiP5Event+0x44)[0x5f7a94] /usr/local/cache-4.1/bin/traffic_server[0x5fd382] /usr/local/cache-4.1/bin/traffic_server(_ZN10DNSHandler8recv_dnsEiP5Event+0x852)[0x5fee72] /usr/local/cache-4.1/bin/traffic_server(_ZN10DNSHandler9mainEventEiP5Event+0x14)[0x5ffd94] /usr/local/cache-4.1/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x91)[0x6b2a41] /usr/local/cache-4.1/bin/traffic_server(_ZN7EThread7executeEv+0x514)[0x6b3534] /usr/local/cache-4.1/bin/traffic_server[0x6b17ea] /lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x2af71486de9a] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x2af71558dccd] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-2193) Trafficserver 4.1 Crash with proxy.config.dns.dedicated_thread = 1
[
https://issues.apache.org/jira/browse/TS-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762366#comment-13762366
]
John Plevyak commented on TS-2193:
--
the code in dns_result will check to see that we only call back on the same
thread that initiated the DNS lookup:
if (h-mutex-thread_holding == e-submit_thread) {
MUTEX_TRY_LOCK(lock, e-action.mutex, h-mutex-thread_holding);
if (!lock) {
Debug(dns, failed lock for result %s, e-qname);
goto Lretry;
}
for (int i = 0; i MAX_DNS_RETRIES; i++) {
if (e-id[i] 0)
break;
h-release_query_id(e-id[i]);
}
e-postEvent(0, 0);
} else {
for (int i = 0; i MAX_DNS_RETRIES; i++) {
if (e-id[i] 0)
break;
h-release_query_id(e-id[i]);
}
e-mutex = e-action.mutex;
SET_CONTINUATION_HANDLER(e, DNSEntry::postEvent);
e-submit_thread-schedule_imm_signal(e);
}
There are calls which will schedule on *ANY* event thread (e.g.
eventProcessor.schedule_XX). These could schedule (e.g. a timeout or other
event) on the ET_DNS thread which perhaps isn't initialized for all the
processors (e.g. sessions).
At one point I removed all calls to the non-specific thread schedule calls, but
it is possible there are some how/still.
Trafficserver 4.1 Crash with proxy.config.dns.dedicated_thread = 1
--
Key: TS-2193
URL: https://issues.apache.org/jira/browse/TS-2193
Project: Traffic Server
Issue Type: Bug
Components: DNS
Affects Versions: 4.1.0
Reporter: Tommy Lee
Fix For: 4.1.0
Hi all,
I've tried to enable DNS Thread without luck.
When i set proxy.config.dns.dedicated_thread to 1, it crashes with the
information below.
The ATS is working in Forward Proxy mode.
Thanks in advance.
--
traffic.out
NOTE: Traffic Server received Sig 11: Segmentation fault
/usr/local/cache-4.1/bin/traffic_server - STACK TRACE:
/lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x2af714875cb0]
/usr/local/cache-4.1/bin/traffic_server(_Z16_acquire_sessionP13SessionBucketPK8sockaddrR7INK_MD5P6HttpSM+0x52)[0x51dac2]
/usr/local/cache-4.1/bin/traffic_server(_ZN18HttpSessionManager15acquire_sessionEP12ContinuationPK8sockaddrPKcP17HttpClientSessionP6HttpSM+0x3d1)[0x51e0f1]
/usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM19do_http_server_openEb+0x30c)[0x53644c]
/usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x6a0)[0x537560]
/usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x57e)[0x53743e]
/usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x57e)[0x53743e]
/usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM27state_hostdb_reverse_lookupEiPv+0xb9)[0x526b99]
/usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM12main_handlerEiPv+0xd8)[0x531be8]
/usr/local/cache-4.1/bin/traffic_server[0x5d7c8a]
/usr/local/cache-4.1/bin/traffic_server(_ZN18HostDBContinuation8dnsEventEiP7HostEnt+0x821)[0x5decd1]
/usr/local/cache-4.1/bin/traffic_server(_ZN8DNSEntry9postEventEiP5Event+0x44)[0x5f7a94]
/usr/local/cache-4.1/bin/traffic_server[0x5fd382]
/usr/local/cache-4.1/bin/traffic_server(_ZN10DNSHandler8recv_dnsEiP5Event+0x852)[0x5fee72]
/usr/local/cache-4.1/bin/traffic_server(_ZN10DNSHandler9mainEventEiP5Event+0x14)[0x5ffd94]
/usr/local/cache-4.1/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x91)[0x6b2a41]
/usr/local/cache-4.1/bin/traffic_server(_ZN7EThread7executeEv+0x514)[0x6b3534]
/usr/local/cache-4.1/bin/traffic_server[0x6b17ea]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x2af71486de9a]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x2af71558dccd]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-2194) alternate renderers for HTTP UI
James Peach created TS-2194: --- Summary: alternate renderers for HTTP UI Key: TS-2194 URL: https://issues.apache.org/jira/browse/TS-2194 Project: Traffic Server Issue Type: New Feature Components: Web UI Reporter: James Peach While reviewing TS-2191, I realized that TS gathers a lot of useful debugging information that is only published in the Web UI pages. We should make more of this information available to command line tools (eg. via traffic_line or SIGINFO, etc). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (TS-2194) alternate renderers for HTTP UI
[ https://issues.apache.org/jira/browse/TS-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Peach reassigned TS-2194: --- Assignee: James Peach alternate renderers for HTTP UI --- Key: TS-2194 URL: https://issues.apache.org/jira/browse/TS-2194 Project: Traffic Server Issue Type: New Feature Components: Web UI Reporter: James Peach Assignee: James Peach While reviewing TS-2191, I realized that TS gathers a lot of useful debugging information that is only published in the Web UI pages. We should make more of this information available to command line tools (eg. via traffic_line or SIGINFO, etc). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-2193) Trafficserver 4.1 Crash with proxy.config.dns.dedicated_thread = 1
[ https://issues.apache.org/jira/browse/TS-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762245#comment-13762245 ] Leif Hedstrom commented on TS-2193: --- I've tried this, and I can not get it to reproduce. It sounds possibly that it's related to proxy.config.http.share_server_sessions=2 ? I've tried with that enabled too, and it does not reproduce with that set either. This is using current master ? Trafficserver 4.1 Crash with proxy.config.dns.dedicated_thread = 1 -- Key: TS-2193 URL: https://issues.apache.org/jira/browse/TS-2193 Project: Traffic Server Issue Type: Bug Components: DNS Affects Versions: 4.1.0 Reporter: Tommy Lee Fix For: 4.1.0 Hi all, I've tried to enable DNS Thread without luck. When i set proxy.config.dns.dedicated_thread to 1, it crashes with the information below. The ATS is working in Forward Proxy mode. Thanks in advance. -- traffic.out NOTE: Traffic Server received Sig 11: Segmentation fault /usr/local/cache-4.1/bin/traffic_server - STACK TRACE: /lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x2af714875cb0] /usr/local/cache-4.1/bin/traffic_server(_Z16_acquire_sessionP13SessionBucketPK8sockaddrR7INK_MD5P6HttpSM+0x52)[0x51dac2] /usr/local/cache-4.1/bin/traffic_server(_ZN18HttpSessionManager15acquire_sessionEP12ContinuationPK8sockaddrPKcP17HttpClientSessionP6HttpSM+0x3d1)[0x51e0f1] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM19do_http_server_openEb+0x30c)[0x53644c] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x6a0)[0x537560] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x57e)[0x53743e] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x57e)[0x53743e] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM27state_hostdb_reverse_lookupEiPv+0xb9)[0x526b99] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM12main_handlerEiPv+0xd8)[0x531be8] /usr/local/cache-4.1/bin/traffic_server[0x5d7c8a] /usr/local/cache-4.1/bin/traffic_server(_ZN18HostDBContinuation8dnsEventEiP7HostEnt+0x821)[0x5decd1] /usr/local/cache-4.1/bin/traffic_server(_ZN8DNSEntry9postEventEiP5Event+0x44)[0x5f7a94] /usr/local/cache-4.1/bin/traffic_server[0x5fd382] /usr/local/cache-4.1/bin/traffic_server(_ZN10DNSHandler8recv_dnsEiP5Event+0x852)[0x5fee72] /usr/local/cache-4.1/bin/traffic_server(_ZN10DNSHandler9mainEventEiP5Event+0x14)[0x5ffd94] /usr/local/cache-4.1/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x91)[0x6b2a41] /usr/local/cache-4.1/bin/traffic_server(_ZN7EThread7executeEv+0x514)[0x6b3534] /usr/local/cache-4.1/bin/traffic_server[0x6b17ea] /lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x2af71486de9a] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x2af71558dccd] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-2176) TSHttpTxnCacheLookupSkip doesn't work
[
https://issues.apache.org/jira/browse/TS-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762398#comment-13762398
]
ASF subversion and git services commented on TS-2176:
-
Commit b1845c4be987a2d0ba331b46839c01e0f17d7666 in branch refs/heads/master
from [~dennovin]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=b1845c4 ]
TS-2176: do not reset value of api_skip_cache_lookup when reading it
When is_request_cache_lookupable reads the value of api_skip_cache_lookup
it also resets the value to false. Since the function is called
from HandleRequest, the flag set by the API call will be ignored
by DecideCacheLookup.
TSHttpTxnCacheLookupSkip doesn't work
-
Key: TS-2176
URL: https://issues.apache.org/jira/browse/TS-2176
Project: Traffic Server
Issue Type: Bug
Components: TS API
Reporter: Corey Cossentino
Assignee: James Peach
Fix For: 4.1.0
Attachments: ts2176_api_skip_cache_lookup.patch
When {{is_request_cache_lookupable}} reads the value of
{{api_skip_cache_lookup}} it also resets the value to false.
Since the function is called from {{HandleRequest}}, the flag set by the API
call will be ignored by {{DecideCacheLookup}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-2195) deprecate TSHttpTxnCacheLookupSkip
James Peach created TS-2195:
---
Summary: deprecate TSHttpTxnCacheLookupSkip
Key: TS-2195
URL: https://issues.apache.org/jira/browse/TS-2195
Project: Traffic Server
Issue Type: Bug
Components: TS API
Reporter: James Peach
{{TSHttpTxnCacheLookupSkip()}} is in experimental, but can be implemented by
stable API, {{TSHttpTxnConfigIntSet(txn, TS_CONFIG_HTTP_CACHE_HTTP, 0)}}.
Let's deprecate this API for 4.1.0, and remove it for 5.0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TS-2195) deprecate TSHttpTxnCacheLookupSkip
[
https://issues.apache.org/jira/browse/TS-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Peach resolved TS-2195.
-
Resolution: Fixed
Fix Version/s: 4.1.0
Assignee: James Peach
deprecate TSHttpTxnCacheLookupSkip
--
Key: TS-2195
URL: https://issues.apache.org/jira/browse/TS-2195
Project: Traffic Server
Issue Type: Bug
Components: TS API
Reporter: James Peach
Assignee: James Peach
Fix For: 4.1.0
{{TSHttpTxnCacheLookupSkip()}} is in experimental, but can be implemented by
stable API, {{TSHttpTxnConfigIntSet(txn, TS_CONFIG_HTTP_CACHE_HTTP, 0)}}.
Let's deprecate this API for 4.1.0, and remove it for 5.0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-2196) remove TSHttpTxnCacheLookupSkip API
[
https://issues.apache.org/jira/browse/TS-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762427#comment-13762427
]
James Peach commented on TS-2196:
-
[~zwoop] should I kill this API now in the 5.0.x branch, or will that create
too many merge conflicts?
remove TSHttpTxnCacheLookupSkip API
---
Key: TS-2196
URL: https://issues.apache.org/jira/browse/TS-2196
Project: Traffic Server
Issue Type: Bug
Components: TS API
Reporter: James Peach
Fix For: 5.0.0
{{TSHttpTxnCacheLookupSkip()}} is in experimental, but can be implemented by
stable API, {{TSHttpTxnConfigIntSet(txn, TS_CONFIG_HTTP_CACHE_HTTP, 0)}}.
Let's deprecate this API for 4.1.0, and remove it for 5.0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-2176) TSHttpTxnCacheLookupSkip doesn't work
[
https://issues.apache.org/jira/browse/TS-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762429#comment-13762429
]
James Peach commented on TS-2176:
-
[~dennovin] please note that I've deprecated this API, though it will remain
(and be fixed by your commit) for the duration of the 4.x release cycle.
TSHttpTxnCacheLookupSkip doesn't work
-
Key: TS-2176
URL: https://issues.apache.org/jira/browse/TS-2176
Project: Traffic Server
Issue Type: Bug
Components: TS API
Reporter: Corey Cossentino
Assignee: James Peach
Fix For: 4.1.0
Attachments: ts2176_api_skip_cache_lookup.patch
When {{is_request_cache_lookupable}} reads the value of
{{api_skip_cache_lookup}} it also resets the value to false.
Since the function is called from {{HandleRequest}}, the flag set by the API
call will be ignored by {{DecideCacheLookup}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-2196) remove TSHttpTxnCacheLookupSkip API
James Peach created TS-2196:
---
Summary: remove TSHttpTxnCacheLookupSkip API
Key: TS-2196
URL: https://issues.apache.org/jira/browse/TS-2196
Project: Traffic Server
Issue Type: Bug
Components: TS API
Reporter: James Peach
{{TSHttpTxnCacheLookupSkip()}} is in experimental, but can be implemented by
stable API, {{TSHttpTxnConfigIntSet(txn, TS_CONFIG_HTTP_CACHE_HTTP, 0)}}.
Let's deprecate this API for 4.1.0, and remove it for 5.0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-2196) remove TSHttpTxnCacheLookupSkip API
[
https://issues.apache.org/jira/browse/TS-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Peach updated TS-2196:
Fix Version/s: 5.0.0
remove TSHttpTxnCacheLookupSkip API
---
Key: TS-2196
URL: https://issues.apache.org/jira/browse/TS-2196
Project: Traffic Server
Issue Type: Bug
Components: TS API
Reporter: James Peach
Fix For: 5.0.0
{{TSHttpTxnCacheLookupSkip()}} is in experimental, but can be implemented by
stable API, {{TSHttpTxnConfigIntSet(txn, TS_CONFIG_HTTP_CACHE_HTTP, 0)}}.
Let's deprecate this API for 4.1.0, and remove it for 5.0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-2195) deprecate TSHttpTxnCacheLookupSkip
[
https://issues.apache.org/jira/browse/TS-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762423#comment-13762423
]
ASF subversion and git services commented on TS-2195:
-
Commit a061d7ca88eb090e3dffe874167c02e4c001301e in branch refs/heads/master
from [~jpe...@apache.org]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=a061d7c ]
TS-2195: Deprecate experimental TSHttpTxnCacheLookupSkip API
TSHttpTxnCacheLookupSkip() is in experimental, but can be implemented
by stable API; TSHttpTxnConfigIntSet(txn, TS_CONFIG_HTTP_CACHE_HTTP, 0).
deprecate TSHttpTxnCacheLookupSkip
--
Key: TS-2195
URL: https://issues.apache.org/jira/browse/TS-2195
Project: Traffic Server
Issue Type: Bug
Components: TS API
Reporter: James Peach
{{TSHttpTxnCacheLookupSkip()}} is in experimental, but can be implemented by
stable API, {{TSHttpTxnConfigIntSet(txn, TS_CONFIG_HTTP_CACHE_HTTP, 0)}}.
Let's deprecate this API for 4.1.0, and remove it for 5.0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (TS-1695) test_certlookup fails on FreeBSD 10
[
https://issues.apache.org/jira/browse/TS-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Peach reassigned TS-1695:
---
Assignee: Igor Galić (was: James Peach)
Igor, how do you feel about setting up a FreeBSD 10 build bot?
test_certlookup fails on FreeBSD 10
---
Key: TS-1695
URL: https://issues.apache.org/jira/browse/TS-1695
Project: Traffic Server
Issue Type: Bug
Components: Portability
Environment: FreeBSD 10, amd64
Reporter: Igor Galić
Assignee: Igor Galić
Labels: freebsd
Fix For: 4.2.0
{noformat}
Reading symbols from
/tmp/org.apache.trafficserver.2624/obj/iocore/net/.libs/test_certlookup...done.
[New process 100244]
[New Thread 803806400 (LWP 100244)]
Core was generated by `test_certlookup'.
Program terminated with signal 10, Bus error.
#0 0x000802cbc43b in ?? () from /lib/libc.so.7
(gdb) bt
#0 0x000802cbc43b in ?? () from /lib/libc.so.7
#1 0x000802cc8c74 in free () from /lib/libc.so.7
#2 0x00405ca6 in TrieSSLContextStorage::SSLEntry::Clear
(this=0x80382c800) at /home/igalic/src/asf/trafficserver/lib/ts/Trie.h:213
#3 0x00405d21 in TrieSSLContextStorage::SSLEntry::~Trie
(this=0x80382c800, __in_chrg=optimized out) at
/home/igalic/src/asf/trafficserver/lib/ts/Trie.h:54
#4 0x00403c11 in SSLContextStorage::~SSLContextStorage
(this=0x80382c800, __in_chrg=optimized out) at
/home/igalic/src/asf/trafficserver/iocore/net/SSLCertLookup.cc:213
#5 0x00403d05 in SSLCertLookup::~SSLCertLookup (this=0x7fffd2e0,
__in_chrg=optimized out) at
/home/igalic/src/asf/trafficserver/iocore/net/SSLCertLookup.cc:102
#6 0x004036a8 in RegressionTest_SSLCertificateLookup (t=0x60daa0
regressionTest_SSLCertificateLookup, atype=0, pstatus=0x60dab8
regressionTest_SSLCertificateLookup+24)
at /home/igalic/src/asf/trafficserver/iocore/net/test_certlookup.cc:78
#7 0x00080085eff6 in start_test (t=0x60daa0
regressionTest_SSLCertificateLookup) at
/home/igalic/src/asf/trafficserver/lib/ts/Regression.cc:77
#8 0x00080085f404 in RegressionTest::run (atest=0x0) at
/home/igalic/src/asf/trafficserver/lib/ts/Regression.cc:98
#9 0x00402ce0 in main (argc=1, argv=0x7fffd470) at
/home/igalic/src/asf/trafficserver/iocore/net/test_certlookup.cc:197
(gdb)
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TS-2188) healthcheck plugin seg faulting
[ https://issues.apache.org/jira/browse/TS-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom resolved TS-2188. --- Resolution: Fixed I believe this is fixed, will go into v4.1.0 (November). You can cherry pick the appropriate fixes if necessary :). healthcheck plugin seg faulting --- Key: TS-2188 URL: https://issues.apache.org/jira/browse/TS-2188 Project: Traffic Server Issue Type: Bug Components: Plugins Reporter: Scott Harris Assignee: Leif Hedstrom Fix For: 4.1.0 When using the experimental healthcheck plugin any request received with a uri of / or null results in a seg fault. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-2193) Trafficserver 4.1 Crash with proxy.config.dns.dedicated_thread = 1
[ https://issues.apache.org/jira/browse/TS-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762288#comment-13762288 ] Leif Hedstrom commented on TS-2193: --- Yeah, attach any bf's you can get. If you get them with the mangled symbols, please 'pipe' them through c++filt (which turns them into human readable symbol names). Trafficserver 4.1 Crash with proxy.config.dns.dedicated_thread = 1 -- Key: TS-2193 URL: https://issues.apache.org/jira/browse/TS-2193 Project: Traffic Server Issue Type: Bug Components: DNS Affects Versions: 4.1.0 Reporter: Tommy Lee Fix For: 4.1.0 Hi all, I've tried to enable DNS Thread without luck. When i set proxy.config.dns.dedicated_thread to 1, it crashes with the information below. The ATS is working in Forward Proxy mode. Thanks in advance. -- traffic.out NOTE: Traffic Server received Sig 11: Segmentation fault /usr/local/cache-4.1/bin/traffic_server - STACK TRACE: /lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x2af714875cb0] /usr/local/cache-4.1/bin/traffic_server(_Z16_acquire_sessionP13SessionBucketPK8sockaddrR7INK_MD5P6HttpSM+0x52)[0x51dac2] /usr/local/cache-4.1/bin/traffic_server(_ZN18HttpSessionManager15acquire_sessionEP12ContinuationPK8sockaddrPKcP17HttpClientSessionP6HttpSM+0x3d1)[0x51e0f1] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM19do_http_server_openEb+0x30c)[0x53644c] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x6a0)[0x537560] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x57e)[0x53743e] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x57e)[0x53743e] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM27state_hostdb_reverse_lookupEiPv+0xb9)[0x526b99] /usr/local/cache-4.1/bin/traffic_server(_ZN6HttpSM12main_handlerEiPv+0xd8)[0x531be8] /usr/local/cache-4.1/bin/traffic_server[0x5d7c8a] /usr/local/cache-4.1/bin/traffic_server(_ZN18HostDBContinuation8dnsEventEiP7HostEnt+0x821)[0x5decd1] /usr/local/cache-4.1/bin/traffic_server(_ZN8DNSEntry9postEventEiP5Event+0x44)[0x5f7a94] /usr/local/cache-4.1/bin/traffic_server[0x5fd382] /usr/local/cache-4.1/bin/traffic_server(_ZN10DNSHandler8recv_dnsEiP5Event+0x852)[0x5fee72] /usr/local/cache-4.1/bin/traffic_server(_ZN10DNSHandler9mainEventEiP5Event+0x14)[0x5ffd94] /usr/local/cache-4.1/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x91)[0x6b2a41] /usr/local/cache-4.1/bin/traffic_server(_ZN7EThread7executeEv+0x514)[0x6b3534] /usr/local/cache-4.1/bin/traffic_server[0x6b17ea] /lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x2af71486de9a] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x2af71558dccd] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-2190) need a way to turn off cacheurl.log for cacheurl plugin
[
https://issues.apache.org/jira/browse/TS-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762480#comment-13762480
]
James Peach commented on TS-2190:
-
The logging in the cacheurl plugin is really just debug statements. I don't
think that log objects are appropriate here.
Would it be a compatible change for 4.x if I switched these to {{TSDebug()}}
statements?
need a way to turn off cacheurl.log for cacheurl plugin
Key: TS-2190
URL: https://issues.apache.org/jira/browse/TS-2190
Project: Traffic Server
Issue Type: Improvement
Components: Plugins
Affects Versions: 4.0.1
Reporter: esmq2092
Priority: Minor
the cacheurl.log may useful for debug only, need a way to turn it off
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-2190) need a way to turn off cacheurl.log for cacheurl plugin
[ https://issues.apache.org/jira/browse/TS-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762493#comment-13762493 ] James Peach commented on TS-2190: - [~mivok] What's the rationale for logging this information? It is operationally useful? need a way to turn off cacheurl.log for cacheurl plugin Key: TS-2190 URL: https://issues.apache.org/jira/browse/TS-2190 Project: Traffic Server Issue Type: Improvement Components: Plugins Affects Versions: 4.0.1 Reporter: esmq2092 Assignee: James Peach Priority: Minor Fix For: 4.1.0 the cacheurl.log may useful for debug only, need a way to turn it off -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-2190) need a way to turn off cacheurl.log for cacheurl plugin
[ https://issues.apache.org/jira/browse/TS-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762587#comment-13762587 ] Mark Harrison commented on TS-2190: --- The reason for adding logging was just to make sure that your rules are set correctly. Operationally it would be useful for troubleshooting issues with multiple pages being cached with the same content unintentionally. That said, I see no reason why that couldn't be done with TSDebug statements and just enable it if/when necessary. need a way to turn off cacheurl.log for cacheurl plugin Key: TS-2190 URL: https://issues.apache.org/jira/browse/TS-2190 Project: Traffic Server Issue Type: Improvement Components: Plugins Affects Versions: 4.0.1 Reporter: esmq2092 Assignee: James Peach Priority: Minor Fix For: 4.1.0 the cacheurl.log may useful for debug only, need a way to turn it off -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-2188) healthcheck plugin seg faulting
[ https://issues.apache.org/jira/browse/TS-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762596#comment-13762596 ] Scott Harris commented on TS-2188: -- applied patches on version 4.0.1 and all tested ok. Thanks again. healthcheck plugin seg faulting --- Key: TS-2188 URL: https://issues.apache.org/jira/browse/TS-2188 Project: Traffic Server Issue Type: Bug Components: Plugins Reporter: Scott Harris Assignee: Leif Hedstrom Fix For: 4.1.0 When using the experimental healthcheck plugin any request received with a uri of / or null results in a seg fault. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1086) Returning 304 response to unconditional request
[ https://issues.apache.org/jira/browse/TS-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762612#comment-13762612 ] seri,Kim commented on TS-1086: -- After applying this patch, the problem disappeared. Thanks!! Returning 304 response to unconditional request --- Key: TS-1086 URL: https://issues.apache.org/jira/browse/TS-1086 Project: Traffic Server Issue Type: Bug Components: HTTP Affects Versions: 3.0.1 Environment: Observed on Amazon/ec2 build, which is 3.0.1 on redhat-like linux. Reporter: Nick Kew Assignee: Nick Kew Fix For: 4.1.0 Attachments: TS-1086.diff ab is reporting HTTP 304 responses to a small number of unconditional requests in a test run: GET /testfile.html HTTP/1.0^M Host: localhost^M User-Agent: ApacheBench/2.3^M Accept: */*^M ^M HTTP/1.0 304 Not Modified^M Date: Mon, 21 Nov 2011 14:23:48 GMT^M Server: ATS/3.0.1^M ETag: 5e24-24cd-4b23b69f6e89c^M Cache-Control: max-age=60^M Age: 2^M ^M I presume what's happening is that trafficserver is sending a conditional request with If-Modified-Since to the origin server, and then returning the origin's 304 response to the client's unconditional request. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-2197) http_sm may not perceive client_vc`s aborted if it is not a new connection
[ https://issues.apache.org/jira/browse/TS-2197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] weijin updated TS-2197: --- Attachment: TS-2197.wj.diff not call the state_read_client_request_header directly, or else the http_sm maybe deleted before the function return. http_sm may not perceive client_vc`s aborted if it is not a new connection -- Key: TS-2197 URL: https://issues.apache.org/jira/browse/TS-2197 Project: Traffic Server Issue Type: Bug Components: HTTP Reporter: weijin Attachments: TS-2197.wj.diff for a keepalive connection, the second request maybe already in the ua_buffer, the current code disabled the client_vc`s read when parse the http_hdr in such case, which means we can not notified the client_vc is aborted as soon as possible. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-2198) backport: CLONE - when http_info enabled, the http_sm may be deleted but a event associated it not cancelled.
Zhao Yongming created TS-2198: - Summary: backport: CLONE - when http_info enabled, the http_sm may be deleted but a event associated it not cancelled. Key: TS-2198 URL: https://issues.apache.org/jira/browse/TS-2198 Project: Traffic Server Issue Type: Bug Components: HTTP Reporter: Zhao Yongming Attachments: TS-2191.wj.diff if the http_info enabled, when the sm_list`s lock not acquired but the client_vc`s timeout event triggered, the race may lead ts crash. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-2198) backport: CLONE - when http_info enabled, the http_sm may be deleted but a event associated it not cancelled.
[ https://issues.apache.org/jira/browse/TS-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao Yongming updated TS-2198: -- Backport to Version: 4.0.2 Fix Version/s: 4.0.2 Assignee: weijin backport: CLONE - when http_info enabled, the http_sm may be deleted but a event associated it not cancelled. -- Key: TS-2198 URL: https://issues.apache.org/jira/browse/TS-2198 Project: Traffic Server Issue Type: Bug Components: HTTP Reporter: Zhao Yongming Assignee: weijin Fix For: 4.0.2 Attachments: TS-2191.wj.diff if the http_info enabled, when the sm_list`s lock not acquired but the client_vc`s timeout event triggered, the race may lead ts crash. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-2191) when http_info enabled, the http_sm may be deleted but a event associated it not cancelled.
[ https://issues.apache.org/jira/browse/TS-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] weijin updated TS-2191: --- Backport to Version: 4.0.2 Assignee: weijin when http_info enabled, the http_sm may be deleted but a event associated it not cancelled. Key: TS-2191 URL: https://issues.apache.org/jira/browse/TS-2191 Project: Traffic Server Issue Type: Bug Components: HTTP Reporter: weijin Assignee: weijin Attachments: TS-2191.wj.diff if the http_info enabled, when the sm_list`s lock not acquired but the client_vc`s timeout event triggered, the race may lead ts crash. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1086) Returning 304 response to unconditional request
[ https://issues.apache.org/jira/browse/TS-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762682#comment-13762682 ] Leif Hedstrom commented on TS-1086: --- Sounds like this bug can be marked Resolved, right? Once resolved, and we publish v4.1.0, it'll get moved to closed. Returning 304 response to unconditional request --- Key: TS-1086 URL: https://issues.apache.org/jira/browse/TS-1086 Project: Traffic Server Issue Type: Bug Components: HTTP Affects Versions: 3.0.1 Environment: Observed on Amazon/ec2 build, which is 3.0.1 on redhat-like linux. Reporter: Nick Kew Assignee: Nick Kew Fix For: 4.1.0 Attachments: TS-1086.diff ab is reporting HTTP 304 responses to a small number of unconditional requests in a test run: GET /testfile.html HTTP/1.0^M Host: localhost^M User-Agent: ApacheBench/2.3^M Accept: */*^M ^M HTTP/1.0 304 Not Modified^M Date: Mon, 21 Nov 2011 14:23:48 GMT^M Server: ATS/3.0.1^M ETag: 5e24-24cd-4b23b69f6e89c^M Cache-Control: max-age=60^M Age: 2^M ^M I presume what's happening is that trafficserver is sending a conditional request with If-Modified-Since to the origin server, and then returning the origin's 304 response to the client's unconditional request. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-2196) remove TSHttpTxnCacheLookupSkip API
[
https://issues.apache.org/jira/browse/TS-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762685#comment-13762685
]
Leif Hedstrom commented on TS-2196:
---
That's a good question. I'd like to say that we should kill it sooner rather
than later, such that the 5.0.x branch is in the state we want it to be as soon
as possible. Hopefully the merge conflicts will be manageable as long as we
continuously merge branch to 5.0.x.
[~jpe...@apache.org]What do you think?
remove TSHttpTxnCacheLookupSkip API
---
Key: TS-2196
URL: https://issues.apache.org/jira/browse/TS-2196
Project: Traffic Server
Issue Type: Bug
Components: TS API
Reporter: James Peach
Fix For: 5.0.0
{{TSHttpTxnCacheLookupSkip()}} is in experimental, but can be implemented by
stable API, {{TSHttpTxnConfigIntSet(txn, TS_CONFIG_HTTP_CACHE_HTTP, 0)}}.
Let's deprecate this API for 4.1.0, and remove it for 5.0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-2199) Warning from livxml: Use of deprecated SAXv1 function endElement
Leif Hedstrom created TS-2199:
-
Summary: Warning from livxml: Use of deprecated SAXv1 function
endElement
Key: TS-2199
URL: https://issues.apache.org/jira/browse/TS-2199
Project: Traffic Server
Issue Type: Bug
Components: Core
Reporter: Leif Hedstrom
When starting traffic_manager, we get a warning when linking with the the
libxml2 library:
{code}
Use of deprecated SAXv1 function endElement
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-2199) Warning from livxml: Use of deprecated SAXv1 function endElement
[
https://issues.apache.org/jira/browse/TS-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-2199:
--
Fix Version/s: 4.1.0
Assignee: Nick Kew
Nick, marking this for you, can you take a look at it?
Warning from livxml: Use of deprecated SAXv1 function endElement
Key: TS-2199
URL: https://issues.apache.org/jira/browse/TS-2199
Project: Traffic Server
Issue Type: Bug
Components: Core
Reporter: Leif Hedstrom
Assignee: Nick Kew
Fix For: 4.1.0
When starting traffic_manager, we get a warning when linking with the the
libxml2 library:
{code}
Use of deprecated SAXv1 function endElement
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-2200) the macro TS_HRTIME_xxx in proxy/api/ts/experimental.h is invalid when plugin use these macros
Yu Qing created TS-2200: --- Summary: the macro TS_HRTIME_xxx in proxy/api/ts/experimental.h is invalid when plugin use these macros Key: TS-2200 URL: https://issues.apache.org/jira/browse/TS-2200 Project: Traffic Server Issue Type: Bug Components: TS API Reporter: Yu Qing such macro defines in proxy/api/ts/experimental.h: #define TS_HRTIME_FOREVER HRTIME_FOREVER #define TS_HRTIME_DECADE HRTIME_DECADE #define TS_HRTIME_YEAR HRTIME_YEAR #define TS_HRTIME_WEEK HRTIME_WEEK #define TS_HRTIME_DAY HRTIME_DAY #define TS_HRTIME_HOUR HRTIME_HOUR #define TS_HRTIME_MINUTE HRTIME_MINUTE #define TS_HRTIME_SECOND HRTIME_SECOND #define TS_HRTIME_MSECOND HRTIME_MSECOND #define TS_HRTIME_USECOND HRTIME_USECOND #define TS_HRTIME_NSECOND HRTIME_NSECOND ... The macros of HRTIME_xxx (such as HRTIME_SECOND) in lib/ts/ink_hrtime.h。 Because the TS plugins SHOULD not include the header file ink_hrtime.h, so they can't use above macros like TS_HRTIME_xxx。 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-2199) Warning from libxml2: Use of deprecated SAXv1 function endElement
[
https://issues.apache.org/jira/browse/TS-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-2199:
--
Summary: Warning from libxml2: Use of deprecated SAXv1 function endElement
(was: Warning from livxml: Use of deprecated SAXv1 function endElement)
Warning from libxml2: Use of deprecated SAXv1 function endElement
-
Key: TS-2199
URL: https://issues.apache.org/jira/browse/TS-2199
Project: Traffic Server
Issue Type: Bug
Components: Core
Reporter: Leif Hedstrom
Assignee: Nick Kew
Fix For: 4.1.0
When starting traffic_manager, we get a warning when linking with the the
libxml2 library:
{code}
Use of deprecated SAXv1 function endElement
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-2194) alternate renderers for HTTP UI
[ https://issues.apache.org/jira/browse/TS-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762714#comment-13762714 ] Leif Hedstrom commented on TS-2194: --- Maybe make it generic such that it's exposed in both TS API's (plugins) and the Mgmt APIs (command line). As a TS API plugin, it would then be easy to rip it out of the core and into a server intercept plugin. alternate renderers for HTTP UI --- Key: TS-2194 URL: https://issues.apache.org/jira/browse/TS-2194 Project: Traffic Server Issue Type: New Feature Components: Web UI Reporter: James Peach Assignee: James Peach While reviewing TS-2191, I realized that TS gathers a lot of useful debugging information that is only published in the Web UI pages. We should make more of this information available to command line tools (eg. via traffic_line or SIGINFO, etc). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1695) test_certlookup fails on FreeBSD 10
[
https://issues.apache.org/jira/browse/TS-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762758#comment-13762758
]
Igor Galić commented on TS-1695:
sure!
--
Sent from my phone. Please excuse my brevity.
test_certlookup fails on FreeBSD 10
---
Key: TS-1695
URL: https://issues.apache.org/jira/browse/TS-1695
Project: Traffic Server
Issue Type: Bug
Components: Portability
Environment: FreeBSD 10, amd64
Reporter: Igor Galić
Assignee: Igor Galić
Labels: freebsd
Fix For: 4.2.0
{noformat}
Reading symbols from
/tmp/org.apache.trafficserver.2624/obj/iocore/net/.libs/test_certlookup...done.
[New process 100244]
[New Thread 803806400 (LWP 100244)]
Core was generated by `test_certlookup'.
Program terminated with signal 10, Bus error.
#0 0x000802cbc43b in ?? () from /lib/libc.so.7
(gdb) bt
#0 0x000802cbc43b in ?? () from /lib/libc.so.7
#1 0x000802cc8c74 in free () from /lib/libc.so.7
#2 0x00405ca6 in TrieSSLContextStorage::SSLEntry::Clear
(this=0x80382c800) at /home/igalic/src/asf/trafficserver/lib/ts/Trie.h:213
#3 0x00405d21 in TrieSSLContextStorage::SSLEntry::~Trie
(this=0x80382c800, __in_chrg=optimized out) at
/home/igalic/src/asf/trafficserver/lib/ts/Trie.h:54
#4 0x00403c11 in SSLContextStorage::~SSLContextStorage
(this=0x80382c800, __in_chrg=optimized out) at
/home/igalic/src/asf/trafficserver/iocore/net/SSLCertLookup.cc:213
#5 0x00403d05 in SSLCertLookup::~SSLCertLookup (this=0x7fffd2e0,
__in_chrg=optimized out) at
/home/igalic/src/asf/trafficserver/iocore/net/SSLCertLookup.cc:102
#6 0x004036a8 in RegressionTest_SSLCertificateLookup (t=0x60daa0
regressionTest_SSLCertificateLookup, atype=0, pstatus=0x60dab8
regressionTest_SSLCertificateLookup+24)
at /home/igalic/src/asf/trafficserver/iocore/net/test_certlookup.cc:78
#7 0x00080085eff6 in start_test (t=0x60daa0
regressionTest_SSLCertificateLookup) at
/home/igalic/src/asf/trafficserver/lib/ts/Regression.cc:77
#8 0x00080085f404 in RegressionTest::run (atest=0x0) at
/home/igalic/src/asf/trafficserver/lib/ts/Regression.cc:98
#9 0x00402ce0 in main (argc=1, argv=0x7fffd470) at
/home/igalic/src/asf/trafficserver/iocore/net/test_certlookup.cc:197
(gdb)
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-2200) the macro TS_HRTIME_xxx in proxy/api/ts/experimental.h is invalid when plugin use these macros
[ https://issues.apache.org/jira/browse/TS-2200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Qing updated TS-2200: Assignee: Yu Qing the macro TS_HRTIME_xxx in proxy/api/ts/experimental.h is invalid when plugin use these macros -- Key: TS-2200 URL: https://issues.apache.org/jira/browse/TS-2200 Project: Traffic Server Issue Type: Bug Components: TS API Reporter: Yu Qing Assignee: Yu Qing such macro defines in proxy/api/ts/experimental.h: #define TS_HRTIME_FOREVER HRTIME_FOREVER #define TS_HRTIME_DECADE HRTIME_DECADE #define TS_HRTIME_YEAR HRTIME_YEAR #define TS_HRTIME_WEEK HRTIME_WEEK #define TS_HRTIME_DAY HRTIME_DAY #define TS_HRTIME_HOUR HRTIME_HOUR #define TS_HRTIME_MINUTE HRTIME_MINUTE #define TS_HRTIME_SECOND HRTIME_SECOND #define TS_HRTIME_MSECOND HRTIME_MSECOND #define TS_HRTIME_USECOND HRTIME_USECOND #define TS_HRTIME_NSECOND HRTIME_NSECOND ... The macros of HRTIME_xxx (such as HRTIME_SECOND) in lib/ts/ink_hrtime.h。 Because the TS plugins SHOULD not include the header file ink_hrtime.h, so they can't use above macros like TS_HRTIME_xxx。 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-2200) the macro TS_HRTIME_xxx in proxy/api/ts/experimental.h is invalid when plugin use these macros
[ https://issues.apache.org/jira/browse/TS-2200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Qing updated TS-2200: Attachment: 0001-define-macro-TS_HRTIME_XXX-directly.patch define these macros directly. the macro TS_HRTIME_xxx in proxy/api/ts/experimental.h is invalid when plugin use these macros -- Key: TS-2200 URL: https://issues.apache.org/jira/browse/TS-2200 Project: Traffic Server Issue Type: Bug Components: TS API Reporter: Yu Qing Assignee: Yu Qing Attachments: 0001-define-macro-TS_HRTIME_XXX-directly.patch such macro defines in proxy/api/ts/experimental.h: #define TS_HRTIME_FOREVER HRTIME_FOREVER #define TS_HRTIME_DECADE HRTIME_DECADE #define TS_HRTIME_YEAR HRTIME_YEAR #define TS_HRTIME_WEEK HRTIME_WEEK #define TS_HRTIME_DAY HRTIME_DAY #define TS_HRTIME_HOUR HRTIME_HOUR #define TS_HRTIME_MINUTE HRTIME_MINUTE #define TS_HRTIME_SECOND HRTIME_SECOND #define TS_HRTIME_MSECOND HRTIME_MSECOND #define TS_HRTIME_USECOND HRTIME_USECOND #define TS_HRTIME_NSECOND HRTIME_NSECOND ... The macros of HRTIME_xxx (such as HRTIME_SECOND) in lib/ts/ink_hrtime.h。 Because the TS plugins SHOULD not include the header file ink_hrtime.h, so they can't use above macros like TS_HRTIME_xxx。 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
