[jira] [Updated] (TS-4223) [Feb 23 14:20:13.554] Manager {0x7f4216adb840} ERROR: [LocalManager::pollMgmtProcessServer] select failed or was interrupted (4)

[bettydramit (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TS-4223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

bettydramit updated TS-4223:

Affects Version/s: 6.1.1

> [Feb 23 14:20:13.554] Manager {0x7f4216adb840} ERROR: 
> [LocalManager::pollMgmtProcessServer] select failed or was interrupted (4)
> 
>
> Key: TS-4223
> URL: https://issues.apache.org/jira/browse/TS-4223
> Project: Traffic Server
>  Issue Type: Bug
>Affects Versions: 6.1.1
>Reporter: bettydramit
>
> update to 6.1.1
> when exec traffic_ctl config reload
> lot of  [Feb 23 14:20:13.554] Manager {0x7f4216adb840} ERROR: 
> [LocalManager::pollMgmtProcessServer] select failed or was interrupted (4) at 
> manager.log 
> traffic.out
> traffic_ctl: configuration reload request failed: [13] Operation not 
> permitted.
> traffic_ctl: configuration reload request failed: [13] Operation not 
> permitted.
> traffic_ctl: configuration reload request failed: [13] Operation not 
> permitted.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (TS-4223) [Feb 23 14:20:13.554] Manager {0x7f4216adb840} ERROR: [LocalManager::pollMgmtProcessServer] select failed or was interrupted (4)

[bettydramit (JIRA)]

bettydramit created TS-4223:
---

 Summary: [Feb 23 14:20:13.554] Manager {0x7f4216adb840} ERROR: 
[LocalManager::pollMgmtProcessServer] select failed or was interrupted (4)
 Key: TS-4223
 URL: https://issues.apache.org/jira/browse/TS-4223
 Project: Traffic Server
  Issue Type: Bug
Reporter: bettydramit


update to 6.1.1


when exec traffic_ctl config reload

lot of  [Feb 23 14:20:13.554] Manager {0x7f4216adb840} ERROR: 
[LocalManager::pollMgmtProcessServer] select failed or was interrupted (4) at 
manager.log 

traffic.out
traffic_ctl: configuration reload request failed: [13] Operation not permitted.
traffic_ctl: configuration reload request failed: [13] Operation not permitted.
traffic_ctl: configuration reload request failed: [13] Operation not permitted.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (TS-4207) Crash in HostDB, likely a regression from 5.x

[Brian Geffon (JIRA)]

[ 
https://issues.apache.org/jira/browse/TS-4207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15158313#comment-15158313
 ] 

Brian Geffon commented on TS-4207:
--

Actually, I take that back, lookup_block could very well cause it to return the 
wrong block if number of levels is less than MAX_LEVELS. [~zwoop], I'd say give 
this patch a try sooner rather than later as it may very well be the cause of 
your problem.

> Crash in HostDB, likely a regression from 5.x
> -
>
> Key: TS-4207
> URL: https://issues.apache.org/jira/browse/TS-4207
> Project: Traffic Server
>  Issue Type: Bug
>  Components: HostDB
>Reporter: Leif Hedstrom
>Priority: Blocker
>  Labels: crash
> Fix For: 6.2.0
>
>
> We're seeing a new crash in HostDB, which did not occur in 5.3.x:
> {code}
> (gdb) bt
> #0  0x2ac7b2bb in HttpSM::process_hostdb_info(HostDBInfo*) () at 
> ../../iocore/hostdb/P_HostDBProcessor.h:295
> #1  0x2ac88b16 in HttpSM::state_hostdb_lookup(int, void*) () at 
> HttpSM.cc:2126
> #2  0x2ac9713d in HttpSM::main_handler(int, void*) () at 
> HttpSM.cc:2561
> #3  0x2ad7803e in reply_to_cont(Continuation*, HostDBInfo*, bool) () 
> at ../../iocore/eventsystem/I_Continuation.h:153
> #4  0x2ad7eca5 in HostDBContinuation::dnsEvent(int, HostEnt*) () at 
> HostDB.cc:1685
> #5  0x2ad98faf in DNSEntry::postEvent(int, Event*) () at 
> ../../iocore/eventsystem/I_Continuation.h:153
> #6  0x2ae7e420 in EThread::process_event(Event*, int) () at 
> I_Continuation.h:153
> #7  0x2ae7f2ab in EThread::execute() () at UnixEThread.cc:179
> #8  0x2ae7de06 in spawn_thread_internal(void*) () at Thread.cc:86
> #9  0x2d6ac9d1 in start_thread () from /lib64/libpthread.so.0
> #10 0x2e8b58fd in clone () from /lib64/libc.so.6
> {code}
> I think some inlining here complicates things, what it looks like the "r" is 
> NULL, but it somehow still ends up using r->rr ?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (TS-4207) Crash in HostDB, likely a regression from 5.x

[Brian Geffon (JIRA)]

[ 
https://issues.apache.org/jira/browse/TS-4207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15158304#comment-15158304
 ] 

Brian Geffon edited comment on TS-4207 at 2/23/16 5:31 AM:
---

[~msekimura] that's a good catch, but it's unlikely it's the source of the 
problem as there are always 3 levels this is hard coded as 
MULTI_CACHE_MAX_LEVELS. 

[~zwoop], can you give this patch a try? I suppose if for whatever reason you 
had a MultiCache with less than MULTI_CACHE_MAX_LEVELS that this hard coded 3 
could cause it to touch memory it shouldn't be, but it's unlikely it would 
delete the wrong block as anything beyond that point wouldn't be part of the 
multicache structure.




was (Author: briang):
[~msekimura] that's a good catch, but it's unlikely it's the source of the 
problem as there are always 3 levels this is hard coded as 
MULTI_CACHE_MAX_LEVELS.

> Crash in HostDB, likely a regression from 5.x
> -
>
> Key: TS-4207
> URL: https://issues.apache.org/jira/browse/TS-4207
> Project: Traffic Server
>  Issue Type: Bug
>  Components: HostDB
>Reporter: Leif Hedstrom
>Priority: Blocker
>  Labels: crash
> Fix For: 6.2.0
>
>
> We're seeing a new crash in HostDB, which did not occur in 5.3.x:
> {code}
> (gdb) bt
> #0  0x2ac7b2bb in HttpSM::process_hostdb_info(HostDBInfo*) () at 
> ../../iocore/hostdb/P_HostDBProcessor.h:295
> #1  0x2ac88b16 in HttpSM::state_hostdb_lookup(int, void*) () at 
> HttpSM.cc:2126
> #2  0x2ac9713d in HttpSM::main_handler(int, void*) () at 
> HttpSM.cc:2561
> #3  0x2ad7803e in reply_to_cont(Continuation*, HostDBInfo*, bool) () 
> at ../../iocore/eventsystem/I_Continuation.h:153
> #4  0x2ad7eca5 in HostDBContinuation::dnsEvent(int, HostEnt*) () at 
> HostDB.cc:1685
> #5  0x2ad98faf in DNSEntry::postEvent(int, Event*) () at 
> ../../iocore/eventsystem/I_Continuation.h:153
> #6  0x2ae7e420 in EThread::process_event(Event*, int) () at 
> I_Continuation.h:153
> #7  0x2ae7f2ab in EThread::execute() () at UnixEThread.cc:179
> #8  0x2ae7de06 in spawn_thread_internal(void*) () at Thread.cc:86
> #9  0x2d6ac9d1 in start_thread () from /lib64/libpthread.so.0
> #10 0x2e8b58fd in clone () from /lib64/libc.so.6
> {code}
> I think some inlining here complicates things, what it looks like the "r" is 
> NULL, but it somehow still ends up using r->rr ?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (TS-4207) Crash in HostDB, likely a regression from 5.x

[Brian Geffon (JIRA)]

[ 
https://issues.apache.org/jira/browse/TS-4207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15158304#comment-15158304
 ] 

Brian Geffon commented on TS-4207:
--

[~msekimura] that's a good catch, but it's unlikely it's the source of the 
problem as there are always 3 levels this is hard coded as 
MULTI_CACHE_MAX_LEVELS.

> Crash in HostDB, likely a regression from 5.x
> -
>
> Key: TS-4207
> URL: https://issues.apache.org/jira/browse/TS-4207
> Project: Traffic Server
>  Issue Type: Bug
>  Components: HostDB
>Reporter: Leif Hedstrom
>Priority: Blocker
>  Labels: crash
> Fix For: 6.2.0
>
>
> We're seeing a new crash in HostDB, which did not occur in 5.3.x:
> {code}
> (gdb) bt
> #0  0x2ac7b2bb in HttpSM::process_hostdb_info(HostDBInfo*) () at 
> ../../iocore/hostdb/P_HostDBProcessor.h:295
> #1  0x2ac88b16 in HttpSM::state_hostdb_lookup(int, void*) () at 
> HttpSM.cc:2126
> #2  0x2ac9713d in HttpSM::main_handler(int, void*) () at 
> HttpSM.cc:2561
> #3  0x2ad7803e in reply_to_cont(Continuation*, HostDBInfo*, bool) () 
> at ../../iocore/eventsystem/I_Continuation.h:153
> #4  0x2ad7eca5 in HostDBContinuation::dnsEvent(int, HostEnt*) () at 
> HostDB.cc:1685
> #5  0x2ad98faf in DNSEntry::postEvent(int, Event*) () at 
> ../../iocore/eventsystem/I_Continuation.h:153
> #6  0x2ae7e420 in EThread::process_event(Event*, int) () at 
> I_Continuation.h:153
> #7  0x2ae7f2ab in EThread::execute() () at UnixEThread.cc:179
> #8  0x2ae7de06 in spawn_thread_internal(void*) () at Thread.cc:86
> #9  0x2d6ac9d1 in start_thread () from /lib64/libpthread.so.0
> #10 0x2e8b58fd in clone () from /lib64/libc.so.6
> {code}
> I think some inlining here complicates things, what it looks like the "r" is 
> NULL, but it somehow still ends up using r->rr ?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (TS-4207) Crash in HostDB, likely a regression from 5.x

[Masa Sekimura (JIRA)]

[ 
https://issues.apache.org/jira/browse/TS-4207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15158299#comment-15158299
 ] 

Masa Sekimura commented on TS-4207:
---

I've just noticed that inside of HostDBContinuation::insert, lookup_block is 
using hardcoded value "3" for levels. It's unlikely to match that md5 value but 
it's possible match a different block due to the hardcoded value? If so, 
hostDB.delete_block(old_r) can be deleting a different block.

{code}
diff --git a/iocore/hostdb/HostDB.cc b/iocore/hostdb/HostDB.cc
index eb5b541..0101848 100644
--- a/iocore/hostdb/HostDB.cc
+++ b/iocore/hostdb/HostDB.cc
@@ -743,7 +743,7 @@ HostDBContinuation::insert(unsigned int attl)

   ink_assert(this_ethread() == hostDB.lock_for_bucket(bucket)->thread_holding);
   // remove the old one to prevent buildup
-  HostDBInfo *old_r = hostDB.lookup_block(folded_md5, 3);
+  HostDBInfo *old_r = hostDB.lookup_block(folded_md5, hostdb.levels);
   if (old_r)
 hostDB.delete_block(old_r);
   HostDBInfo *r = hostDB.insert_block(folded_md5, NULL, 0);
{code}

> Crash in HostDB, likely a regression from 5.x
> -
>
> Key: TS-4207
> URL: https://issues.apache.org/jira/browse/TS-4207
> Project: Traffic Server
>  Issue Type: Bug
>  Components: HostDB
>Reporter: Leif Hedstrom
>Priority: Blocker
>  Labels: crash
> Fix For: 6.2.0
>
>
> We're seeing a new crash in HostDB, which did not occur in 5.3.x:
> {code}
> (gdb) bt
> #0  0x2ac7b2bb in HttpSM::process_hostdb_info(HostDBInfo*) () at 
> ../../iocore/hostdb/P_HostDBProcessor.h:295
> #1  0x2ac88b16 in HttpSM::state_hostdb_lookup(int, void*) () at 
> HttpSM.cc:2126
> #2  0x2ac9713d in HttpSM::main_handler(int, void*) () at 
> HttpSM.cc:2561
> #3  0x2ad7803e in reply_to_cont(Continuation*, HostDBInfo*, bool) () 
> at ../../iocore/eventsystem/I_Continuation.h:153
> #4  0x2ad7eca5 in HostDBContinuation::dnsEvent(int, HostEnt*) () at 
> HostDB.cc:1685
> #5  0x2ad98faf in DNSEntry::postEvent(int, Event*) () at 
> ../../iocore/eventsystem/I_Continuation.h:153
> #6  0x2ae7e420 in EThread::process_event(Event*, int) () at 
> I_Continuation.h:153
> #7  0x2ae7f2ab in EThread::execute() () at UnixEThread.cc:179
> #8  0x2ae7de06 in spawn_thread_internal(void*) () at Thread.cc:86
> #9  0x2d6ac9d1 in start_thread () from /lib64/libpthread.so.0
> #10 0x2e8b58fd in clone () from /lib64/libc.so.6
> {code}
> I think some inlining here complicates things, what it looks like the "r" is 
> NULL, but it somehow still ends up using r->rr ?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (TS-4175) unset INSTALL_BASE when installing

[James Peach (JIRA)]

[ 
https://issues.apache.org/jira/browse/TS-4175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15158284#comment-15158284
 ] 

James Peach commented on TS-4175:
-

[~zwoop] does this work for you?

{code}
jpeach$ git diff
diff --git a/lib/perl/Makefile.am b/lib/perl/Makefile.am
index bfba2af..c3447fe 100644
--- a/lib/perl/Makefile.am
+++ b/lib/perl/Makefile.am
@@ -26,7 +26,7 @@ install-exec-local: Makefile-pl
 # copy them to the build directory if we are building out of tree.
 Makefile-pl: Makefile.PL
test -f "$(top_builddir)/$(subdir)/Makefile.PL" || cp -rf "$(srcdir)/." 
"$(top_builddir)/$(subdir)/"
-   $(PERL) Makefile.PL INSTALLDIRS=$(INSTALLDIRS) PREFIX=$(prefix)
+   $(PERL) Makefile.PL INSTALLDIRS=$(INSTALLDIRS) INSTALL_BASE=$(prefix) 
PREFIX=

 distclean-local:
-rm -rf Makefile-pl MYMETA.* blip
{code}

> unset INSTALL_BASE when installing
> --
>
> Key: TS-4175
> URL: https://issues.apache.org/jira/browse/TS-4175
> Project: Traffic Server
>  Issue Type: Bug
>  Components: Build, Management API
>Reporter: James Peach
>Assignee: James Peach
> Fix For: 6.2.0
>
>
> If you have CPAN set up, it will inject environment variables that break the 
> perl module installation, specifically 
> {{PERL_MM_OPT=INSTALL_BASE=/home/jpeach/perl5}}.
> The resulting error is:
> {code}
> Making all in perl
> make[3]: Entering directory '/tmp/org.apache.trafficserver.3277/obj/lib/perl'
> test -f "../../lib/perl/Makefile.PL" || cp -rf 
> "/home/jpeach/tmp/trafficserver-6.1.1/lib/perl/." "../../lib/perl/"
> /usr/bin/perl Makefile.PL INSTALLDIRS= 
> PREFIX=/tmp/org.apache.trafficserver.3277/dst
> Only one of PREFIX or INSTALL_BASE can be given.  Not both.
> Makefile:712: recipe for target 'Makefile-pl' failed
> make[3]: *** [Makefile-pl] Error 25
> make[3]: Leaving directory '/tmp/org.apache.trafficserver.3277/obj/lib/perl'
> Makefile:638: recipe for target 'all-recursive' failed
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory '/tmp/org.apache.trafficserver.3277/obj/lib'
> Makefile:577: recipe for target 'all' failed
> make[1]: *** [all] Error 2
> make[1]: Leaving directory '/tmp/org.apache.trafficserver.3277/obj/lib'
> Makefile:674: recipe for target 'all-recursive' failed
> {code}
> We ought to clear at least some of the perl environment variables when 
> installing so  that it doesn't fail in weird ways like this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (TS-4095) New cppapi plugin for converting image formats to wepb

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/TS-4095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15158280#comment-15158280
 ] 

ASF subversion and git services commented on TS-4095:
-

Commit f06708f5b502fd1eef69257a7d0a66081c749e1f in trafficserver's branch 
refs/heads/master from John J. Rushford
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=f06708f ]

