[jira] [Commented] (TS-1653) Crash report: HostDBContinuation::probeEvent MutexTryLock

2013-02-06 Thread weijin (JIRA)

[ 
https://issues.apache.org/jira/browse/TS-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13572268#comment-13572268
 ] 

weijin commented on TS-1653:


committed bc7a84441ca1d6c13d1117b9515c879c70cf9d3b

 Crash report: HostDBContinuation::probeEvent MutexTryLock
 -

 Key: TS-1653
 URL: https://issues.apache.org/jira/browse/TS-1653
 Project: Traffic Server
  Issue Type: Bug
  Components: Core
Reporter: Zhao Yongming
Assignee: Alan M. Carroll

 {code}
 Core was generated by `/usr/bin/traffic_server -M --httpport 8080:fd=7'.
 Program terminated with signal 11, Segmentation fault.
 #0  Mutex_trylock (this=0x2b994a800ce0, am=0x0, t=0x2b9948fea010) at 
 ../iocore/eventsystem/I_Lock.h:170
 170 if (m-thread_holding != t) {
 Missing separate debuginfos, use: debuginfo-install 
 expat-2.0.1-11.el6_2.x86_64 glibc-2.12-1.47.el6_2.9.x86_64 
 keyutils-libs-1.4-3.el6.x86_64 krb5-libs-1.9-22.el6_2.1.x86_64 
 libcom_err-1.41.12-11.el6.x86_64 libgcc-4.4.6-3.el6.x86_64 
 libselinux-2.0.94-5.2.el6.x86_64 libstdc++-4.4.6-3.el6.x86_64 
 openssl-1.0.0-20.el6_2.4.x86_64 pcre-7.8-3.1.el6.x86_64 
 tcl-8.5.7-6.el6.x86_64 xz-libs-4.999.9-0.3.beta.20091007git.el6.x86_64 
 zlib-1.2.3-27.el6.x86_64
 (gdb) bt
 #0  Mutex_trylock (this=0x2b994a800ce0, am=0x0, t=0x2b9948fea010) at 
 ../iocore/eventsystem/I_Lock.h:170
 #1  MutexTryLock::MutexTryLock (this=0x2b994a800ce0, am=0x0, 
 t=0x2b9948fea010) at ../iocore/eventsystem/I_Lock.h:385
 #2  0x005b38dc in HostDBContinuation::probeEvent 
 (this=0x2b997329df10, event=value optimized out, e=0x2b99b8050030) at 
 HostDB.cc:1762
 #3  0x0065a1b4 in handleEvent (this=0x2b9948fea010, e=0x2b99b8050030, 
 calling_code=2) at I_Continuation.h:146
 #4  EThread::process_event (this=0x2b9948fea010, e=0x2b99b8050030, 
 calling_code=2) at UnixEThread.cc:142
 #5  0x0065ad83 in EThread::execute (this=0x2b9948fea010) at 
 UnixEThread.cc:221
 #6  0x006594d2 in spawn_thread_internal (a=0x2fb8350) at Thread.cc:88
 #7  0x003e878077f1 in start_thread () from /lib64/libpthread.so.0
 #8  0x003e86ce5ccd in clone () from /lib64/libc.so.6
 (gdb) f 2
 #2  0x005b38dc in HostDBContinuation::probeEvent 
 (this=0x2b997329df10, event=value optimized out, e=0x2b99b8050030) at 
 HostDB.cc:1762
 1762MUTEX_TRY_LOCK_FOR(lock, action.mutex, t, action.continuation);
 (gdb) p action.mutex
 $1 = {m_ptr = 0x0}
 (gdb) p t
 $2 = value optimized out
 (gdb) p action
 $3 = {_vptr.Action = 0x6601d0, continuation = 0x0, mutex = {m_ptr = 0x0}, 
 cancelled = 1}
 (gdb) 
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (TS-1695) test_certlookup fails on FreeBSD

2013-02-06 Thread JIRA

[ 
https://issues.apache.org/jira/browse/TS-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13572278#comment-13572278
 ] 

Igor Galić commented on TS-1695:


Some further digging: If I --disable-freelist {{test_certlookup}} still 
segfaults:
{noformat}
igalic@daemonix ...che.trafficserver.81460/obj/iocore/net % 
LD_LIBRARY_PATH=/tmp/org.apache.trafficserver.81460/obj/lib/ts/.libs:/usr/local/lib:$LD_LIBRARY_PATH
 gdb .libs/test_certlookup ./test_certlookup.core 
GNU gdb (GDB) 7.5.1 [GDB v7.5.1 for FreeBSD]
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as x86_64-portbld-freebsd10.0.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/...
Reading symbols from 
/tmp/org.apache.trafficserver.81460/obj/iocore/net/.libs/test_certlookup...done.
[New process 100107]
[New Thread 803806400 (LWP 100107)]
Core was generated by `test_certlookup'.
Program terminated with signal 10, Bus error.
#0  0x000802cbc43b in ?? () from /lib/libc.so.7
(gdb) bt
#0  0x000802cbc43b in ?? () from /lib/libc.so.7
#1  0x000802cc8c74 in free () from /lib/libc.so.7
#2  0x00405ca6 in TrieSSLContextStorage::SSLEntry::Clear 
(this=0x80382c800) at /home/igalic/src/asf/trafficserver/lib/ts/Trie.h:213
#3  0x00405d21 in TrieSSLContextStorage::SSLEntry::~Trie 
(this=0x80382c800, __in_chrg=optimized out) at 
/home/igalic/src/asf/trafficserver/lib/ts/Trie.h:54
#4  0x00403c11 in SSLContextStorage::~SSLContextStorage 
(this=0x80382c800, __in_chrg=optimized out) at 
/home/igalic/src/asf/trafficserver/iocore/net/SSLCertLookup.cc:213
#5  0x00403d05 in SSLCertLookup::~SSLCertLookup (this=0x7fffd2d0, 
__in_chrg=optimized out) at 
/home/igalic/src/asf/trafficserver/iocore/net/SSLCertLookup.cc:102
#6  0x004036a8 in RegressionTest_SSLCertificateLookup (t=0x60daa0 
regressionTest_SSLCertificateLookup, atype=0, pstatus=0x60dab8 
regressionTest_SSLCertificateLookup+24)
at /home/igalic/src/asf/trafficserver/iocore/net/test_certlookup.cc:78
#7  0x00080085e516 in start_test (t=0x60daa0 
regressionTest_SSLCertificateLookup) at 
/home/igalic/src/asf/trafficserver/lib/ts/Regression.cc:77
#8  0x00080085e924 in RegressionTest::run (atest=0x0) at 
/home/igalic/src/asf/trafficserver/lib/ts/Regression.cc:98
#9  0x00402ce0 in main (argc=1, argv=0x7fffd460) at 
/home/igalic/src/asf/trafficserver/iocore/net/test_certlookup.cc:197
(gdb)
{noformat}

