[jira] [Updated] (TS-2678) Some sites (e.g. craigslist) fails to load with patch in e6b9cb533bba28
[
https://issues.apache.org/jira/browse/TS-2678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-2678:
--
Fix Version/s: 5.0.0
Some sites (e.g. craigslist) fails to load with patch in e6b9cb533bba28
---
Key: TS-2678
URL: https://issues.apache.org/jira/browse/TS-2678
Project: Traffic Server
Issue Type: Bug
Components: HTTP
Reporter: Leif Hedstrom
Assignee: James Peach
Priority: Critical
Fix For: 5.0.0
The commit e6b9cb533bba28, from
TS-2559: Disconnect clients on unrecoverable origin errors
is causing some sites to break badly:
{code}
curl: (52) Empty reply from server
{code}
or sometimes
{code}
HTTP/1.1 302 Found
Location: http://www.craigslist.org/
Date: Mon, 31 Mar 2014 02:36:51 GMT
Age: 0
Transfer-Encoding: chunked
Proxy-Connection: keep-alive
Server: ATS/5.0.0
curl: (18) transfer closed with outstanding read data remaining
{code}
The first one happens most frequently in my test, and the second one is close
to what is expected (but not quite). Both makes the page not load properly
from any browser.
To reproduce this, using a default installation, with remap.require
disabled (so, forward proxy), I run
{code}
curl -D - -x localhost:8080 http://www.craigslist.com
{code}
I don't know what it is that Craigslist does to trigger this, but backing out
the patch from TS-2559 does fix the problem.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (TS-2554) New plugin: detect 206 responses from origin, and do a background fill on the entire object
[ https://issues.apache.org/jira/browse/TS-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13955197#comment-13955197 ] Faysal Banna commented on TS-2554: -- Hi Guys I Enabled background_fetch.so and tried to see how things go. i got server restarting always and also had these msgs in traffic.out NOTE: Traffic Server received Sig 11: Segmentation fault /usr/local/bin/traffic_server - STACK TRACE: /lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x2b478c92acb0] /usr/local/bin/traffic_server(TSContDestroy+0xd)[0x4b684d] /usr/local/libexec/trafficserver/background_fetch.so(_ZN11BGFetchDataD1Ev+0x15a)[0x2b479700db2a] /usr/local/libexec/trafficserver/background_fetch.so(+0x3490)[0x2b479700c490] /usr/local/bin/traffic_server(_ZN6HttpSM17state_api_calloutEiPv+0x100)[0x52fc50] /usr/local/bin/traffic_server(_ZN6HttpSM18state_api_callbackEiPv+0x8a)[0x5325fa] /usr/local/bin/traffic_server(TSHttpTxnReenable+0x141)[0x4be971] /usr/local/libexec/trafficserver/header_rewrite.so(+0x1574d)[0x2b4796df074d] /usr/local/bin/traffic_server(_ZN6HttpSM17state_api_calloutEiPv+0x100)[0x52fc50] /usr/local/bin/traffic_server(_ZN6HttpSM33state_read_server_response_headerEiPv+0x370)[0x5317a0] /usr/local/bin/traffic_server(_ZN6HttpSM12main_handlerEiPv+0xd8)[0x530d78] /usr/local/bin/traffic_server[0x6a0c10] /usr/local/bin/traffic_server(_ZN10NetHandler12mainNetEventEiP5Event+0x1ed)[0x692add] /usr/local/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x91)[0x6c2b51] /usr/local/bin/traffic_server(_ZN7EThread7executeEv+0x484)[0x6c3444] /usr/local/bin/traffic_server[0x6c1dea] /lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x2b478c922e9a] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x2b478d6443fd] much regards New plugin: detect 206 responses from origin, and do a background fill on the entire object --- Key: TS-2554 URL: https://issues.apache.org/jira/browse/TS-2554 Project: Traffic Server Issue Type: New Feature Components: Plugins Reporter: Leif Hedstrom Assignee: Leif Hedstrom Fix For: 5.0.0 This is one solution to the caching partial objects problem, in that it allows the server to automatically detect objects which should be cached, and setup a background task to do so. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (TS-2679) detect 206 range requests
Faysal Banna created TS-2679: Summary: detect 206 range requests Key: TS-2679 URL: https://issues.apache.org/jira/browse/TS-2679 Project: Traffic Server Issue Type: Bug Components: Cache, Plugins Reporter: Faysal Banna Hi Guys I Enabled background_fetch.so and tried to see how things go. i got server restarting always and also had these msgs in traffic.out NOTE: Traffic Server received Sig 11: Segmentation fault /usr/local/bin/traffic_server - STACK TRACE: /lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x2b478c92acb0] /usr/local/bin/traffic_server(TSContDestroy+0xd)[0x4b684d] /usr/local/libexec/trafficserver/background_fetch.so(_ZN11BGFetchDataD1Ev+0x15a)[0x2b479700db2a] /usr/local/libexec/trafficserver/background_fetch.so(+0x3490)[0x2b479700c490] /usr/local/bin/traffic_server(_ZN6HttpSM17state_api_calloutEiPv+0x100)[0x52fc50] /usr/local/bin/traffic_server(_ZN6HttpSM18state_api_callbackEiPv+0x8a)[0x5325fa] /usr/local/bin/traffic_server(TSHttpTxnReenable+0x141)[0x4be971] /usr/local/libexec/trafficserver/header_rewrite.so(+0x1574d)[0x2b4796df074d] /usr/local/bin/traffic_server(_ZN6HttpSM17state_api_calloutEiPv+0x100)[0x52fc50] /usr/local/bin/traffic_server(_ZN6HttpSM33state_read_server_response_headerEiPv+0x370)[0x5317a0] /usr/local/bin/traffic_server(_ZN6HttpSM12main_handlerEiPv+0xd8)[0x530d78] /usr/local/bin/traffic_server[0x6a0c10] /usr/local/bin/traffic_server(_ZN10NetHandler12mainNetEventEiP5Event+0x1ed)[0x692add] /usr/local/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x91)[0x6c2b51] /usr/local/bin/traffic_server(_ZN7EThread7executeEv+0x484)[0x6c3444] /usr/local/bin/traffic_server[0x6c1dea] /lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x2b478c922e9a] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x2b478d6443fd] much regards -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2679) detect 206 range requests
[
https://issues.apache.org/jira/browse/TS-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-2679:
--
Description:
Hi Guys
I Enabled background_fetch.so and tried to see how things go.
i got server restarting always
and also had these msgs in traffic.out
NOTE: Traffic Server received Sig 11: Segmentation fault
{code}
/usr/local/bin/traffic_server - STACK TRACE:
/lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x2b478c92acb0]
/usr/local/bin/traffic_server(TSContDestroy+0xd)[0x4b684d]
/usr/local/libexec/trafficserver/background_fetch.so(BGFetchData::~BGFetchData()+0x15a)[0x2b479700db2a]
/usr/local/libexec/trafficserver/background_fetch.so(+0x3490)[0x2b479700c490]
/usr/local/bin/traffic_server(HttpSM::state_api_callout(int,
void*)+0x100)[0x52fc50]
/usr/local/bin/traffic_server(HttpSM::state_api_callback(int,
void*)+0x8a)[0x5325fa]
/usr/local/bin/traffic_server(TSHttpTxnReenable+0x141)[0x4be971]
/usr/local/libexec/trafficserver/header_rewrite.so(+0x1574d)[0x2b4796df074d]
/usr/local/bin/traffic_server(HttpSM::state_api_callout(int,
void*)+0x100)[0x52fc50]
/usr/local/bin/traffic_server(HttpSM::state_read_server_response_header(int,
void*)+0x370)[0x5317a0]
/usr/local/bin/traffic_server(HttpSM::main_handler(int, void*)+0xd8)[0x530d78]
/usr/local/bin/traffic_server[0x6a0c10]
/usr/local/bin/traffic_server(NetHandler::mainNetEvent(int,
Event*)+0x1ed)[0x692add]
/usr/local/bin/traffic_server(EThread::process_event(Event*,
int)+0x91)[0x6c2b51]
/usr/local/bin/traffic_server(EThread::execute()+0x484)[0x6c3444]
/usr/local/bin/traffic_server[0x6c1dea]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x2b478c922e9a]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x2b478d6443fd]
{code}
much regards
was:
Hi Guys
I Enabled background_fetch.so and tried to see how things go.
i got server restarting always
and also had these msgs in traffic.out
NOTE: Traffic Server received Sig 11: Segmentation fault
/usr/local/bin/traffic_server - STACK TRACE:
/lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x2b478c92acb0]
/usr/local/bin/traffic_server(TSContDestroy+0xd)[0x4b684d]
/usr/local/libexec/trafficserver/background_fetch.so(_ZN11BGFetchDataD1Ev+0x15a)[0x2b479700db2a]
/usr/local/libexec/trafficserver/background_fetch.so(+0x3490)[0x2b479700c490]
/usr/local/bin/traffic_server(_ZN6HttpSM17state_api_calloutEiPv+0x100)[0x52fc50]
/usr/local/bin/traffic_server(_ZN6HttpSM18state_api_callbackEiPv+0x8a)[0x5325fa]
/usr/local/bin/traffic_server(TSHttpTxnReenable+0x141)[0x4be971]
/usr/local/libexec/trafficserver/header_rewrite.so(+0x1574d)[0x2b4796df074d]
/usr/local/bin/traffic_server(_ZN6HttpSM17state_api_calloutEiPv+0x100)[0x52fc50]
/usr/local/bin/traffic_server(_ZN6HttpSM33state_read_server_response_headerEiPv+0x370)[0x5317a0]
/usr/local/bin/traffic_server(_ZN6HttpSM12main_handlerEiPv+0xd8)[0x530d78]
/usr/local/bin/traffic_server[0x6a0c10]
/usr/local/bin/traffic_server(_ZN10NetHandler12mainNetEventEiP5Event+0x1ed)[0x692add]
/usr/local/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x91)[0x6c2b51]
/usr/local/bin/traffic_server(_ZN7EThread7executeEv+0x484)[0x6c3444]
/usr/local/bin/traffic_server[0x6c1dea]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x2b478c922e9a]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x2b478d6443fd]
much regards
detect 206 range requests
--
Key: TS-2679
URL: https://issues.apache.org/jira/browse/TS-2679
Project: Traffic Server
Issue Type: Bug
Components: Cache, Plugins
Reporter: Faysal Banna
Hi Guys
I Enabled background_fetch.so and tried to see how things go.
i got server restarting always
and also had these msgs in traffic.out
NOTE: Traffic Server received Sig 11: Segmentation fault
{code}
/usr/local/bin/traffic_server - STACK TRACE:
/lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x2b478c92acb0]
/usr/local/bin/traffic_server(TSContDestroy+0xd)[0x4b684d]
/usr/local/libexec/trafficserver/background_fetch.so(BGFetchData::~BGFetchData()+0x15a)[0x2b479700db2a]
/usr/local/libexec/trafficserver/background_fetch.so(+0x3490)[0x2b479700c490]
/usr/local/bin/traffic_server(HttpSM::state_api_callout(int,
void*)+0x100)[0x52fc50]
/usr/local/bin/traffic_server(HttpSM::state_api_callback(int,
void*)+0x8a)[0x5325fa]
/usr/local/bin/traffic_server(TSHttpTxnReenable+0x141)[0x4be971]
/usr/local/libexec/trafficserver/header_rewrite.so(+0x1574d)[0x2b4796df074d]
/usr/local/bin/traffic_server(HttpSM::state_api_callout(int,
void*)+0x100)[0x52fc50]
/usr/local/bin/traffic_server(HttpSM::state_read_server_response_header(int,
void*)+0x370)[0x5317a0]
/usr/local/bin/traffic_server(HttpSM::main_handler(int, void*)+0xd8)[0x530d78]
/usr/local/bin/traffic_server[0x6a0c10]
/usr/local/bin/traffic_server(NetHandler::mainNetEvent(int,
Event*)+0x1ed)[0x692add]
[jira] [Created] (TS-2680) Occasional crash in HdrHeap
Peter Walsh created TS-2680: --- Summary: Occasional crash in HdrHeap Key: TS-2680 URL: https://issues.apache.org/jira/browse/TS-2680 Project: Traffic Server Issue Type: Bug Reporter: Peter Walsh Every few days we are seeing a crash in HdrHeap. We have not been able to reproduce in test environments, but will attach additional information when we do. NOTE: Traffic Server received Sig 11: Segmentation fault /usr/local/bin/traffic_server - STACK TRACE: /lib64/libpthread.so.0[0x3583c0eca0] /usr/local/bin/traffic_server(HdrHeap::attach_block(IOBufferBlock*, char const*)+0x80)[0x5c13f0] /usr/local/bin/traffic_server(HTTPHdr::parse_resp(HTTPParser*, IOBufferReader*, int*, bool)+0x15d)[0x5c15fd] /usr/local/bin/traffic_server(HttpSM::state_read_server_response_header(int, void*)+0x138)[0x52eea8] /usr/local/bin/traffic_server(HttpSM::main_handler(int, void*)+0xdc)[0x530fec] /usr/local/bin/traffic_server[0x69415b] /usr/local/bin/traffic_server(NetHandler::mainNetEvent(int, Event*)+0x479)[0x68a2c9] /usr/local/bin/traffic_server(EThread::process_event(Event*, int)+0x22f)[0x6b9bbf] /usr/local/bin/traffic_server(EThread::execute()+0x5bc)[0x6ba4cc] /usr/local/bin/traffic_server[0x6b900e] /lib64/libpthread.so.0[0x3583c0683d] /lib64/libc.so.6(clone+0x6d)[0x35834d526d] -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (TS-2681) Crash in MIOBuffer write_avail
Peter Walsh created TS-2681: --- Summary: Crash in MIOBuffer write_avail Key: TS-2681 URL: https://issues.apache.org/jira/browse/TS-2681 Project: Traffic Server Issue Type: Bug Reporter: Peter Walsh We have only seen this happen once but since it is a crasher I wanted to document it as a bug. I will update this ticket as I gather additional data. NOTE: Traffic Server received Sig 11: Segmentation fault /usr/local/bin/traffic_server - STACK TRACE: /lib64/libpthread.so.0[0x3583c0eca0] /usr/local/bin/traffic_server(MIOBuffer::write_avail()+0x30)[0x696090] /usr/local/bin/traffic_server(write_to_net_io(NetHandler*, UnixNetVConnection*, EThread*)+0x9e3)[0x692353] /usr/local/bin/traffic_server(NetHandler::mainNetEvent(int, Event*)+0x460)[0x68a2b0] /usr/local/bin/traffic_server(EThread::process_event(Event*, int)+0x22f)[0x6b9bbf] /usr/local/bin/traffic_server(EThread::execute()+0x5bc)[0x6ba4cc] /usr/local/bin/traffic_server[0x6b900e] /lib64/libpthread.so.0[0x3583c0683d] /lib64/libc.so.6(clone+0x6d)[0x35834d526d] -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2679) background_fetch plugin can use an initialized cont
[
https://issues.apache.org/jira/browse/TS-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-2679:
--
Priority: Critical (was: Major)
Fix Version/s: 5.0.0
Assignee: Leif Hedstrom
Summary: background_fetch plugin can use an initialized cont (was:
detect 206 range requests )
background_fetch plugin can use an initialized cont
---
Key: TS-2679
URL: https://issues.apache.org/jira/browse/TS-2679
Project: Traffic Server
Issue Type: Bug
Components: Cache, Plugins
Reporter: Faysal Banna
Assignee: Leif Hedstrom
Priority: Critical
Fix For: 5.0.0
Hi Guys
I Enabled background_fetch.so and tried to see how things go.
i got server restarting always
and also had these msgs in traffic.out
NOTE: Traffic Server received Sig 11: Segmentation fault
{code}
/usr/local/bin/traffic_server - STACK TRACE:
/lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x2b478c92acb0]
/usr/local/bin/traffic_server(TSContDestroy+0xd)[0x4b684d]
/usr/local/libexec/trafficserver/background_fetch.so(BGFetchData::~BGFetchData()+0x15a)[0x2b479700db2a]
/usr/local/libexec/trafficserver/background_fetch.so(+0x3490)[0x2b479700c490]
/usr/local/bin/traffic_server(HttpSM::state_api_callout(int,
void*)+0x100)[0x52fc50]
/usr/local/bin/traffic_server(HttpSM::state_api_callback(int,
void*)+0x8a)[0x5325fa]
/usr/local/bin/traffic_server(TSHttpTxnReenable+0x141)[0x4be971]
/usr/local/libexec/trafficserver/header_rewrite.so(+0x1574d)[0x2b4796df074d]
/usr/local/bin/traffic_server(HttpSM::state_api_callout(int,
void*)+0x100)[0x52fc50]
/usr/local/bin/traffic_server(HttpSM::state_read_server_response_header(int,
void*)+0x370)[0x5317a0]
/usr/local/bin/traffic_server(HttpSM::main_handler(int, void*)+0xd8)[0x530d78]
/usr/local/bin/traffic_server[0x6a0c10]
/usr/local/bin/traffic_server(NetHandler::mainNetEvent(int,
Event*)+0x1ed)[0x692add]
/usr/local/bin/traffic_server(EThread::process_event(Event*,
int)+0x91)[0x6c2b51]
/usr/local/bin/traffic_server(EThread::execute()+0x484)[0x6c3444]
/usr/local/bin/traffic_server[0x6c1dea]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x2b478c922e9a]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x2b478d6443fd]
{code}
much regards
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (TS-2679) background_fetch plugin can use an initialized cont
[
https://issues.apache.org/jira/browse/TS-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13955388#comment-13955388
]
ASF subversion and git services commented on TS-2679:
-
Commit 5d55b7562f78467db357d7c3dd05ff3fa8b4350b in trafficserver's branch
refs/heads/master from [~zwoop]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=5d55b75 ]
TS-2679 background_fetch plugin can use uninitialized cont pointer
background_fetch plugin can use an initialized cont
---
Key: TS-2679
URL: https://issues.apache.org/jira/browse/TS-2679
Project: Traffic Server
Issue Type: Bug
Components: Cache, Plugins
Reporter: Faysal Banna
Assignee: Leif Hedstrom
Priority: Critical
Fix For: 5.0.0
Hi Guys
I Enabled background_fetch.so and tried to see how things go.
i got server restarting always
and also had these msgs in traffic.out
NOTE: Traffic Server received Sig 11: Segmentation fault
{code}
/usr/local/bin/traffic_server - STACK TRACE:
/lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x2b478c92acb0]
/usr/local/bin/traffic_server(TSContDestroy+0xd)[0x4b684d]
/usr/local/libexec/trafficserver/background_fetch.so(BGFetchData::~BGFetchData()+0x15a)[0x2b479700db2a]
/usr/local/libexec/trafficserver/background_fetch.so(+0x3490)[0x2b479700c490]
/usr/local/bin/traffic_server(HttpSM::state_api_callout(int,
void*)+0x100)[0x52fc50]
/usr/local/bin/traffic_server(HttpSM::state_api_callback(int,
void*)+0x8a)[0x5325fa]
/usr/local/bin/traffic_server(TSHttpTxnReenable+0x141)[0x4be971]
/usr/local/libexec/trafficserver/header_rewrite.so(+0x1574d)[0x2b4796df074d]
/usr/local/bin/traffic_server(HttpSM::state_api_callout(int,
void*)+0x100)[0x52fc50]
/usr/local/bin/traffic_server(HttpSM::state_read_server_response_header(int,
void*)+0x370)[0x5317a0]
/usr/local/bin/traffic_server(HttpSM::main_handler(int, void*)+0xd8)[0x530d78]
/usr/local/bin/traffic_server[0x6a0c10]
/usr/local/bin/traffic_server(NetHandler::mainNetEvent(int,
Event*)+0x1ed)[0x692add]
/usr/local/bin/traffic_server(EThread::process_event(Event*,
int)+0x91)[0x6c2b51]
/usr/local/bin/traffic_server(EThread::execute()+0x484)[0x6c3444]
/usr/local/bin/traffic_server[0x6c1dea]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x2b478c922e9a]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x2b478d6443fd]
{code}
much regards
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (TS-2679) background_fetch plugin can use an initialized cont
[
https://issues.apache.org/jira/browse/TS-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom resolved TS-2679.
---
Resolution: Fixed
background_fetch plugin can use an initialized cont
---
Key: TS-2679
URL: https://issues.apache.org/jira/browse/TS-2679
Project: Traffic Server
Issue Type: Bug
Components: Cache, Plugins
Reporter: Faysal Banna
Assignee: Leif Hedstrom
Priority: Critical
Fix For: 5.0.0
Hi Guys
I Enabled background_fetch.so and tried to see how things go.
i got server restarting always
and also had these msgs in traffic.out
NOTE: Traffic Server received Sig 11: Segmentation fault
{code}
/usr/local/bin/traffic_server - STACK TRACE:
/lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x2b478c92acb0]
/usr/local/bin/traffic_server(TSContDestroy+0xd)[0x4b684d]
/usr/local/libexec/trafficserver/background_fetch.so(BGFetchData::~BGFetchData()+0x15a)[0x2b479700db2a]
/usr/local/libexec/trafficserver/background_fetch.so(+0x3490)[0x2b479700c490]
/usr/local/bin/traffic_server(HttpSM::state_api_callout(int,
void*)+0x100)[0x52fc50]
/usr/local/bin/traffic_server(HttpSM::state_api_callback(int,
void*)+0x8a)[0x5325fa]
/usr/local/bin/traffic_server(TSHttpTxnReenable+0x141)[0x4be971]
/usr/local/libexec/trafficserver/header_rewrite.so(+0x1574d)[0x2b4796df074d]
/usr/local/bin/traffic_server(HttpSM::state_api_callout(int,
void*)+0x100)[0x52fc50]
/usr/local/bin/traffic_server(HttpSM::state_read_server_response_header(int,
void*)+0x370)[0x5317a0]
/usr/local/bin/traffic_server(HttpSM::main_handler(int, void*)+0xd8)[0x530d78]
/usr/local/bin/traffic_server[0x6a0c10]
/usr/local/bin/traffic_server(NetHandler::mainNetEvent(int,
Event*)+0x1ed)[0x692add]
/usr/local/bin/traffic_server(EThread::process_event(Event*,
int)+0x91)[0x6c2b51]
/usr/local/bin/traffic_server(EThread::execute()+0x484)[0x6c3444]
/usr/local/bin/traffic_server[0x6c1dea]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x2b478c922e9a]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x2b478d6443fd]
{code}
much regards
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (TS-2679) background_fetch plugin can use an initialized cont
[
https://issues.apache.org/jira/browse/TS-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13955511#comment-13955511
]
ASF subversion and git services commented on TS-2679:
-
Commit 1578a5b35166ef40bcb5651812c5729c5c2314fb in trafficserver's branch
refs/heads/master from [~zwoop]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=1578a5b ]
TS-2679 Change asserts to debug asserts
background_fetch plugin can use an initialized cont
---
Key: TS-2679
URL: https://issues.apache.org/jira/browse/TS-2679
Project: Traffic Server
Issue Type: Bug
Components: Cache, Plugins
Reporter: Faysal Banna
Assignee: Leif Hedstrom
Priority: Critical
Fix For: 5.0.0
Hi Guys
I Enabled background_fetch.so and tried to see how things go.
i got server restarting always
and also had these msgs in traffic.out
NOTE: Traffic Server received Sig 11: Segmentation fault
{code}
/usr/local/bin/traffic_server - STACK TRACE:
/lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x2b478c92acb0]
/usr/local/bin/traffic_server(TSContDestroy+0xd)[0x4b684d]
/usr/local/libexec/trafficserver/background_fetch.so(BGFetchData::~BGFetchData()+0x15a)[0x2b479700db2a]
/usr/local/libexec/trafficserver/background_fetch.so(+0x3490)[0x2b479700c490]
/usr/local/bin/traffic_server(HttpSM::state_api_callout(int,
void*)+0x100)[0x52fc50]
/usr/local/bin/traffic_server(HttpSM::state_api_callback(int,
void*)+0x8a)[0x5325fa]
/usr/local/bin/traffic_server(TSHttpTxnReenable+0x141)[0x4be971]
/usr/local/libexec/trafficserver/header_rewrite.so(+0x1574d)[0x2b4796df074d]
/usr/local/bin/traffic_server(HttpSM::state_api_callout(int,
void*)+0x100)[0x52fc50]
/usr/local/bin/traffic_server(HttpSM::state_read_server_response_header(int,
void*)+0x370)[0x5317a0]
/usr/local/bin/traffic_server(HttpSM::main_handler(int, void*)+0xd8)[0x530d78]
/usr/local/bin/traffic_server[0x6a0c10]
/usr/local/bin/traffic_server(NetHandler::mainNetEvent(int,
Event*)+0x1ed)[0x692add]
/usr/local/bin/traffic_server(EThread::process_event(Event*,
int)+0x91)[0x6c2b51]
/usr/local/bin/traffic_server(EThread::execute()+0x484)[0x6c3444]
/usr/local/bin/traffic_server[0x6c1dea]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x2b478c922e9a]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x2b478d6443fd]
{code}
much regards
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Assigned] (TS-2682) Add per remap configuration / activation to background_fetch
[ https://issues.apache.org/jira/browse/TS-2682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom reassigned TS-2682: - Assignee: Leif Hedstrom Add per remap configuration / activation to background_fetch Key: TS-2682 URL: https://issues.apache.org/jira/browse/TS-2682 Project: Traffic Server Issue Type: New Feature Components: Plugins Reporter: Leif Hedstrom Assignee: Leif Hedstrom Fix For: 5.0.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (TS-2682) Add per remap configuration / activation to background_fetch
Leif Hedstrom created TS-2682: - Summary: Add per remap configuration / activation to background_fetch Key: TS-2682 URL: https://issues.apache.org/jira/browse/TS-2682 Project: Traffic Server Issue Type: New Feature Components: Plugins Reporter: Leif Hedstrom -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2682) Add per remap configuration / activation to background_fetch
[ https://issues.apache.org/jira/browse/TS-2682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2682: -- Fix Version/s: 5.0.0 Add per remap configuration / activation to background_fetch Key: TS-2682 URL: https://issues.apache.org/jira/browse/TS-2682 Project: Traffic Server Issue Type: New Feature Components: Plugins Reporter: Leif Hedstrom Assignee: Leif Hedstrom Fix For: 5.0.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (TS-2683) Add some control for which content to activate the background_fetch plugin
Leif Hedstrom created TS-2683: - Summary: Add some control for which content to activate the background_fetch plugin Key: TS-2683 URL: https://issues.apache.org/jira/browse/TS-2683 Project: Traffic Server Issue Type: New Feature Components: Plugins Reporter: Leif Hedstrom This would be both in global and per-remap configurations. Such as, only trigger background_fetch for certain content types, or also per remap rule. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (TS-2683) Add some control for which content to activate the background_fetch plugin
[ https://issues.apache.org/jira/browse/TS-2683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom reassigned TS-2683: - Assignee: Leif Hedstrom Add some control for which content to activate the background_fetch plugin -- Key: TS-2683 URL: https://issues.apache.org/jira/browse/TS-2683 Project: Traffic Server Issue Type: New Feature Components: Plugins Reporter: Leif Hedstrom Assignee: Leif Hedstrom Fix For: 5.0.0 This would be both in global and per-remap configurations. Such as, only trigger background_fetch for certain content types, or also per remap rule. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2683) Add some control for which content to activate the background_fetch plugin
[ https://issues.apache.org/jira/browse/TS-2683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2683: -- Fix Version/s: 5.0.0 Add some control for which content to activate the background_fetch plugin -- Key: TS-2683 URL: https://issues.apache.org/jira/browse/TS-2683 Project: Traffic Server Issue Type: New Feature Components: Plugins Reporter: Leif Hedstrom Fix For: 5.0.0 This would be both in global and per-remap configurations. Such as, only trigger background_fetch for certain content types, or also per remap rule. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (TS-2684) Add a log-file feature to background fetch plugin
Leif Hedstrom created TS-2684: - Summary: Add a log-file feature to background fetch plugin Key: TS-2684 URL: https://issues.apache.org/jira/browse/TS-2684 Project: Traffic Server Issue Type: New Feature Components: Plugins Reporter: Leif Hedstrom -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2684) Add a log-file feature to background fetch plugin
[ https://issues.apache.org/jira/browse/TS-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2684: -- Fix Version/s: 5.0.0 Add a log-file feature to background fetch plugin - Key: TS-2684 URL: https://issues.apache.org/jira/browse/TS-2684 Project: Traffic Server Issue Type: New Feature Components: Plugins Reporter: Leif Hedstrom Assignee: Leif Hedstrom Fix For: 5.0.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (TS-2684) Add a log-file feature to background fetch plugin
[ https://issues.apache.org/jira/browse/TS-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom reassigned TS-2684: - Assignee: Leif Hedstrom Add a log-file feature to background fetch plugin - Key: TS-2684 URL: https://issues.apache.org/jira/browse/TS-2684 Project: Traffic Server Issue Type: New Feature Components: Plugins Reporter: Leif Hedstrom Assignee: Leif Hedstrom Fix For: 5.0.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2683) Add some control for which content to activate the background_fetch plugin
[ https://issues.apache.org/jira/browse/TS-2683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2683: -- Fix Version/s: (was: 5.0.0) sometime Add some control for which content to activate the background_fetch plugin -- Key: TS-2683 URL: https://issues.apache.org/jira/browse/TS-2683 Project: Traffic Server Issue Type: New Feature Components: Plugins Reporter: Leif Hedstrom Fix For: sometime This would be both in global and per-remap configurations. Such as, only trigger background_fetch for certain content types. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2683) Add some control for which content to activate the background_fetch plugin
[ https://issues.apache.org/jira/browse/TS-2683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2683: -- Assignee: (was: Leif Hedstrom) Add some control for which content to activate the background_fetch plugin -- Key: TS-2683 URL: https://issues.apache.org/jira/browse/TS-2683 Project: Traffic Server Issue Type: New Feature Components: Plugins Reporter: Leif Hedstrom Fix For: sometime This would be both in global and per-remap configurations. Such as, only trigger background_fetch for certain content types, or also per remap rule. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2683) Add some control for which content to activate the background_fetch plugin
[ https://issues.apache.org/jira/browse/TS-2683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2683: -- Description: This would be both in global and per-remap configurations. Such as, only trigger background_fetch for certain content types. (was: This would be both in global and per-remap configurations. Such as, only trigger background_fetch for certain content types, or also per remap rule.) Add some control for which content to activate the background_fetch plugin -- Key: TS-2683 URL: https://issues.apache.org/jira/browse/TS-2683 Project: Traffic Server Issue Type: New Feature Components: Plugins Reporter: Leif Hedstrom Fix For: sometime This would be both in global and per-remap configurations. Such as, only trigger background_fetch for certain content types. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (TS-2685) TSHttpEventNameLookup can't lookup TSEvent values
James Peach created TS-2685:
---
Summary: TSHttpEventNameLookup can't lookup TSEvent values
Key: TS-2685
URL: https://issues.apache.org/jira/browse/TS-2685
Project: Traffic Server
Issue Type: Bug
Components: TS API
Reporter: James Peach
{{TSHttpEventNameLookup}} can't look up {{TSEvent}} values, see the
implementation of {{HttpDebugNames::get_event_name}}.
It would also be pretty neat if it formatted the event class if it didn't know
about the specific event, e.g. {{ICP_EVENT_EVENTS_START+22}}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (TS-2632) Range request will always lock object in cache, even thought it's rarely cacheable
[ https://issues.apache.org/jira/browse/TS-2632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13956011#comment-13956011 ] William Bardwell commented on TS-2632: -- It is not unusual for a server to return a full object to a range request if you are doing range requests on random stuff, especially on dynamically generated or assembled content. But those things are much less likely to be cached, although certainly not impossible. Obviously serving video, audio and PDFs that would normally get Range requests from a normal client/user-agent should support Range requests. But if you have something wacky trying to do partial object loads of everything, it could mess up your caching a bit with this change. Obviously if it is configurable, and configurable per-transaction then developers/deployers can decide which behavior they want. Range request will always lock object in cache, even thought it's rarely cacheable -- Key: TS-2632 URL: https://issues.apache.org/jira/browse/TS-2632 Project: Traffic Server Issue Type: Bug Components: Cache, HTTP Reporter: Leif Hedstrom Assignee: Leif Hedstrom Fix For: 5.0.0 Right now, if a client sends a Range: request, we still lock the URL in the cache, under the assumption that it will be written to. Since we don't support partial objects, in almost all cases, we'll not write the object and therefore release the object. I suggest we change this such that we never try to write lock a URL in the presence of a Range: header in the client request. This will allow other requests to go to origin faster, and better yet, it allows a request without a Range: header to properly lock the URL for writing. This turns out to be important for implementing e.g. background filling as a plugin. There is one use case where this might be useful; If the origin does not respond with a 206 (partial object), we can now cache the full object. However, this is a pretty rare case, and for someone to support this, all you have to do is to remove the Range: header on the request. I'm opening up this bug right now for discussion, if anyone have any concerns about this change, please let me know. It is an incompatible change, without configuration options, but that should be ok for the v5.0.0 release. -- This message was sent by Atlassian JIRA (v6.2#6252)