TS-4095: Fix the dependency check for the webp_transform plugin

This closes #494.


> New cppapi plugin for converting image formats to wepb
> --
>
> Key: TS-4095
> URL: https://issues.apache.org/jira/browse/TS-4095
> Project: Traffic Server
>  Issue Type: New Feature
>  Components: CPP API, Plugins
>Reporter: Sandeep Davu
>Assignee: Brian Geffon
>  Labels: review
> Fix For: 6.2.0
>
>
> Support for png and jpeg only.  Webp is a format introduced by google and can 
> retain the quality of the image by reducing the image size.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (TS-3938) Add hardening (fortify) as an option to configure

[James Peach (JIRA)]

[ 
https://issues.apache.org/jira/browse/TS-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15158198#comment-15158198
 ] 

James Peach commented on TS-3938:
-

PIE only applies to executables not libraries. Since {{tsxs}} doesn't know this 
it passes it to the linker when linking a plugin and the linker chokes on it.

> Add hardening (fortify) as an option to configure
> -
>
> Key: TS-3938
> URL: https://issues.apache.org/jira/browse/TS-3938
> Project: Traffic Server
>  Issue Type: New Feature
>  Components: Build
>Reporter: Leif Hedstrom
>Assignee: Jason Kenny
> Fix For: sometime
>
>
> It might be useful to add an option, e.g. --with-hardening, such that we can 
> build with various hardening compiler options. For example. I've used
> {code}
> CC="/opt/gcc5/bin/gcc"; export CC
> CXX="/opt/gcc5/bin/g++"; export CXX
> CFLAGS="-fstack-protector -fno-omit-frame-pointer"; export CFLAGS
> CXXFLAGS="-fstack-protector -fno-omit-frame-pointer"; export CXXFLAGS
> CPPFLAGS="-D_FORTIFY_SOURCE=2"; export CPPFLAGS
> LDFLAGS="-Wl,-z,relro -Wl,-z,now"; export LDFLAGS
> "./configure" \
> "--enable-experimental-plugins" \
> "--prefix=/opt/ats" \
> "CC=/opt/gcc5/bin/gcc" \
> "CXX=/opt/gcc5/bin/g++" \
> "CFLAGS=-fstack-protector -fno-omit-frame-pointer" \
> "CXXFLAGS=-fstack-protector -fno-omit-frame-pointer" \
> "CPPFLAGS=-D_FORTIFY_SOURCE=2" \
> "LDFLAGS=-Wl,-z,relro -Wl,-z,now" \
> "$@"
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (TS-3938) Add hardening (fortify) as an option to configure

[Bryan Call (JIRA)]

[ 
https://issues.apache.org/jira/browse/TS-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15157947#comment-15157947
 ] 

Bryan Call commented on TS-3938:


[~jpe...@apache.org]

What is the issue if you don't trip the  {{-fPIE}}

> Add hardening (fortify) as an option to configure
> -
>
> Key: TS-3938
> URL: https://issues.apache.org/jira/browse/TS-3938
> Project: Traffic Server
>  Issue Type: New Feature
>  Components: Build
>Reporter: Leif Hedstrom
>Assignee: Jason Kenny
> Fix For: sometime
>
>
> It might be useful to add an option, e.g. --with-hardening, such that we can 
> build with various hardening compiler options. For example. I've used
> {code}
> CC="/opt/gcc5/bin/gcc"; export CC
> CXX="/opt/gcc5/bin/g++"; export CXX
> CFLAGS="-fstack-protector -fno-omit-frame-pointer"; export CFLAGS
> CXXFLAGS="-fstack-protector -fno-omit-frame-pointer"; export CXXFLAGS
> CPPFLAGS="-D_FORTIFY_SOURCE=2"; export CPPFLAGS
> LDFLAGS="-Wl,-z,relro -Wl,-z,now"; export LDFLAGS
> "./configure" \
> "--enable-experimental-plugins" \
> "--prefix=/opt/ats" \
> "CC=/opt/gcc5/bin/gcc" \
> "CXX=/opt/gcc5/bin/g++" \
> "CFLAGS=-fstack-protector -fno-omit-frame-pointer" \
> "CXXFLAGS=-fstack-protector -fno-omit-frame-pointer" \
> "CPPFLAGS=-D_FORTIFY_SOURCE=2" \
> "LDFLAGS=-Wl,-z,relro -Wl,-z,now" \
> "$@"
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (TS-3938) Add hardening (fortify) as an option to configure

[Bryan Call (JIRA)]

[ 
https://issues.apache.org/jira/browse/TS-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15157947#comment-15157947
 ] 

Bryan Call edited comment on TS-3938 at 2/22/16 11:31 PM:
--

[~jpe...@apache.org]

What is the issue if you don't strip the  {{-fPIE}}?


was (Author: bcall):
[~jpe...@apache.org]

What is the issue if you don't trip the  {{-fPIE}}

> Add hardening (fortify) as an option to configure
> -
>
> Key: TS-3938
> URL: https://issues.apache.org/jira/browse/TS-3938
> Project: Traffic Server
>  Issue Type: New Feature
>  Components: Build
>Reporter: Leif Hedstrom
>Assignee: Jason Kenny
> Fix For: sometime
>
>
> It might be useful to add an option, e.g. --with-hardening, such that we can 
> build with various hardening compiler options. For example. I've used
> {code}
> CC="/opt/gcc5/bin/gcc"; export CC
> CXX="/opt/gcc5/bin/g++"; export CXX
> CFLAGS="-fstack-protector -fno-omit-frame-pointer"; export CFLAGS
> CXXFLAGS="-fstack-protector -fno-omit-frame-pointer"; export CXXFLAGS
> CPPFLAGS="-D_FORTIFY_SOURCE=2"; export CPPFLAGS
> LDFLAGS="-Wl,-z,relro -Wl,-z,now"; export LDFLAGS
> "./configure" \
> "--enable-experimental-plugins" \
> "--prefix=/opt/ats" \
> "CC=/opt/gcc5/bin/gcc" \
> "CXX=/opt/gcc5/bin/g++" \
> "CFLAGS=-fstack-protector -fno-omit-frame-pointer" \
> "CXXFLAGS=-fstack-protector -fno-omit-frame-pointer" \
> "CPPFLAGS=-D_FORTIFY_SOURCE=2" \
> "LDFLAGS=-Wl,-z,relro -Wl,-z,now" \
> "$@"
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (TS-4222) ATS 6.2.0 seg faults while processing ssl_multicert.config

