[jira] [Commented] (TS-4264) ATS gzip problem!!!
[ https://issues.apache.org/jira/browse/TS-4264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15190693#comment-15190693 ] Otto van der Schaaf commented on TS-4264: - I don't know what is going on here. More information about the specifics of the problem would help! > ATS gzip problem!!! > --- > > Key: TS-4264 > URL: https://issues.apache.org/jira/browse/TS-4264 > Project: Traffic Server > Issue Type: Bug >Reporter: gehaijiang >Assignee: Otto van der Schaaf > Fix For: 6.2.0 > > > ATS 5.3.2 > use ATS gzip plugin probably due to page error code， Is there anything > wrong！！！ > gzip.config file： > $ cat /usr/local/ts/libexec/trafficserver/gzip.config > # Set some global options first > cache true > enabled true > remove-accept-encoding true > compressible-content-type text/html > compressible-content-type application/json > flush true -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-1250) Cache inspector does not seem to work properly
[ https://issues.apache.org/jira/browse/TS-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13269620#comment-13269620 ] Otto van der Schaaf commented on TS-1250: - also, i have experienced crashes when executing a regex lookup over a large cache, and crashes when looking up large urls. > Cache inspector does not seem to work properly > -- > > Key: TS-1250 > URL: https://issues.apache.org/jira/browse/TS-1250 > Project: Traffic Server > Issue Type: Bug > Components: HTTP >Reporter: Leif Hedstrom >Priority: Critical > Fix For: 3.1.4 > > > It seems the cache inspector is not functioning properly. Regex lookups > mostly works, but individual URLs does not. When it displays the error > results page from a lookup, it also tends to truncate the URL by one > character. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1262) allow the alternate selection api to force an alternate using a magick return value
Otto van der Schaaf created TS-1262: --- Summary: allow the alternate selection api to force an alternate using a magick return value Key: TS-1262 URL: https://issues.apache.org/jira/browse/TS-1262 Project: Traffic Server Issue Type: Improvement Reporter: Otto van der Schaaf Attachments: force alt selection.diff -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1262) allow the alternate selection api to force an alternate using a magick return value
[ https://issues.apache.org/jira/browse/TS-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otto van der Schaaf updated TS-1262: Attachment: force alt selection.diff > allow the alternate selection api to force an alternate using a magick return > value > --- > > Key: TS-1262 > URL: https://issues.apache.org/jira/browse/TS-1262 > Project: Traffic Server > Issue Type: Improvement >Reporter: Otto van der Schaaf > Attachments: force alt selection.diff > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1262) allow the alternate selection api to force an alternate using a magick return value
[ https://issues.apache.org/jira/browse/TS-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13276612#comment-13276612 ] Otto van der Schaaf commented on TS-1262: - a use case is picking an alternate based on a cookie value. this patch has been field tested. returning 999.0 from the select alternate hook will force the current alternate > allow the alternate selection api to force an alternate using a magick return > value > --- > > Key: TS-1262 > URL: https://issues.apache.org/jira/browse/TS-1262 > Project: Traffic Server > Issue Type: Improvement >Reporter: Otto van der Schaaf > Attachments: force alt selection.diff > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1262) allow the alternate selection api to force an alternate using a magick return value
[ https://issues.apache.org/jira/browse/TS-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280029#comment-13280029 ] Otto van der Schaaf commented on TS-1262: - that number was abritrary indeed, i agree that FLT_MAX would probably make more sense. > allow the alternate selection api to force an alternate using a magick return > value > --- > > Key: TS-1262 > URL: https://issues.apache.org/jira/browse/TS-1262 > Project: Traffic Server > Issue Type: Improvement >Reporter: Otto van der Schaaf >Assignee: Leif Hedstrom > Fix For: 3.1.4 > > Attachments: force alt selection.diff > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1119) fatal error when uploading gzip-transform plugin
[
https://issues.apache.org/jira/browse/TS-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280032#comment-13280032
]
Otto van der Schaaf commented on TS-1119:
-
the gzip plugin at
https://github.com/apache/trafficserver-plugins/tree/master/gzip already fixed
this
> fatal error when uploading gzip-transform plugin
>
>
> Key: TS-1119
> URL: https://issues.apache.org/jira/browse/TS-1119
> Project: Traffic Server
> Issue Type: Bug
> Components: Plugins
>Affects Versions: 3.0.2
>Reporter: angela asher
>Priority: Blocker
> Fix For: 3.3.0
>
> Attachments: gzip-transform.diff
>
>
> getting the following error on traffic.out when running the traffic server
> with gzip-transform plugin:
> [Feb 23 16:28:15.509] Server {47392853811680} DEBUG: (http) [13] calling
> plugin on hook TS_HTTP_READ_RESPONSE_HDR_HOOK at hook 0x35BBEE0
> FATAL: InkAPI.cc:3036: failed assert `sdk_sanity_check_null_ptr((void*)
> value_len_ptr) == TS_SUCCESS`
> /usr/local/bin/traffic_server - STACK TRACE:
> /usr/local/lib/libtsutil.so.3(ink_fatal_va+0x9d)[0x2b1a7ecca37d]
> /usr/local/lib/libtsutil.so.3(ink_fatal+0x88)[0x2b1a7ecca4d8]
> /usr/local/lib/libtsutil.so.3(_ink_assert+0x85)[0x2b1a7ecc8af5]
> /usr/local/bin/traffic_server(TSMimeHdrFieldValueStringGet+0x124)[0x4a9144]
> /usr/local/libexec/trafficserver/gzip-transform.so(+0x1bde)[0x2b1a8b3c7bde]
> /usr/local/libexec/trafficserver/gzip-transform.so(+0x27c4)[0x2b1a8b3c87c4]
> /usr/local/bin/traffic_server(_ZN6HttpSM17state_api_calloutEiPv+0x525)[0x52cfa5]
> /usr/local/bin/traffic_server(_ZN6HttpSM33state_read_server_response_headerEiPv+0x420)[0x52f1c0]
> /usr/local/bin/traffic_server(_ZN6HttpSM12main_handlerEiPv+0xe8)[0x530568]
> /usr/local/bin/traffic_server[0x681dcb]
> /usr/local/bin/traffic_server[0x6848f1]
> /usr/local/bin/traffic_server(_ZN10NetHandler12mainNetEventEiP5Event+0x2e2)[0x67d402]
> /usr/local/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0xb4)[0x6a9ce4]
> /usr/local/bin/traffic_server(_ZN7EThread7executeEv+0x4c3)[0x6aa673]
> /usr/local/bin/traffic_server(main+0x1128)[0x4c07e8]
> /lib64/libc.so.6(__libc_start_main+0xfd)[0x2b1a81092c5d]
> /usr/local/bin/traffic_server[0x47e0e9]
> [Feb 23 16:28:15.512] Manager {140400187066336} ERROR:
> [LocalManager::pollMgmtProcessServer] Server Process terminated due to Sig 6:
> Aborted
> [Feb 23 16:28:15.512] Manager {140400187066336} ERROR: (last system error 2:
> No such file or directory)
> [Feb 23 16:28:15.512] Manager {140400187066336} ERROR: [Alarms::signalAlarm]
> Server Process was reset
> [Feb 23 16:28:15.512] Manager {140400187066336} ERROR: (last system error 2:
> No such file or directory)
> [Feb 23 16:28:16.522] Manager {140400187066336} NOTE:
> [LocalManager::startProxy] Launching ts process
> [TrafficServer] using root directory '/usr/local'
> [Feb 23 16:28:16.527] Manager {140400187066336} NOTE:
> [LocalManager::pollMgmtProcessServer] New process connecting fd '11'
> [Feb 23 16:28:16.527] Manager {140400187066336} NOTE: [Alarms::signalAlarm]
> Server Process born
> [Feb 23 16:28:17.539] {47668265021920} STATUS: opened
> /usr/local/var/log/trafficserver/diags.log
> [Feb 23 16:28:17.539] {47668265021920} NOTE: updated diags config
> [Feb 23 16:28:17.541] Server {47668265021920} DEBUG: (http_aeua)
> [HttpConfig::init_aeua_filter] - Config:
> "/usr/local/etc/trafficserver/ae_ua.config"
> [Feb 23 16:28:17.541] Server {47668265021920} DEBUG: (http_aeua)
> [HttpConfig::init_aeua_filter] - Opening config
> "/usr/local/etc/trafficserver/ae_ua.config"
> [Feb 23 16:28:17.541] Server {47668265021920} DEBUG: (http_aeua)
> [HttpConfig::init_aeua_filter] - Added 0 REGEXP filters
> [Feb 23 16:28:17.541] Server {47668265021920} DEBUG: (http_aeua)
> [init_http_aeua_filter] - Total loaded 0 REGEXP for
> Accept-Enconding/User-Agent filtering
> [Feb 23 16:28:17.542] Server {47668265021920} NOTE: cache clustering disabled
> [Feb 23 16:28:17.543] Server {47668265021920} DEBUG: (dns) ink_dns_init:
> called with init_called = 0
> [Feb 23 16:28:17.546] Server {47668265021920} DEBUG: (dns)
> localhost=isk-vsrv227
> [Feb 23 16:28:17.546] Server {47668265021920} DEBUG: (dns) Round-robin
> nameservers = 0
> [Feb 23 16:28:17.547] Server {47668265021920} NOTE: cache clustering disabled
> [Feb 23 16:28:17.568] Server {47668265021920} NOTE: logging initialized[7],
> logging_mode = 3
> [Feb 23 16:28:17.569] Server {47668265021920} NOTE: loading plugin
> '/usr/local/libexec/trafficserver/gzip-transform.so'
> [Feb 23 16:28:17.570] Server {47668265021920} DEBUG: (http_init)
> proxy.config.http.redirection_enabled = 0
> [Feb 23 16:28:17.570] Server {47668265021920} DEBUG: (http_init)
> proxy.config.http.number_of_redirections = 1
> [Feb 23 16:28:17.570] Serv
[jira] [Commented] (TS-1262) allow the alternate selection api to force an alternate using a magick return value
[ https://issues.apache.org/jira/browse/TS-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280122#comment-13280122 ] Otto van der Schaaf commented on TS-1262: - done > allow the alternate selection api to force an alternate using a magick return > value > --- > > Key: TS-1262 > URL: https://issues.apache.org/jira/browse/TS-1262 > Project: Traffic Server > Issue Type: Improvement >Reporter: Otto van der Schaaf >Assignee: Leif Hedstrom > Fix For: 3.1.4 > > Attachments: force alt selection w flt_max.diff, force alt > selection.diff > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1262) allow the alternate selection api to force an alternate using a magick return value
[ https://issues.apache.org/jira/browse/TS-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otto van der Schaaf updated TS-1262: Attachment: force alt selection w flt_max.diff > allow the alternate selection api to force an alternate using a magick return > value > --- > > Key: TS-1262 > URL: https://issues.apache.org/jira/browse/TS-1262 > Project: Traffic Server > Issue Type: Improvement >Reporter: Otto van der Schaaf >Assignee: Leif Hedstrom > Fix For: 3.1.4 > > Attachments: force alt selection w flt_max.diff, force alt > selection.diff > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1261) enable keepalive/chunking when transforming from cache
[ https://issues.apache.org/jira/browse/TS-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otto van der Schaaf updated TS-1261: Fix Version/s: (was: 3.0.5) (was: 3.1.4) > enable keepalive/chunking when transforming from cache > -- > > Key: TS-1261 > URL: https://issues.apache.org/jira/browse/TS-1261 > Project: Traffic Server > Issue Type: Improvement > Components: HTTP >Affects Versions: 3.1.3 >Reporter: Otto van der Schaaf >Assignee: Otto van der Schaaf > Labels: patch > Attachments: cache_transform_chunking.diff > > > when transforming a document from cache, we will currently either close the > connection, or send a content length header (probably when the full response > is buffered). sending chunked responses could help lowering latencies and > memory requirements in some use cases. > the attached patch has only been lab tested, and has not got any production > mileage yet. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1250) Cache inspector does not seem to work properly
[ https://issues.apache.org/jira/browse/TS-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280217#comment-13280217 ] Otto van der Schaaf commented on TS-1250: - @James: taking a long time is fine, crashing is not (and hanging indefinitly isn't either. i have not experienced that tough). i don't think the user interface is capable of handling large amounts of documents either.. so maybe the regex lookup should just be dropped? Or it's results truncated? A timeout argument to the cache scan might be nice to have too. I have found purging using regexes usefull, but i stopped using that, as it caused crashes. One other thing, unrelated to this issue: when performing a search with multiple disks, it doesn't seem that trafficserver parallizes the search. I see massive i/o on one disk for a few seconds, followed by massive i/o on another disk. @Leif: That sounds awefully usefull. > Cache inspector does not seem to work properly > -- > > Key: TS-1250 > URL: https://issues.apache.org/jira/browse/TS-1250 > Project: Traffic Server > Issue Type: Bug > Components: HTTP >Reporter: Leif Hedstrom >Assignee: James Peach >Priority: Critical > Fix For: 3.1.4 > > > It seems the cache inspector is not functioning properly. Regex lookups > mostly works, but individual URLs does not. When it displays the error > results page from a lookup, it also tends to truncate the URL by one > character. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1004) transformation plugins cause connection close when content length is not known ahead
[ https://issues.apache.org/jira/browse/TS-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281436#comment-13281436 ] Otto van der Schaaf commented on TS-1004: - Hi Brian, Thanks, i'll have a look at this today, and see if i can figure out a proper way to address this. My initial thought is, that when the transfer encoding is chunked, the content-length header field should never be send no matter what. the specs say something like this about this ambiguous situation / violation (http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html) "Messages MUST NOT include both a Content-Length header field and a non-identity transfer-coding. If the message does include a non- identity transfer-coding, the Content-Length MUST be ignored." so, it seems we are lucky on this. but it still needs to be addressed indeed :) > transformation plugins cause connection close when content length is not > known ahead > > > Key: TS-1004 > URL: https://issues.apache.org/jira/browse/TS-1004 > Project: Traffic Server > Issue Type: Bug > Components: HTTP, Plugins >Affects Versions: 3.0.1 >Reporter: Otto van der Schaaf >Assignee: Otto van der Schaaf > Fix For: 3.1.1, 3.0.3 > > Attachments: chunk_transform_response.diff > > > whenever the null transform plugin (or gzip) is executed, ATS will force the > ua connection closed. > when the user agent supports it, sending a chunked response w/ keepalive > enabled would be preferred i guess > i'll add a patch for review. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1004) transformation plugins cause connection close when content length is not known ahead
[ https://issues.apache.org/jira/browse/TS-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otto van der Schaaf updated TS-1004: Attachment: no_cl_when_chunking.diff > transformation plugins cause connection close when content length is not > known ahead > > > Key: TS-1004 > URL: https://issues.apache.org/jira/browse/TS-1004 > Project: Traffic Server > Issue Type: Bug > Components: HTTP, Plugins >Affects Versions: 3.0.1 >Reporter: Otto van der Schaaf >Assignee: Otto van der Schaaf > Fix For: 3.1.1, 3.0.3 > > Attachments: chunk_transform_response.diff, no_cl_when_chunking.diff > > > whenever the null transform plugin (or gzip) is executed, ATS will force the > ua connection closed. > when the user agent supports it, sending a chunked response w/ keepalive > enabled would be preferred i guess > i'll add a patch for review. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1004) transformation plugins cause connection close when content length is not known ahead
[ https://issues.apache.org/jira/browse/TS-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281457#comment-13281457 ] Otto van der Schaaf commented on TS-1004: - The new patch applies to trunk. I think it fixes the problems; Brian, are you able to confirm that? > transformation plugins cause connection close when content length is not > known ahead > > > Key: TS-1004 > URL: https://issues.apache.org/jira/browse/TS-1004 > Project: Traffic Server > Issue Type: Bug > Components: HTTP, Plugins >Affects Versions: 3.0.1 >Reporter: Otto van der Schaaf >Assignee: Otto van der Schaaf > Fix For: 3.1.1, 3.0.3 > > Attachments: chunk_transform_response.diff, no_cl_when_chunking.diff > > > whenever the null transform plugin (or gzip) is executed, ATS will force the > ua connection closed. > when the user agent supports it, sending a chunked response w/ keepalive > enabled would be preferred i guess > i'll add a patch for review. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1004) transformation plugins cause connection close when content length is not known ahead
[ https://issues.apache.org/jira/browse/TS-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13282493#comment-13282493 ] Otto van der Schaaf commented on TS-1004: - Hi Brianm, great work, i think this fixes similar issues I encountered while testing https://issues.apache.org/jira/browse/TS-1261 too. I do find the current interaction between handle_response_keep_alive_headers and handle_content_length_header a bit ... tricky, but that may need a jira ticket on its own. :) > transformation plugins cause connection close when content length is not > known ahead > > > Key: TS-1004 > URL: https://issues.apache.org/jira/browse/TS-1004 > Project: Traffic Server > Issue Type: Bug > Components: HTTP, Plugins >Affects Versions: 3.0.1 >Reporter: Otto van der Schaaf >Assignee: Otto van der Schaaf > Fix For: 3.1.1, 3.0.3 > > Attachments: chunk_transform_response.diff, no_cl_when_chunking.diff, > no_cl_when_chunking_v2.patch > > > whenever the null transform plugin (or gzip) is executed, ATS will force the > ua connection closed. > when the user agent supports it, sending a chunked response w/ keepalive > enabled would be preferred i guess > i'll add a patch for review. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1261) enable keepalive/chunking when transforming from cache
[ https://issues.apache.org/jira/browse/TS-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13292506#comment-13292506 ] Otto van der Schaaf commented on TS-1261: - yes it is. me and Brian performed some work on content-length header handling, which fixed problems for https://issues.apache.org/jira/browse/TS-1004, and probably this patch as well. I think those where the changes you remember. > enable keepalive/chunking when transforming from cache > -- > > Key: TS-1261 > URL: https://issues.apache.org/jira/browse/TS-1261 > Project: Traffic Server > Issue Type: Improvement > Components: HTTP >Affects Versions: 3.1.3 >Reporter: Otto van der Schaaf >Assignee: Otto van der Schaaf > Labels: patch > Attachments: cache_transform_chunking.diff > > > when transforming a document from cache, we will currently either close the > connection, or send a content length header (probably when the full response > is buffered). sending chunked responses could help lowering latencies and > memory requirements in some use cases. > the attached patch has only been lab tested, and has not got any production > mileage yet. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1261) enable keepalive/chunking when transforming from cache
[ https://issues.apache.org/jira/browse/TS-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13292577#comment-13292577 ] Otto van der Schaaf commented on TS-1261: - No, this should not be closed, this is still applicable > enable keepalive/chunking when transforming from cache > -- > > Key: TS-1261 > URL: https://issues.apache.org/jira/browse/TS-1261 > Project: Traffic Server > Issue Type: Improvement > Components: HTTP >Affects Versions: 3.1.3 >Reporter: Otto van der Schaaf >Assignee: Otto van der Schaaf > Labels: patch > Attachments: cache_transform_chunking.diff > > > when transforming a document from cache, we will currently either close the > connection, or send a content length header (probably when the full response > is buffered). sending chunked responses could help lowering latencies and > memory requirements in some use cases. > the attached patch has only been lab tested, and has not got any production > mileage yet. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1261) enable keepalive/chunking when transforming from cache
[ https://issues.apache.org/jira/browse/TS-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294182#comment-13294182 ] Otto van der Schaaf commented on TS-1261: - i think this is ok, and doesnt need work. > enable keepalive/chunking when transforming from cache > -- > > Key: TS-1261 > URL: https://issues.apache.org/jira/browse/TS-1261 > Project: Traffic Server > Issue Type: Improvement > Components: HTTP >Affects Versions: 3.1.3 >Reporter: Otto van der Schaaf >Assignee: Otto van der Schaaf > Labels: patch > Fix For: 3.3.0 > > Attachments: cache_transform_chunking.diff > > > when transforming a document from cache, we will currently either close the > connection, or send a content length header (probably when the full response > is buffered). sending chunked responses could help lowering latencies and > memory requirements in some use cases. > the attached patch has only been lab tested, and has not got any production > mileage yet. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1341) Calling TSCacheHookAdd from a plugin compiles, but results in "undefined object"
Otto van der Schaaf created TS-1341:
---
Summary: Calling TSCacheHookAdd from a plugin compiles, but
results in "undefined object"
Key: TS-1341
URL: https://issues.apache.org/jira/browse/TS-1341
Project: Traffic Server
Issue Type: Bug
Components: Plugins
Affects Versions: 3.3.0
Reporter: Otto van der Schaaf
Calling TSCacheHookAdd from a plugin compiles, but results in an "undefined
object" error when starting traffic server
[Jul 10 14:22:18.459] Server {0x7ffd30759740} ERROR: unable to load
'/usr/local/libexec/trafficserver/cache_control.so':
/usr/local/libexec/trafficserver/cache_control.so: undefined symbol:
TSCacheHookAdd
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1341) Calling TSCacheHookAdd from a plugin compiles, but results in "undefined object"
[
https://issues.apache.org/jira/browse/TS-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13410756#comment-13410756
]
Otto van der Schaaf commented on TS-1341:
-
well that's a bummer :( no replacement for this api?
> Calling TSCacheHookAdd from a plugin compiles, but results in "undefined
> object"
>
>
> Key: TS-1341
> URL: https://issues.apache.org/jira/browse/TS-1341
> Project: Traffic Server
> Issue Type: Bug
> Components: Plugins
>Affects Versions: 3.3.0
>Reporter: Otto van der Schaaf
>Assignee: Leif Hedstrom
> Fix For: 3.3.0
>
>
> Calling TSCacheHookAdd from a plugin compiles, but results in an "undefined
> object" error when starting traffic server
> [Jul 10 14:22:18.459] Server {0x7ffd30759740} ERROR: unable to load
> '/usr/local/libexec/trafficserver/cache_control.so':
> /usr/local/libexec/trafficserver/cache_control.so: undefined symbol:
> TSCacheHookAdd
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1413) TSHttpTxnOutgoingAddrSet forward declaration still does not match implementation?
[ https://issues.apache.org/jira/browse/TS-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otto van der Schaaf updated TS-1413: Attachment: TSHttpTxnOutgoingAddrSet.diff this patch removes the said parameter (socklen_t addrlen), making the forward declaration match the implementation again > TSHttpTxnOutgoingAddrSet forward declaration still does not match > implementation? > - > > Key: TS-1413 > URL: https://issues.apache.org/jira/browse/TS-1413 > Project: Traffic Server > Issue Type: Bug > Components: TS API >Reporter: Otto van der Schaaf > Attachments: TSHttpTxnOutgoingAddrSet.diff > > > It seems TSHttpTxnOutgoingAddrSet in InkAPI.cc contains a parameter that > isn't needed as far as i can tell ( socklen_t addrlen). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1413) TSHttpTxnOutgoingAddrSet forward declaration still does not match implementation?
Otto van der Schaaf created TS-1413: --- Summary: TSHttpTxnOutgoingAddrSet forward declaration still does not match implementation? Key: TS-1413 URL: https://issues.apache.org/jira/browse/TS-1413 Project: Traffic Server Issue Type: Bug Components: TS API Reporter: Otto van der Schaaf Attachments: TSHttpTxnOutgoingAddrSet.diff It seems TSHttpTxnOutgoingAddrSet in InkAPI.cc contains a parameter that isn't needed as far as i can tell ( socklen_t addrlen). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1414) make the gzip plugin actually support gzip, next to deflate
Otto van der Schaaf created TS-1414: --- Summary: make the gzip plugin actually support gzip, next to deflate Key: TS-1414 URL: https://issues.apache.org/jira/browse/TS-1414 Project: Traffic Server Issue Type: Improvement Components: Plugins Reporter: Otto van der Schaaf -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1414) make the gzip plugin actually support gzip, next to deflate
[ https://issues.apache.org/jira/browse/TS-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otto van der Schaaf updated TS-1414: Attachment: gzip_support.diff > make the gzip plugin actually support gzip, next to deflate > --- > > Key: TS-1414 > URL: https://issues.apache.org/jira/browse/TS-1414 > Project: Traffic Server > Issue Type: Improvement > Components: Plugins >Reporter: Otto van der Schaaf > Attachments: gzip_support.diff > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1414) make the gzip plugin actually support gzip, next to deflate
[ https://issues.apache.org/jira/browse/TS-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439088#comment-13439088 ] Otto van der Schaaf commented on TS-1414: - also cleans superfluous comments and debug logging, and fixes a valgrind error. the provided patch makes the plugin support gzip and deflate compression. deflate will be preferred when both are accepted by the user agent. > make the gzip plugin actually support gzip, next to deflate > --- > > Key: TS-1414 > URL: https://issues.apache.org/jira/browse/TS-1414 > Project: Traffic Server > Issue Type: Improvement > Components: Plugins >Reporter: Otto van der Schaaf > Attachments: gzip_support.diff > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1414) make the gzip plugin actually support gzip, next to deflate
[ https://issues.apache.org/jira/browse/TS-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otto van der Schaaf updated TS-1414: Attachment: gzip_support_and_more.diff this patch includes all changes from the previously attached patch, and the following improvements and fixed: - added an option to remove accept encoding from the origin request - for offloading - for when responses need to be parsed, and the compression/decompression that would ensue would just be wasting using cpu cycles - added transforming uncompressed documents from cache - fix: do not alter weak etags - added an option to specify if an alternate should be saved for the compressed document - now prefers gzip over raw deflate. maybe raw deflate should just be dropped (http://www.vervestudios.co/projects/compression-tests/results) - most of the above is now controlled through defines - next up will be configuration and a some cleanup/refactoring > make the gzip plugin actually support gzip, next to deflate > --- > > Key: TS-1414 > URL: https://issues.apache.org/jira/browse/TS-1414 > Project: Traffic Server > Issue Type: Improvement > Components: Plugins >Reporter: Otto van der Schaaf > Attachments: gzip_support_and_more.diff, gzip_support.diff > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (TS-1414) make the gzip plugin actually support gzip, next to deflate
[ https://issues.apache.org/jira/browse/TS-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439783#comment-13439783 ] Otto van der Schaaf edited comment on TS-1414 at 8/23/12 6:32 AM: -- this patch includes all changes from the previously attached patch, and the following improvements and fixes: - added an option to remove accept encoding from the origin request (for offloading/for when responses need to be parsed, and the compression/decompression that would ensue would just be wasting using cpu cycles) - added transforming uncompressed documents from cache - fix: do not alter weak etags - added an option to specify if an alternate should be saved for the compressed document - now prefers gzip over raw deflate. maybe raw deflate should just be dropped (http://www.vervestudios.co/projects/compression-tests/results) - most of the above is now controlled through defines - next up will be configuration and a some cleanup/refactoring was (Author: oschaaf): this patch includes all changes from the previously attached patch, and the following improvements and fixed: - added an option to remove accept encoding from the origin request (for offloading/for when responses need to be parsed, and the compression/decompression that would ensue would just be wasting using cpu cycles) - added transforming uncompressed documents from cache - fix: do not alter weak etags - added an option to specify if an alternate should be saved for the compressed document - now prefers gzip over raw deflate. maybe raw deflate should just be dropped (http://www.vervestudios.co/projects/compression-tests/results) - most of the above is now controlled through defines - next up will be configuration and a some cleanup/refactoring > make the gzip plugin actually support gzip, next to deflate > --- > > Key: TS-1414 > URL: https://issues.apache.org/jira/browse/TS-1414 > Project: Traffic Server > Issue Type: Improvement > Components: Plugins >Reporter: Otto van der Schaaf > Attachments: gzip_support_and_more.diff, gzip_support.diff > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (TS-1414) make the gzip plugin actually support gzip, next to deflate
[ https://issues.apache.org/jira/browse/TS-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439783#comment-13439783 ] Otto van der Schaaf edited comment on TS-1414 at 8/23/12 6:31 AM: -- this patch includes all changes from the previously attached patch, and the following improvements and fixed: - added an option to remove accept encoding from the origin request (for offloading/for when responses need to be parsed, and the compression/decompression that would ensue would just be wasting using cpu cycles) - added transforming uncompressed documents from cache - fix: do not alter weak etags - added an option to specify if an alternate should be saved for the compressed document - now prefers gzip over raw deflate. maybe raw deflate should just be dropped (http://www.vervestudios.co/projects/compression-tests/results) - most of the above is now controlled through defines - next up will be configuration and a some cleanup/refactoring was (Author: oschaaf): this patch includes all changes from the previously attached patch, and the following improvements and fixed: - added an option to remove accept encoding from the origin request - for offloading - for when responses need to be parsed, and the compression/decompression that would ensue would just be wasting using cpu cycles - added transforming uncompressed documents from cache - fix: do not alter weak etags - added an option to specify if an alternate should be saved for the compressed document - now prefers gzip over raw deflate. maybe raw deflate should just be dropped (http://www.vervestudios.co/projects/compression-tests/results) - most of the above is now controlled through defines - next up will be configuration and a some cleanup/refactoring > make the gzip plugin actually support gzip, next to deflate > --- > > Key: TS-1414 > URL: https://issues.apache.org/jira/browse/TS-1414 > Project: Traffic Server > Issue Type: Improvement > Components: Plugins >Reporter: Otto van der Schaaf > Attachments: gzip_support_and_more.diff, gzip_support.diff > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1431) the gzip needs cleanup and refactoring
Otto van der Schaaf created TS-1431: --- Summary: the gzip needs cleanup and refactoring Key: TS-1431 URL: https://issues.apache.org/jira/browse/TS-1431 Project: Traffic Server Issue Type: Improvement Components: Plugins Reporter: Otto van der Schaaf Assignee: Otto van der Schaaf Fix For: 3.3.1 -- 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-1431) the gzip plugin needs cleanup and refactoring
[ https://issues.apache.org/jira/browse/TS-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otto van der Schaaf updated TS-1431: Summary: the gzip plugin needs cleanup and refactoring (was: the gzip needs cleanup and refactoring) > the gzip plugin needs cleanup and refactoring > - > > Key: TS-1431 > URL: https://issues.apache.org/jira/browse/TS-1431 > Project: Traffic Server > Issue Type: Improvement > Components: Plugins >Reporter: Otto van der Schaaf >Assignee: Otto van der Schaaf > Fix For: 3.3.1 > > -- 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-1431) the gzip plugin needs cleanup and refactoring
[ https://issues.apache.org/jira/browse/TS-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otto van der Schaaf resolved TS-1431. - Resolution: Fixed committed in d59c7b9b17251eae4a4a29020c079875a9da0c61 > the gzip plugin needs cleanup and refactoring > - > > Key: TS-1431 > URL: https://issues.apache.org/jira/browse/TS-1431 > Project: Traffic Server > Issue Type: Improvement > Components: Plugins >Reporter: Otto van der Schaaf >Assignee: Otto van der Schaaf > Fix For: 3.3.1 > > -- 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-1180) gzip plugin needs to be configurable for certain file/mime types
[ https://issues.apache.org/jira/browse/TS-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otto van der Schaaf resolved TS-1180. - Resolution: Fixed committed in 86550f2988ffbf9c434bdbc8e1ca546526dd86d1 > gzip plugin needs to be configurable for certain file/mime types > > > Key: TS-1180 > URL: https://issues.apache.org/jira/browse/TS-1180 > Project: Traffic Server > Issue Type: New Feature > Components: Plugins >Reporter: Igor Galić >Assignee: Otto van der Schaaf > Fix For: 3.3.1 > > > Most browsers don't take it very well when JavaScript is compressed - or > rather, when AJAX requests are. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1007) SSN Close called before TXN Close
[ https://issues.apache.org/jira/browse/TS-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13446899#comment-13446899 ] Otto van der Schaaf commented on TS-1007: - Could it be that this behaviour is by design? That ordering of these events is indeterminate? Maybe a transaction sometimes has to live longer then the session (one use case i can think of is finishing a background fill) > SSN Close called before TXN Close > - > > Key: TS-1007 > URL: https://issues.apache.org/jira/browse/TS-1007 > Project: Traffic Server > Issue Type: Bug > Components: TS API >Affects Versions: 3.0.1 >Reporter: Nick Kew >Priority: Critical > Fix For: 3.3.1 > > > Where a plugin implements both SSN_CLOSE_HOOK and TXN_CLOSE_HOOK, the > SSN_CLOSE_HOOK is called first of the two. This messes up normal cleanups! > Details: > Register a SSN_START event globally > In the SSN START, add a TXN_START and a SSN_CLOSE > In the TXN START, add a TXN_CLOSE > Stepping through, I see the order of events actually called, for the simple > case of a one-off HTTP request with no keepalive: > SSN_START > TXN_START > SSN_END > TXN_END > Whoops, SSN_END cleaned up the SSN context, leaving dangling pointers in the > TXN! -- This message 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-1441) fix possible null reference to configuration in gzip plugin
Otto van der Schaaf created TS-1441: --- Summary: fix possible null reference to configuration in gzip plugin Key: TS-1441 URL: https://issues.apache.org/jira/browse/TS-1441 Project: Traffic Server Issue Type: Bug Components: Plugins Reporter: Otto van der Schaaf Assignee: Otto van der Schaaf Fix For: 3.3.1 -- 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-1441) fix possible null reference to configuration in gzip plugin
[ https://issues.apache.org/jira/browse/TS-1441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otto van der Schaaf updated TS-1441: Attachment: gzip (3).diff > fix possible null reference to configuration in gzip plugin > --- > > Key: TS-1441 > URL: https://issues.apache.org/jira/browse/TS-1441 > Project: Traffic Server > Issue Type: Bug > Components: Plugins >Reporter: Otto van der Schaaf >Assignee: Otto van der Schaaf > Fix For: 3.3.1 > > Attachments: gzip (3).diff > > -- 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-1442) assertion fails when there is a transformation plugin active and lots of disconnects are done
[ https://issues.apache.org/jira/browse/TS-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otto van der Schaaf updated TS-1442: Description: stack trace: [Switching to Thread 0x73d7f700 (LWP 25497)] 0x75a02445 in __GI_raise (sig=) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 64 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 0x75a02445 in __GI_raise (sig=) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #1 0x75a05bab in __GI_abort () at abort.c:91 #2 0x77bad734 in ink_die_die_die (retval=1) at ink_error.cc:43 #3 0x77bad815 in ink_fatal_va(int, const char *, typedef __va_list_tag __va_list_tag *) (return_code=1, message_format=0x77bc99e0 "%s:%d: failed assert `%s`", ap=0x73d7a848) at ink_error.cc:65 #4 0x77bad8ce in ink_fatal (return_code=1, message_format=0x77bc99e0 "%s:%d: failed assert `%s`") at ink_error.cc:73 #5 0x77bac71c in _ink_assert (expression=0x70f490 "server_entry->vc == c->producer->vc", file=0x70dae5 "HttpSM.cc", line=2976) at ink_assert.cc:38 #6 0x0056e12c in HttpSM::tunnel_handler_ua (this=0x7fffe2ec6eb0, event=104, c=0x7fffe2ec8b58) at HttpSM.cc:2976 #7 0x005b3a99 in HttpTunnel::consumer_handler (this=0x7fffe2ec8a38, event=104, c=0x7fffe2ec8b58) at HttpTunnel.cc:1243 #8 0x005b41f3 in HttpTunnel::main_handler (this=0x7fffe2ec8a38, event=104, data=0x7fffdc0159c0) at HttpTunnel.cc:1467 #9 0x004e36ee in Continuation::handleEvent (this=0x7fffe2ec8a38, event=104, data=0x7fffdc0159c0) at ../iocore/eventsystem/I_Continuation.h:146 #10 0x00566d1e in HttpSM::state_watch_for_client_abort (this=0x7fffe2ec6eb0, event=104, data=0x7fffdc015950) at HttpSM.cc:873 #11 0x0056c296 in HttpSM::main_handler (this=0x7fffe2ec6eb0, event=104, data=0x7fffdc015950) at HttpSM.cc:2444 #12 0x004e36ee in Continuation::handleEvent (this=0x7fffe2ec6eb0, event=104, data=0x7fffdc015950) at ../iocore/eventsystem/I_Continuation.h:146 #13 0x006c17f4 in read_signal_and_update (event=104, vc=0x7fffdc015840) at UnixNetVConnection.cc:138 #14 0x006c19a6 in read_signal_done (event=104, nh=0x741871e8, vc=0x7fffdc015840) at UnixNetVConnection.cc:168 #15 0x006c1f1e in read_from_net (nh=0x741871e8, vc=0x7fffdc015840, thread=0x74184010) at UnixNetVConnection.cc:291 #16 0x006c3d27 in UnixNetVConnection::net_read_io (this=0x7fffdc015840, nh=0x741871e8, lthread=0x74184010) at UnixNetVConnection.cc:816 #17 0x006be5e9 in NetHandler::mainNetEvent (this=0x741871e8, event=5, e=0x10ac160) at UnixNet.cc:372 #18 0x004e36ee in Continuation::handleEvent (this=0x741871e8, event=5, data=0x10ac160) at ../iocore/eventsystem/I_Continuation.h:146 #19 0x006e427a in EThread::process_event (this=0x74184010, e=0x10ac160, calling_code=5) at UnixEThread.cc:142 #20 0x006e481c in EThread::execute (this=0x74184010) at UnixEThread.cc:264 #21 0x006e34c2 in spawn_thread_internal (a=0x10a6560) at Thread.cc:88 #22 0x7797be9a in start_thread (arg=0x73d7f700) at pthread_create.c:308 #23 0x75abe4bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #24 0x in ?? () > assertion fails when there is a transformation plugin active and lots of > disconnects are done > - > > Key: TS-1442 > URL: https://issues.apache.org/jira/browse/TS-1442 > Project: Traffic Server > Issue Type: Bug >Affects Versions: 3.3.1 >Reporter: Otto van der Schaaf >Priority: Critical > > stack trace: > [Switching to Thread 0x73d7f700 (LWP 25497)] > 0x75a02445 in __GI_raise (sig=) at > ../nptl/sysdeps/unix/sysv/linux/raise.c:64 > 64 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory. > (gdb) bt > #0 0x75a02445 in __GI_raise (sig=) at > ../nptl/sysdeps/unix/sysv/linux/raise.c:64 > #1 0x75a05bab in __GI_abort () at abort.c:91 > #2 0x77bad734 in ink_die_die_die (retval=1) at ink_error.cc:43 > #3 0x77bad815 in ink_fatal_va(int, const char *, typedef > __va_list_tag __va_list_tag *) (return_code=1, > message_format=0x77bc99e0 "%s:%d: failed assert `%s`", > ap=0x73d7a848) at ink_error.cc:65 > #4 0x77bad8ce in ink_fatal (return_code=1, > message_format=0x77bc99e0 "%s:%d: failed assert `%s`") at ink_error.cc:73 > #5 0x77bac71c in _ink_assert (expression=0x70f490 "server_entry->vc > == c->producer->vc", file=0x70dae5 "HttpSM.cc", > line=2976) at ink_assert.cc:38 > #6 0x0056e12c in HttpSM::tunnel_handler_ua (this=0x7fffe2ec6eb0, > event=104, c=0x7fffe2ec8b58) at HttpSM.cc:
[jira] [Created] (TS-1442) assertion fails when there is a transformation plugin active and lots of disconnects are done
Otto van der Schaaf created TS-1442: --- Summary: assertion fails when there is a transformation plugin active and lots of disconnects are done Key: TS-1442 URL: https://issues.apache.org/jira/browse/TS-1442 Project: Traffic Server Issue Type: Bug Affects Versions: 3.3.1 Reporter: Otto van der Schaaf Priority: Critical -- 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] [Closed] (TS-1442) assertion fails when there is a transformation plugin active and lots of disconnects are done
[ https://issues.apache.org/jira/browse/TS-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otto van der Schaaf closed TS-1442. --- Resolution: Invalid sorry, closing this. i cannot reproduce this anymore. i think i had an incorrect build. > assertion fails when there is a transformation plugin active and lots of > disconnects are done > - > > Key: TS-1442 > URL: https://issues.apache.org/jira/browse/TS-1442 > Project: Traffic Server > Issue Type: Bug >Affects Versions: 3.3.1 >Reporter: Otto van der Schaaf >Priority: Critical > > stack trace: > [Switching to Thread 0x73d7f700 (LWP 25497)] > 0x75a02445 in __GI_raise (sig=) at > ../nptl/sysdeps/unix/sysv/linux/raise.c:64 > 64 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory. > (gdb) bt > #0 0x75a02445 in __GI_raise (sig=) at > ../nptl/sysdeps/unix/sysv/linux/raise.c:64 > #1 0x75a05bab in __GI_abort () at abort.c:91 > #2 0x77bad734 in ink_die_die_die (retval=1) at ink_error.cc:43 > #3 0x77bad815 in ink_fatal_va(int, const char *, typedef > __va_list_tag __va_list_tag *) (return_code=1, > message_format=0x77bc99e0 "%s:%d: failed assert `%s`", > ap=0x73d7a848) at ink_error.cc:65 > #4 0x77bad8ce in ink_fatal (return_code=1, > message_format=0x77bc99e0 "%s:%d: failed assert `%s`") at ink_error.cc:73 > #5 0x77bac71c in _ink_assert (expression=0x70f490 "server_entry->vc > == c->producer->vc", file=0x70dae5 "HttpSM.cc", > line=2976) at ink_assert.cc:38 > #6 0x0056e12c in HttpSM::tunnel_handler_ua (this=0x7fffe2ec6eb0, > event=104, c=0x7fffe2ec8b58) at HttpSM.cc:2976 > #7 0x005b3a99 in HttpTunnel::consumer_handler (this=0x7fffe2ec8a38, > event=104, c=0x7fffe2ec8b58) at HttpTunnel.cc:1243 > #8 0x005b41f3 in HttpTunnel::main_handler (this=0x7fffe2ec8a38, > event=104, data=0x7fffdc0159c0) at HttpTunnel.cc:1467 > #9 0x004e36ee in Continuation::handleEvent (this=0x7fffe2ec8a38, > event=104, data=0x7fffdc0159c0) > at ../iocore/eventsystem/I_Continuation.h:146 > #10 0x00566d1e in HttpSM::state_watch_for_client_abort > (this=0x7fffe2ec6eb0, event=104, data=0x7fffdc015950) at HttpSM.cc:873 > #11 0x0056c296 in HttpSM::main_handler (this=0x7fffe2ec6eb0, > event=104, data=0x7fffdc015950) at HttpSM.cc:2444 > #12 0x004e36ee in Continuation::handleEvent (this=0x7fffe2ec6eb0, > event=104, data=0x7fffdc015950) > at ../iocore/eventsystem/I_Continuation.h:146 > #13 0x006c17f4 in read_signal_and_update (event=104, > vc=0x7fffdc015840) at UnixNetVConnection.cc:138 > #14 0x006c19a6 in read_signal_done (event=104, nh=0x741871e8, > vc=0x7fffdc015840) at UnixNetVConnection.cc:168 > #15 0x006c1f1e in read_from_net (nh=0x741871e8, > vc=0x7fffdc015840, thread=0x74184010) at UnixNetVConnection.cc:291 > #16 0x006c3d27 in UnixNetVConnection::net_read_io > (this=0x7fffdc015840, nh=0x741871e8, lthread=0x74184010) > at UnixNetVConnection.cc:816 > #17 0x006be5e9 in NetHandler::mainNetEvent (this=0x741871e8, > event=5, e=0x10ac160) at UnixNet.cc:372 > #18 0x004e36ee in Continuation::handleEvent (this=0x741871e8, > event=5, data=0x10ac160) > at ../iocore/eventsystem/I_Continuation.h:146 > #19 0x006e427a in EThread::process_event (this=0x74184010, > e=0x10ac160, calling_code=5) at UnixEThread.cc:142 > #20 0x006e481c in EThread::execute (this=0x74184010) at > UnixEThread.cc:264 > #21 0x006e34c2 in spawn_thread_internal (a=0x10a6560) at Thread.cc:88 > #22 0x7797be9a in start_thread (arg=0x73d7f700) at > pthread_create.c:308 > #23 0x75abe4bd in clone () at > ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 > #24 0x in ?? () -- 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-1443) add enable-gzip option for gzip plugin
[
https://issues.apache.org/jira/browse/TS-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13451410#comment-13451410
]
Otto van der Schaaf commented on TS-1443:
-
I renamed the option from "enable_gzip" from the patch to just "enabled", since
this is about enabling compression instead of enabling gzip specifically.
> add enable-gzip option for gzip plugin
> --
>
> Key: TS-1443
> URL: https://issues.apache.org/jira/browse/TS-1443
> Project: Traffic Server
> Issue Type: Improvement
> Components: Configuration, Plugins
>Reporter: Conan Wang
>Assignee: Otto van der Schaaf
> Fix For: 3.3.1
>
> Attachments: gzip_enable_option.patch
>
>
> gzip plugin is global enabled. adding 'enable-gzip' option allows us to
> enable/disable the plugin for certain host.
> {code}
> #global config (here we disable gzip)
> enable-gzip false
> remove-accept-encoding false
> cache false
> compressible-content-type text/*
> disallow /notthis/*.js
> #override the global configuration for a host.⋅
> #www.foo.nl does NOT inherit anything
> [www.foo.nl]
> # (enable gzip in this host)
> enable-gzip true
> remove-accept-encoding true
> cache true
> compressible-content-type text/*
> compressible-content-type application/json
> compressible-content-type application/x-javascript
> {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-1445) Gzip plugin appends 2 adlers when using gzip compression
Otto van der Schaaf created TS-1445: --- Summary: Gzip plugin appends 2 adlers when using gzip compression Key: TS-1445 URL: https://issues.apache.org/jira/browse/TS-1445 Project: Traffic Server Issue Type: Bug Components: Plugins Reporter: Otto van der Schaaf Assignee: Otto van der Schaaf Fix For: 3.3.1 When compressing to the gzip format, the plugin appends the adler two times. -- 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-1445) Gzip plugin appends 2 adlers when using gzip compression
[ https://issues.apache.org/jira/browse/TS-1445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otto van der Schaaf resolved TS-1445. - Resolution: Fixed comitted in 18baa9efe6ecdc1b387b341b01fe35b43eee6fe0 > Gzip plugin appends 2 adlers when using gzip compression > > > Key: TS-1445 > URL: https://issues.apache.org/jira/browse/TS-1445 > Project: Traffic Server > Issue Type: Bug > Components: Plugins >Reporter: Otto van der Schaaf >Assignee: Otto van der Schaaf > Fix For: 3.3.1 > > > When compressing to the gzip format, the plugin appends the adler two times. -- 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-1450) add gzip to automake
Otto van der Schaaf created TS-1450: --- Summary: add gzip to automake Key: TS-1450 URL: https://issues.apache.org/jira/browse/TS-1450 Project: Traffic Server Issue Type: Improvement Reporter: Otto van der Schaaf Fix For: 3.3.1 -- 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-1450) add gzip to automake
[ https://issues.apache.org/jira/browse/TS-1450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otto van der Schaaf reassigned TS-1450: --- Assignee: Otto van der Schaaf > add gzip to automake > > > Key: TS-1450 > URL: https://issues.apache.org/jira/browse/TS-1450 > Project: Traffic Server > Issue Type: Improvement >Reporter: Otto van der Schaaf >Assignee: Otto van der Schaaf > Fix For: 3.3.1 > > -- 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-1450) add gzip to automake
[ https://issues.apache.org/jira/browse/TS-1450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otto van der Schaaf resolved TS-1450. - Resolution: Fixed committed in 58f3312a5cac9b25f2b262cf7b65307e4003f279 > add gzip to automake > > > Key: TS-1450 > URL: https://issues.apache.org/jira/browse/TS-1450 > Project: Traffic Server > Issue Type: Improvement >Reporter: Otto van der Schaaf >Assignee: Otto van der Schaaf > Fix For: 3.3.1 > > -- 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-1450) add gzip to automake
[ https://issues.apache.org/jira/browse/TS-1450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13451657#comment-13451657 ] Otto van der Schaaf commented on TS-1450: - and also in 81aa9b51c18ba962382f8fcf9e3b7ff3b0d5b48f, i forgot the automake file in /plugins/experimental > add gzip to automake > > > Key: TS-1450 > URL: https://issues.apache.org/jira/browse/TS-1450 > Project: Traffic Server > Issue Type: Improvement >Reporter: Otto van der Schaaf >Assignee: Otto van der Schaaf > Fix For: 3.3.1 > > -- 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-1452) gzip build failure with Apple/clang-421.0.57
[ https://issues.apache.org/jira/browse/TS-1452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13451815#comment-13451815 ] Otto van der Schaaf commented on TS-1452: - These changes look fine to me. I will recheck that ssize_t/PRId64 are used where applicable in this plugin later this day, as I think there are other places those would be preferred. Thanks! > gzip build failure with Apple/clang-421.0.57 > - > > Key: TS-1452 > URL: https://issues.apache.org/jira/browse/TS-1452 > Project: Traffic Server > Issue Type: Bug > Components: Plugins >Reporter: James Peach >Assignee: James Peach > Labels: gzip > Fix For: 3.3.1 > > > The gzip module has a couple of compiler errors failure with > Apple/clang-421.0.57. -- 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-1455) memory leak when using the gzip plugin
Otto van der Schaaf created TS-1455: --- Summary: memory leak when using the gzip plugin Key: TS-1455 URL: https://issues.apache.org/jira/browse/TS-1455 Project: Traffic Server Issue Type: Bug Reporter: Otto van der Schaaf Assignee: Otto van der Schaaf Fix For: 3.3.1 -- 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-1455) memory leak when using the gzip plugin
[ https://issues.apache.org/jira/browse/TS-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otto van der Schaaf resolved TS-1455. - Resolution: Fixed committed in d0a57a7e3de8f0df8062cf5167b8356cf0ba5c78 > memory leak when using the gzip plugin > -- > > Key: TS-1455 > URL: https://issues.apache.org/jira/browse/TS-1455 > Project: Traffic Server > Issue Type: Bug >Reporter: Otto van der Schaaf >Assignee: Otto van der Schaaf > Fix For: 3.3.1 > > -- 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-1452) gzip build failure with Apple/clang-421.0.57
[ https://issues.apache.org/jira/browse/TS-1452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13451902#comment-13451902 ] Otto van der Schaaf commented on TS-1452: - could you retry compiling with the new automake file? > gzip build failure with Apple/clang-421.0.57 > - > > Key: TS-1452 > URL: https://issues.apache.org/jira/browse/TS-1452 > Project: Traffic Server > Issue Type: Bug > Components: Plugins >Reporter: James Peach >Assignee: James Peach > Labels: gzip > Fix For: 3.3.1 > > > The gzip module has a couple of compiler errors failure with > Apple/clang-421.0.57. -- 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] [Reopened] (TS-1452) gzip build failure with Apple/clang-421.0.57
[ https://issues.apache.org/jira/browse/TS-1452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otto van der Schaaf reopened TS-1452: - > gzip build failure with Apple/clang-421.0.57 > - > > Key: TS-1452 > URL: https://issues.apache.org/jira/browse/TS-1452 > Project: Traffic Server > Issue Type: Bug > Components: Plugins >Reporter: James Peach >Assignee: James Peach > Labels: gzip > Fix For: 3.3.1 > > > The gzip module has a couple of compiler errors failure with > Apple/clang-421.0.57. -- 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-1452) gzip build failure with Apple/clang-421.0.57
[ https://issues.apache.org/jira/browse/TS-1452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13452450#comment-13452450 ] Otto van der Schaaf commented on TS-1452: - __STDC_FORMAT_MACROS added in 99c70136854201ae862f63847c7ffe4406905a97 > gzip build failure with Apple/clang-421.0.57 > - > > Key: TS-1452 > URL: https://issues.apache.org/jira/browse/TS-1452 > Project: Traffic Server > Issue Type: Bug > Components: Plugins >Reporter: James Peach >Assignee: James Peach > Labels: gzip > Fix For: 3.3.1 > > > The gzip module has a couple of compiler errors failure with > Apple/clang-421.0.57. -- 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] [Reopened] (TS-1455) memory leak when using the gzip plugin
[ https://issues.apache.org/jira/browse/TS-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otto van der Schaaf reopened TS-1455: - > memory leak when using the gzip plugin > -- > > Key: TS-1455 > URL: https://issues.apache.org/jira/browse/TS-1455 > Project: Traffic Server > Issue Type: Bug >Reporter: Otto van der Schaaf >Assignee: Otto van der Schaaf > Fix For: 3.3.1 > > Attachments: another_leak.diff > > -- 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-1455) memory leak when using the gzip plugin
[ https://issues.apache.org/jira/browse/TS-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otto van der Schaaf resolved TS-1455. - Resolution: Fixed patch applied in 711674da9cf08e6865dcb919bb9d82522bd2dec3 Thanks Conan! > memory leak when using the gzip plugin > -- > > Key: TS-1455 > URL: https://issues.apache.org/jira/browse/TS-1455 > Project: Traffic Server > Issue Type: Bug >Reporter: Otto van der Schaaf >Assignee: Otto van der Schaaf > Fix For: 3.3.1 > > Attachments: another_leak.diff > > -- 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-1659) Gzip: Make it possible to "remove" compressible-content-type
[
https://issues.apache.org/jira/browse/TS-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otto van der Schaaf reassigned TS-1659:
---
Assignee: Otto van der Schaaf
> Gzip: Make it possible to "remove" compressible-content-type
>
>
> Key: TS-1659
> URL: https://issues.apache.org/jira/browse/TS-1659
> Project: Traffic Server
> Issue Type: Improvement
> Components: Plugins
>Reporter: Igor Galić
>Assignee: Otto van der Schaaf
>
> I would like to be able to make a simple configuration like:
> {noformat}
> compressible-content-type text/*
> compressible-content-type !text/javascript
> {noformat}
> This should result in:
> Add all {{text/*}} types, remove {{text/javascript}}
--
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-1659) Gzip: Make it possible to "remove" compressible-content-type
[
https://issues.apache.org/jira/browse/TS-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13556373#comment-13556373
]
Otto van der Schaaf commented on TS-1659:
-
I committed this in 594c41ac1eb128c5757e2d95db9241243b8d2520
I have not tested this yet though, since I couldn't get traffic server to
compile on ubuntu 12.04/x64
> Gzip: Make it possible to "remove" compressible-content-type
>
>
> Key: TS-1659
> URL: https://issues.apache.org/jira/browse/TS-1659
> Project: Traffic Server
> Issue Type: Improvement
> Components: Plugins
>Reporter: Igor Galić
>Assignee: Otto van der Schaaf
>
> I would like to be able to make a simple configuration like:
> {noformat}
> compressible-content-type text/*
> compressible-content-type !text/javascript
> {noformat}
> This should result in:
> Add all {{text/*}} types, remove {{text/javascript}}
--
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-1659) Gzip: Make it possible to "remove" compressible-content-type
[
https://issues.apache.org/jira/browse/TS-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13558871#comment-13558871
]
Otto van der Schaaf commented on TS-1659:
-
ibrezac has prepared a patch for the vary header issue , so I'll close this
ticket and create a new one for the patch
> Gzip: Make it possible to "remove" compressible-content-type
>
>
> Key: TS-1659
> URL: https://issues.apache.org/jira/browse/TS-1659
> Project: Traffic Server
> Issue Type: Improvement
> Components: Plugins
>Reporter: Igor Galić
>Assignee: Otto van der Schaaf
>
> I would like to be able to make a simple configuration like:
> {noformat}
> compressible-content-type text/*
> compressible-content-type !text/javascript
> {noformat}
> This should result in:
> Add all {{text/*}} types, remove {{text/javascript}}
--
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-1659) Gzip: Make it possible to "remove" compressible-content-type
[
https://issues.apache.org/jira/browse/TS-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otto van der Schaaf resolved TS-1659.
-
Resolution: Fixed
> Gzip: Make it possible to "remove" compressible-content-type
>
>
> Key: TS-1659
> URL: https://issues.apache.org/jira/browse/TS-1659
> Project: Traffic Server
> Issue Type: Improvement
> Components: Plugins
>Reporter: Igor Galić
>Assignee: Otto van der Schaaf
>
> I would like to be able to make a simple configuration like:
> {noformat}
> compressible-content-type text/*
> compressible-content-type !text/javascript
> {noformat}
> This should result in:
> Add all {{text/*}} types, remove {{text/javascript}}
--
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-1664) Gzip doesn't check vary and accept-encoding before adding them
Otto van der Schaaf created TS-1664: --- Summary: Gzip doesn't check vary and accept-encoding before adding them Key: TS-1664 URL: https://issues.apache.org/jira/browse/TS-1664 Project: Traffic Server Issue Type: Bug Components: Plugins Reporter: Otto van der Schaaf Gzip doesn't check vary and accept-encoding before adding them. So we may end up sending these headers out twice -- 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-1664) Gzip doesn't check vary and accept-encoding before adding them
[ https://issues.apache.org/jira/browse/TS-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otto van der Schaaf updated TS-1664: Assignee: Igor Brezac > Gzip doesn't check vary and accept-encoding before adding them > -- > > Key: TS-1664 > URL: https://issues.apache.org/jira/browse/TS-1664 > Project: Traffic Server > Issue Type: Bug > Components: Plugins >Reporter: Otto van der Schaaf >Assignee: Igor Brezac > > Gzip doesn't check vary and accept-encoding before adding them. So we may end > up sending these headers out twice -- 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-1664) Gzip doesn't check vary and accept-encoding before adding them
[ https://issues.apache.org/jira/browse/TS-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13559701#comment-13559701 ] Otto van der Schaaf commented on TS-1664: - committed in 26368e5f2c53ea81443401042e32e27bb638be8e > Gzip doesn't check vary and accept-encoding before adding them > -- > > Key: TS-1664 > URL: https://issues.apache.org/jira/browse/TS-1664 > Project: Traffic Server > Issue Type: Bug > Components: Plugins >Reporter: Otto van der Schaaf >Assignee: Otto van der Schaaf > Attachments: gzip.patch > > > Gzip doesn't check vary and accept-encoding before adding them. So we may end > up sending these headers out twice -- 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-1666) gzip plugin crash report
Otto van der Schaaf created TS-1666:
---
Summary: gzip plugin crash report
Key: TS-1666
URL: https://issues.apache.org/jira/browse/TS-1666
Project: Traffic Server
Issue Type: Bug
Components: Plugins
Reporter: Otto van der Schaaf
ibrezac dumped this trace on irc:
[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'
--
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-1666) gzip plugin crash report
[
https://issues.apache.org/jira/browse/TS-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otto van der Schaaf updated TS-1666:
Assignee: Otto van der Schaaf
> gzip plugin crash report
>
>
> Key: TS-1666
> URL: https://issues.apache.org/jira/browse/TS-1666
> Project: Traffic Server
> Issue Type: Bug
> Components: Plugins
>Reporter: Otto van der Schaaf
>Assignee: Otto van der Schaaf
>
> ibrezac dumped this trace on irc:
> [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'
--
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-1666) gzip plugin crash report
[
https://issues.apache.org/jira/browse/TS-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otto van der Schaaf updated TS-1666:
Description:
ibrezac dumped this trace on irc:
[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'
configuration used:
cache true
enabled true
remove-accept-encoding false
compressible-content-type text/*
compressible-content-type *javascript*
was:
ibrezac dumped this trace on irc:
[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'
http://apaste.info/DMrb
configuration used:
cache true
enabled true
remove-accept-encoding false
compressible-content-type text/*
compressible-content-type *javascript*
> gzip plugin crash report
>
>
> Key: TS-1666
> URL: https://issues.apache.org/jira/browse/TS-1666
> Project: Traffic Server
> Issue Type: Bug
> Componen
[jira] [Updated] (TS-1666) gzip plugin crash report
[
https://issues.apache.org/jira/browse/TS-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otto van der Schaaf updated TS-1666:
Description:
ibrezac dumped this trace on irc:
[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'
http://apaste.info/DMrb
configuration used:
cache true
enabled true
remove-accept-encoding false
compressible-content-type text/*
compressible-content-type *javascript*
was:
ibrezac dumped this trace on irc:
[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'
> gzip plugin crash report
>
>
> Key: TS-1666
> URL: https://issues.apache.org/jira/browse/TS-1666
> Project: Traffic Server
> Issue Type: Bug
> Components: Plugins
>Reporter: Otto van der Schaaf
>Assignee: Otto van der Schaaf
>
> ibrezac dumped this trace on irc:
> [Jan 22 21:
[jira] [Updated] (TS-1666) gzip plugin crash report
[
https://issues.apache.org/jira/browse/TS-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otto van der Schaaf updated TS-1666:
Description:
ibrezac dumped this trace on irc:
[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'
configuration used:
cache true
enabled true
remove-accept-encoding false
compressible-content-type text/*
compressible-content-type *javascript*
=== misc info
TS Version 3.2.4
Running at around 50 qps
crashes every 10 seconds
was:
ibrezac dumped this trace on irc:
[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'
configuration used:
cache true
enabled true
remove-accept-encoding false
compressible-content-type text/*
compressible-content-type *javascript*
> gzip plugin crash report
>
>
> Key: TS-1666
> URL: https://issues.apache.org/jira/browse/TS-1666
> Project:
[jira] [Updated] (TS-1666) gzip plugin crash report
[
https://issues.apache.org/jira/browse/TS-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otto van der Schaaf updated TS-1666:
Description:
ibrezac dumped this trace on irc:
[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'
configuration used:
cache true
enabled true
remove-accept-encoding false
compressible-content-type text/*
compressible-content-type *javascript*
=== misc info
TS Version 3.2.4
Running at around 50 qps
crashes every 10 seconds
== c++filt stack trace
/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]
was:
ibrezac dumped this trace on irc:
[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(mai
[jira] [Commented] (TS-1666) gzip plugin crash report
[
https://issues.apache.org/jira/browse/TS-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13603626#comment-13603626
]
Otto van der Schaaf commented on TS-1666:
-
I'm not sure, I couldn't reproduce it myself. I'll see if I can ping ibrezac
about it, he was subject to this issue
> gzip plugin crash report
>
>
> Key: TS-1666
> URL: https://issues.apache.org/jira/browse/TS-1666
> Project: Traffic Server
> Issue Type: Bug
> Components: Plugins
>Reporter: Otto van der Schaaf
>Assignee: Otto van der Schaaf
>
> ibrezac dumped this trace on irc:
> [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'
> configuration used:
> cache true
> enabled true
> remove-accept-encoding false
> compressible-content-type text/*
> compressible-content-type *javascript*
> === misc info
> TS Version 3.2.4
> Running at around 50 qps
> crashes every 10 seconds
> == c++filt stack trace
> /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]
--
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) gzip plugin crash report
[
https://issues.apache.org/jira/browse/TS-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13688407#comment-13688407
]
Otto van der Schaaf commented on TS-1666:
-
I have never been able to reproduce it - and couldn't figure this out just by
the stack trace.
so, no - this probably isn't fixed, and I still have no idea what could cause
this.
> gzip plugin crash report
>
>
> 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
>Assignee: Otto van der Schaaf
> Labels: crash
> Fix For: sometime
>
>
> ibrezac dumped this trace on irc:
> [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'
> configuration used:
> cache true
> enabled true
> remove-accept-encoding false
> compressible-content-type text/*
> compressible-content-type *javascript*
> === misc info
> TS Version 3.2.4
> Running at around 50 qps
> crashes every 10 seconds
> == c++filt stack trace
> /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]
--
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) gzip plugin crash report
[
https://issues.apache.org/jira/browse/TS-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13689207#comment-13689207
]
Otto van der Schaaf commented on TS-1666:
-
This was reported with 3.2.x - no idea about the configuration that was used.
[~ibrezac] was initially reporting this stack trace, and might remember?
> gzip plugin crash report
>
>
> 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
>Assignee: Otto van der Schaaf
> Labels: crash
> Fix For: sometime
>
>
> ibrezac dumped this trace on irc:
> [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'
> configuration used:
> cache true
> enabled true
> remove-accept-encoding false
> compressible-content-type text/*
> compressible-content-type *javascript*
> === misc info
> TS Version 3.2.4
> Running at around 50 qps
> crashes every 10 seconds
> == c++filt stack trace
> /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]
--
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-2926) IP Clearance for ats_speed - PageSpeed Optimization plugin
Otto van der Schaaf created TS-2926: --- Summary: IP Clearance for ats_speed - PageSpeed Optimization plugin Key: TS-2926 URL: https://issues.apache.org/jira/browse/TS-2926 Project: Traffic Server Issue Type: Task Reporter: Otto van der Schaaf Attachments: ats_speed-master.zip Ats_speed is a plugin by We-Amp which enables easy and automatic web performance optimization powered by Google's PageSpeed optimization SDK (like mod_pagespeed). The donated code currently lives at https://github.com/We-Amp/ats_speed Also, See www.atsspeed.com for more information. Since this code was developed outside of the Apache process it is required to go through the IP Clearance procedure which is managed by the Incubator - https://incubator.apache.org/ip-clearance/index.html This issue will act as a tracking point for tasks related to carrying out the IP Clearance process. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2926) IP Clearance for ats_speed - PageSpeed Optimization plugin
[ https://issues.apache.org/jira/browse/TS-2926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otto van der Schaaf updated TS-2926: Attachment: ats_speed-master.zip > IP Clearance for ats_speed - PageSpeed Optimization plugin > -- > > Key: TS-2926 > URL: https://issues.apache.org/jira/browse/TS-2926 > Project: Traffic Server > Issue Type: Task >Reporter: Otto van der Schaaf > Attachments: ats_speed-master.zip > > > Ats_speed is a plugin by We-Amp which enables easy and automatic web > performance optimization powered by Google's PageSpeed optimization SDK (like > mod_pagespeed). > The donated code currently lives at https://github.com/We-Amp/ats_speed > Also, See www.atsspeed.com for more information. > Since this code was developed outside of the Apache process it is required to > go through the IP Clearance procedure which is managed by the Incubator - > https://incubator.apache.org/ip-clearance/index.html > This issue will act as a tracking point for tasks related to carrying out the > IP Clearance process. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2926) IP Clearance for ats_speed - PageSpeed Optimization plugin
[ https://issues.apache.org/jira/browse/TS-2926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otto van der Schaaf updated TS-2926: Description: Ats_speed is a plugin by We-Amp which enables easy and automatic web performance optimization powered by Google's PageSpeed optimization SDK (like mod_pagespeed). The donated code currently lives at https://github.com/We-Amp/ats_speed Also, See www.atsspeed.com for more information. Since this code was developed outside of the Apache process it is required to go through the IP Clearance procedure which is managed by the Incubator - https://incubator.apache.org/ip-clearance/index.html This issue will act as a tracking point for tasks related to carrying out the IP Clearance process: https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/ats-ats_speed.xml was: Ats_speed is a plugin by We-Amp which enables easy and automatic web performance optimization powered by Google's PageSpeed optimization SDK (like mod_pagespeed). The donated code currently lives at https://github.com/We-Amp/ats_speed Also, See www.atsspeed.com for more information. Since this code was developed outside of the Apache process it is required to go through the IP Clearance procedure which is managed by the Incubator - https://incubator.apache.org/ip-clearance/index.html This issue will act as a tracking point for tasks related to carrying out the IP Clearance process. > IP Clearance for ats_speed - PageSpeed Optimization plugin > -- > > Key: TS-2926 > URL: https://issues.apache.org/jira/browse/TS-2926 > Project: Traffic Server > Issue Type: Task >Reporter: Otto van der Schaaf > Attachments: ats_speed-master.zip > > > Ats_speed is a plugin by We-Amp which enables easy and automatic web > performance optimization powered by Google's PageSpeed optimization SDK (like > mod_pagespeed). > The donated code currently lives at https://github.com/We-Amp/ats_speed > Also, See www.atsspeed.com for more information. > Since this code was developed outside of the Apache process it is required to > go through the IP Clearance procedure which is managed by the Incubator - > https://incubator.apache.org/ip-clearance/index.html > This issue will act as a tracking point for tasks related to carrying out the > IP Clearance process: > https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/ats-ats_speed.xml -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2926) IP Clearance for ats_speed - PageSpeed Optimization plugin
[ https://issues.apache.org/jira/browse/TS-2926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14056670#comment-14056670 ] Otto van der Schaaf commented on TS-2926: - Done, I submitted the grant file to secret...@apache.org this afternoon > IP Clearance for ats_speed - PageSpeed Optimization plugin > -- > > Key: TS-2926 > URL: https://issues.apache.org/jira/browse/TS-2926 > Project: Traffic Server > Issue Type: Task > Components: Plugins >Reporter: Otto van der Schaaf > Fix For: 5.1.0 > > Attachments: ats_speed-master.zip > > > Ats_speed is a plugin by We-Amp which enables easy and automatic web > performance optimization powered by Google's PageSpeed optimization SDK (like > mod_pagespeed). > The donated code currently lives at https://github.com/We-Amp/ats_speed > Also, See http://www.atsspeed.com/ for more information. > Since this code was developed outside of the Apache process it is required to > go through the IP Clearance procedure which is managed by the Incubator - > https://incubator.apache.org/ip-clearance/index.html > This issue will act as a tracking point for tasks related to carrying out the > IP Clearance process: > https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/ats-ats_speed.xml -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2926) IP Clearance for ats_speed - PageSpeed Optimization plugin
[ https://issues.apache.org/jira/browse/TS-2926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otto van der Schaaf updated TS-2926: Description: Ats_speed is a plugin by We-Amp which enables easy and automatic web performance optimization powered by Google's PageSpeed optimization SDK (like mod_pagespeed). The donated code currently lives at https://github.com/We-Amp/ats_speed Also, See http://www.atsspeed.com/ for more information. Since this code was developed outside of the Apache process it is required to go through the IP Clearance procedure which is managed by the Incubator - https://incubator.apache.org/ip-clearance/index.html This issue will act as a tracking point for tasks related to carrying out the IP Clearance process: https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/ats-ats_speed.xml was: Ats_speed is a plugin by We-Amp which enables easy and automatic web performance optimization powered by Google's PageSpeed optimization SDK (like mod_pagespeed). The donated code currently lives at https://github.com/We-Amp/ats_speed Also, See www.atsspeed.com for more information. Since this code was developed outside of the Apache process it is required to go through the IP Clearance procedure which is managed by the Incubator - https://incubator.apache.org/ip-clearance/index.html This issue will act as a tracking point for tasks related to carrying out the IP Clearance process: https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/ats-ats_speed.xml > IP Clearance for ats_speed - PageSpeed Optimization plugin > -- > > Key: TS-2926 > URL: https://issues.apache.org/jira/browse/TS-2926 > Project: Traffic Server > Issue Type: Task > Components: Plugins >Reporter: Otto van der Schaaf > Fix For: 5.1.0 > > Attachments: ats_speed-master.zip > > > Ats_speed is a plugin by We-Amp which enables easy and automatic web > performance optimization powered by Google's PageSpeed optimization SDK (like > mod_pagespeed). > The donated code currently lives at https://github.com/We-Amp/ats_speed > Also, See http://www.atsspeed.com/ for more information. > Since this code was developed outside of the Apache process it is required to > go through the IP Clearance procedure which is managed by the Incubator - > https://incubator.apache.org/ip-clearance/index.html > This issue will act as a tracking point for tasks related to carrying out the > IP Clearance process: > https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/ats-ats_speed.xml -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (TS-3607) ats_pagespeed make error
[ https://issues.apache.org/jira/browse/TS-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otto van der Schaaf reassigned TS-3607: --- Assignee: Otto van der Schaaf > ats_pagespeed make error > > > Key: TS-3607 > URL: https://issues.apache.org/jira/browse/TS-3607 > Project: Traffic Server > Issue Type: Bug >Reporter: Sebastian Pesman >Assignee: Otto van der Schaaf > > When compiling ats_pagespeed from the current master git > /tmp/trafficserver/plugins/experimental/ats_pagespeed the make process > results in an error. > The error: > ats_pagespeed.cc: In function 'void ats_transform_init(TSCont, > TransformCtx*)': > ats_pagespeed.cc:485:109: error: 'INT64_MAX' was not declared in this scope >ctx->downstream_vio = TSVConnWrite(downstream_conn, contp, > TSIOBufferReaderAlloc(ctx->downstream_buffer), INT64_MAX); > >^ > make: *** [ats_pagespeed.so] Error 1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (TS-3607) ats_pagespeed make error
[ https://issues.apache.org/jira/browse/TS-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TS-3607 started by Otto van der Schaaf. --- > ats_pagespeed make error > > > Key: TS-3607 > URL: https://issues.apache.org/jira/browse/TS-3607 > Project: Traffic Server > Issue Type: Bug >Reporter: Sebastian Pesman >Assignee: Otto van der Schaaf > > When compiling ats_pagespeed from the current master git > /tmp/trafficserver/plugins/experimental/ats_pagespeed the make process > results in an error. > The error: > ats_pagespeed.cc: In function 'void ats_transform_init(TSCont, > TransformCtx*)': > ats_pagespeed.cc:485:109: error: 'INT64_MAX' was not declared in this scope >ctx->downstream_vio = TSVConnWrite(downstream_conn, contp, > TSIOBufferReaderAlloc(ctx->downstream_buffer), INT64_MAX); > >^ > make: *** [ats_pagespeed.so] Error 1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (TS-3629) TS corrupts Link: header in response
[
https://issues.apache.org/jira/browse/TS-3629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otto van der Schaaf reassigned TS-3629:
---
Assignee: Otto van der Schaaf
> TS corrupts Link: header in response
>
>
> Key: TS-3629
> URL: https://issues.apache.org/jira/browse/TS-3629
> Project: Traffic Server
> Issue Type: Bug
>Reporter: Felicity Tarnell
>Assignee: Otto van der Schaaf
>
> (Using 5.3.0 on 64-bit Linux.)
> We have an origin that links a {{Link}} header in its response. Requesting
> the document directly from the origin (nginx) shows the correct header:
> {noformat}
> by-staging-1:~# curl -Ix localhost:81 http://plan-staging.torchboxapps.com/
> HTTP/1.1 200 OK
> Server: nginx
> Date: Thu, 21 May 2015 10:04:54 GMT
> Content-Type: text/html; charset=utf-8
> Connection: keep-alive
> Vary: Accept-Encoding
> Expires: Sun, 19 Nov 1978 05:00:00 GMT
> Cache-Control: no-cache, must-revalidate, post-check=0, pre-check=0
> Content-Language: en
> Link:
[jira] [Commented] (TS-3629) TS corrupts Link: header in response
[
https://issues.apache.org/jira/browse/TS-3629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14554216#comment-14554216
]
Otto van der Schaaf commented on TS-3629:
-
[~sudheerv] Sure. I assigned this bug to myself -- I won't have time to work on
ats_pagespeed this week, but will look into it all outstanding issues early
next week.
> TS corrupts Link: header in response
>
>
> Key: TS-3629
> URL: https://issues.apache.org/jira/browse/TS-3629
> Project: Traffic Server
> Issue Type: Bug
>Reporter: Felicity Tarnell
>Assignee: Otto van der Schaaf
>
> (Using 5.3.0 on 64-bit Linux.)
> We have an origin that links a {{Link}} header in its response. Requesting
> the document directly from the origin (nginx) shows the correct header:
> {noformat}
> by-staging-1:~# curl -Ix localhost:81 http://plan-staging.torchboxapps.com/
> HTTP/1.1 200 OK
> Server: nginx
> Date: Thu, 21 May 2015 10:04:54 GMT
> Content-Type: text/html; charset=utf-8
> Connection: keep-alive
> Vary: Accept-Encoding
> Expires: Sun, 19 Nov 1978 05:00:00 GMT
> Cache-Control: no-cache, must-revalidate, post-check=0, pre-check=0
> Content-Language: en
> Link:
[jira] [Commented] (TS-3748) Seg fault on Centos inside Ats-pageSpeed plugin always
[ https://issues.apache.org/jira/browse/TS-3748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15060544#comment-15060544 ] Otto van der Schaaf commented on TS-3748: - Yes, I'll look into it. This honestly slipped my mind, I was planning to fix this earlier. While I'm at it, I'll subsequently upgrade the plugin from 1.9 to the new 1.10 pagespeed beta that got out yesterday as well -- under a separate jira. > Seg fault on Centos inside Ats-pageSpeed plugin always > -- > > Key: TS-3748 > URL: https://issues.apache.org/jira/browse/TS-3748 > Project: Traffic Server > Issue Type: Bug > Components: Plugins >Reporter: wanrui >Assignee: Otto van der Schaaf >Priority: Critical > Labels: crash > Fix For: 6.2.0 > > > Program terminated with signal 6, Aborted. > #0 0x079a25d7 in raise () from /lib64/libc.so.6 > Missing separate debuginfos, use: debuginfo-install expat-2.1.0-8.el7.x86_64 > glibc-2.17-78.el7.x86_64 keyutils-libs-1.5.8-3.el7.x86_64 > krb5-libs-1.12.2-14.el7.x86_64 libattr-2.4.46-12.el7.x86_64 > libcap-2.22-8.el7.x86_64 libcom_err-1.42.9-7.el7.x86_64 > libgcc-4.8.3-9.el7.x86_64 libpciaccess-0.13.1-4.1.el7.x86_64 > libselinux-2.2.2-6.el7.x86_64 pcre-8.32-14.el7.x86_64 > valgrind-3.10.0-7.el7.x86_64 xz-libs-5.1.2-9alpha.el7.x86_64 > zlib-1.2.7-13.el7.x86_64 > (gdb) bt > #0 0x079a25d7 in raise () from /lib64/libc.so.6 > #1 0x079a3cc8 in abort () from /lib64/libc.so.6 > #2 0x005019f2 in ink_mutex_acquire (m=0x420e8b0) at > ../lib/ts/ink_mutex.h:115 > #3 0x00509987 in Mutex_lock (m=0x420e8a0, t=0x2e031d60) at > ../iocore/eventsystem/I_Lock.h:488 > #4 0x0052da9f in TSMutexLock (mutexp=0x420e8a0) at > InkIOCoreAPI.cc:224 > #5 0x1caec2cf in net_instaweb::AtsBaseFetch::ForwardData > (this=0x30ded530, sp=..., reenable=false, last=false) at ats_base_fetch.cc:123 > #6 0x1caec44d in net_instaweb::AtsBaseFetch::HandleWrite > (this=, sp=..., handler=) at > ats_base_fetch.cc:81 > #7 0x1cc01887 in > net_instaweb::AsyncFetch::Write(base::BasicStringPiece const&, > net_instaweb::MessageHandler*) () >from /home/aca/dca/libexec/trafficserver/ats_pagespeed.so > #8 0x1cc61418 in > net_instaweb::HtmlWriterFilter::EmitBytes(base::BasicStringPiece > const&) () from /home/aca/dca/libexec/trafficserver/ats_pagespeed.so > #9 0x1cc619cb in > net_instaweb::HtmlWriterFilter::StartElement(net_instaweb::HtmlElement*) () > from /home/aca/dca/libexec/trafficserver/ats_pagespeed.so > #10 0x1cc5eca4 in > net_instaweb::HtmlParse::ApplyFilter(net_instaweb::HtmlFilter*) () from > /home/aca/dca/libexec/trafficserver/ats_pagespeed.so > #11 0x1cc5eeaa in net_instaweb::HtmlParse::Flush() () from > /home/aca/dca/libexec/trafficserver/ats_pagespeed.so > #12 0x1cb3feb5 in net_instaweb::RewriteDriver::FlushAsyncDone(int, > net_instaweb::Function*) () from > /home/aca/dca/libexec/trafficserver/ats_pagespeed.so > #13 0x1cc2416f in net_instaweb::Function::CallRun() () from > /home/aca/dca/libexec/trafficserver/ats_pagespeed.so > #14 0x1cafc30c in > net_instaweb::QueuedWorkerPool::Run(net_instaweb::QueuedWorkerPool::Sequence*, > net_instaweb::QueuedWorker*) () >from /home/aca/dca/libexec/trafficserver/ats_pagespeed.so > #15 0x1cc2416f in net_instaweb::Function::CallRun() () from > /home/aca/dca/libexec/trafficserver/ats_pagespeed.so > #16 0x1cafe0c6 in net_instaweb::Worker::WorkThread::Run() () from > /home/aca/dca/libexec/trafficserver/ats_pagespeed.so > #17 0x1cafe9d8 in net_instaweb::PthreadThreadImpl::InvokeRun(void*) > () from /home/aca/dca/libexec/trafficserver/ats_pagespeed.so > #18 0x05089df5 in start_thread () from /lib64/libpthread.so.0 > #19 0x07a631ad in clone () from /lib64/libc.so.6 > Looks like the mutex lock return 22.then abort . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-2926) IP Clearance for ats_speed - PageSpeed Optimization plugin
[ https://issues.apache.org/jira/browse/TS-2926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14084092#comment-14084092 ] Otto van der Schaaf commented on TS-2926: - @Alan - will do tomorrow! > IP Clearance for ats_speed - PageSpeed Optimization plugin > -- > > Key: TS-2926 > URL: https://issues.apache.org/jira/browse/TS-2926 > Project: Traffic Server > Issue Type: Task > Components: Plugins >Reporter: Otto van der Schaaf >Assignee: Otto van der Schaaf > Fix For: 5.1.0 > > Attachments: ats_speed-master.zip > > > Ats_speed is a plugin by We-Amp which enables easy and automatic web > performance optimization powered by Google's PageSpeed optimization SDK (like > mod_pagespeed). > The donated code currently lives at https://github.com/We-Amp/ats_speed > Also, See http://www.atsspeed.com/ for more information. > Since this code was developed outside of the Apache process it is required to > go through the IP Clearance procedure which is managed by the Incubator - > https://incubator.apache.org/ip-clearance/index.html > This issue will act as a tracking point for tasks related to carrying out the > IP Clearance process: > https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/ats-ats_speed.xml -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2926) IP Clearance for ats_speed - PageSpeed Optimization plugin
[ https://issues.apache.org/jira/browse/TS-2926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14084506#comment-14084506 ] Otto van der Schaaf commented on TS-2926: - Alan, I've prepared https://github.com/We-Amp/trafficserver/compare/oschaaf-ats-speed?expand=1 It just adds the code as-is to experimental, and doesn't wire up building yet. As ats_speed has some 'special' build requirements, I thought it might be wise to address to later, and first just get the code in. LGTY? If so, I'll update the commit/pull comment to something better and make a pull for this. > IP Clearance for ats_speed - PageSpeed Optimization plugin > -- > > Key: TS-2926 > URL: https://issues.apache.org/jira/browse/TS-2926 > Project: Traffic Server > Issue Type: Task > Components: Plugins >Reporter: Otto van der Schaaf >Assignee: Otto van der Schaaf > Fix For: 5.1.0 > > Attachments: ats_speed-master.zip > > > Ats_speed is a plugin by We-Amp which enables easy and automatic web > performance optimization powered by Google's PageSpeed optimization SDK (like > mod_pagespeed). > The donated code currently lives at https://github.com/We-Amp/ats_speed > Also, See http://www.atsspeed.com/ for more information. > Since this code was developed outside of the Apache process it is required to > go through the IP Clearance procedure which is managed by the Incubator - > https://incubator.apache.org/ip-clearance/index.html > This issue will act as a tracking point for tasks related to carrying out the > IP Clearance process: > https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/ats-ats_speed.xml -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (TS-2988) ats_speed: bail out when gurl->IsWebValid() != true
Otto van der Schaaf created TS-2988:
---
Summary: ats_speed: bail out when gurl->IsWebValid() != true
Key: TS-2988
URL: https://issues.apache.org/jira/browse/TS-2988
Project: Traffic Server
Issue Type: Bug
Components: Plugins
Reporter: Otto van der Schaaf
Reported via https://github.com/We-Amp/ats_speed/issues/12
Prevent a CHECK failure by bailing out on urls that apparently can't be parsed
as web valid. Preferrably should emit a warning about it as well, as it might
be interesting to see which urls would fail.
[Aug 2 19:24:21.165] Server {0x7fc5b9a05700} DIAG: (ats-speed-vlog)
[1.7.30.4-3847] [0802/192421:FATAL:ats_speed.cc(719)] Check failed:
ctx->gurl->IsWebValid(). Invalid URL!
Backtrace:
/usr/libexec/trafficserver/ats_speed.so(+0x88f8a) [0x7fc5b6e26f8a]
/usr/libexec/trafficserver/ats_speed.so(+0x7b9d0) [0x7fc5b6e199d0]
/usr/libexec/trafficserver/ats_speed.so(+0x85fc9) [0x7fc5b6e23fc9]
/usr/libexec/trafficserver/ats_speed.so(handle_read_request_header(tsapi_httptxn*)+0x49d)
[0x7fc5b6e209cd]
/usr/libexec/trafficserver/ats_speed.so(+0x83218) [0x7fc5b6e21218]
traffic_server(HttpSM::state_api_callout(int, void*)+0x102) [0x5abee2]
traffic_server(HttpSM::state_api_callback(int, void*)+0x82) [0x5b0c22]
traffic_server(TSHttpTxnReenable+0x244) [0x4c8494]
/usr/libexec/trafficserver/gzip.so(+0x742b) [0x7fc5b765842b]
traffic_server(HttpSM::state_api_callout(int, void*)+0x102) [0x5abee2]
traffic_server(HttpSM::set_next_state()+0x1db) [0x5b0efb]
traffic_server(HttpSM::state_read_client_request_header(int, void*)+0x38f)
[0x5a4c9f]
traffic_server(HttpSM::main_handler(int, void*)+0xbd) [0x5b0a3d]
traffic_server(HttpSM::state_api_callout(int, void*)+0x2c0) [0x5ac0a0]
traffic_server(HttpSM::state_add_to_list(int, void*)+0x190) [0x5aca10]
traffic_server(HttpSM::attach_client_session(HttpClientSession*,
IOBufferReader*)+0x38a) [0x5b089a]
traffic_server(HttpClientSession::new_transaction()+0x9f) [0x58f54f]
traffic_server(HttpClientSession::state_api_callout(int, void*)+0x1cf)
[0x59086f]
traffic_server(HttpClientSession::new_connection(NetVConnection*, bool,
MIOBuffer*, IOBufferReader*)+0x4d9) [0x5914c9]
traffic_server(HttpSessionAccept::accept(NetVConnection*, MIOBuffer*,
IOBufferReader*)+0x203) [0x58bbd3]
traffic_server(ProtocolProbeTrampoline::ioCompletionEvent(int,
void*)+0x3c8) [0x4eb968]
traffic_server() [0x715ebb]
traffic_server(NetHandler::mainNetEvent(int, Event*)+0x1f2) [0x709122]
traffic_server(EThread::execute()+0xad3) [0x737e93]
traffic_server() [0x7368ca]
/lib64/libpthread.so.0(+0x7f18) [0x7fc5bd15ff18]
/lib64/libc.so.6(clone+0x6d) [0x7fc5bc112e9d]
Aborted
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (TS-2989) ats_speed: implement In-Place-Resource-Optimization flow
Otto van der Schaaf created TS-2989: --- Summary: ats_speed: implement In-Place-Resource-Optimization flow Key: TS-2989 URL: https://issues.apache.org/jira/browse/TS-2989 Project: Traffic Server Issue Type: Improvement Components: Plugins Reporter: Otto van der Schaaf The PageSpeed optimization libraries also support a flow where images/js/css can be optimized on the original url. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (TS-2990) ats_speed: migrate to CPP api
Otto van der Schaaf created TS-2990: --- Summary: ats_speed: migrate to CPP api Key: TS-2990 URL: https://issues.apache.org/jira/browse/TS-2990 Project: Traffic Server Issue Type: Improvement Components: Plugins Reporter: Otto van der Schaaf The new CPP api offers an opportunity to simplify much of the code - it would be good to migrate towards it where possible. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (TS-2988) ats_speed: bail out when gurl->IsWebValid() != true
[
https://issues.apache.org/jira/browse/TS-2988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otto van der Schaaf reassigned TS-2988:
---
Assignee: Otto van der Schaaf
> ats_speed: bail out when gurl->IsWebValid() != true
> ---
>
> Key: TS-2988
> URL: https://issues.apache.org/jira/browse/TS-2988
> Project: Traffic Server
> Issue Type: Bug
> Components: Plugins
>Reporter: Otto van der Schaaf
>Assignee: Otto van der Schaaf
>
> Reported via https://github.com/We-Amp/ats_speed/issues/12
> Prevent a CHECK failure by bailing out on urls that apparently can't be
> parsed as web valid. Preferrably should emit a warning about it as well, as
> it might be interesting to see which urls would fail.
> [Aug 2 19:24:21.165] Server {0x7fc5b9a05700} DIAG: (ats-speed-vlog)
> [1.7.30.4-3847] [0802/192421:FATAL:ats_speed.cc(719)] Check failed:
> ctx->gurl->IsWebValid(). Invalid URL!
> Backtrace:
> /usr/libexec/trafficserver/ats_speed.so(+0x88f8a) [0x7fc5b6e26f8a]
> /usr/libexec/trafficserver/ats_speed.so(+0x7b9d0) [0x7fc5b6e199d0]
> /usr/libexec/trafficserver/ats_speed.so(+0x85fc9) [0x7fc5b6e23fc9]
>
> /usr/libexec/trafficserver/ats_speed.so(handle_read_request_header(tsapi_httptxn*)+0x49d)
> [0x7fc5b6e209cd]
> /usr/libexec/trafficserver/ats_speed.so(+0x83218) [0x7fc5b6e21218]
> traffic_server(HttpSM::state_api_callout(int, void*)+0x102) [0x5abee2]
> traffic_server(HttpSM::state_api_callback(int, void*)+0x82) [0x5b0c22]
> traffic_server(TSHttpTxnReenable+0x244) [0x4c8494]
> /usr/libexec/trafficserver/gzip.so(+0x742b) [0x7fc5b765842b]
> traffic_server(HttpSM::state_api_callout(int, void*)+0x102) [0x5abee2]
> traffic_server(HttpSM::set_next_state()+0x1db) [0x5b0efb]
> traffic_server(HttpSM::state_read_client_request_header(int,
> void*)+0x38f) [0x5a4c9f]
> traffic_server(HttpSM::main_handler(int, void*)+0xbd) [0x5b0a3d]
> traffic_server(HttpSM::state_api_callout(int, void*)+0x2c0) [0x5ac0a0]
> traffic_server(HttpSM::state_add_to_list(int, void*)+0x190) [0x5aca10]
> traffic_server(HttpSM::attach_client_session(HttpClientSession*,
> IOBufferReader*)+0x38a) [0x5b089a]
> traffic_server(HttpClientSession::new_transaction()+0x9f) [0x58f54f]
> traffic_server(HttpClientSession::state_api_callout(int, void*)+0x1cf)
> [0x59086f]
> traffic_server(HttpClientSession::new_connection(NetVConnection*, bool,
> MIOBuffer*, IOBufferReader*)+0x4d9) [0x5914c9]
> traffic_server(HttpSessionAccept::accept(NetVConnection*, MIOBuffer*,
> IOBufferReader*)+0x203) [0x58bbd3]
> traffic_server(ProtocolProbeTrampoline::ioCompletionEvent(int,
> void*)+0x3c8) [0x4eb968]
> traffic_server() [0x715ebb]
> traffic_server(NetHandler::mainNetEvent(int, Event*)+0x1f2) [0x709122]
> traffic_server(EThread::execute()+0xad3) [0x737e93]
> traffic_server() [0x7368ca]
> /lib64/libpthread.so.0(+0x7f18) [0x7fc5bd15ff18]
> /lib64/libc.so.6(clone+0x6d) [0x7fc5bc112e9d]
> Aborted
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (TS-2988) ats_speed: bail out when gurl->IsWebValid() != true
[
https://issues.apache.org/jira/browse/TS-2988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otto van der Schaaf updated TS-2988:
Fix Version/s: 5.1.0
> ats_speed: bail out when gurl->IsWebValid() != true
> ---
>
> Key: TS-2988
> URL: https://issues.apache.org/jira/browse/TS-2988
> Project: Traffic Server
> Issue Type: Bug
> Components: Plugins
>Reporter: Otto van der Schaaf
>Assignee: Otto van der Schaaf
> Fix For: 5.1.0
>
>
> Reported via https://github.com/We-Amp/ats_speed/issues/12
> Prevent a CHECK failure by bailing out on urls that apparently can't be
> parsed as web valid. Preferrably should emit a warning about it as well, as
> it might be interesting to see which urls would fail.
> [Aug 2 19:24:21.165] Server {0x7fc5b9a05700} DIAG: (ats-speed-vlog)
> [1.7.30.4-3847] [0802/192421:FATAL:ats_speed.cc(719)] Check failed:
> ctx->gurl->IsWebValid(). Invalid URL!
> Backtrace:
> /usr/libexec/trafficserver/ats_speed.so(+0x88f8a) [0x7fc5b6e26f8a]
> /usr/libexec/trafficserver/ats_speed.so(+0x7b9d0) [0x7fc5b6e199d0]
> /usr/libexec/trafficserver/ats_speed.so(+0x85fc9) [0x7fc5b6e23fc9]
>
> /usr/libexec/trafficserver/ats_speed.so(handle_read_request_header(tsapi_httptxn*)+0x49d)
> [0x7fc5b6e209cd]
> /usr/libexec/trafficserver/ats_speed.so(+0x83218) [0x7fc5b6e21218]
> traffic_server(HttpSM::state_api_callout(int, void*)+0x102) [0x5abee2]
> traffic_server(HttpSM::state_api_callback(int, void*)+0x82) [0x5b0c22]
> traffic_server(TSHttpTxnReenable+0x244) [0x4c8494]
> /usr/libexec/trafficserver/gzip.so(+0x742b) [0x7fc5b765842b]
> traffic_server(HttpSM::state_api_callout(int, void*)+0x102) [0x5abee2]
> traffic_server(HttpSM::set_next_state()+0x1db) [0x5b0efb]
> traffic_server(HttpSM::state_read_client_request_header(int,
> void*)+0x38f) [0x5a4c9f]
> traffic_server(HttpSM::main_handler(int, void*)+0xbd) [0x5b0a3d]
> traffic_server(HttpSM::state_api_callout(int, void*)+0x2c0) [0x5ac0a0]
> traffic_server(HttpSM::state_add_to_list(int, void*)+0x190) [0x5aca10]
> traffic_server(HttpSM::attach_client_session(HttpClientSession*,
> IOBufferReader*)+0x38a) [0x5b089a]
> traffic_server(HttpClientSession::new_transaction()+0x9f) [0x58f54f]
> traffic_server(HttpClientSession::state_api_callout(int, void*)+0x1cf)
> [0x59086f]
> traffic_server(HttpClientSession::new_connection(NetVConnection*, bool,
> MIOBuffer*, IOBufferReader*)+0x4d9) [0x5914c9]
> traffic_server(HttpSessionAccept::accept(NetVConnection*, MIOBuffer*,
> IOBufferReader*)+0x203) [0x58bbd3]
> traffic_server(ProtocolProbeTrampoline::ioCompletionEvent(int,
> void*)+0x3c8) [0x4eb968]
> traffic_server() [0x715ebb]
> traffic_server(NetHandler::mainNetEvent(int, Event*)+0x1f2) [0x709122]
> traffic_server(EThread::execute()+0xad3) [0x737e93]
> traffic_server() [0x7368ca]
> /lib64/libpthread.so.0(+0x7f18) [0x7fc5bd15ff18]
> /lib64/libc.so.6(clone+0x6d) [0x7fc5bc112e9d]
> Aborted
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Assigned] (TS-2989) ats_speed: implement In-Place-Resource-Optimization flow
[ https://issues.apache.org/jira/browse/TS-2989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otto van der Schaaf reassigned TS-2989: --- Assignee: Otto van der Schaaf > ats_speed: implement In-Place-Resource-Optimization flow > > > Key: TS-2989 > URL: https://issues.apache.org/jira/browse/TS-2989 > Project: Traffic Server > Issue Type: Improvement > Components: Plugins >Reporter: Otto van der Schaaf >Assignee: Otto van der Schaaf > > The PageSpeed optimization libraries also support a flow where images/js/css > can be optimized on the original url. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2988) ats_speed: bail out when gurl->IsWebValid() != true
[
https://issues.apache.org/jira/browse/TS-2988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14087503#comment-14087503
]
Otto van der Schaaf commented on TS-2988:
-
Fix commited in 8abc04d
> ats_speed: bail out when gurl->IsWebValid() != true
> ---
>
> Key: TS-2988
> URL: https://issues.apache.org/jira/browse/TS-2988
> Project: Traffic Server
> Issue Type: Bug
> Components: Plugins
>Reporter: Otto van der Schaaf
>Assignee: Otto van der Schaaf
> Fix For: 5.1.0
>
>
> Reported via https://github.com/We-Amp/ats_speed/issues/12
> Prevent a CHECK failure by bailing out on urls that apparently can't be
> parsed as web valid. Preferrably should emit a warning about it as well, as
> it might be interesting to see which urls would fail.
> [Aug 2 19:24:21.165] Server {0x7fc5b9a05700} DIAG: (ats-speed-vlog)
> [1.7.30.4-3847] [0802/192421:FATAL:ats_speed.cc(719)] Check failed:
> ctx->gurl->IsWebValid(). Invalid URL!
> Backtrace:
> /usr/libexec/trafficserver/ats_speed.so(+0x88f8a) [0x7fc5b6e26f8a]
> /usr/libexec/trafficserver/ats_speed.so(+0x7b9d0) [0x7fc5b6e199d0]
> /usr/libexec/trafficserver/ats_speed.so(+0x85fc9) [0x7fc5b6e23fc9]
>
> /usr/libexec/trafficserver/ats_speed.so(handle_read_request_header(tsapi_httptxn*)+0x49d)
> [0x7fc5b6e209cd]
> /usr/libexec/trafficserver/ats_speed.so(+0x83218) [0x7fc5b6e21218]
> traffic_server(HttpSM::state_api_callout(int, void*)+0x102) [0x5abee2]
> traffic_server(HttpSM::state_api_callback(int, void*)+0x82) [0x5b0c22]
> traffic_server(TSHttpTxnReenable+0x244) [0x4c8494]
> /usr/libexec/trafficserver/gzip.so(+0x742b) [0x7fc5b765842b]
> traffic_server(HttpSM::state_api_callout(int, void*)+0x102) [0x5abee2]
> traffic_server(HttpSM::set_next_state()+0x1db) [0x5b0efb]
> traffic_server(HttpSM::state_read_client_request_header(int,
> void*)+0x38f) [0x5a4c9f]
> traffic_server(HttpSM::main_handler(int, void*)+0xbd) [0x5b0a3d]
> traffic_server(HttpSM::state_api_callout(int, void*)+0x2c0) [0x5ac0a0]
> traffic_server(HttpSM::state_add_to_list(int, void*)+0x190) [0x5aca10]
> traffic_server(HttpSM::attach_client_session(HttpClientSession*,
> IOBufferReader*)+0x38a) [0x5b089a]
> traffic_server(HttpClientSession::new_transaction()+0x9f) [0x58f54f]
> traffic_server(HttpClientSession::state_api_callout(int, void*)+0x1cf)
> [0x59086f]
> traffic_server(HttpClientSession::new_connection(NetVConnection*, bool,
> MIOBuffer*, IOBufferReader*)+0x4d9) [0x5914c9]
> traffic_server(HttpSessionAccept::accept(NetVConnection*, MIOBuffer*,
> IOBufferReader*)+0x203) [0x58bbd3]
> traffic_server(ProtocolProbeTrampoline::ioCompletionEvent(int,
> void*)+0x3c8) [0x4eb968]
> traffic_server() [0x715ebb]
> traffic_server(NetHandler::mainNetEvent(int, Event*)+0x1f2) [0x709122]
> traffic_server(EThread::execute()+0xad3) [0x737e93]
> traffic_server() [0x7368ca]
> /lib64/libpthread.so.0(+0x7f18) [0x7fc5bd15ff18]
> /lib64/libc.so.6(clone+0x6d) [0x7fc5bc112e9d]
> Aborted
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (TS-2992) EThread schedule fast_signal default
[ https://issues.apache.org/jira/browse/TS-2992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otto van der Schaaf updated TS-2992: Attachment: ethread.patch > EThread schedule fast_signal default > > > Key: TS-2992 > URL: https://issues.apache.org/jira/browse/TS-2992 > Project: Traffic Server > Issue Type: Task > Components: Core >Reporter: Otto van der Schaaf > Attachments: ethread.patch > > > For ats_speed, changing the fast_signal argument's default from false to true > in I_EThread::schedule helped improve latency when scheduling an event from > an external thread pool (up to 5 ms per scheduled operation). > This ticket at least documents this fact, and can perhaps serve as a > discussion point. Perhaps it's worth it to make a setting out of this hard > coded default. > I'm not sure that setting fast_signal to true would be a good idea in > general, as there probably is a cost to it. It was working fine for us > though, and considering ats_speed's cause (leaning towards favoring user > agents) I think it can sometimes be beneficial. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (TS-2992) EThread schedule fast_signal default
Otto van der Schaaf created TS-2992: --- Summary: EThread schedule fast_signal default Key: TS-2992 URL: https://issues.apache.org/jira/browse/TS-2992 Project: Traffic Server Issue Type: Task Components: Core Reporter: Otto van der Schaaf Attachments: ethread.patch For ats_speed, changing the fast_signal argument's default from false to true in I_EThread::schedule helped improve latency when scheduling an event from an external thread pool (up to 5 ms per scheduled operation). This ticket at least documents this fact, and can perhaps serve as a discussion point. Perhaps it's worth it to make a setting out of this hard coded default. I'm not sure that setting fast_signal to true would be a good idea in general, as there probably is a cost to it. It was working fine for us though, and considering ats_speed's cause (leaning towards favoring user agents) I think it can sometimes be beneficial. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (TS-2993) ats_speed: update towards 1.8.31.4-stable
Otto van der Schaaf created TS-2993: --- Summary: ats_speed: update towards 1.8.31.4-stable Key: TS-2993 URL: https://issues.apache.org/jira/browse/TS-2993 Project: Traffic Server Issue Type: Improvement Components: Plugins Reporter: Otto van der Schaaf A new stable mod_pagespeed release was announced yesterday[1]. Upgrade ats_speed to use the latest and greatest stable PageSpeed optimization libraries. [1] https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/mod-pagespeed-discuss/Qng-Da0IwcY/Y63-WlDHg5wJ -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (TS-2993) ats_speed: update towards 1.8.31.4-stable
[ https://issues.apache.org/jira/browse/TS-2993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otto van der Schaaf reassigned TS-2993: --- Assignee: Otto van der Schaaf > ats_speed: update towards 1.8.31.4-stable > - > > Key: TS-2993 > URL: https://issues.apache.org/jira/browse/TS-2993 > Project: Traffic Server > Issue Type: Improvement > Components: Plugins >Reporter: Otto van der Schaaf >Assignee: Otto van der Schaaf > > A new stable mod_pagespeed release was announced yesterday[1]. > Upgrade ats_speed to use the latest and greatest stable PageSpeed > optimization libraries. > [1] > https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/mod-pagespeed-discuss/Qng-Da0IwcY/Y63-WlDHg5wJ -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (TS-3005) Rename ats_speed plugin -> ats_pagespeed
[ https://issues.apache.org/jira/browse/TS-3005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otto van der Schaaf reassigned TS-3005: --- Assignee: Otto van der Schaaf > Rename ats_speed plugin -> ats_pagespeed > > > Key: TS-3005 > URL: https://issues.apache.org/jira/browse/TS-3005 > Project: Traffic Server > Issue Type: Improvement > Components: Plugins >Reporter: Otto van der Schaaf >Assignee: Otto van der Schaaf > > Renaming the plugin to ats_pagespeed just was approved by Google. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (TS-3005) Rename ats_speed plugin -> ats_pagespeed
Otto van der Schaaf created TS-3005: --- Summary: Rename ats_speed plugin -> ats_pagespeed Key: TS-3005 URL: https://issues.apache.org/jira/browse/TS-3005 Project: Traffic Server Issue Type: Improvement Components: Plugins Reporter: Otto van der Schaaf Renaming the plugin to ats_pagespeed just was approved by Google. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-3005) Rename ats_speed plugin -> ats_pagespeed
[ https://issues.apache.org/jira/browse/TS-3005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14102905#comment-14102905 ] Otto van der Schaaf commented on TS-3005: - Please wait with this one. I've been working on an upgrade to the latest pagespeed SDK plus the new in-place flow at https://github.com/apache/trafficserver/tree/oschaaf-ipro-flow I fair that renaming all these things could make things very-hard to merge, as it's not a minor change. > Rename ats_speed plugin -> ats_pagespeed > > > Key: TS-3005 > URL: https://issues.apache.org/jira/browse/TS-3005 > Project: Traffic Server > Issue Type: Improvement > Components: Plugins >Reporter: Otto van der Schaaf >Assignee: Otto van der Schaaf > Fix For: 5.1.0 > > > Renaming the plugin to ats_pagespeed just was approved by Google. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (TS-3005) Rename ats_speed plugin -> ats_pagespeed
[ https://issues.apache.org/jira/browse/TS-3005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14102905#comment-14102905 ] Otto van der Schaaf edited comment on TS-3005 at 8/19/14 9:46 PM: -- Please wait with this one. I've been working on an upgrade to the latest pagespeed SDK plus the new in-place flow at https://github.com/apache/trafficserver/tree/oschaaf-ipro-flow I fear that renaming all these things could make things very-hard to merge, as it's not a minor change. was (Author: oschaaf): Please wait with this one. I've been working on an upgrade to the latest pagespeed SDK plus the new in-place flow at https://github.com/apache/trafficserver/tree/oschaaf-ipro-flow I fair that renaming all these things could make things very-hard to merge, as it's not a minor change. > Rename ats_speed plugin -> ats_pagespeed > > > Key: TS-3005 > URL: https://issues.apache.org/jira/browse/TS-3005 > Project: Traffic Server > Issue Type: Improvement > Components: Plugins >Reporter: Otto van der Schaaf >Assignee: Otto van der Schaaf > Fix For: 5.1.0 > > > Renaming the plugin to ats_pagespeed just was approved by Google. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2988) ats_speed: bail out when gurl->IsWebValid() != true
[
https://issues.apache.org/jira/browse/TS-2988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14102931#comment-14102931
]
Otto van der Schaaf commented on TS-2988:
-
This is already fixed. Where can I find the workflow for jira issues and the
release process? Should be marked fix-version 5.1.0?
> ats_speed: bail out when gurl->IsWebValid() != true
> ---
>
> Key: TS-2988
> URL: https://issues.apache.org/jira/browse/TS-2988
> Project: Traffic Server
> Issue Type: Bug
> Components: Plugins
>Reporter: Otto van der Schaaf
>Assignee: Otto van der Schaaf
> Fix For: 5.2.0
>
>
> Reported via https://github.com/We-Amp/ats_speed/issues/12
> Prevent a CHECK failure by bailing out on urls that apparently can't be
> parsed as web valid. Preferrably should emit a warning about it as well, as
> it might be interesting to see which urls would fail.
> [Aug 2 19:24:21.165] Server {0x7fc5b9a05700} DIAG: (ats-speed-vlog)
> [1.7.30.4-3847] [0802/192421:FATAL:ats_speed.cc(719)] Check failed:
> ctx->gurl->IsWebValid(). Invalid URL!
> Backtrace:
> /usr/libexec/trafficserver/ats_speed.so(+0x88f8a) [0x7fc5b6e26f8a]
> /usr/libexec/trafficserver/ats_speed.so(+0x7b9d0) [0x7fc5b6e199d0]
> /usr/libexec/trafficserver/ats_speed.so(+0x85fc9) [0x7fc5b6e23fc9]
>
> /usr/libexec/trafficserver/ats_speed.so(handle_read_request_header(tsapi_httptxn*)+0x49d)
> [0x7fc5b6e209cd]
> /usr/libexec/trafficserver/ats_speed.so(+0x83218) [0x7fc5b6e21218]
> traffic_server(HttpSM::state_api_callout(int, void*)+0x102) [0x5abee2]
> traffic_server(HttpSM::state_api_callback(int, void*)+0x82) [0x5b0c22]
> traffic_server(TSHttpTxnReenable+0x244) [0x4c8494]
> /usr/libexec/trafficserver/gzip.so(+0x742b) [0x7fc5b765842b]
> traffic_server(HttpSM::state_api_callout(int, void*)+0x102) [0x5abee2]
> traffic_server(HttpSM::set_next_state()+0x1db) [0x5b0efb]
> traffic_server(HttpSM::state_read_client_request_header(int,
> void*)+0x38f) [0x5a4c9f]
> traffic_server(HttpSM::main_handler(int, void*)+0xbd) [0x5b0a3d]
> traffic_server(HttpSM::state_api_callout(int, void*)+0x2c0) [0x5ac0a0]
> traffic_server(HttpSM::state_add_to_list(int, void*)+0x190) [0x5aca10]
> traffic_server(HttpSM::attach_client_session(HttpClientSession*,
> IOBufferReader*)+0x38a) [0x5b089a]
> traffic_server(HttpClientSession::new_transaction()+0x9f) [0x58f54f]
> traffic_server(HttpClientSession::state_api_callout(int, void*)+0x1cf)
> [0x59086f]
> traffic_server(HttpClientSession::new_connection(NetVConnection*, bool,
> MIOBuffer*, IOBufferReader*)+0x4d9) [0x5914c9]
> traffic_server(HttpSessionAccept::accept(NetVConnection*, MIOBuffer*,
> IOBufferReader*)+0x203) [0x58bbd3]
> traffic_server(ProtocolProbeTrampoline::ioCompletionEvent(int,
> void*)+0x3c8) [0x4eb968]
> traffic_server() [0x715ebb]
> traffic_server(NetHandler::mainNetEvent(int, Event*)+0x1f2) [0x709122]
> traffic_server(EThread::execute()+0xad3) [0x737e93]
> traffic_server() [0x7368ca]
> /lib64/libpthread.so.0(+0x7f18) [0x7fc5bd15ff18]
> /lib64/libc.so.6(clone+0x6d) [0x7fc5bc112e9d]
> Aborted
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (TS-2989) ats_speed: implement In-Place-Resource-Optimization flow
[ https://issues.apache.org/jira/browse/TS-2989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14109114#comment-14109114 ] Otto van der Schaaf commented on TS-2989: - Working on this at https://github.com/apache/trafficserver/tree/oschaaf-ipro-flow Codewise it is ready, but I need to test it more thoroughly before committing it to master > ats_speed: implement In-Place-Resource-Optimization flow > > > Key: TS-2989 > URL: https://issues.apache.org/jira/browse/TS-2989 > Project: Traffic Server > Issue Type: Improvement > Components: Plugins >Reporter: Otto van der Schaaf >Assignee: Otto van der Schaaf > Fix For: sometime > > > The PageSpeed optimization libraries also support a flow where images/js/css > can be optimized on the original url. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (TS-3003) Remove overwriting of robots.txt in page speed plugin
[ https://issues.apache.org/jira/browse/TS-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otto van der Schaaf resolved TS-3003. - Resolution: Fixed > Remove overwriting of robots.txt in page speed plugin > - > > Key: TS-3003 > URL: https://issues.apache.org/jira/browse/TS-3003 > Project: Traffic Server > Issue Type: Bug > Components: Plugins >Reporter: Christian Grobmeier >Assignee: Otto van der Schaaf > Fix For: 5.1.0 > > > Currently the page speed plugin overwrites /robots.txt with its own content. > This leads to problems in our setup, as Google cannot index our cached > website. > The following lines: > https://github.com/apache/trafficserver/blob/master/plugins/experimental/ats_speed/ats_resource_intercept.cc#L281-L286 > demonstrate how page speed subdues our own robots.txt and overwrites it with > own content for unknown reasons. > Also the second if/else can be removed as it currently has no further use. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-3003) Remove overwriting of robots.txt in page speed plugin
[ https://issues.apache.org/jira/browse/TS-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14109116#comment-14109116 ] Otto van der Schaaf commented on TS-3003: - This is fixed via 335cbf4100e79c9333a4a4d06cce1d17149c4935 on master (5.1.x too via afa93fa9277f0cab6446b46b782971c88bfdb8ef) Changing fix version to 5.1.x and marking as resolved. > Remove overwriting of robots.txt in page speed plugin > - > > Key: TS-3003 > URL: https://issues.apache.org/jira/browse/TS-3003 > Project: Traffic Server > Issue Type: Bug > Components: Plugins >Reporter: Christian Grobmeier >Assignee: Otto van der Schaaf > Fix For: 5.1.0 > > > Currently the page speed plugin overwrites /robots.txt with its own content. > This leads to problems in our setup, as Google cannot index our cached > website. > The following lines: > https://github.com/apache/trafficserver/blob/master/plugins/experimental/ats_speed/ats_resource_intercept.cc#L281-L286 > demonstrate how page speed subdues our own robots.txt and overwrites it with > own content for unknown reasons. > Also the second if/else can be removed as it currently has no further use. -- This message was sent by Atlassian JIRA (v6.2#6252)
