You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@trafficserver.apache.org by Bryan Call <bc...@apache.org> on 2015/09/08 21:21:38 UTC
[VOTE] Release Apache Traffic Server 6.0.0 (RC0)
I've prepared a release for 6.0.0 (RC0) which is the next major version of Apache Traffic Server. This version breaks binary compatibility and plugins will need to be recompiled. This is detailed in our Release Management document:
https://cwiki.apache.org/confluence/display/TS/Release+Management
Release notes for 6.0.0:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12324897&styleName=&projectId=12310963
A summary of the new features in 6.0.0 are here:
https://cwiki.apache.org/confluence/display/TS/What%27s+New+in+6.0.x
Information about upgrading to this release from previous ones is available at:
https://cwiki.apache.org/confluence/display/TS/Upgrading+to+v6.0
The cache in this release is compatible with the previous 5.x and 4.x releases.
The artifacts are available for download at:
https://people.apache.org/~bcall/6.0.0-rc0/
MD5: d5128ccc6a2bb01cffce7cfbfb1576f5
SHA1: 5b47466a4575b4252fafb717574fed689176f670
This corresponds to git:
Hash: af8b01153ff94a2a5f8149c8852b5b585f1ddbf1
Tag: 6.0.0-rc0
Which can be verified with the following:
git tag -v 6.0.0-rc0
My code signing key is available here:
http://people.apache.org/~bcall/gpg-code-signing-key.asc
Make sure you refresh from a key server to get all relevant signatures.
The vote is open until Saturday Sept 15th, 2015.
Thank you
-Bryan
Re: [VOTE] Release Apache Traffic Server 6.0.0 (RC0)
Posted by Leif Hedstrom <zw...@apache.org>.
> On Sep 9, 2015, at 11:20 PM, Esmq <es...@163.com> wrote:
>
> hi bryan,
>
> i had got further clue~
>
> regex_remap only work for the ervery first entry in the remap.config~
>
> the other regex_remap entries will due to 404.
>
> # first entry, work for *.a.com
> regex_map http://(.*).a.com/ http://$1.a.com/ <http://$1.a.com/>
> # the following entries, doesn't work
> regex_map http://(.*).b.com/ http://$1.b.com/ <http://$1.b.com/>
Confirmed. This is a definite show stopper, so -1 on this RC.
Thanks “Esmq” and everyone for testing and finding this! Our community is awesome.
Cheers,
— Leif
Re: [VOTE] Release Apache Traffic Server 6.0.0 (RC0)
Posted by Leif Hedstrom <zw...@apache.org>.
> On Sep 9, 2015, at 11:20 PM, Esmq <es...@163.com> wrote:
>
> hi bryan,
>
> i had got further clue~
>
> regex_remap only work for the ervery first entry in the remap.config~
>
> the other regex_remap entries will due to 404.
>
> # first entry, work for *.a.com
> regex_map http://(.*).a.com/ http://$1.a.com/ <http://$1.a.com/>
> # the following entries, doesn't work
> regex_map http://(.*).b.com/ http://$1.b.com/ <http://$1.b.com/>
Confirmed. This is a definite show stopper, so -1 on this RC.
Thanks “Esmq” and everyone for testing and finding this! Our community is awesome.
Cheers,
— Leif
Re:Re: [VOTE] Release Apache Traffic Server 6.0.0 (RC0)
Posted by Esmq <es...@163.com>.
hi bryan,
i had got further clue~
regex_remap only work for the ervery first entry in the remap.config~
the other regex_remap entries will due to 404.
# first entry, work for *.a.com
regex_map http://(.*).a.com/ http://$1.a.com/
# the following entries, doesn't work
regex_map http://(.*).b.com/ http://$1.b.com/
在 2015-09-09 23:44:56,"Bryan Call" <bc...@apache.org> 写道:
I created this ticket to track the issue: https://issues.apache.org/jira/browse/TS-3897
-Bryan
On Sep 8, 2015, at 9:27 PM, Esmq <es...@163.com> wrote:
build pass on Debian 7 64bit,
but ts behaved strangely with old config that previous work for v5.3.1 (reverse proxy):
ats return HTTP/1.1 404 Not Found on Accelerator for all request ~
remap.config:
regex_map http://(.*).aa.com/ http://$1.aa.com/
diag.log:
[Sep 9 11:49:16.506] Server {0x2b6567a0e700} NOTE: cache enabled
[Sep 9 11:49:17.890] Server {0x2b6568014700} WARNING: pcre_exec() failed with error code 0
[Sep 9 11:49:17.892] Server {0x2b6566687e00} NOTE: traffic server running
[Sep 9 11:53:32.954] Server {0x2b6568115700} WARNING: pcre_exec() failed with error code 0
[Sep 9 11:53:38.587] Server {0x2b6566687e00} WARNING: pcre_exec() failed with error code 0
[Sep 9 11:59:57.908] Server {0x2b6567c10700} WARNING: pcre_exec() failed with error code 0
[Sep 9 12:04:42.012] Server {0x2b656770b700} WARNING: pcre_exec() failed with error code 0
[Sep 9 12:05:30.299] Server {0x2b6567e12700} WARNING: pcre_exec() failed with error code 0
traffic.out(debug)
[Sep 9 12:23:43.091] Server {0x2b6567d11700} DEBUG: (dns) [HttpTransact::HandleRequest] Skipping DNS lookup for 127.0.0.1 because it's loopback
[Sep 9 12:23:53.094] Server {0x2b6567e12700} DEBUG: (dns) [HttpTransact::HandleRequest] Skipping DNS lookup for 127.0.0.1 because it's loopback
[Sep 9 12:24:03.098] Server {0x2b6567f13700} DEBUG: (dns) [HttpTransact::HandleRequest] Skipping DNS lookup for 127.0.0.1 because it's loopback
[Sep 9 12:24:13.102] Server {0x2b6568014700} DEBUG: (dns) [HttpTransact::HandleRequest] Skipping DNS lookup for 127.0.0.1 because it's loopback
[Sep 9 12:24:23.105] Server {0x2b6568115700} DEBUG: (dns) [HttpTransact::HandleRequest] Skipping DNS lookup for 127.0.0.1 because it's loopback
[Sep 9 12:24:33.109] Server {0x2b6566687e00} DEBUG: (dns) [HttpTransact::HandleRequest] Skipping DNS lookup for 127.0.0.1 because it's loopback
my pcre version:
ii libpcre3:amd64 1:8.30-5 amd64 Perl 5 Compatible Regular Expression Library - runtime files
ii libpcre3-dev 1:8.30-5 amd64 Perl 5 Compatible Regular Expression Library - development files
ii libpcrecpp0:amd64 1:8.30-5 amd64 Perl 5 Compatible Regular Expression Library - C++ runtime files
At 2015-09-09 11:11:50, "Bryan Call" <bc...@apache.org> wrote:
>I rsync it again and verified it worked.
>
>-Bryan
>
>
>> On Sep 8, 2015, at 7:59 PM, Leif Hedstrom <zw...@apache.org> wrote:
>>
>>
>>> On Sep 8, 2015, at 8:44 PM, Gmail <b1...@gmail.com> wrote:
>>>
>>> HI!all
>>>
>>> uncompress 6.0.0-rc0.tar.bz2 fail!
>>>
>>> trafficserver-6.0.0/lib/wccp/Wccp.h trafficserver-6.0.0/lib/wccp/WccpMeta.h trafficserver-6.0.0/lib/wccp/WccpLocal.h trafficserver-6.0.0/lib/wccp/WccpMsg.cc bzip2: Compressed file ends unexpectedly; perhaps it is corrupted? *Possible* reason follows. bzip2: Inappropriate ioctl for device Input file = (stdin), output file = (stdout) It is possible that the compressed file(s) have become corrupted. You can use the -tvv option to test integrity of such files. You can use the `bzip2recover' program to attempt to recover data from undamaged sections of corrupted files. tar: Unexpected EOF in archive tar: Unexpected EOF in archive tar: Error is not recoverable: exiting now
>>
>>
>> Confirmed, it’s broken. What’s odd is that this file got changed after the checksum files were generated:
>>
>> -
>>
>> trafficserver-6.0.0-rc0.tar.bz2
>> 08-Sep-2015 19:32 5.2M
>>
>> trafficserver-6.0.0-rc0.tar.bz2.asc
>> 08-Sep-2015 17:46 819
>>
>> trafficserver-6.0.0-rc0.tar.bz2.md5
>> 08-Sep-2015 17:45 66
>>
>> trafficserver-6.0.0-rc0.tar.bz2.sha1 08-Sep-2015 17:45 74
>>
>>
>>
>> — Leif
>>
>
Re: [VOTE] Release Apache Traffic Server 6.0.0 (RC0)
Posted by Bryan Call <bc...@apache.org>.
I created this ticket to track the issue: https://issues.apache.org/jira/browse/TS-3897 <https://issues.apache.org/jira/browse/TS-3897>
-Bryan
> On Sep 8, 2015, at 9:27 PM, Esmq <es...@163.com> wrote:
>
> build pass on Debian 7 64bit,
>
> but ts behaved strangely with old config that previous work for v5.3.1 (reverse proxy):
>
> ats return HTTP/1.1 404 Not Found on Accelerator for all request ~
>
> remap.config:
> regex_map http://(.*).aa.com/ http://$1.aa.com/
>
> diag.log:
> [Sep 9 11:49:16.506] Server {0x2b6567a0e700} NOTE: cache enabled
> [Sep 9 11:49:17.890] Server {0x2b6568014700} WARNING: pcre_exec() failed with error code 0
> [Sep 9 11:49:17.892] Server {0x2b6566687e00} NOTE: traffic server running
> [Sep 9 11:53:32.954] Server {0x2b6568115700} WARNING: pcre_exec() failed with error code 0
> [Sep 9 11:53:38.587] Server {0x2b6566687e00} WARNING: pcre_exec() failed with error code 0
> [Sep 9 11:59:57.908] Server {0x2b6567c10700} WARNING: pcre_exec() failed with error code 0
> [Sep 9 12:04:42.012] Server {0x2b656770b700} WARNING: pcre_exec() failed with error code 0
> [Sep 9 12:05:30.299] Server {0x2b6567e12700} WARNING: pcre_exec() failed with error code 0
>
> traffic.out(debug)
> [Sep 9 12:23:43.091] Server {0x2b6567d11700} DEBUG: (dns) [HttpTransact::HandleRequest] Skipping DNS lookup for 127.0.0.1 because it's loopback
> [Sep 9 12:23:53.094] Server {0x2b6567e12700} DEBUG: (dns) [HttpTransact::HandleRequest] Skipping DNS lookup for 127.0.0.1 because it's loopback
> [Sep 9 12:24:03.098] Server {0x2b6567f13700} DEBUG: (dns) [HttpTransact::HandleRequest] Skipping DNS lookup for 127.0.0.1 because it's loopback
> [Sep 9 12:24:13.102] Server {0x2b6568014700} DEBUG: (dns) [HttpTransact::HandleRequest] Skipping DNS lookup for 127.0.0.1 because it's loopback
> [Sep 9 12:24:23.105] Server {0x2b6568115700} DEBUG: (dns) [HttpTransact::HandleRequest] Skipping DNS lookup for 127.0.0.1 because it's loopback
> [Sep 9 12:24:33.109] Server {0x2b6566687e00} DEBUG: (dns) [HttpTransact::HandleRequest] Skipping DNS lookup for 127.0.0.1 because it's loopback
>
>
> my pcre version:
> ii libpcre3:amd64 1:8.30-5 amd64 Perl 5 Compatible Regular Expression Library - runtime files
> ii libpcre3-dev 1:8.30-5 amd64 Perl 5 Compatible Regular Expression Library - development files
> ii libpcrecpp0:amd64 1:8.30-5 amd64 Perl 5 Compatible Regular Expression Library - C++ runtime files
>
> At 2015-09-09 11:11:50, "Bryan Call" <bc...@apache.org> wrote:
> >I rsync it again and verified it worked.
> >
> >-Bryan
> >
> >
> >> On Sep 8, 2015, at 7:59 PM, Leif Hedstrom <zw...@apache.org> wrote:
> >>
> >>
> >>> On Sep 8, 2015, at 8:44 PM, Gmail <b1...@gmail.com> wrote:
> >>>
> >>> HI!all
> >>>
> >>> uncompress 6.0.0-rc0.tar.bz2 fail!
> >>>
> >>> trafficserver-6.0.0/lib/wccp/Wccp.h trafficserver-6.0.0/lib/wccp/WccpMeta.h trafficserver-6.0.0/lib/wccp/WccpLocal.h trafficserver-6.0.0/lib/wccp/WccpMsg.cc bzip2: Compressed file ends unexpectedly; perhaps it is corrupted? *Possible* reason follows. bzip2: Inappropriate ioctl for device Input file = (stdin), output file = (stdout) It is possible that the compressed file(s) have become corrupted. You can use the -tvv option to test integrity of such files. You can use the `bzip2recover' program to attempt to recover data from undamaged sections of corrupted files. tar: Unexpected EOF in archive tar: Unexpected EOF in archive tar: Error is not recoverable: exiting now
> >>
> >>
> >> Confirmed, it’s broken. What’s odd is that this file got changed after the checksum files were generated:
> >>
> >> -
> >>
> >> trafficserver-6.0.0-rc0.tar.bz2
> >> 08-Sep-2015 19:32 5.2M
> >>
> >> trafficserver-6.0.0-rc0.tar.bz2.asc
> >> 08-Sep-2015 17:46 819
> >>
> >> trafficserver-6.0.0-rc0.tar.bz2.md5
> >> 08-Sep-2015 17:45 66
> >>
> >> trafficserver-6.0.0-rc0.tar.bz2.sha1 08-Sep-2015 17:45 74
> >>
> >>
> >>
> >> — Leif
> >>
> >
>
>
>
Re: Re: Re: [VOTE] Release Apache Traffic Server 6.0.0 (RC0)
Posted by Brian Geffon <br...@gmail.com>.
Right, the reason that's logging is likely due to synthetic checks which
are done as 127.0.0.1. Your assessment seems correct that the pcre_exec
calls failing are the likely issue.
This might be related to commit 2f3251a2e31abcdd6a94d94dc53ddc2457e64d19
Brian
On Wed, Sep 9, 2015 at 4:12 PM, Esmq <es...@163.com> wrote:
> 1) i don't have any entries that related to 127.0.0.1
> "Skipping DNS lookup for 127.0.0.1 because xxx" , this messages emits
> every 10 seconds in traffic.out when turn on debug. it may not the problem .
>
> 2) i think the pcre_exec and regex_map is the probleam.
> the following message appears for eath access.
> [Sep 9 16:07:43.531] Server {0x2b50afc92700} WARNING: pcre_exec() failed
> with error code 0
>
> if i use map http://xxx/ http://xxx/ insteand, it works fine...
> when use regex_map, problem occurs.
>
> 在 2015-09-09 15:35:25,"Brian Geffon" <br...@apache.org> 写道:
>
> Yes, there was an optimization added that will prevent a lookup if remap
> contains "127.0.0.1" or "::1" as these would previously end up hitting
> hostdb unnecessarily. Do you have entires in remap that map to a loopback
> interface via 127.0.0.1 or ::1?
>
> Brian
>
> On Wed, Sep 9, 2015 at 12:27 PM, Esmq <es...@163.com> wrote:
>
>> build pass on Debian 7 64bit,
>>
>> but ts behaved strangely with old config that previous work for v5.3.1
>> (reverse proxy):
>>
>> ats return HTTP/1.1 404 Not Found on Accelerator for all request ~
>>
>> remap.config:
>> regex_map http://(.*).aa.com/ http://$
>> 1.aa.com/
>>
>> diag.log:
>> [Sep 9 11:49:16.506] Server {0x2b6567a0e700} NOTE: cache enabled
>> [Sep 9 11:49:17.890] Server {0x2b6568014700} WARNING: pcre_exec() failed
>> with error code 0
>> [Sep 9 11:49:17.892] Server {0x2b6566687e00} NOTE: traffic server running
>> [Sep 9 11:53:32.954] Server {0x2b6568115700} WARNING: pcre_exec() failed
>> with error code 0
>> [Sep 9 11:53:38.587] Server {0x2b6566687e00} WARNING: pcre_exec() failed
>> with error code 0
>> [Sep 9 11:59:57.908] Server {0x2b6567c10700} WARNING: pcre_exec() failed
>> with error code 0
>> [Sep 9 12:04:42.012] Server {0x2b656770b700} WARNING: pcre_exec() failed
>> with error code 0
>> [Sep 9 12:05:30.299] Server {0x2b6567e12700} WARNING: pcre_exec() failed
>> with error code 0
>>
>> traffic.out(debug)
>> [Sep 9 12:23:43.091] Server {0x2b6567d11700} DEBUG: (dns)
>> [HttpTransact::HandleRequest] Skipping DNS lookup for 127.0.0.1 because
>> it's loopback
>> [Sep 9 12:23:53.094] Server {0x2b6567e12700} DEBUG: (dns)
>> [HttpTransact::HandleRequest] Skipping DNS lookup for 127.0.0.1 because
>> it's loopback
>> [Sep 9 12:24:03.098] Server {0x2b6567f13700} DEBUG: (dns)
>> [HttpTransact::HandleRequest] Skipping DNS lookup for 127.0.0.1 because
>> it's loopback
>> [Sep 9 12:24:13.102] Server {0x2b6568014700} DEBUG: (dns)
>> [HttpTransact::HandleRequest] Skipping DNS lookup for 127.0.0.1 because
>> it's loopback
>> [Sep 9 12:24:23.105] Server {0x2b6568115700} DEBUG: (dns)
>> [HttpTransact::HandleRequest] Skipping DNS lookup for 127.0.0.1 because
>> it's loopback
>> [Sep 9 12:24:33.109] Server {0x2b6566687e00} DEBUG: (dns)
>> [HttpTransact::HandleRequest] Skipping DNS lookup for 127.0.0.1 because
>> it's loopback
>>
>>
>> my pcre version:
>> ii libpcre3:amd64 1:8.30-5
>> amd64 Perl 5 Compatible Regular Expression Library - runtime files
>> ii libpcre3-dev 1:8.30-5
>> amd64 Perl 5 Compatible Regular Expression Library - development
>> files
>> ii libpcrecpp0:amd64 1:8.30-5
>> amd64 Perl 5 Compatible Regular Expression Library - C++ runtime
>> files
>>
>>
>> At 2015-09-09 11:11:50, "Bryan Call" <bc...@apache.org> wrote:
>> >I rsync it again and verified it worked.
>> >
>> >-Bryan
>> >
>> >
>> >> On Sep 8, 2015, at 7:59 PM, Leif Hedstrom <zw...@apache.org> wrote:
>> >>
>> >>
>> >>> On Sep 8, 2015, at 8:44 PM, Gmail <b1...@gmail.com> wrote:
>> >>>
>> >>> HI!all
>> >>>
>> >>> uncompress 6.0.0-rc0.tar.bz2 fail!
>> >>>
>> >>> trafficserver-6.0.0/lib/wccp/Wccp.h trafficserver-6.0.0/lib/wccp/WccpMeta.h trafficserver-6.0.0/lib/wccp/WccpLocal.h trafficserver-6.0.0/lib/wccp/WccpMsg.cc bzip2: Compressed file ends unexpectedly; perhaps it is corrupted? *Possible* reason follows. bzip2: Inappropriate ioctl for device Input file = (stdin), output file = (stdout) It is possible that the compressed file(s) have become corrupted. You can use the -tvv option to test integrity of such files. You can use the `bzip2recover' program to attempt to recover data from undamaged sections of corrupted files. tar: Unexpected EOF in archive tar: Unexpected EOF in archive tar: Error is not recoverable: exiting now
>> >>
>> >>
>> >> Confirmed, it’s broken. What’s odd is that this file got changed after the checksum files were generated:
>> >>
>> >> -
>> >>
>> >> trafficserver-6.0.0-rc0.tar.bz2
>> >> 08-Sep-2015 19:32 5.2M
>> >>
>> >> trafficserver-6.0.0-rc0.tar.bz2.asc
>> >> 08-Sep-2015 17:46 819
>> >>
>> >> trafficserver-6.0.0-rc0.tar.bz2.md5
>> >> 08-Sep-2015 17:45 66
>> >>
>> >> trafficserver-6.0.0-rc0.tar.bz2.sha1 08-Sep-2015 17:45 74
>> >>
>> >>
>> >>
>> >> — Leif
>> >>
>> >
>>
>>
>>
>>
>>
>
>
>
>
>
Re:Re: Re: [VOTE] Release Apache Traffic Server 6.0.0 (RC0)
Posted by Esmq <es...@163.com>.
1) i don't have any entries that related to 127.0.0.1
"Skipping DNS lookup for 127.0.0.1 because xxx" , this messages emits every 10 seconds in traffic.out when turn on debug. it may not the problem .
2) i think the pcre_exec and regex_map is the probleam.
the following message appears for eath access.
[Sep 9 16:07:43.531] Server {0x2b50afc92700} WARNING: pcre_exec() failed with error code 0
if i use map http://xxx/http://xxx/ insteand, it works fine...
when use regex_map, problem occurs.
在 2015-09-09 15:35:25,"Brian Geffon" <br...@apache.org> 写道:
Yes, there was an optimization added that will prevent a lookup if remap contains "127.0.0.1" or "::1" as these would previously end up hitting hostdb unnecessarily. Do you have entires in remap that map to a loopback interface via 127.0.0.1 or ::1?
Brian
On Wed, Sep 9, 2015 at 12:27 PM, Esmq <es...@163.com> wrote:
build pass on Debian 7 64bit,
but ts behaved strangely with old config that previous work for v5.3.1 (reverse proxy):
ats return HTTP/1.1 404 Not Found on Accelerator for all request ~
remap.config:
regex_map http://(.*).aa.com/ http://$1.aa.com/
diag.log:
[Sep 9 11:49:16.506] Server {0x2b6567a0e700} NOTE: cache enabled
[Sep 9 11:49:17.890] Server {0x2b6568014700} WARNING: pcre_exec() failed with error code 0
[Sep 9 11:49:17.892] Server {0x2b6566687e00} NOTE: traffic server running
[Sep 9 11:53:32.954] Server {0x2b6568115700} WARNING: pcre_exec() failed with error code 0
[Sep 9 11:53:38.587] Server {0x2b6566687e00} WARNING: pcre_exec() failed with error code 0
[Sep 9 11:59:57.908] Server {0x2b6567c10700} WARNING: pcre_exec() failed with error code 0
[Sep 9 12:04:42.012] Server {0x2b656770b700} WARNING: pcre_exec() failed with error code 0
[Sep 9 12:05:30.299] Server {0x2b6567e12700} WARNING: pcre_exec() failed with error code 0
traffic.out(debug)
[Sep 9 12:23:43.091] Server {0x2b6567d11700} DEBUG: (dns) [HttpTransact::HandleRequest] Skipping DNS lookup for 127.0.0.1 because it's loopback
[Sep 9 12:23:53.094] Server {0x2b6567e12700} DEBUG: (dns) [HttpTransact::HandleRequest] Skipping DNS lookup for 127.0.0.1 because it's loopback
[Sep 9 12:24:03.098] Server {0x2b6567f13700} DEBUG: (dns) [HttpTransact::HandleRequest] Skipping DNS lookup for 127.0.0.1 because it's loopback
[Sep 9 12:24:13.102] Server {0x2b6568014700} DEBUG: (dns) [HttpTransact::HandleRequest] Skipping DNS lookup for 127.0.0.1 because it's loopback
[Sep 9 12:24:23.105] Server {0x2b6568115700} DEBUG: (dns) [HttpTransact::HandleRequest] Skipping DNS lookup for 127.0.0.1 because it's loopback
[Sep 9 12:24:33.109] Server {0x2b6566687e00} DEBUG: (dns) [HttpTransact::HandleRequest] Skipping DNS lookup for 127.0.0.1 because it's loopback
my pcre version:
ii libpcre3:amd64 1:8.30-5 amd64 Perl 5 Compatible Regular Expression Library - runtime files
ii libpcre3-dev 1:8.30-5 amd64 Perl 5 Compatible Regular Expression Library - development files
ii libpcrecpp0:amd64 1:8.30-5 amd64 Perl 5 Compatible Regular Expression Library - C++ runtime files
At 2015-09-09 11:11:50, "Bryan Call" <bc...@apache.org> wrote:
>I rsync it again and verified it worked.
>
>-Bryan
>
>
>> On Sep 8, 2015, at 7:59 PM, Leif Hedstrom <zw...@apache.org> wrote:
>>
>>
>>> On Sep 8, 2015, at 8:44 PM, Gmail <b1...@gmail.com> wrote:
>>>
>>> HI!all
>>>
>>> uncompress 6.0.0-rc0.tar.bz2 fail!
>>>
>>> trafficserver-6.0.0/lib/wccp/Wccp.h trafficserver-6.0.0/lib/wccp/WccpMeta.h trafficserver-6.0.0/lib/wccp/WccpLocal.h trafficserver-6.0.0/lib/wccp/WccpMsg.cc bzip2: Compressed file ends unexpectedly; perhaps it is corrupted? *Possible* reason follows. bzip2: Inappropriate ioctl for device Input file = (stdin), output file = (stdout) It is possible that the compressed file(s) have become corrupted. You can use the -tvv option to test integrity of such files. You can use the `bzip2recover' program to attempt to recover data from undamaged sections of corrupted files. tar: Unexpected EOF in archive tar: Unexpected EOF in archive tar: Error is not recoverable: exiting now
>>
>>
>> Confirmed, it’s broken. What’s odd is that this file got changed after the checksum files were generated:
>>
>> -
>>
>> trafficserver-6.0.0-rc0.tar.bz2
>> 08-Sep-2015 19:32 5.2M
>>
>> trafficserver-6.0.0-rc0.tar.bz2.asc
>> 08-Sep-2015 17:46 819
>>
>> trafficserver-6.0.0-rc0.tar.bz2.md5
>> 08-Sep-2015 17:45 66
>>
>> trafficserver-6.0.0-rc0.tar.bz2.sha1 08-Sep-2015 17:45 74
>>
>>
>>
>> — Leif
>>
>
Re: Re: [VOTE] Release Apache Traffic Server 6.0.0 (RC0)
Posted by Brian Geffon <br...@apache.org>.
Yes, there was an optimization added that will prevent a lookup if remap
contains "127.0.0.1" or "::1" as these would previously end up hitting
hostdb unnecessarily. Do you have entires in remap that map to a loopback
interface via 127.0.0.1 or ::1?
Brian
On Wed, Sep 9, 2015 at 12:27 PM, Esmq <es...@163.com> wrote:
> build pass on Debian 7 64bit,
>
> but ts behaved strangely with old config that previous work for v5.3.1
> (reverse proxy):
>
> ats return HTTP/1.1 404 Not Found on Accelerator for all request ~
>
> remap.config:
> regex_map http://(.*).aa.com/ http://$
> 1.aa.com/
>
> diag.log:
> [Sep 9 11:49:16.506] Server {0x2b6567a0e700} NOTE: cache enabled
> [Sep 9 11:49:17.890] Server {0x2b6568014700} WARNING: pcre_exec() failed
> with error code 0
> [Sep 9 11:49:17.892] Server {0x2b6566687e00} NOTE: traffic server running
> [Sep 9 11:53:32.954] Server {0x2b6568115700} WARNING: pcre_exec() failed
> with error code 0
> [Sep 9 11:53:38.587] Server {0x2b6566687e00} WARNING: pcre_exec() failed
> with error code 0
> [Sep 9 11:59:57.908] Server {0x2b6567c10700} WARNING: pcre_exec() failed
> with error code 0
> [Sep 9 12:04:42.012] Server {0x2b656770b700} WARNING: pcre_exec() failed
> with error code 0
> [Sep 9 12:05:30.299] Server {0x2b6567e12700} WARNING: pcre_exec() failed
> with error code 0
>
> traffic.out(debug)
> [Sep 9 12:23:43.091] Server {0x2b6567d11700} DEBUG: (dns)
> [HttpTransact::HandleRequest] Skipping DNS lookup for 127.0.0.1 because
> it's loopback
> [Sep 9 12:23:53.094] Server {0x2b6567e12700} DEBUG: (dns)
> [HttpTransact::HandleRequest] Skipping DNS lookup for 127.0.0.1 because
> it's loopback
> [Sep 9 12:24:03.098] Server {0x2b6567f13700} DEBUG: (dns)
> [HttpTransact::HandleRequest] Skipping DNS lookup for 127.0.0.1 because
> it's loopback
> [Sep 9 12:24:13.102] Server {0x2b6568014700} DEBUG: (dns)
> [HttpTransact::HandleRequest] Skipping DNS lookup for 127.0.0.1 because
> it's loopback
> [Sep 9 12:24:23.105] Server {0x2b6568115700} DEBUG: (dns)
> [HttpTransact::HandleRequest] Skipping DNS lookup for 127.0.0.1 because
> it's loopback
> [Sep 9 12:24:33.109] Server {0x2b6566687e00} DEBUG: (dns)
> [HttpTransact::HandleRequest] Skipping DNS lookup for 127.0.0.1 because
> it's loopback
>
>
> my pcre version:
> ii libpcre3:amd64 1:8.30-5
> amd64 Perl 5 Compatible Regular Expression Library - runtime files
> ii libpcre3-dev 1:8.30-5
> amd64 Perl 5 Compatible Regular Expression Library - development
> files
> ii libpcrecpp0:amd64 1:8.30-5
> amd64 Perl 5 Compatible Regular Expression Library - C++ runtime
> files
>
>
> At 2015-09-09 11:11:50, "Bryan Call" <bc...@apache.org> wrote:
> >I rsync it again and verified it worked.
> >
> >-Bryan
> >
> >
> >> On Sep 8, 2015, at 7:59 PM, Leif Hedstrom <zw...@apache.org> wrote:
> >>
> >>
> >>> On Sep 8, 2015, at 8:44 PM, Gmail <b1...@gmail.com> wrote:
> >>>
> >>> HI!all
> >>>
> >>> uncompress 6.0.0-rc0.tar.bz2 fail!
> >>>
> >>> trafficserver-6.0.0/lib/wccp/Wccp.h trafficserver-6.0.0/lib/wccp/WccpMeta.h trafficserver-6.0.0/lib/wccp/WccpLocal.h trafficserver-6.0.0/lib/wccp/WccpMsg.cc bzip2: Compressed file ends unexpectedly; perhaps it is corrupted? *Possible* reason follows. bzip2: Inappropriate ioctl for device Input file = (stdin), output file = (stdout) It is possible that the compressed file(s) have become corrupted. You can use the -tvv option to test integrity of such files. You can use the `bzip2recover' program to attempt to recover data from undamaged sections of corrupted files. tar: Unexpected EOF in archive tar: Unexpected EOF in archive tar: Error is not recoverable: exiting now
> >>
> >>
> >> Confirmed, it’s broken. What’s odd is that this file got changed after the checksum files were generated:
> >>
> >> -
> >>
> >> trafficserver-6.0.0-rc0.tar.bz2
> >> 08-Sep-2015 19:32 5.2M
> >>
> >> trafficserver-6.0.0-rc0.tar.bz2.asc
> >> 08-Sep-2015 17:46 819
> >>
> >> trafficserver-6.0.0-rc0.tar.bz2.md5
> >> 08-Sep-2015 17:45 66
> >>
> >> trafficserver-6.0.0-rc0.tar.bz2.sha1 08-Sep-2015 17:45 74
> >>
> >>
> >>
> >> — Leif
> >>
> >
>
>
>
>
>
Re:Re: [VOTE] Release Apache Traffic Server 6.0.0 (RC0)
Posted by Esmq <es...@163.com>.
build pass on Debian 7 64bit,
but ts behaved strangely with old config that previous work for v5.3.1 (reverse proxy):
ats return HTTP/1.1 404 Not Found on Accelerator for all request ~
remap.config:
regex_map http://(.*).aa.com/ http://$1.aa.com/
diag.log:
[Sep 9 11:49:16.506] Server {0x2b6567a0e700} NOTE: cache enabled
[Sep 9 11:49:17.890] Server {0x2b6568014700} WARNING: pcre_exec() failed with error code 0
[Sep 9 11:49:17.892] Server {0x2b6566687e00} NOTE: traffic server running
[Sep 9 11:53:32.954] Server {0x2b6568115700} WARNING: pcre_exec() failed with error code 0
[Sep 9 11:53:38.587] Server {0x2b6566687e00} WARNING: pcre_exec() failed with error code 0
[Sep 9 11:59:57.908] Server {0x2b6567c10700} WARNING: pcre_exec() failed with error code 0
[Sep 9 12:04:42.012] Server {0x2b656770b700} WARNING: pcre_exec() failed with error code 0
[Sep 9 12:05:30.299] Server {0x2b6567e12700} WARNING: pcre_exec() failed with error code 0
traffic.out(debug)
[Sep 9 12:23:43.091] Server {0x2b6567d11700} DEBUG: (dns) [HttpTransact::HandleRequest] Skipping DNS lookup for 127.0.0.1 because it's loopback
[Sep 9 12:23:53.094] Server {0x2b6567e12700} DEBUG: (dns) [HttpTransact::HandleRequest] Skipping DNS lookup for 127.0.0.1 because it's loopback
[Sep 9 12:24:03.098] Server {0x2b6567f13700} DEBUG: (dns) [HttpTransact::HandleRequest] Skipping DNS lookup for 127.0.0.1 because it's loopback
[Sep 9 12:24:13.102] Server {0x2b6568014700} DEBUG: (dns) [HttpTransact::HandleRequest] Skipping DNS lookup for 127.0.0.1 because it's loopback
[Sep 9 12:24:23.105] Server {0x2b6568115700} DEBUG: (dns) [HttpTransact::HandleRequest] Skipping DNS lookup for 127.0.0.1 because it's loopback
[Sep 9 12:24:33.109] Server {0x2b6566687e00} DEBUG: (dns) [HttpTransact::HandleRequest] Skipping DNS lookup for 127.0.0.1 because it's loopback
my pcre version:
ii libpcre3:amd64 1:8.30-5 amd64 Perl 5 Compatible Regular Expression Library - runtime files
ii libpcre3-dev 1:8.30-5 amd64 Perl 5 Compatible Regular Expression Library - development files
ii libpcrecpp0:amd64 1:8.30-5 amd64 Perl 5 Compatible Regular Expression Library - C++ runtime files
At 2015-09-09 11:11:50, "Bryan Call" <bc...@apache.org> wrote:
>I rsync it again and verified it worked.
>
>-Bryan
>
>
>> On Sep 8, 2015, at 7:59 PM, Leif Hedstrom <zw...@apache.org> wrote:
>>
>>
>>> On Sep 8, 2015, at 8:44 PM, Gmail <b1...@gmail.com> wrote:
>>>
>>> HI!all
>>>
>>> uncompress 6.0.0-rc0.tar.bz2 fail!
>>>
>>> trafficserver-6.0.0/lib/wccp/Wccp.h trafficserver-6.0.0/lib/wccp/WccpMeta.h trafficserver-6.0.0/lib/wccp/WccpLocal.h trafficserver-6.0.0/lib/wccp/WccpMsg.cc bzip2: Compressed file ends unexpectedly; perhaps it is corrupted? *Possible* reason follows. bzip2: Inappropriate ioctl for device Input file = (stdin), output file = (stdout) It is possible that the compressed file(s) have become corrupted. You can use the -tvv option to test integrity of such files. You can use the `bzip2recover' program to attempt to recover data from undamaged sections of corrupted files. tar: Unexpected EOF in archive tar: Unexpected EOF in archive tar: Error is not recoverable: exiting now
>>
>>
>> Confirmed, it’s broken. What’s odd is that this file got changed after the checksum files were generated:
>>
>> -
>>
>> trafficserver-6.0.0-rc0.tar.bz2
>> 08-Sep-2015 19:32 5.2M
>>
>> trafficserver-6.0.0-rc0.tar.bz2.asc
>> 08-Sep-2015 17:46 819
>>
>> trafficserver-6.0.0-rc0.tar.bz2.md5
>> 08-Sep-2015 17:45 66
>>
>> trafficserver-6.0.0-rc0.tar.bz2.sha1 08-Sep-2015 17:45 74
>>
>>
>>
>> — Leif
>>
>
Re: [VOTE] Release Apache Traffic Server 6.0.0 (RC0)
Posted by Bryan Call <bc...@apache.org>.
I rsync it again and verified it worked.
-Bryan
> On Sep 8, 2015, at 7:59 PM, Leif Hedstrom <zw...@apache.org> wrote:
>
>
>> On Sep 8, 2015, at 8:44 PM, Gmail <b1...@gmail.com> wrote:
>>
>> HI!all
>>
>> uncompress 6.0.0-rc0.tar.bz2 fail!
>>
>> trafficserver-6.0.0/lib/wccp/Wccp.h trafficserver-6.0.0/lib/wccp/WccpMeta.h trafficserver-6.0.0/lib/wccp/WccpLocal.h trafficserver-6.0.0/lib/wccp/WccpMsg.cc bzip2: Compressed file ends unexpectedly; perhaps it is corrupted? *Possible* reason follows. bzip2: Inappropriate ioctl for device Input file = (stdin), output file = (stdout) It is possible that the compressed file(s) have become corrupted. You can use the -tvv option to test integrity of such files. You can use the `bzip2recover' program to attempt to recover data from undamaged sections of corrupted files. tar: Unexpected EOF in archive tar: Unexpected EOF in archive tar: Error is not recoverable: exiting now
>
>
> Confirmed, it’s broken. What’s odd is that this file got changed after the checksum files were generated:
>
> -
>
> trafficserver-6.0.0-rc0.tar.bz2
> 08-Sep-2015 19:32 5.2M
>
> trafficserver-6.0.0-rc0.tar.bz2.asc
> 08-Sep-2015 17:46 819
>
> trafficserver-6.0.0-rc0.tar.bz2.md5
> 08-Sep-2015 17:45 66
>
> trafficserver-6.0.0-rc0.tar.bz2.sha1 08-Sep-2015 17:45 74
>
>
>
> — Leif
>
Re: [VOTE] Release Apache Traffic Server 6.0.0 (RC0)
Posted by Leif Hedstrom <zw...@apache.org>.
> On Sep 8, 2015, at 8:44 PM, Gmail <b1...@gmail.com> wrote:
>
> HI!all
>
> uncompress 6.0.0-rc0.tar.bz2 fail!
>
> trafficserver-6.0.0/lib/wccp/Wccp.h trafficserver-6.0.0/lib/wccp/WccpMeta.h trafficserver-6.0.0/lib/wccp/WccpLocal.h trafficserver-6.0.0/lib/wccp/WccpMsg.cc bzip2: Compressed file ends unexpectedly; perhaps it is corrupted? *Possible* reason follows. bzip2: Inappropriate ioctl for device Input file = (stdin), output file = (stdout) It is possible that the compressed file(s) have become corrupted. You can use the -tvv option to test integrity of such files. You can use the `bzip2recover' program to attempt to recover data from undamaged sections of corrupted files. tar: Unexpected EOF in archive tar: Unexpected EOF in archive tar: Error is not recoverable: exiting now
Confirmed, it’s broken. What’s odd is that this file got changed after the checksum files were generated:
-
trafficserver-6.0.0-rc0.tar.bz2
08-Sep-2015 19:32 5.2M
trafficserver-6.0.0-rc0.tar.bz2.asc
08-Sep-2015 17:46 819
trafficserver-6.0.0-rc0.tar.bz2.md5
08-Sep-2015 17:45 66
trafficserver-6.0.0-rc0.tar.bz2.sha1 08-Sep-2015 17:45 74
— Leif
Re: [VOTE] Release Apache Traffic Server 6.0.0 (RC0)
Posted by Gmail <b1...@gmail.com>.
HI!all
uncompress 6.0.0-rc0.tar.bz2 fail!
trafficserver-6.0.0/lib/wccp/Wccp.h trafficserver-6.0.0/lib/wccp/WccpMeta.h trafficserver-6.0.0/lib/wccp/WccpLocal.h trafficserver-6.0.0/lib/wccp/WccpMsg.cc bzip2: Compressed file ends unexpectedly; perhaps it is corrupted? *Possible* reason follows. bzip2: Inappropriate ioctl for device Input file = (stdin), output file = (stdout) It is possible that the compressed file(s) have become corrupted. You can use the -tvv option to test integrity of such files. You can use the `bzip2recover' program to attempt to recover data from undamaged sections of corrupted files. tar: Unexpected EOF in archive tar: Unexpected EOF in archive tar: Error is not recoverable: exiting now
md5 trafficserver-6.0.0-rc0.tar.bz2
MD5 (trafficserver-6.0.0-rc0.tar.bz2) = 019f0207117cb3cbc245c4767d0f6f22
[root@builder opt]# wget https://people.apache.org/~bcall/6.0.0-rc0/trafficserver-6.0.0-rc0.tar.bz2
--2015-09-09 10:43:36-- https://people.apache.org/~bcall/6.0.0-rc0/trafficserver-6.0.0-rc0.tar.bz2
Resolving people.apache.org... 140.211.11.9
Connecting to people.apache.org|140.211.11.9|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 5448088 (5.2M) [application/x-bzip2]
Saving to: “trafficserver-6.0.0-rc0.tar.bz2”
100%[==================================================================================================>] 5,448,088 75.8K/s in 42s
2015-09-09 10:44:20 (126 KB/s) - “trafficserver-6.0.0-rc0.tar.bz2” saved [5448088/5448088]
[root@builder opt]# md5sum trafficserver-6.0.0-rc0.tar.bz2
019f0207117cb3cbc245c4767d0f6f22 trafficserver-6.0.0-rc0.tar.bz2
> 在 2015年9月9日,03:21,Bryan Call <bc...@apache.org> 写道:
>
> I've prepared a release for 6.0.0 (RC0) which is the next major version of Apache Traffic Server. This version breaks binary compatibility and plugins will need to be recompiled. This is detailed in our Release Management document:
>
> https://cwiki.apache.org/confluence/display/TS/Release+Management
>
> Release notes for 6.0.0:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12324897&styleName=&projectId=12310963
>
> A summary of the new features in 6.0.0 are here:
>
> https://cwiki.apache.org/confluence/display/TS/What%27s+New+in+6.0.x
>
> Information about upgrading to this release from previous ones is available at:
>
> https://cwiki.apache.org/confluence/display/TS/Upgrading+to+v6.0
>
> The cache in this release is compatible with the previous 5.x and 4.x releases.
>
> The artifacts are available for download at:
>
> https://people.apache.org/~bcall/6.0.0-rc0/
>
> MD5: d5128ccc6a2bb01cffce7cfbfb1576f5
> SHA1: 5b47466a4575b4252fafb717574fed689176f670
>
> This corresponds to git:
>
> Hash: af8b01153ff94a2a5f8149c8852b5b585f1ddbf1
> Tag: 6.0.0-rc0
>
> Which can be verified with the following:
>
> git tag -v 6.0.0-rc0
>
> My code signing key is available here:
>
> http://people.apache.org/~bcall/gpg-code-signing-key.asc
>
> Make sure you refresh from a key server to get all relevant signatures.
>
> The vote is open until Saturday Sept 15th, 2015.
>
> Thank you
>
> -Bryan