[Leif Hedstrom (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TS-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Leif Hedstrom updated TS-4222:
--
Fix Version/s: 6.1.2

> ATS 6.2.0 seg faults while processing ssl_multicert.config
> --
>
> Key: TS-4222
> URL: https://issues.apache.org/jira/browse/TS-4222
> Project: Traffic Server
>  Issue Type: Bug
>  Components: SSL
>Affects Versions: 6.2.0
>Reporter: Prakhar Rudra
>Assignee: Sudheer Vinukonda
> Fix For: 6.1.2, 6.2.0
>
>
> ATS version 6.2.0 segment fault error while checking config using 
> traffic_server -Cverify_config
> It occurs after  "INFO: Successfully loaded plugin.config"
> only entry in ssl_multicert.config is as below,
> dest_ip=* ssl_cert_name=fullchain1.pem ssl_key_name=privkey1.pem
> gdb --args traffic_server -Cverify_config
> (gdb) run
> yields
> INFO: Successfully loaded plugin.config
> Thread 1 "traffic_server" received signal SIGSEGV, Segmentation fault.
> 0x in ?? ()
> (gdb) print SSLConfigParams::load_ssl_file_cb
> $1 = (load_ssl_file_func) 0x0
> Thanks jpeach
> Details:
> http://pastebin.com/K0876r2T
> http://pastebin.com/iP5MAYLu
> Thanks
> Pulling the info from the above pastebin's to jira for posterity.
> {code}
> git clone https://github.com/tatsuhiro-t/spdylay.git
> cd spdylay/
> autoreconf -if
> automake
> autoconf
> ./configure --prefix=/usr
> make
> make install
> cd ../trafficserver/
> autoreconf -if
> export PKG_CONFIG_PATH=/usr/lib/pkgconfig
> ./configure --enable-spdy --enable-experimental-plugins 
> --enable-linux-native-aio --with-zlib=/root/c/ats/zlib-1.2.8 
> --with-pcre=/root/c/ats/pcre-8.38 
> --with-openssl=/root/c/ats/openssl-1.0.1f[WITH CLOUDFLARE PATCH]
> **
> gdb --args traffic_server -Cverify_config
> ...standard info..
> (gdb) run
> Starting program: /usr/local/bin/traffic_server -Cverify_config
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> traffic_server: using root directory '/usr/local'
> [New Thread 0x71f55700 (LWP 19595)]
> NOTE: VERIFY
> [New Thread 0x70c16700 (LWP 19596)]
> [New Thread 0x70a14700 (LWP 19597)]
> INFO:Successfully loaded remap.config
> INFO: Successfully loaded records.config
> INFO: Successfully loaded plugin.config
> Thread 1 "traffic_server" received signal SIGSEGV, Segmentation fault.
> 0x in ?? ()
> (gdb) bt full
> #0  0x in ?? ()
> No symbol table info available.
> #1  0x00789374 in SSLInitServerContext 
> (params=params@entry=0x117a140, sslMultCertSettings=..., certList=...)
> at SSLUtils.cc:1384
> bio = {_r = 0x1181f50}
> cert = 0x1182100
> ca = 
> certname = 
> cert_tok = {_data = , _delimiter = 44 ',', _mode = 0, 
> _escape = 92 '\\', _start = ,
>   _length = }
> key_tok = {_data = , _delimiter = 44 ',', _mode = 0, 
> _escape = 92 '\\', _start = 0,
>   _length = }
> ca_tok = {_data = , _delimiter = 44 ',', _mode = 0, 
> _escape = 92 '\\', _start = 0,
>   _length = }
> server_verify_client = 
> completeServerCertPath = 
> ctx = 
> digest = {digest = 0x0, engine = 0x77ffe4e0, flags = 
> 140737488346576, md_data = 0x1f7ff7600, pctx = 0x77ffe188,
>   update = 0x7fffddc0}
> ca_list = 0x0
> hash_buf = 
> "\277\037D\000\000\000\000\000~KgY\000\000\000\000\377\377\377\377\000\000\000\000@\241\027\001\000\000\000\000\b\206\271\367\377\177\000\000\000v\377\367\377\177\000\000)\371\203\000\000\000\000\000\000l\231\365\377\177\000"
> hash_len = 0
> __FUNCTION__ = "SSLInitServerContext"
> additional_cache_flags = 
> ud = {_configParams = 0x117a140, _serverDialog = 0x0, _serverCert = 
> 0x117cef0 "fullchain1.pem",
>   _serverKey = 0x117ceb0 "privkey1.pem"}
> #2  0x0078a370 in ssl_store_ssl_context 
> (params=params@entry=0x117a140, lookup=lookup@entry=0x117c550,
> sslMultCertSettings=...) at SSLUtils.cc:1666
> cert_list = {n = 1, i = 0, v = 0x7fffded8, e = {0x1182100, 0x0, 
> 0x0, 0x0}}
> ctx = 
> keyblock = 
> inserted = 
> #3  0x0078b5e5 in SSLParseCertificateConfiguration 
> (params=params@entry=0x117a140, lookup=lookup@entry=0x117c550)
> at SSLUtils.cc:1902
> sslMultiCertSettings = {session_ticket_enabled = 1, addr = 
> {> = {
>   _r = 0x0}, }, cert = 
> {> = {
>   _r = 0x117ce90 "fullchain1.pem"}, },
>   first_cert = 
> {> = {
>   _r = 0x117cef0 "fullchain1.pem"}, },
>   ca = 

[jira] [Commented] (TS-4222) ATS 6.2.0 seg faults while processing ssl_multicert.config

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/TS-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15157892#comment-15157892
 ] 

ASF subversion and git services commented on TS-4222:
-

Commit 829a12ac6efab7405fdfc047466de83fa0aa in trafficserver's branch 
refs/heads/6.1.x from [~sudheerv]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=829a12a ]

[TS-4222] Add check to see if SSLConfigParams::load_ssl_file_cb is initialized.

(cherry picked from commit 69381bb0a9f256f64e8365a08dd35349f729fcbf)


> ATS 6.2.0 seg faults while processing ssl_multicert.config
> --
>
> Key: TS-4222
> URL: https://issues.apache.org/jira/browse/TS-4222
> Project: Traffic Server
>  Issue Type: Bug
>  Components: SSL
>Affects Versions: 6.2.0
>Reporter: Prakhar Rudra
>Assignee: Sudheer Vinukonda
> Fix For: 6.1.2, 6.2.0
>
>
> ATS version 6.2.0 segment fault error while checking config using 
> traffic_server -Cverify_config
> It occurs after  "INFO: Successfully loaded plugin.config"
> only entry in ssl_multicert.config is as below,
> dest_ip=* ssl_cert_name=fullchain1.pem ssl_key_name=privkey1.pem
> gdb --args traffic_server -Cverify_config
> (gdb) run
> yields
> INFO: Successfully loaded plugin.config
> Thread 1 "traffic_server" received signal SIGSEGV, Segmentation fault.
> 0x in ?? ()
> (gdb) print SSLConfigParams::load_ssl_file_cb
> $1 = (load_ssl_file_func) 0x0
> Thanks jpeach
> Details:
> http://pastebin.com/K0876r2T
> http://pastebin.com/iP5MAYLu
> Thanks
> Pulling the info from the above pastebin's to jira for posterity.
> {code}
> git clone https://github.com/tatsuhiro-t/spdylay.git
> cd spdylay/
> autoreconf -if
> automake
> autoconf
> ./configure --prefix=/usr
> make
> make install
> cd ../trafficserver/
> autoreconf -if
> export PKG_CONFIG_PATH=/usr/lib/pkgconfig
> ./configure --enable-spdy --enable-experimental-plugins 
> --enable-linux-native-aio --with-zlib=/root/c/ats/zlib-1.2.8 
> --with-pcre=/root/c/ats/pcre-8.38 
> --with-openssl=/root/c/ats/openssl-1.0.1f[WITH CLOUDFLARE PATCH]
> **
> gdb --args traffic_server -Cverify_config
> ...standard info..
> (gdb) run
> Starting program: /usr/local/bin/traffic_server -Cverify_config
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> traffic_server: using root directory '/usr/local'
> [New Thread 0x71f55700 (LWP 19595)]
> NOTE: VERIFY
> [New Thread 0x70c16700 (LWP 19596)]
> [New Thread 0x70a14700 (LWP 19597)]
> INFO:Successfully loaded remap.config
> INFO: Successfully loaded records.config
> INFO: Successfully loaded plugin.config
> Thread 1 "traffic_server" received signal SIGSEGV, Segmentation fault.
> 0x in ?? ()
> (gdb) bt full
> #0  0x in ?? ()
> No symbol table info available.
> #1  0x00789374 in SSLInitServerContext 
> (params=params@entry=0x117a140, sslMultCertSettings=..., certList=...)
> at SSLUtils.cc:1384
> bio = {_r = 0x1181f50}
> cert = 0x1182100
> ca = 
> certname = 
> cert_tok = {_data = , _delimiter = 44 ',', _mode = 0, 
> _escape = 92 '\\', _start = ,
>   _length = }
> key_tok = {_data = , _delimiter = 44 ',', _mode = 0, 
> _escape = 92 '\\', _start = 0,
>   _length = }
> ca_tok = {_data = , _delimiter = 44 ',', _mode = 0, 
> _escape = 92 '\\', _start = 0,
>   _length = }
> server_verify_client = 
> completeServerCertPath = 
> ctx = 
> digest = {digest = 0x0, engine = 0x77ffe4e0, flags = 
> 140737488346576, md_data = 0x1f7ff7600, pctx = 0x77ffe188,
>   update = 0x7fffddc0}
> ca_list = 0x0
> hash_buf = 
> "\277\037D\000\000\000\000\000~KgY\000\000\000\000\377\377\377\377\000\000\000\000@\241\027\001\000\000\000\000\b\206\271\367\377\177\000\000\000v\377\367\377\177\000\000)\371\203\000\000\000\000\000\000l\231\365\377\177\000"
> hash_len = 0
> __FUNCTION__ = "SSLInitServerContext"
> additional_cache_flags = 
> ud = {_configParams = 0x117a140, _serverDialog = 0x0, _serverCert = 
> 0x117cef0 "fullchain1.pem",
>   _serverKey = 0x117ceb0 "privkey1.pem"}
> #2  0x0078a370 in ssl_store_ssl_context 
> (params=params@entry=0x117a140, lookup=lookup@entry=0x117c550,
> sslMultCertSettings=...) at SSLUtils.cc:1666
> cert_list = {n = 1, i = 0, v = 0x7fffded8, e = {0x1182100, 0x0, 
> 0x0, 0x0}}
> ctx = 
> keyblock = 
> inserted = 
> #3  0x0078b5e5 in SSLParseCertificateConfiguration 
> (params=params@entry=0x117a140, lookup=lookup@entry=0x117c550)
> at SSLUtils.cc:1902
> sslMultiCertSettings = 

[jira] [Updated] (TS-4222) ATS 6.2.0 seg faults while processing ssl_multicert.config

[Leif Hedstrom (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TS-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Leif Hedstrom updated TS-4222:
--
Backport to Version:   (was: 6.1.2)

> ATS 6.2.0 seg faults while processing ssl_multicert.config
> --
>
> Key: TS-4222
> URL: https://issues.apache.org/jira/browse/TS-4222
> Project: Traffic Server
>  Issue Type: Bug
>  Components: SSL
>Affects Versions: 6.2.0
>Reporter: Prakhar Rudra
>Assignee: Sudheer Vinukonda
> Fix For: 6.1.2, 6.2.0
>
>
> ATS version 6.2.0 segment fault error while checking config using 
> traffic_server -Cverify_config
> It occurs after  "INFO: Successfully loaded plugin.config"
> only entry in ssl_multicert.config is as below,
> dest_ip=* ssl_cert_name=fullchain1.pem ssl_key_name=privkey1.pem
> gdb --args traffic_server -Cverify_config
> (gdb) run
> yields
> INFO: Successfully loaded plugin.config
> Thread 1 "traffic_server" received signal SIGSEGV, Segmentation fault.
> 0x in ?? ()
> (gdb) print SSLConfigParams::load_ssl_file_cb
> $1 = (load_ssl_file_func) 0x0
> Thanks jpeach
> Details:
> http://pastebin.com/K0876r2T
> http://pastebin.com/iP5MAYLu
> Thanks
> Pulling the info from the above pastebin's to jira for posterity.
> {code}
> git clone https://github.com/tatsuhiro-t/spdylay.git
> cd spdylay/
> autoreconf -if
> automake
> autoconf
> ./configure --prefix=/usr
> make
> make install
> cd ../trafficserver/
> autoreconf -if
> export PKG_CONFIG_PATH=/usr/lib/pkgconfig
> ./configure --enable-spdy --enable-experimental-plugins 
> --enable-linux-native-aio --with-zlib=/root/c/ats/zlib-1.2.8 
> --with-pcre=/root/c/ats/pcre-8.38 
> --with-openssl=/root/c/ats/openssl-1.0.1f[WITH CLOUDFLARE PATCH]
> **
> gdb --args traffic_server -Cverify_config
> ...standard info..
> (gdb) run
> Starting program: /usr/local/bin/traffic_server -Cverify_config
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> traffic_server: using root directory '/usr/local'
> [New Thread 0x71f55700 (LWP 19595)]
> NOTE: VERIFY
> [New Thread 0x70c16700 (LWP 19596)]
> [New Thread 0x70a14700 (LWP 19597)]
> INFO:Successfully loaded remap.config
> INFO: Successfully loaded records.config
> INFO: Successfully loaded plugin.config
> Thread 1 "traffic_server" received signal SIGSEGV, Segmentation fault.
> 0x in ?? ()
> (gdb) bt full
> #0  0x in ?? ()
> No symbol table info available.
> #1  0x00789374 in SSLInitServerContext 
> (params=params@entry=0x117a140, sslMultCertSettings=..., certList=...)
> at SSLUtils.cc:1384
> bio = {_r = 0x1181f50}
> cert = 0x1182100
> ca = 
> certname = 
> cert_tok = {_data = , _delimiter = 44 ',', _mode = 0, 
> _escape = 92 '\\', _start = ,
>   _length = }
> key_tok = {_data = , _delimiter = 44 ',', _mode = 0, 
> _escape = 92 '\\', _start = 0,
>   _length = }
> ca_tok = {_data = , _delimiter = 44 ',', _mode = 0, 
> _escape = 92 '\\', _start = 0,
>   _length = }
> server_verify_client = 
> completeServerCertPath = 
> ctx = 
> digest = {digest = 0x0, engine = 0x77ffe4e0, flags = 
> 140737488346576, md_data = 0x1f7ff7600, pctx = 0x77ffe188,
>   update = 0x7fffddc0}
> ca_list = 0x0
> hash_buf = 
> "\277\037D\000\000\000\000\000~KgY\000\000\000\000\377\377\377\377\000\000\000\000@\241\027\001\000\000\000\000\b\206\271\367\377\177\000\000\000v\377\367\377\177\000\000)\371\203\000\000\000\000\000\000l\231\365\377\177\000"
> hash_len = 0
> __FUNCTION__ = "SSLInitServerContext"
> additional_cache_flags = 
> ud = {_configParams = 0x117a140, _serverDialog = 0x0, _serverCert = 
> 0x117cef0 "fullchain1.pem",
>   _serverKey = 0x117ceb0 "privkey1.pem"}
> #2  0x0078a370 in ssl_store_ssl_context 
> (params=params@entry=0x117a140, lookup=lookup@entry=0x117c550,
> sslMultCertSettings=...) at SSLUtils.cc:1666
> cert_list = {n = 1, i = 0, v = 0x7fffded8, e = {0x1182100, 0x0, 
> 0x0, 0x0}}
> ctx = 
> keyblock = 
> inserted = 
> #3  0x0078b5e5 in SSLParseCertificateConfiguration 
> (params=params@entry=0x117a140, lookup=lookup@entry=0x117c550)
> at SSLUtils.cc:1902
> sslMultiCertSettings = {session_ticket_enabled = 1, addr = 
> {> = {
>   _r = 0x0}, }, cert = 
> {> = {
>   _r = 0x117ce90 "fullchain1.pem"}, },
>   first_cert = 
> {> = {
>   _r = 0x117cef0 "fullchain1.pem"}, },
>   

[jira] [Updated] (TS-4222) ATS 6.2.0 seg faults while processing ssl_multicert.config

[Sudheer Vinukonda (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TS-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sudheer Vinukonda updated TS-4222:
--
Backport to Version: 6.1.2
  Fix Version/s: 6.2.0

> ATS 6.2.0 seg faults while processing ssl_multicert.config
> --
>
> Key: TS-4222
> URL: https://issues.apache.org/jira/browse/TS-4222
> Project: Traffic Server
>  Issue Type: Bug
>  Components: SSL
>Affects Versions: 6.2.0
>Reporter: Prakhar Rudra
>Assignee: Sudheer Vinukonda
> Fix For: 6.2.0
>
>
> ATS version 6.2.0 segment fault error while checking config using 
> traffic_server -Cverify_config
> It occurs after  "INFO: Successfully loaded plugin.config"
> only entry in ssl_multicert.config is as below,
> dest_ip=* ssl_cert_name=fullchain1.pem ssl_key_name=privkey1.pem
> gdb --args traffic_server -Cverify_config
> (gdb) run
> yields
> INFO: Successfully loaded plugin.config
> Thread 1 "traffic_server" received signal SIGSEGV, Segmentation fault.
> 0x in ?? ()
> (gdb) print SSLConfigParams::load_ssl_file_cb
> $1 = (load_ssl_file_func) 0x0
> Thanks jpeach
> Details:
> http://pastebin.com/K0876r2T
> http://pastebin.com/iP5MAYLu
> Thanks
> Pulling the info from the above pastebin's to jira for posterity.
> {code}
> git clone https://github.com/tatsuhiro-t/spdylay.git
> cd spdylay/
> autoreconf -if
> automake
> autoconf
> ./configure --prefix=/usr
> make
> make install
> cd ../trafficserver/
> autoreconf -if
> export PKG_CONFIG_PATH=/usr/lib/pkgconfig
> ./configure --enable-spdy --enable-experimental-plugins 
> --enable-linux-native-aio --with-zlib=/root/c/ats/zlib-1.2.8 
> --with-pcre=/root/c/ats/pcre-8.38 
> --with-openssl=/root/c/ats/openssl-1.0.1f[WITH CLOUDFLARE PATCH]
> **
> gdb --args traffic_server -Cverify_config
> ...standard info..
> (gdb) run
> Starting program: /usr/local/bin/traffic_server -Cverify_config
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> traffic_server: using root directory '/usr/local'
> [New Thread 0x71f55700 (LWP 19595)]
> NOTE: VERIFY
> [New Thread 0x70c16700 (LWP 19596)]
> [New Thread 0x70a14700 (LWP 19597)]
> INFO:Successfully loaded remap.config
> INFO: Successfully loaded records.config
> INFO: Successfully loaded plugin.config
> Thread 1 "traffic_server" received signal SIGSEGV, Segmentation fault.
> 0x in ?? ()
> (gdb) bt full
> #0  0x in ?? ()
> No symbol table info available.
> #1  0x00789374 in SSLInitServerContext 
> (params=params@entry=0x117a140, sslMultCertSettings=..., certList=...)
> at SSLUtils.cc:1384
> bio = {_r = 0x1181f50}
> cert = 0x1182100
> ca = 
> certname = 
> cert_tok = {_data = , _delimiter = 44 ',', _mode = 0, 
> _escape = 92 '\\', _start = ,
>   _length = }
> key_tok = {_data = , _delimiter = 44 ',', _mode = 0, 
> _escape = 92 '\\', _start = 0,
>   _length = }
> ca_tok = {_data = , _delimiter = 44 ',', _mode = 0, 
> _escape = 92 '\\', _start = 0,
>   _length = }
> server_verify_client = 
> completeServerCertPath = 
> ctx = 
> digest = {digest = 0x0, engine = 0x77ffe4e0, flags = 
> 140737488346576, md_data = 0x1f7ff7600, pctx = 0x77ffe188,
>   update = 0x7fffddc0}
> ca_list = 0x0
> hash_buf = 
> "\277\037D\000\000\000\000\000~KgY\000\000\000\000\377\377\377\377\000\000\000\000@\241\027\001\000\000\000\000\b\206\271\367\377\177\000\000\000v\377\367\377\177\000\000)\371\203\000\000\000\000\000\000l\231\365\377\177\000"
> hash_len = 0
> __FUNCTION__ = "SSLInitServerContext"
> additional_cache_flags = 
> ud = {_configParams = 0x117a140, _serverDialog = 0x0, _serverCert = 
> 0x117cef0 "fullchain1.pem",
>   _serverKey = 0x117ceb0 "privkey1.pem"}
> #2  0x0078a370 in ssl_store_ssl_context 
> (params=params@entry=0x117a140, lookup=lookup@entry=0x117c550,
> sslMultCertSettings=...) at SSLUtils.cc:1666
> cert_list = {n = 1, i = 0, v = 0x7fffded8, e = {0x1182100, 0x0, 
> 0x0, 0x0}}
> ctx = 
> keyblock = 
> inserted = 
> #3  0x0078b5e5 in SSLParseCertificateConfiguration 
> (params=params@entry=0x117a140, lookup=lookup@entry=0x117c550)
> at SSLUtils.cc:1902
> sslMultiCertSettings = {session_ticket_enabled = 1, addr = 
> {> = {
>   _r = 0x0}, }, cert = 
> {> = {
>   _r = 0x117ce90 "fullchain1.pem"}, },
>   first_cert = 
> {> = {
>   _r = 0x117cef0 

[jira] [Resolved] (TS-4222) ATS 6.2.0 seg faults while processing ssl_multicert.config

[Sudheer Vinukonda (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TS-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sudheer Vinukonda resolved TS-4222.
---
Resolution: Fixed

> ATS 6.2.0 seg faults while processing ssl_multicert.config
> --
>
> Key: TS-4222
> URL: https://issues.apache.org/jira/browse/TS-4222
> Project: Traffic Server
>  Issue Type: Bug
>  Components: SSL
>Affects Versions: 6.2.0
>Reporter: Prakhar Rudra
>Assignee: Sudheer Vinukonda
> Fix For: 6.2.0
>
>
> ATS version 6.2.0 segment fault error while checking config using 
> traffic_server -Cverify_config
> It occurs after  "INFO: Successfully loaded plugin.config"
> only entry in ssl_multicert.config is as below,
> dest_ip=* ssl_cert_name=fullchain1.pem ssl_key_name=privkey1.pem
> gdb --args traffic_server -Cverify_config
> (gdb) run
> yields
> INFO: Successfully loaded plugin.config
> Thread 1 "traffic_server" received signal SIGSEGV, Segmentation fault.
> 0x in ?? ()
> (gdb) print SSLConfigParams::load_ssl_file_cb
> $1 = (load_ssl_file_func) 0x0
> Thanks jpeach
> Details:
> http://pastebin.com/K0876r2T
> http://pastebin.com/iP5MAYLu
> Thanks
> Pulling the info from the above pastebin's to jira for posterity.
> {code}
> git clone https://github.com/tatsuhiro-t/spdylay.git
> cd spdylay/
> autoreconf -if
> automake
> autoconf
> ./configure --prefix=/usr
> make
> make install
> cd ../trafficserver/
> autoreconf -if
> export PKG_CONFIG_PATH=/usr/lib/pkgconfig
> ./configure --enable-spdy --enable-experimental-plugins 
> --enable-linux-native-aio --with-zlib=/root/c/ats/zlib-1.2.8 
> --with-pcre=/root/c/ats/pcre-8.38 
> --with-openssl=/root/c/ats/openssl-1.0.1f[WITH CLOUDFLARE PATCH]
> **
> gdb --args traffic_server -Cverify_config
> ...standard info..
> (gdb) run
> Starting program: /usr/local/bin/traffic_server -Cverify_config
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> traffic_server: using root directory '/usr/local'
> [New Thread 0x71f55700 (LWP 19595)]
> NOTE: VERIFY
> [New Thread 0x70c16700 (LWP 19596)]
> [New Thread 0x70a14700 (LWP 19597)]
> INFO:Successfully loaded remap.config
> INFO: Successfully loaded records.config
> INFO: Successfully loaded plugin.config
> Thread 1 "traffic_server" received signal SIGSEGV, Segmentation fault.
> 0x in ?? ()
> (gdb) bt full
> #0  0x in ?? ()
> No symbol table info available.
> #1  0x00789374 in SSLInitServerContext 
> (params=params@entry=0x117a140, sslMultCertSettings=..., certList=...)
> at SSLUtils.cc:1384
> bio = {_r = 0x1181f50}
> cert = 0x1182100
> ca = 
> certname = 
> cert_tok = {_data = , _delimiter = 44 ',', _mode = 0, 
> _escape = 92 '\\', _start = ,
>   _length = }
> key_tok = {_data = , _delimiter = 44 ',', _mode = 0, 
> _escape = 92 '\\', _start = 0,
>   _length = }
> ca_tok = {_data = , _delimiter = 44 ',', _mode = 0, 
> _escape = 92 '\\', _start = 0,
>   _length = }
> server_verify_client = 
> completeServerCertPath = 
> ctx = 
> digest = {digest = 0x0, engine = 0x77ffe4e0, flags = 
> 140737488346576, md_data = 0x1f7ff7600, pctx = 0x77ffe188,
>   update = 0x7fffddc0}
> ca_list = 0x0
> hash_buf = 
> "\277\037D\000\000\000\000\000~KgY\000\000\000\000\377\377\377\377\000\000\000\000@\241\027\001\000\000\000\000\b\206\271\367\377\177\000\000\000v\377\367\377\177\000\000)\371\203\000\000\000\000\000\000l\231\365\377\177\000"
> hash_len = 0
> __FUNCTION__ = "SSLInitServerContext"
> additional_cache_flags = 
> ud = {_configParams = 0x117a140, _serverDialog = 0x0, _serverCert = 
> 0x117cef0 "fullchain1.pem",
>   _serverKey = 0x117ceb0 "privkey1.pem"}
> #2  0x0078a370 in ssl_store_ssl_context 
> (params=params@entry=0x117a140, lookup=lookup@entry=0x117c550,
> sslMultCertSettings=...) at SSLUtils.cc:1666
> cert_list = {n = 1, i = 0, v = 0x7fffded8, e = {0x1182100, 0x0, 
> 0x0, 0x0}}
> ctx = 
> keyblock = 
> inserted = 
> #3  0x0078b5e5 in SSLParseCertificateConfiguration 
> (params=params@entry=0x117a140, lookup=lookup@entry=0x117c550)
> at SSLUtils.cc:1902
> sslMultiCertSettings = {session_ticket_enabled = 1, addr = 
> {> = {
>   _r = 0x0}, }, cert = 
> {> = {
>   _r = 0x117ce90 "fullchain1.pem"}, },
>   first_cert = 
> {> = {
>   _r = 0x117cef0 "fullchain1.pem"}, },
>   ca = 

[jira] [Commented] (TS-4222) ATS 6.2.0 seg faults while processing ssl_multicert.config

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/TS-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15157769#comment-15157769
 ] 

ASF subversion and git services commented on TS-4222:
-

Commit 69381bb0a9f256f64e8365a08dd35349f729fcbf in trafficserver's branch 
refs/heads/master from [~sudheerv]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=69381bb ]

[TS-4222] Add check to see if SSLConfigParams::load_ssl_file_cb is initialized.


> ATS 6.2.0 seg faults while processing ssl_multicert.config
> --
>
> Key: TS-4222
> URL: https://issues.apache.org/jira/browse/TS-4222
> Project: Traffic Server
>  Issue Type: Bug
>  Components: SSL
>Affects Versions: 6.2.0
>Reporter: Prakhar Rudra
>Assignee: Sudheer Vinukonda
>
> ATS version 6.2.0 segment fault error while checking config using 
> traffic_server -Cverify_config
> It occurs after  "INFO: Successfully loaded plugin.config"
> only entry in ssl_multicert.config is as below,
> dest_ip=* ssl_cert_name=fullchain1.pem ssl_key_name=privkey1.pem
> gdb --args traffic_server -Cverify_config
> (gdb) run
> yields
> INFO: Successfully loaded plugin.config
> Thread 1 "traffic_server" received signal SIGSEGV, Segmentation fault.
> 0x in ?? ()
> (gdb) print SSLConfigParams::load_ssl_file_cb
> $1 = (load_ssl_file_func) 0x0
> Thanks jpeach
> Details:
> http://pastebin.com/K0876r2T
> http://pastebin.com/iP5MAYLu
> Thanks
> Pulling the info from the above pastebin's to jira for posterity.
> {code}
> git clone https://github.com/tatsuhiro-t/spdylay.git
> cd spdylay/
> autoreconf -if
> automake
> autoconf
> ./configure --prefix=/usr
> make
> make install
> cd ../trafficserver/
> autoreconf -if
> export PKG_CONFIG_PATH=/usr/lib/pkgconfig
> ./configure --enable-spdy --enable-experimental-plugins 
> --enable-linux-native-aio --with-zlib=/root/c/ats/zlib-1.2.8 
> --with-pcre=/root/c/ats/pcre-8.38 
> --with-openssl=/root/c/ats/openssl-1.0.1f[WITH CLOUDFLARE PATCH]
> **
> gdb --args traffic_server -Cverify_config
> ...standard info..
> (gdb) run
> Starting program: /usr/local/bin/traffic_server -Cverify_config
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> traffic_server: using root directory '/usr/local'
> [New Thread 0x71f55700 (LWP 19595)]
> NOTE: VERIFY
> [New Thread 0x70c16700 (LWP 19596)]
> [New Thread 0x70a14700 (LWP 19597)]
> INFO:Successfully loaded remap.config
> INFO: Successfully loaded records.config
> INFO: Successfully loaded plugin.config
> Thread 1 "traffic_server" received signal SIGSEGV, Segmentation fault.
> 0x in ?? ()
> (gdb) bt full
> #0  0x in ?? ()
> No symbol table info available.
> #1  0x00789374 in SSLInitServerContext 
> (params=params@entry=0x117a140, sslMultCertSettings=..., certList=...)
> at SSLUtils.cc:1384
> bio = {_r = 0x1181f50}
> cert = 0x1182100
> ca = 
> certname = 
> cert_tok = {_data = , _delimiter = 44 ',', _mode = 0, 
> _escape = 92 '\\', _start = ,
>   _length = }
> key_tok = {_data = , _delimiter = 44 ',', _mode = 0, 
> _escape = 92 '\\', _start = 0,
>   _length = }
> ca_tok = {_data = , _delimiter = 44 ',', _mode = 0, 
> _escape = 92 '\\', _start = 0,
>   _length = }
> server_verify_client = 
> completeServerCertPath = 
> ctx = 
> digest = {digest = 0x0, engine = 0x77ffe4e0, flags = 
> 140737488346576, md_data = 0x1f7ff7600, pctx = 0x77ffe188,
>   update = 0x7fffddc0}
> ca_list = 0x0
> hash_buf = 
> "\277\037D\000\000\000\000\000~KgY\000\000\000\000\377\377\377\377\000\000\000\000@\241\027\001\000\000\000\000\b\206\271\367\377\177\000\000\000v\377\367\377\177\000\000)\371\203\000\000\000\000\000\000l\231\365\377\177\000"
> hash_len = 0
> __FUNCTION__ = "SSLInitServerContext"
> additional_cache_flags = 
> ud = {_configParams = 0x117a140, _serverDialog = 0x0, _serverCert = 
> 0x117cef0 "fullchain1.pem",
>   _serverKey = 0x117ceb0 "privkey1.pem"}
> #2  0x0078a370 in ssl_store_ssl_context 
> (params=params@entry=0x117a140, lookup=lookup@entry=0x117c550,
> sslMultCertSettings=...) at SSLUtils.cc:1666
> cert_list = {n = 1, i = 0, v = 0x7fffded8, e = {0x1182100, 0x0, 
> 0x0, 0x0}}
> ctx = 
> keyblock = 
> inserted = 
> #3  0x0078b5e5 in SSLParseCertificateConfiguration 
> (params=params@entry=0x117a140, lookup=lookup@entry=0x117c550)
> at SSLUtils.cc:1902
> sslMultiCertSettings = {session_ticket_enabled = 1, addr = 
> {> = {
>   _r = 0x0}, 

[jira] [Commented] (TS-4222) ATS 6.2.0 seg faults while processing ssl_multicert.config

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/TS-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15157770#comment-15157770
 ] 

ASF GitHub Bot commented on TS-4222:


Github user asfgit closed the pull request at:

https://github.com/apache/trafficserver/pull/495


> ATS 6.2.0 seg faults while processing ssl_multicert.config
> --
>
> Key: TS-4222
> URL: https://issues.apache.org/jira/browse/TS-4222
> Project: Traffic Server
>  Issue Type: Bug
>  Components: SSL
>Affects Versions: 6.2.0
>Reporter: Prakhar Rudra
>Assignee: Sudheer Vinukonda
>
> ATS version 6.2.0 segment fault error while checking config using 
> traffic_server -Cverify_config
> It occurs after  "INFO: Successfully loaded plugin.config"
> only entry in ssl_multicert.config is as below,
> dest_ip=* ssl_cert_name=fullchain1.pem ssl_key_name=privkey1.pem
> gdb --args traffic_server -Cverify_config
> (gdb) run
> yields
> INFO: Successfully loaded plugin.config
> Thread 1 "traffic_server" received signal SIGSEGV, Segmentation fault.
> 0x in ?? ()
> (gdb) print SSLConfigParams::load_ssl_file_cb
> $1 = (load_ssl_file_func) 0x0
> Thanks jpeach
> Details:
> http://pastebin.com/K0876r2T
> http://pastebin.com/iP5MAYLu
> Thanks
> Pulling the info from the above pastebin's to jira for posterity.
> {code}
> git clone https://github.com/tatsuhiro-t/spdylay.git
> cd spdylay/
> autoreconf -if
> automake
> autoconf
> ./configure --prefix=/usr
> make
> make install
> cd ../trafficserver/
> autoreconf -if
> export PKG_CONFIG_PATH=/usr/lib/pkgconfig
> ./configure --enable-spdy --enable-experimental-plugins 
> --enable-linux-native-aio --with-zlib=/root/c/ats/zlib-1.2.8 
> --with-pcre=/root/c/ats/pcre-8.38 
> --with-openssl=/root/c/ats/openssl-1.0.1f[WITH CLOUDFLARE PATCH]
> **
> gdb --args traffic_server -Cverify_config
> ...standard info..
> (gdb) run
> Starting program: /usr/local/bin/traffic_server -Cverify_config
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> traffic_server: using root directory '/usr/local'
> [New Thread 0x71f55700 (LWP 19595)]
> NOTE: VERIFY
> [New Thread 0x70c16700 (LWP 19596)]
> [New Thread 0x70a14700 (LWP 19597)]
> INFO:Successfully loaded remap.config
> INFO: Successfully loaded records.config
> INFO: Successfully loaded plugin.config
> Thread 1 "traffic_server" received signal SIGSEGV, Segmentation fault.
> 0x in ?? ()
> (gdb) bt full
> #0  0x in ?? ()
> No symbol table info available.
> #1  0x00789374 in SSLInitServerContext 
> (params=params@entry=0x117a140, sslMultCertSettings=..., certList=...)
> at SSLUtils.cc:1384
> bio = {_r = 0x1181f50}
> cert = 0x1182100
> ca = 
> certname = 
> cert_tok = {_data = , _delimiter = 44 ',', _mode = 0, 
> _escape = 92 '\\', _start = ,
>   _length = }
> key_tok = {_data = , _delimiter = 44 ',', _mode = 0, 
> _escape = 92 '\\', _start = 0,
>   _length = }
> ca_tok = {_data = , _delimiter = 44 ',', _mode = 0, 
> _escape = 92 '\\', _start = 0,
>   _length = }
> server_verify_client = 
> completeServerCertPath = 
> ctx = 
> digest = {digest = 0x0, engine = 0x77ffe4e0, flags = 
> 140737488346576, md_data = 0x1f7ff7600, pctx = 0x77ffe188,
>   update = 0x7fffddc0}
> ca_list = 0x0
> hash_buf = 
> "\277\037D\000\000\000\000\000~KgY\000\000\000\000\377\377\377\377\000\000\000\000@\241\027\001\000\000\000\000\b\206\271\367\377\177\000\000\000v\377\367\377\177\000\000)\371\203\000\000\000\000\000\000l\231\365\377\177\000"
> hash_len = 0
> __FUNCTION__ = "SSLInitServerContext"
> additional_cache_flags = 
> ud = {_configParams = 0x117a140, _serverDialog = 0x0, _serverCert = 
> 0x117cef0 "fullchain1.pem",
>   _serverKey = 0x117ceb0 "privkey1.pem"}
> #2  0x0078a370 in ssl_store_ssl_context 
> (params=params@entry=0x117a140, lookup=lookup@entry=0x117c550,
> sslMultCertSettings=...) at SSLUtils.cc:1666
> cert_list = {n = 1, i = 0, v = 0x7fffded8, e = {0x1182100, 0x0, 
> 0x0, 0x0}}
> ctx = 
> keyblock = 
> inserted = 
> #3  0x0078b5e5 in SSLParseCertificateConfiguration 
> (params=params@entry=0x117a140, lookup=lookup@entry=0x117c550)
> at SSLUtils.cc:1902
> sslMultiCertSettings = {session_ticket_enabled = 1, addr = 
> {> = {
>   _r = 0x0}, }, cert = 
> {> = {
>   _r = 0x117ce90 "fullchain1.pem"}, },
>   first_cert = 
> 

[jira] [Commented] (TS-4212) Add option to track memory allocation with OpenSSL

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/TS-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15157765#comment-15157765
 ] 

ASF GitHub Bot commented on TS-4212:


Github user bryancall commented on the pull request:

https://github.com/apache/trafficserver/pull/489#issuecomment-187401764
  
@jpeach They are both counters.

@PSUdaemon Yes, old_size > new_size  :)


> Add option to track memory allocation with OpenSSL
> --
>
> Key: TS-4212
> URL: https://issues.apache.org/jira/browse/TS-4212
> Project: Traffic Server
>  Issue Type: Bug
>  Components: Core, SSL
>Reporter: Bryan Call
> Fix For: 6.2.0
>
>
> For example:
> {code}
> [bcall@l1 ~]$ sudo traffic_line -s proxy.config.res_track_memory -v 2
> [bcall@l1 ~]$ sudo kill -sigusr1 $(pidof traffic_server); tail traffic.out
> Total Allocated  | Total Freed  | Currently Allocated  | Type
> -|--|--|--
>  18437960662 |  17181254510 |   1256706152 | SSL 
> Allocated Memory
> -|--|--|--
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (TS-4222) ATS 6.2.0 seg faults while processing ssl_multicert.config

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/TS-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15157766#comment-15157766
 ] 

ASF GitHub Bot commented on TS-4222:


Github user jpeach commented on the pull request:

https://github.com/apache/trafficserver/pull/495#issuecomment-187401866
  
Looks good. Merge it.


> ATS 6.2.0 seg faults while processing ssl_multicert.config
> --
>
> Key: TS-4222
> URL: https://issues.apache.org/jira/browse/TS-4222
> Project: Traffic Server
>  Issue Type: Bug
>  Components: SSL
>Affects Versions: 6.2.0
>Reporter: Prakhar Rudra
>Assignee: Sudheer Vinukonda
>
> ATS version 6.2.0 segment fault error while checking config using 
> traffic_server -Cverify_config
> It occurs after  "INFO: Successfully loaded plugin.config"
> only entry in ssl_multicert.config is as below,
> dest_ip=* ssl_cert_name=fullchain1.pem ssl_key_name=privkey1.pem
> gdb --args traffic_server -Cverify_config
> (gdb) run
> yields
> INFO: Successfully loaded plugin.config
> Thread 1 "traffic_server" received signal SIGSEGV, Segmentation fault.
> 0x in ?? ()
> (gdb) print SSLConfigParams::load_ssl_file_cb
> $1 = (load_ssl_file_func) 0x0
> Thanks jpeach
> Details:
> http://pastebin.com/K0876r2T
> http://pastebin.com/iP5MAYLu
> Thanks
> Pulling the info from the above pastebin's to jira for posterity.
> {code}
> git clone https://github.com/tatsuhiro-t/spdylay.git
> cd spdylay/
> autoreconf -if
> automake
> autoconf
> ./configure --prefix=/usr
> make
> make install
> cd ../trafficserver/
> autoreconf -if
> export PKG_CONFIG_PATH=/usr/lib/pkgconfig
> ./configure --enable-spdy --enable-experimental-plugins 
> --enable-linux-native-aio --with-zlib=/root/c/ats/zlib-1.2.8 
> --with-pcre=/root/c/ats/pcre-8.38 
> --with-openssl=/root/c/ats/openssl-1.0.1f[WITH CLOUDFLARE PATCH]
> **
> gdb --args traffic_server -Cverify_config
> ...standard info..
> (gdb) run
> Starting program: /usr/local/bin/traffic_server -Cverify_config
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> traffic_server: using root directory '/usr/local'
> [New Thread 0x71f55700 (LWP 19595)]
> NOTE: VERIFY
> [New Thread 0x70c16700 (LWP 19596)]
> [New Thread 0x70a14700 (LWP 19597)]
> INFO:Successfully loaded remap.config
> INFO: Successfully loaded records.config
> INFO: Successfully loaded plugin.config
> Thread 1 "traffic_server" received signal SIGSEGV, Segmentation fault.
> 0x in ?? ()
> (gdb) bt full
> #0  0x in ?? ()
> No symbol table info available.
> #1  0x00789374 in SSLInitServerContext 
> (params=params@entry=0x117a140, sslMultCertSettings=..., certList=...)
> at SSLUtils.cc:1384
> bio = {_r = 0x1181f50}
> cert = 0x1182100
> ca = 
> certname = 
> cert_tok = {_data = , _delimiter = 44 ',', _mode = 0, 
> _escape = 92 '\\', _start = ,
>   _length = }
> key_tok = {_data = , _delimiter = 44 ',', _mode = 0, 
> _escape = 92 '\\', _start = 0,
>   _length = }
> ca_tok = {_data = , _delimiter = 44 ',', _mode = 0, 
> _escape = 92 '\\', _start = 0,
>   _length = }
> server_verify_client = 
> completeServerCertPath = 
> ctx = 
> digest = {digest = 0x0, engine = 0x77ffe4e0, flags = 
> 140737488346576, md_data = 0x1f7ff7600, pctx = 0x77ffe188,
>   update = 0x7fffddc0}
> ca_list = 0x0
> hash_buf = 
> "\277\037D\000\000\000\000\000~KgY\000\000\000\000\377\377\377\377\000\000\000\000@\241\027\001\000\000\000\000\b\206\271\367\377\177\000\000\000v\377\367\377\177\000\000)\371\203\000\000\000\000\000\000l\231\365\377\177\000"
> hash_len = 0
> __FUNCTION__ = "SSLInitServerContext"
> additional_cache_flags = 
> ud = {_configParams = 0x117a140, _serverDialog = 0x0, _serverCert = 
> 0x117cef0 "fullchain1.pem",
>   _serverKey = 0x117ceb0 "privkey1.pem"}
> #2  0x0078a370 in ssl_store_ssl_context 
> (params=params@entry=0x117a140, lookup=lookup@entry=0x117c550,
> sslMultCertSettings=...) at SSLUtils.cc:1666
> cert_list = {n = 1, i = 0, v = 0x7fffded8, e = {0x1182100, 0x0, 
> 0x0, 0x0}}
> ctx = 
> keyblock = 
> inserted = 
> #3  0x0078b5e5 in SSLParseCertificateConfiguration 
> (params=params@entry=0x117a140, lookup=lookup@entry=0x117c550)
> at SSLUtils.cc:1902
> sslMultiCertSettings = {session_ticket_enabled = 1, addr = 
> {> = {
>   _r = 0x0}, }, cert = 
> {> = {
>   _r = 0x117ce90 "fullchain1.pem"}, },
>   

[jira] [Commented] (TS-4222) ATS 6.2.0 seg faults while processing ssl_multicert.config

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/TS-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15157761#comment-15157761
 ] 

ASF GitHub Bot commented on TS-4222:


GitHub user sudheerv opened a pull request:

https://github.com/apache/trafficserver/pull/495

[TS-4222] Add check to see if SSLConfigParams::load_ssl_file_cb is in…

…itialized.

@jpeach : pls review

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/apache/trafficserver ts4222

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/trafficserver/pull/495.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #495


commit 69381bb0a9f256f64e8365a08dd35349f729fcbf
Author: Sudheer Vinukonda 
Date:   2016-02-22T21:47:22Z

[TS-4222] Add check to see if SSLConfigParams::load_ssl_file_cb is 
initialized.




> ATS 6.2.0 seg faults while processing ssl_multicert.config
> --
>
> Key: TS-4222
> URL: https://issues.apache.org/jira/browse/TS-4222
> Project: Traffic Server
>  Issue Type: Bug
>  Components: SSL
>Affects Versions: 6.2.0
>Reporter: Prakhar Rudra
>Assignee: Sudheer Vinukonda
>
> ATS version 6.2.0 segment fault error while checking config using 
> traffic_server -Cverify_config
> It occurs after  "INFO: Successfully loaded plugin.config"
> only entry in ssl_multicert.config is as below,
> dest_ip=* ssl_cert_name=fullchain1.pem ssl_key_name=privkey1.pem
> gdb --args traffic_server -Cverify_config
> (gdb) run
> yields
> INFO: Successfully loaded plugin.config
> Thread 1 "traffic_server" received signal SIGSEGV, Segmentation fault.
> 0x in ?? ()
> (gdb) print SSLConfigParams::load_ssl_file_cb
> $1 = (load_ssl_file_func) 0x0
> Thanks jpeach
> Details:
> http://pastebin.com/K0876r2T
> http://pastebin.com/iP5MAYLu
> Thanks
> Pulling the info from the above pastebin's to jira for posterity.
> {code}
> git clone https://github.com/tatsuhiro-t/spdylay.git
> cd spdylay/
> autoreconf -if
> automake
> autoconf
> ./configure --prefix=/usr
> make
> make install
> cd ../trafficserver/
> autoreconf -if
> export PKG_CONFIG_PATH=/usr/lib/pkgconfig
> ./configure --enable-spdy --enable-experimental-plugins 
> --enable-linux-native-aio --with-zlib=/root/c/ats/zlib-1.2.8 
> --with-pcre=/root/c/ats/pcre-8.38 
> --with-openssl=/root/c/ats/openssl-1.0.1f[WITH CLOUDFLARE PATCH]
> **
> gdb --args traffic_server -Cverify_config
> ...standard info..
> (gdb) run
> Starting program: /usr/local/bin/traffic_server -Cverify_config
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> traffic_server: using root directory '/usr/local'
> [New Thread 0x71f55700 (LWP 19595)]
> NOTE: VERIFY
> [New Thread 0x70c16700 (LWP 19596)]
> [New Thread 0x70a14700 (LWP 19597)]
> INFO:Successfully loaded remap.config
> INFO: Successfully loaded records.config
> INFO: Successfully loaded plugin.config
> Thread 1 "traffic_server" received signal SIGSEGV, Segmentation fault.
> 0x in ?? ()
> (gdb) bt full
> #0  0x in ?? ()
> No symbol table info available.
> #1  0x00789374 in SSLInitServerContext 
> (params=params@entry=0x117a140, sslMultCertSettings=..., certList=...)
> at SSLUtils.cc:1384
> bio = {_r = 0x1181f50}
> cert = 0x1182100
> ca = 
> certname = 
> cert_tok = {_data = , _delimiter = 44 ',', _mode = 0, 
> _escape = 92 '\\', _start = ,
>   _length = }
> key_tok = {_data = , _delimiter = 44 ',', _mode = 0, 
> _escape = 92 '\\', _start = 0,
>   _length = }
> ca_tok = {_data = , _delimiter = 44 ',', _mode = 0, 
> _escape = 92 '\\', _start = 0,
>   _length = }
> server_verify_client = 
> completeServerCertPath = 
> ctx = 
> digest = {digest = 0x0, engine = 0x77ffe4e0, flags = 
> 140737488346576, md_data = 0x1f7ff7600, pctx = 0x77ffe188,
>   update = 0x7fffddc0}
> ca_list = 0x0
> hash_buf = 
> "\277\037D\000\000\000\000\000~KgY\000\000\000\000\377\377\377\377\000\000\000\000@\241\027\001\000\000\000\000\b\206\271\367\377\177\000\000\000v\377\367\377\177\000\000)\371\203\000\000\000\000\000\000l\231\365\377\177\000"
> hash_len = 0
> __FUNCTION__ = "SSLInitServerContext"
> additional_cache_flags = 
> ud = {_configParams = 0x117a140, _serverDialog = 0x0, _serverCert = 
> 0x117cef0 "fullchain1.pem",
>   _serverKey = 0x117ceb0 "privkey1.pem"}
> #2  0x0078a370 in ssl_store_ssl_context 
> 

[jira] [Updated] (TS-4222) ATS 6.2.0 seg faults while processing ssl_multicert.config

[Sudheer Vinukonda (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TS-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sudheer Vinukonda updated TS-4222:
--
Description: 
ATS version 6.2.0 segment fault error while checking config using 
traffic_server -Cverify_config
It occurs after  "INFO: Successfully loaded plugin.config"

only entry in ssl_multicert.config is as below,
dest_ip=* ssl_cert_name=fullchain1.pem ssl_key_name=privkey1.pem

gdb --args traffic_server -Cverify_config
(gdb) run
yields
INFO: Successfully loaded plugin.config
Thread 1 "traffic_server" received signal SIGSEGV, Segmentation fault.
0x in ?? ()

(gdb) print SSLConfigParams::load_ssl_file_cb
$1 = (load_ssl_file_func) 0x0

Thanks jpeach

Details:
http://pastebin.com/K0876r2T
http://pastebin.com/iP5MAYLu

Thanks


Pulling the info from the above pastebin's to jira for posterity.

{code}
git clone https://github.com/tatsuhiro-t/spdylay.git
cd spdylay/
autoreconf -if
automake
autoconf
./configure --prefix=/usr
make
make install
cd ../trafficserver/
autoreconf -if
export PKG_CONFIG_PATH=/usr/lib/pkgconfig
./configure --enable-spdy --enable-experimental-plugins 
--enable-linux-native-aio --with-zlib=/root/c/ats/zlib-1.2.8 
--with-pcre=/root/c/ats/pcre-8.38 
--with-openssl=/root/c/ats/openssl-1.0.1f[WITH CLOUDFLARE PATCH]
**
gdb --args traffic_server -Cverify_config
...standard info..
(gdb) run
Starting program: /usr/local/bin/traffic_server -Cverify_config
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
traffic_server: using root directory '/usr/local'
[New Thread 0x71f55700 (LWP 19595)]
NOTE: VERIFY

[New Thread 0x70c16700 (LWP 19596)]
[New Thread 0x70a14700 (LWP 19597)]
INFO:Successfully loaded remap.config

INFO: Successfully loaded records.config

INFO: Successfully loaded plugin.config


Thread 1 "traffic_server" received signal SIGSEGV, Segmentation fault.
0x in ?? ()

(gdb) bt full
#0  0x in ?? ()
No symbol table info available.
#1  0x00789374 in SSLInitServerContext (params=params@entry=0x117a140, 
sslMultCertSettings=..., certList=...)
at SSLUtils.cc:1384
bio = {_r = 0x1181f50}
cert = 0x1182100
ca = 
certname = 
cert_tok = {_data = , _delimiter = 44 ',', _mode = 0, 
_escape = 92 '\\', _start = ,
  _length = }
key_tok = {_data = , _delimiter = 44 ',', _mode = 0, 
_escape = 92 '\\', _start = 0,
  _length = }
ca_tok = {_data = , _delimiter = 44 ',', _mode = 0, 
_escape = 92 '\\', _start = 0,
  _length = }
server_verify_client = 
completeServerCertPath = 
ctx = 
digest = {digest = 0x0, engine = 0x77ffe4e0, flags = 
140737488346576, md_data = 0x1f7ff7600, pctx = 0x77ffe188,
  update = 0x7fffddc0}
ca_list = 0x0
hash_buf = 
"\277\037D\000\000\000\000\000~KgY\000\000\000\000\377\377\377\377\000\000\000\000@\241\027\001\000\000\000\000\b\206\271\367\377\177\000\000\000v\377\367\377\177\000\000)\371\203\000\000\000\000\000\000l\231\365\377\177\000"
hash_len = 0
__FUNCTION__ = "SSLInitServerContext"
additional_cache_flags = 
ud = {_configParams = 0x117a140, _serverDialog = 0x0, _serverCert = 
0x117cef0 "fullchain1.pem",
  _serverKey = 0x117ceb0 "privkey1.pem"}
#2  0x0078a370 in ssl_store_ssl_context (params=params@entry=0x117a140, 
lookup=lookup@entry=0x117c550,
sslMultCertSettings=...) at SSLUtils.cc:1666
cert_list = {n = 1, i = 0, v = 0x7fffded8, e = {0x1182100, 0x0, 
0x0, 0x0}}
ctx = 
keyblock = 
inserted = 
#3  0x0078b5e5 in SSLParseCertificateConfiguration 
(params=params@entry=0x117a140, lookup=lookup@entry=0x117c550)
at SSLUtils.cc:1902
sslMultiCertSettings = {session_ticket_enabled = 1, addr = 
{> = {
  _r = 0x0}, }, cert = 
{> = {
  _r = 0x117ce90 "fullchain1.pem"}, },
  first_cert = {> = {
  _r = 0x117cef0 "fullchain1.pem"}, },
  ca = {> = 
{_r = 0x0}, },
  key = {> = 
{_r = 0x117ceb0 "privkey1.pem"}, },
  ticket_key_filename = 
{> = {_r = 0x0}, },
---Type  to continue, or q  to quit---
  dialog = {> 
= {_r = 0x0}, },
  opt = SSLCertContext::OPT_NONE}
errPtr = 
tok_state = 0x1180cfe ""
line = 
file_buf = 
line_num = 73
line_info = {type = MATCH_NONE, dest_entry = 0, num_el = 2, line = 
{{0x1180cc8 

[jira] [Assigned] (TS-4222) ATS 6.2.0 seg faults while processing ssl_multicert.config

[Sudheer Vinukonda (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TS-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sudheer Vinukonda reassigned TS-4222:
-

Assignee: Sudheer Vinukonda

> ATS 6.2.0 seg faults while processing ssl_multicert.config
> --
>
> Key: TS-4222
> URL: https://issues.apache.org/jira/browse/TS-4222
> Project: Traffic Server
>  Issue Type: Bug
>  Components: SSL
>Affects Versions: 6.2.0
>Reporter: Prakhar Rudra
>Assignee: Sudheer Vinukonda
>
> ATS version 6.2.0 segment fault error while checking config using 
> traffic_server -Cverify_config
> It occurs after  "INFO: Successfully loaded plugin.config"
> only entry in ssl_multicert.config is as below,
> dest_ip=* ssl_cert_name=fullchain1.pem ssl_key_name=privkey1.pem
> gdb --args traffic_server -Cverify_config
> (gdb) run
> yields
> INFO: Successfully loaded plugin.config
> Thread 1 "traffic_server" received signal SIGSEGV, Segmentation fault.
> 0x in ?? ()
> (gdb) print SSLConfigParams::load_ssl_file_cb
> $1 = (load_ssl_file_func) 0x0
> Thanks jpeach
> Details:
> http://pastebin.com/K0876r2T
> http://pastebin.com/iP5MAYLu
> Thanks



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (TS-4222) ATS 6.2.0 seg faults while processing ssl_multicert.config

[Prakhar Rudra (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TS-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prakhar Rudra updated TS-4222:
--
Affects Version/s: 6.2.0

> ATS 6.2.0 seg faults while processing ssl_multicert.config
> --
>
> Key: TS-4222
> URL: https://issues.apache.org/jira/browse/TS-4222
> Project: Traffic Server
>  Issue Type: Bug
>  Components: SSL
>Affects Versions: 6.2.0
>Reporter: Prakhar Rudra
>
> ATS version 6.2.0 segment fault error while checking config using 
> traffic_server -Cverify_config
> It occurs after  "INFO: Successfully loaded plugin.config"
> only entry in ssl_multicert.config is as below,
> dest_ip=* ssl_cert_name=fullchain1.pem ssl_key_name=privkey1.pem
> gdb --args traffic_server -Cverify_config
> (gdb) run
> yields
> INFO: Successfully loaded plugin.config
> Thread 1 "traffic_server" received signal SIGSEGV, Segmentation fault.
> 0x in ?? ()
> (gdb) print SSLConfigParams::load_ssl_file_cb
> $1 = (load_ssl_file_func) 0x0
> Thanks jpeach
> Details:
> http://pastebin.com/K0876r2T
> http://pastebin.com/iP5MAYLu
> Thanks



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (TS-4212) Add option to track memory allocation with OpenSSL

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/TS-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15157452#comment-15157452
 ] 

ASF GitHub Bot commented on TS-4212:


Github user bryancall commented on the pull request:

https://github.com/apache/trafficserver/pull/489#issuecomment-187312131
  
@jpeach 
Do you know what the overhead is on malloc_usable_size().  Maybe switching 
over to that would be a better idea.


> Add option to track memory allocation with OpenSSL
> --
>
> Key: TS-4212
> URL: https://issues.apache.org/jira/browse/TS-4212
> Project: Traffic Server
>  Issue Type: Bug
>  Components: Core, SSL
>Reporter: Bryan Call
> Fix For: 6.2.0
>
>
> For example:
> {code}
> [bcall@l1 ~]$ sudo traffic_line -s proxy.config.res_track_memory -v 2
> [bcall@l1 ~]$ sudo kill -sigusr1 $(pidof traffic_server); tail traffic.out
> Total Allocated  | Total Freed  | Currently Allocated  | Type
> -|--|--|--
>  18437960662 |  17181254510 |   1256706152 | SSL 
> Allocated Memory
> -|--|--|--
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (TS-4212) Add option to track memory allocation with OpenSSL

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/TS-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15157451#comment-15157451
 ] 

ASF GitHub Bot commented on TS-4212:


Github user dragon512 commented on the pull request:

https://github.com/apache/trafficserver/pull/489#issuecomment-187311382
  
I take back what I said after talking to Bryan call.. This is using a 
openssl lib callback API. So this looks good. The CPU is going to fine as long 
as we are on 32-bit bounds, so 8 or 16 bytes will be fine. There is just 
overhead with each alloc. 



> Add option to track memory allocation with OpenSSL
> --
>
> Key: TS-4212
> URL: https://issues.apache.org/jira/browse/TS-4212
> Project: Traffic Server
>  Issue Type: Bug
>  Components: Core, SSL
>Reporter: Bryan Call
> Fix For: 6.2.0
>
>
> For example:
> {code}
> [bcall@l1 ~]$ sudo traffic_line -s proxy.config.res_track_memory -v 2
> [bcall@l1 ~]$ sudo kill -sigusr1 $(pidof traffic_server); tail traffic.out
> Total Allocated  | Total Freed  | Currently Allocated  | Type
> -|--|--|--
>  18437960662 |  17181254510 |   1256706152 | SSL 
> Allocated Memory
> -|--|--|--
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (TS-4212) Add option to track memory allocation with OpenSSL

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/TS-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15157445#comment-15157445
 ] 

ASF GitHub Bot commented on TS-4212:


Github user bryancall commented on the pull request:

https://github.com/apache/trafficserver/pull/489#issuecomment-187310269
  
@jpeach 
I don't think it can get less ugly.  I tried to clean it up as much as 
possible.

What do you mean by duplicates the memory tracking that is already done?  
There is no memory tracking for OpenSSL right now.  This is how I was able to 
see an issue with OpenSSL memory usage in our production environment and 
resolve the issue.

Is there an issue with memory alignment and is there a performance concern 
if we are using this as a diagnostic tool?



> Add option to track memory allocation with OpenSSL
> --
>
> Key: TS-4212
> URL: https://issues.apache.org/jira/browse/TS-4212
> Project: Traffic Server
>  Issue Type: Bug
>  Components: Core, SSL
>Reporter: Bryan Call
> Fix For: 6.2.0
>
>
> For example:
> {code}
> [bcall@l1 ~]$ sudo traffic_line -s proxy.config.res_track_memory -v 2
> [bcall@l1 ~]$ sudo kill -sigusr1 $(pidof traffic_server); tail traffic.out
> Total Allocated  | Total Freed  | Currently Allocated  | Type
> -|--|--|--
>  18437960662 |  17181254510 |   1256706152 | SSL 
> Allocated Memory
> -|--|--|--
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (TS-4221) Truncated objects in the cache

[Leif Hedstrom (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TS-4221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Leif Hedstrom updated TS-4221:
--
Priority: Critical  (was: Major)

> Truncated objects in the cache
> --
>
> Key: TS-4221
> URL: https://issues.apache.org/jira/browse/TS-4221
> Project: Traffic Server
>  Issue Type: Bug
>  Components: Cache
>Reporter: Leif Hedstrom
>Priority: Critical
>  Labels: A
> Fix For: 6.2.0
>
>
> After upgrading to v6.1.x, we see a fair amount of these warnings:
> {code}
> Feb 21 22:36:49 s_...@machine-020.example.com traffic_server[33391]: 
> {0x2aaab3c03700} WARNING:  Document B302849 
> truncated at -941936464 of 1899191218, missing fragment 7B671521
> Feb 22 00:19:01 s_...@machine-020.example.com traffic_server[33391]: 
> {0x2aaab3d04700} WARNING:  Document FC28AC1D 
> truncated at 792669024 of 884706125, missing fragment E85697A4
> Feb 22 00:57:28 s_...@machine-020.example.com traffic_server[33391]: 
> {0x2aaab4a11700} WARNING:  Document A2D26C6 
> truncated at 353345848 of 1978566429, missing fragment 8B26D5F3
> {code}
> It's happening across the border on all boxes upgraded to 6.1. We're not 
> seeing any (or many) of these on the 5.3.x machines. According to Plevyak, 
> this is indicative of bad writes, possibly broken connections. What's odd in 
> our case is that we only see this on our child caches, the parents (running 
> 6.1) do not see this at all.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (TS-4221) Truncated objects in the cache

[Leif Hedstrom (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TS-4221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Leif Hedstrom updated TS-4221:
--
Labels: A  (was: )

> Truncated objects in the cache
> --
>
> Key: TS-4221
> URL: https://issues.apache.org/jira/browse/TS-4221
> Project: Traffic Server
>  Issue Type: Bug
>  Components: Cache
>Reporter: Leif Hedstrom
>  Labels: A
> Fix For: 6.2.0
>
>
> After upgrading to v6.1.x, we see a fair amount of these warnings:
> {code}
> Feb 21 22:36:49 s_...@machine-020.example.com traffic_server[33391]: 
> {0x2aaab3c03700} WARNING:  Document B302849 
> truncated at -941936464 of 1899191218, missing fragment 7B671521
> Feb 22 00:19:01 s_...@machine-020.example.com traffic_server[33391]: 
> {0x2aaab3d04700} WARNING:  Document FC28AC1D 
> truncated at 792669024 of 884706125, missing fragment E85697A4
> Feb 22 00:57:28 s_...@machine-020.example.com traffic_server[33391]: 
> {0x2aaab4a11700} WARNING:  Document A2D26C6 
> truncated at 353345848 of 1978566429, missing fragment 8B26D5F3
> {code}
> It's happening across the border on all boxes upgraded to 6.1. We're not 
> seeing any (or many) of these on the 5.3.x machines. According to Plevyak, 
> this is indicative of bad writes, possibly broken connections. What's odd in 
> our case is that we only see this on our child caches, the parents (running 
> 6.1) do not see this at all.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (TS-4221) Truncated objects in the cache

[Leif Hedstrom (JIRA)]

Leif Hedstrom created TS-4221:
-

 Summary: Truncated objects in the cache
 Key: TS-4221
 URL: https://issues.apache.org/jira/browse/TS-4221
 Project: Traffic Server
  Issue Type: Bug
  Components: Cache
Reporter: Leif Hedstrom


After upgrading to v6.1.x, we see a fair amount of these warnings:

{code}
Feb 21 22:36:49 s_...@machine-020.example.com traffic_server[33391]: 
{0x2aaab3c03700} WARNING:  Document B302849 
truncated at -941936464 of 1899191218, missing fragment 7B671521
Feb 22 00:19:01 s_...@machine-020.example.com traffic_server[33391]: 
{0x2aaab3d04700} WARNING:  Document FC28AC1D 
truncated at 792669024 of 884706125, missing fragment E85697A4
Feb 22 00:57:28 s_...@machine-020.example.com traffic_server[33391]: 
{0x2aaab4a11700} WARNING:  Document A2D26C6 
truncated at 353345848 of 1978566429, missing fragment 8B26D5F3
{code}

It's happening across the border on all boxes upgraded to 6.1. We're not seeing 
any (or many) of these on the 5.3.x machines. According to Plevyak, this is 
indicative of bad writes, possibly broken connections. What's odd in our case 
is that we only see this on our child caches, the parents (running 6.1) do not 
see this at all.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (TS-4221) Truncated objects in the cache

[Leif Hedstrom (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TS-4221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Leif Hedstrom updated TS-4221:
--
Fix Version/s: 6.2.0

> Truncated objects in the cache
> --
>
> Key: TS-4221
> URL: https://issues.apache.org/jira/browse/TS-4221
> Project: Traffic Server
>  Issue Type: Bug
>  Components: Cache
>Reporter: Leif Hedstrom
>  Labels: A
> Fix For: 6.2.0
>
>
> After upgrading to v6.1.x, we see a fair amount of these warnings:
> {code}
> Feb 21 22:36:49 s_...@machine-020.example.com traffic_server[33391]: 
> {0x2aaab3c03700} WARNING:  Document B302849 
> truncated at -941936464 of 1899191218, missing fragment 7B671521
> Feb 22 00:19:01 s_...@machine-020.example.com traffic_server[33391]: 
> {0x2aaab3d04700} WARNING:  Document FC28AC1D 
> truncated at 792669024 of 884706125, missing fragment E85697A4
> Feb 22 00:57:28 s_...@machine-020.example.com traffic_server[33391]: 
> {0x2aaab4a11700} WARNING:  Document A2D26C6 
> truncated at 353345848 of 1978566429, missing fragment 8B26D5F3
> {code}
> It's happening across the border on all boxes upgraded to 6.1. We're not 
> seeing any (or many) of these on the 5.3.x machines. According to Plevyak, 
> this is indicative of bad writes, possibly broken connections. What's odd in 
> our case is that we only see this on our child caches, the parents (running 
> 6.1) do not see this at all.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (TS-4048) Broken Vagrantfile in a lot of ways

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/TS-4048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15157276#comment-15157276
 ] 

ASF GitHub Bot commented on TS-4048:


Github user jpeach commented on the pull request:

https://github.com/apache/trafficserver/pull/490#issuecomment-187268952
  
> Yeah i know what you mean about that patch series... working on it

thanks :)

> I just checked for configure to run in default configuration when looking 
for those dependencies
> trying to keep the images small.
> 
> I can add those optional dependencies as well. Would be great if they 
were documented as optional
> though (doclink).
>
> What do you think about dependencies for plugins? Shall they be added as 
well?

The original goal of these was so that dev could spin up build environments 
for configurations they didn't have easy access to, which meant that I 
installed all the dependencies to build all the optional components. If you can 
get all the dependencies in, that would be great. On RHEL-based systems I 
remember it was a bit tedious to get the right dependencies out of EPEL though. 

> That FreeBSD image is gone and there wasn't any provisioning at all so 
that probably never worked
> ootb anyways. If that's still needed i'll try to add it as well but i'd 
prefer to do that after all the other stuff
> is working again.

No that's fine; I just wanted to check whether this was a deliberate 
decision. A FreeBSD image will just bitrot again unless there's someone to take 
care of it.


> Broken Vagrantfile in a lot of ways
> ---
>
> Key: TS-4048
> URL: https://issues.apache.org/jira/browse/TS-4048
> Project: Traffic Server
>  Issue Type: Bug
>  Components: Build, Tools
>Reporter: Christoph Keller
>Priority: Minor
> Fix For: sometime
>
>
> The Vagrant-File seems to be broken.
> 1. I tried to "vagrant up centos64" which failed due to files that could not 
> be downloaded during provisioning.
> 2. Saucy Images are no longer available and should be removed from 
> Vagrantfile.
> 3. I guess it would be better to use sshfs instead of nfs for the shared 
> folder due to the fact that a lot of people use encrypted home-directories 
> these days which makes mounting the shared folder fail. You don't even get a 
> proper errormessage for that.
> I didn't check all resources refered to by either Vagrantfile or the puppet 
> files but i guess there are even more broken links.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (TS-4158) Fix a few plugins missing to release URL MLocs

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/TS-4158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15157143#comment-15157143
 ] 

ASF GitHub Bot commented on TS-4158:


Github user sudheerv commented on the pull request:

https://github.com/apache/trafficserver/pull/491#issuecomment-187231165
  
sorry for coming late to the party, but, lgtm as well, can't believe the 
printfs :)


> Fix a few plugins missing to release URL MLocs
> --
>
> Key: TS-4158
> URL: https://issues.apache.org/jira/browse/TS-4158
> Project: Traffic Server
>  Issue Type: Bug
>  Components: Plugins
>Reporter: Leif Hedstrom
>Assignee: Leif Hedstrom
> Fix For: 6.2.0
>
>
> Even though benign (no-op), we should release the URL MLoc consistently, as 
> required. Right now, for this particular case (pristine URLs) about half the 
> time we release the URL MLoc, and half we do not.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (TS-4212) Add option to track memory allocation with OpenSSL

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/TS-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15157087#comment-15157087
 ] 

ASF GitHub Bot commented on TS-4212:


Github user dragon512 commented on the pull request:

https://github.com/apache/trafficserver/pull/489#issuecomment-187217377
  
I am not sure why we are using C++ and not using new to do this? We want to 
track memory in Traffic server that is being used to alloc memory for OpenSSL ( 
ie not in OpenSSL as we would have to do fancier instrumentation to do this 
right). We can just overload new so we code do a 

auto p = new(track::openssl) myobj;

This would be more functional and maintainable for this attempt. 


> Add option to track memory allocation with OpenSSL
> --
>
> Key: TS-4212
> URL: https://issues.apache.org/jira/browse/TS-4212
> Project: Traffic Server
>  Issue Type: Bug
>  Components: Core, SSL
>Reporter: Bryan Call
> Fix For: 6.2.0
>
>
> For example:
> {code}
> [bcall@l1 ~]$ sudo traffic_line -s proxy.config.res_track_memory -v 2
> [bcall@l1 ~]$ sudo kill -sigusr1 $(pidof traffic_server); tail traffic.out
> Total Allocated  | Total Freed  | Currently Allocated  | Type
> -|--|--|--
>  18437960662 |  17181254510 |   1256706152 | SSL 
> Allocated Memory
> -|--|--|--
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Build failed in Jenkins: clang-analyzer #1965

[jenkins]

See 

--
Started by timer
Building on master in workspace 

 > /usr/bin/git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > /usr/bin/git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/trafficserver.git # timeout=10
Cleaning workspace
 > /usr/bin/git rev-parse --verify HEAD # timeout=10
Resetting working tree
 > /usr/bin/git reset --hard # timeout=10
ERROR: Error fetching remote repo 'origin'
ERROR: Error fetching remote repo 'origin'