our standard regression tests however now run and pass (almost):
{noformat}
FAILED: (test #1) print req output mismatch
FAILED: (test #2) print req output mismatch
FAILED: (test #3) print req output mismatch
FAILED: (test #4) print req output mismatch
FAILED: (test #5) print req output mismatch
FAILED: (test #6) print req output mismatch
FAILED: (test #7) print req output mismatch
RPRINT Hdrs:   HdrTest test_http_hdr_print_and_copy: FAILED
REGRESSION_RESULT Hdrs: FAILED
Tests Failed: 0
{noformat}

 test_certlookup fails on FreeBSD
 

 Key: TS-1695
 URL: https://issues.apache.org/jira/browse/TS-1695
 Project: Traffic Server
  Issue Type: Bug
Reporter: Igor Galić

 {noformat}
 Reading symbols from 
 /tmp/org.apache.trafficserver.2624/obj/iocore/net/.libs/test_certlookup...done.
 [New process 100244]
 [New Thread 803806400 (LWP 100244)]
 Core was generated by `test_certlookup'.
 Program terminated with signal 10, Bus error.
 #0  0x000802cbc43b in ?? () from /lib/libc.so.7
 (gdb) bt
 #0  0x000802cbc43b in ?? () from /lib/libc.so.7
 #1  0x000802cc8c74 in free () from /lib/libc.so.7
 #2  0x00405ca6 in TrieSSLContextStorage::SSLEntry::Clear 
 (this=0x80382c800) at /home/igalic/src/asf/trafficserver/lib/ts/Trie.h:213
 #3  0x00405d21 in TrieSSLContextStorage::SSLEntry::~Trie 
 (this=0x80382c800, __in_chrg=optimized out) at 
 /home/igalic/src/asf/trafficserver/lib/ts/Trie.h:54
 #4  0x00403c11 in SSLContextStorage::~SSLContextStorage 
 (this=0x80382c800, __in_chrg=optimized out) at 
 /home/igalic/src/asf/trafficserver/iocore/net/SSLCertLookup.cc:213
 #5  0x00403d05 in SSLCertLookup::~SSLCertLookup (this=0x7fffd2e0, 
 __in_chrg=optimized out) at 
 /home/igalic/src/asf/trafficserver/iocore/net/SSLCertLookup.cc:102
 #6  0x004036a8 in RegressionTest_SSLCertificateLookup (t=0x60daa0 
 regressionTest_SSLCertificateLookup, atype=0, pstatus=0x60dab8 
 regressionTest_SSLCertificateLookup+24)
 at /home/igalic/src/asf/trafficserver/iocore/net/test_certlookup.cc:78
 #7  0x00080085eff6 in 

[jira] [Commented] (TS-1698) thread/pthread mis-match on Solaris 10

2013-02-06 Thread JIRA

[ 
https://issues.apache.org/jira/browse/TS-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13572297#comment-13572297
 ] 

Igor Galić commented on TS-1698:


These comments out of order seem.

 thread/pthread mis-match on Solaris 10
 --

 Key: TS-1698
 URL: https://issues.apache.org/jira/browse/TS-1698
 Project: Traffic Server
  Issue Type: Bug
  Components: Core
Reporter: Igor Galić
 Attachments: ink_pthead.patch


 {noformat}
   CXX  UnixEventProcessor.o
 UnixEventProcessor.cc: In member function 'virtual int 
 EventProcessor::start(int)':
 UnixEventProcessor.cc:186:7: error: format '%lu' expects argument of type 
 'long unsigned int', but argument 8 has type 'ink_thread {aka unsigned int}' 
 [-Werror=format]
 UnixEventProcessor.cc:188:9: error: format '%lu' expects argument of type 
 'long unsigned int', but argument 8 has type 'ink_thread {aka unsigned int}' 
 [-Werror=format]
 cc1plus: all warnings being treated as errors
 gmake[2]: *** [UnixEventProcessor.o] Error 1
 gmake[2]: Leaving directory 
 `/export/home/buildbot/slave5/tserver-solaris-trunk-debug/build/iocore/eventsystem'
 gmake[1]: *** [all-recursive] Error 1
 {noformat}
 This seems to be caused by our naïve code to distinguish between different 
 platforms:
 {code}
 #include P_EventSystem.h  /* MAGIC_EDITING_TAG */
 #include sched.h
 #if TS_USE_HWLOC
 #if HAVE_HWLOC_H
 #include hwloc.h
 #endif
 #if HAVE_SCHED_H
 #include sched.h
 #if !defined(solaris)  !defined(freebsd)
 typedef cpu_set_t ink_cpuset_t;
 #define PTR_FMT PRIuPTR
 #endif
 #endif
 #if HAVE_SYS_PARAM_H
 #include sys/param.h
 #endif
 #if HAVE_SYS_CPUSET_H
 #include sys/cpuset.h
 typedef cpuset_t ink_cpuset_t;
 #define PTR_FMT p
 #endif
 #if HAVE_PTHREAD_NP_H
 #include pthread_np.h
 #endif
 #if HAVE_SYS_PSET_H
 #include sys/pset.h
 typedef psetid_t ink_cpuset_t;
 #define PTR_FMT PRIuPTR
 #endif
 #if HAVE_SYS_TYPES_H
 #include sys/types.h
 #endif
 #endif
 #include ink_defs.h
 #if TS_USE_HWLOC
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (TS-1626) remove WUTS proxy code

2013-02-06 Thread Uri Shachar (JIRA)

[ 
https://issues.apache.org/jira/browse/TS-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13572344#comment-13572344
 ] 

Uri Shachar commented on TS-1626:
-

I've dug around code from ~2006 -- haven't been able to find any useful info on 
this (It does seem to be related to the log_spider_codes option).
Maybe John Plevyak knows what it's all about?

 remove WUTS proxy code
 --

 Key: TS-1626
 URL: https://issues.apache.org/jira/browse/TS-1626
 Project: Traffic Server
  Issue Type: Improvement
  Components: Core
Reporter: James Peach

 There is a bunch of code doing something with WUTS proxy status codes. What 
 is a WUTS and why do we care? If this is cruft, let's get rid of it!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (TS-1006) memory management, cut down memory waste ?

2013-02-06 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/TS-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13572367#comment-13572367
 ] 

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

Commit 616203849743e32d446f09a9089da29116982947 from Zhao Yongming 
ming@gmail.com
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=6162038 ]

TS-1006: Remove unused InkFreeList-offset

I have simplified ink_freelist_init API by removing offset parameter,
but I forgot to remove unused InkFreeList-offset when rebasing code.

So now, the code using an uninitialized value, it would be a bug. Let's
clean it completely.

Signed-off-by: Yunkai Zhang qiushu@taobao.com
Signed-off-by: Zhao Yongming ming@gmail.com


 memory management, cut down memory waste ?
 --

 Key: TS-1006
 URL: https://issues.apache.org/jira/browse/TS-1006
 Project: Traffic Server
  Issue Type: Improvement
  Components: Core
Affects Versions: 3.1.1
Reporter: Zhao Yongming
Assignee: Bin Chen
 Fix For: 3.3.2

 Attachments: 
 0001-TS-1006-Add-an-enable-reclaimable-freelist-option.patch, 
 0002-TS-1006-Add-a-new-wrapper-ink_atomic_decrement.patch, 
 0003-TS-1006-Introduce-a-reclaimable-InkFreeList.patch, 
 0004-TS-1006-Make-InkFreeList-memory-pool-configurable.patch, 
 Memory-Usage-After-Introduced-New-Allocator.png, memusage.ods, memusage.ods


 when we review the memory usage in the production, there is something 
 abnormal, ie, looks like TS take much memory than index data + common system 
 waste, and here is some memory dump result by set 
 proxy.config.dump_mem_info_frequency
 1, the one on a not so busy forwarding system:
 physics memory: 32G
 RAM cache: 22G
 DISK: 6140 GB
 average_object_size 64000
 {code}
  allocated  |in-use  | type size  |   free list name
 |||--
   671088640 |   37748736 |2097152 | 
 memory/ioBufAllocator[14]
  2248146944 | 2135949312 |1048576 | 
 memory/ioBufAllocator[13]
  1711276032 | 1705508864 | 524288 | 
 memory/ioBufAllocator[12]
  1669332992 | 1667760128 | 262144 | 
 memory/ioBufAllocator[11]
  2214592512 | 221184 | 131072 | 
 memory/ioBufAllocator[10]
  2325741568 | 2323775488 |  65536 | 
 memory/ioBufAllocator[9]
  2091909120 | 2089123840 |  32768 | 
 memory/ioBufAllocator[8]
  1956642816 | 1956478976 |  16384 | 
 memory/ioBufAllocator[7]
  2094530560 | 2094071808 |   8192 | 
 memory/ioBufAllocator[6]
   356515840 |  355540992 |   4096 | 
 memory/ioBufAllocator[5]
 1048576 |  14336 |   2048 | 
 memory/ioBufAllocator[4]
  131072 |  0 |   1024 | 
 memory/ioBufAllocator[3]
   65536 |  0 |512 | 
 memory/ioBufAllocator[2]
   32768 |  0 |256 | 
 memory/ioBufAllocator[1]
   16384 |  0 |128 | 
 memory/ioBufAllocator[0]
   0 |  0 |576 | 
 memory/ICPRequestCont_allocator
   0 |  0 |112 | 
 memory/ICPPeerReadContAllocator
   0 |  0 |432 | 
 memory/PeerReadDataAllocator
   0 |  0 | 32 | 
 memory/MIMEFieldSDKHandle
   0 |  0 |240 | 
 memory/INKVConnAllocator
   0 |  0 | 96 | 
 memory/INKContAllocator
4096 |  0 | 32 | 
 memory/apiHookAllocator
   0 |  0 |288 | 
 memory/FetchSMAllocator
   0 |  0 | 80 | 
 memory/prefetchLockHandlerAllocator
   0 |  0 |176 | 
 memory/PrefetchBlasterAllocator
   0 |  0 | 80 | 
 memory/prefetchUrlBlaster
   0 |  0 | 96 | memory/blasterUrlList
   0 |  0 | 96 | 
 memory/prefetchUrlEntryAllocator
   0 |  0 |128 | 
 memory/socksProxyAllocator
   0 |  0 |144 | 
 memory/ObjectReloadCont
 3258368 | 576016 |592 | 
 memory/httpClientSessionAllocator
  825344 | 139568 |208 | 
 memory/httpServerSessionAllocator
22597632 |1284848 |   9808 | memory/httpSMAllocator
   0 | 

[jira] [Created] (TS-1699) document proxy.config.http.doc_in_cache_skip_dns

2013-02-06 Thread James Peach (JIRA)
James Peach created TS-1699:
---

 Summary: document proxy.config.http.doc_in_cache_skip_dns
 Key: TS-1699
 URL: https://issues.apache.org/jira/browse/TS-1699
 Project: Traffic Server
  Issue Type: Bug
  Components: Documentation
Reporter: James Peach


Authentication plugins typically attache to the OS_DNS_HOOK, but if they do 
then they need to set proxy.config.http.doc_in_cache_skip_dns=0 so that the DNS 
hook gets called on every request.

We should document this parameter.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira