[jira] [Updated] (TS-882) traffic_logstats dies when printing log

2011-07-17 Thread Leif Hedstrom (JIRA)

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

Leif Hedstrom updated TS-882:
-

 Priority: Critical  (was: Major)
Fix Version/s: 3.1.0

 traffic_logstats dies when printing log
 ---

 Key: TS-882
 URL: https://issues.apache.org/jira/browse/TS-882
 Project: Traffic Server
  Issue Type: Bug
  Components: Logging
Affects Versions: 3.0.0
 Environment: Mac OSX 10.6.8
Reporter: Alan Cabrera
Priority: Critical
  Labels: crash
 Fix For: 3.1.0


 {code}
 [daruma:trafficserver 598]$ ./bin/traffic_logstats  -l 
 var/log/trafficserver/squid.blog 
 FATAL: ./logging/LogStandalone.cc:96: failed assert `setrlimit((RLIMCAST) 
 which, rl) = 0`
 ./bin/traffic_logstats - STACK TRACE: 
 0   libtsutil.3.dylib   0x0001000cbb6b ink_fatal + 123
 1   libtsutil.3.dylib   0x0001000ca571 _ink_assert + 145
 2   traffic_logstats0x000152f4 _Z11init_systemv + 
 100
 3   traffic_logstats0x0001538b 
 _Z25init_log_standalone_basicPKc + 27
 4   traffic_logstats0x000155ab main + 411
 5   traffic_logstats0x00011484 start + 52
 6   ??? 0x0003 0x0 + 3
 Abort trap
 [daruma:trafficserver 599]$ ./bin/traffic_logstats  -f 
 var/log/trafficserver/squid.blog 
 FATAL: ./logging/LogStandalone.cc:96: failed assert `setrlimit((RLIMCAST) 
 which, rl) = 0`
 ./bin/traffic_logstats - STACK TRACE: 
 0   libtsutil.3.dylib   0x0001000cbb6b ink_fatal + 123
 1   libtsutil.3.dylib   0x0001000ca571 _ink_assert + 145
 2   traffic_logstats0x000152f4 _Z11init_systemv + 
 100
 3   traffic_logstats0x0001538b 
 _Z25init_log_standalone_basicPKc + 27
 4   traffic_logstats0x000155ab main + 411
 5   traffic_logstats0x00011484 start + 52
 6   ??? 0x0003 0x0 + 3
 Abort trap
 [daruma:trafficserver 600]$ ./bin/traffic_logstats
 FATAL: ./logging/LogStandalone.cc:96: failed assert `setrlimit((RLIMCAST) 
 which, rl) = 0`
 ./bin/traffic_logstats - STACK TRACE: 
 0   libtsutil.3.dylib   0x0001000cbb6b ink_fatal + 123
 1   libtsutil.3.dylib   0x0001000ca571 _ink_assert + 145
 2   traffic_logstats0x000152f4 _Z11init_systemv + 
 100
 3   traffic_logstats0x0001538b 
 _Z25init_log_standalone_basicPKc + 27
 4   traffic_logstats0x000155ab main + 411
 5   traffic_logstats0x00011484 start + 52
 6   ??? 0x0001 0x0 + 1
 Abort trap
 {code}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Updated] (TS-882) traffic_logstats dies when printing log

2011-07-17 Thread Leif Hedstrom (JIRA)

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

Leif Hedstrom updated TS-882:
-

Labels: crash  (was: )

 traffic_logstats dies when printing log
 ---

 Key: TS-882
 URL: https://issues.apache.org/jira/browse/TS-882
 Project: Traffic Server
  Issue Type: Bug
  Components: Logging
Affects Versions: 3.0.0
 Environment: Mac OSX 10.6.8
Reporter: Alan Cabrera
Priority: Critical
  Labels: crash
 Fix For: 3.1.0


 {code}
 [daruma:trafficserver 598]$ ./bin/traffic_logstats  -l 
 var/log/trafficserver/squid.blog 
 FATAL: ./logging/LogStandalone.cc:96: failed assert `setrlimit((RLIMCAST) 
 which, rl) = 0`
 ./bin/traffic_logstats - STACK TRACE: 
 0   libtsutil.3.dylib   0x0001000cbb6b ink_fatal + 123
 1   libtsutil.3.dylib   0x0001000ca571 _ink_assert + 145
 2   traffic_logstats0x000152f4 _Z11init_systemv + 
 100
 3   traffic_logstats0x0001538b 
 _Z25init_log_standalone_basicPKc + 27
 4   traffic_logstats0x000155ab main + 411
 5   traffic_logstats0x00011484 start + 52
 6   ??? 0x0003 0x0 + 3
 Abort trap
 [daruma:trafficserver 599]$ ./bin/traffic_logstats  -f 
 var/log/trafficserver/squid.blog 
 FATAL: ./logging/LogStandalone.cc:96: failed assert `setrlimit((RLIMCAST) 
 which, rl) = 0`
 ./bin/traffic_logstats - STACK TRACE: 
 0   libtsutil.3.dylib   0x0001000cbb6b ink_fatal + 123
 1   libtsutil.3.dylib   0x0001000ca571 _ink_assert + 145
 2   traffic_logstats0x000152f4 _Z11init_systemv + 
 100
 3   traffic_logstats0x0001538b 
 _Z25init_log_standalone_basicPKc + 27
 4   traffic_logstats0x000155ab main + 411
 5   traffic_logstats0x00011484 start + 52
 6   ??? 0x0003 0x0 + 3
 Abort trap
 [daruma:trafficserver 600]$ ./bin/traffic_logstats
 FATAL: ./logging/LogStandalone.cc:96: failed assert `setrlimit((RLIMCAST) 
 which, rl) = 0`
 ./bin/traffic_logstats - STACK TRACE: 
 0   libtsutil.3.dylib   0x0001000cbb6b ink_fatal + 123
 1   libtsutil.3.dylib   0x0001000ca571 _ink_assert + 145
 2   traffic_logstats0x000152f4 _Z11init_systemv + 
 100
 3   traffic_logstats0x0001538b 
 _Z25init_log_standalone_basicPKc + 27
 4   traffic_logstats0x000155ab main + 411
 5   traffic_logstats0x00011484 start + 52
 6   ??? 0x0001 0x0 + 1
 Abort trap
 {code}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Resolved] (TS-874) asf-dist should be git nice

2011-07-17 Thread mohan_zl (JIRA)

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

mohan_zl resolved TS-874.
-

Resolution: Fixed

fixed, and closed

 asf-dist should be git nice
 ---

 Key: TS-874
 URL: https://issues.apache.org/jira/browse/TS-874
 Project: Traffic Server
  Issue Type: Improvement
  Components: Build
Affects Versions: 3.1.0
Reporter: Zhao Yongming
Assignee: Zhao Yongming
Priority: Trivial
 Fix For: 3.1.0

 Attachments: TS-874.txt


 the asf-dist make target should be git nice, I think many of us on git.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Updated] (TS-813) http_ui /stat/ should response with content type

2011-07-17 Thread mohan_zl (JIRA)

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

mohan_zl updated TS-813:


Fix Version/s: (was: 3.1.0)
   3.1.1

 http_ui /stat/ should response with content type
 

 Key: TS-813
 URL: https://issues.apache.org/jira/browse/TS-813
 Project: Traffic Server
  Issue Type: Improvement
  Components: HTTP
Affects Versions: 2.1.8
Reporter: Zhao Yongming
Assignee: Zhao Yongming
Priority: Minor
  Labels: http_ui
 Fix For: 3.1.1

 Attachments: TS-813.patch


 when requesting /stat/
 the header missing content type, and that will confusing browsers
 {code}
 HTTP/1.0 200 Ok^M
 Date: Wed, 01 Jun 2011 02:34:02 GMT^M
 Connection: close^M
 Server: ATS/2.1.9-unstable^M
 Content-Length: 54952^M
 ^M
 pre
 proxy.config.proxy_name=
 {code}
 the others should be checked too.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Updated] (TS-849) proxy.config.http.slow.log.threshold is unable to set from traffic_line -s

2011-07-17 Thread mohan_zl (JIRA)

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

mohan_zl updated TS-849:


Fix Version/s: (was: 3.1.0)
   3.1.1

 proxy.config.http.slow.log.threshold is unable to set from traffic_line -s
 --

 Key: TS-849
 URL: https://issues.apache.org/jira/browse/TS-849
 Project: Traffic Server
  Issue Type: Bug
  Components: Configuration
Affects Versions: 3.1.0, 3.0.1
Reporter: Zhao Yongming
Assignee: Zhao Yongming
 Fix For: 3.1.1


 I am wondering how many config items from records have the same situation?
 {code}
 [root@cache164 trafficserver]# traffic_line -s 
 proxy.config.http.slow.log.threshold -v 30
 Layout configuration
   --prefix = '/usr'
  --exec_prefix = '/usr'
   --bindir = '/usr/bin'
  --sbindir = '/usr/sbin'
   --sysconfdir = '/etc/trafficserver'
  --datadir = '/usr/share/trafficserver'
   --includedir = '/usr/include/trafficserver'
   --libdir = '/usr/lib64/trafficserver'
   --libexecdir = '/usr/lib64/trafficserver/plugins'
--localstatedir = '/var/trafficserver'
   --runtimedir = '/var/run/trafficserver'
   --logdir = '/var/log/trafficserver'
   --mandir = '/usr/share/man'
  --infodir = '/usr/share/info'
 --cachedir = '/var/cache/trafficserver'
 traffic_line: Only configuration vars can be set
 {code}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Updated] (TS-796) Crash Report: mime_str_u16_set, possible

2011-07-17 Thread mohan_zl (JIRA)

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

mohan_zl updated TS-796:


Fix Version/s: (was: 3.1.0)
   3.1.1

 Crash Report: mime_str_u16_set, possible
 

 Key: TS-796
 URL: https://issues.apache.org/jira/browse/TS-796
 Project: Traffic Server
  Issue Type: Bug
Affects Versions: 2.1.8
Reporter: Zhao Yongming
  Labels: crash
 Fix For: 3.1.1


 report from user, may need more detail
 {code}
 /usr/local/ts/bin/traffic_server(mime_str_u16_set(HdrHeap*, char const*, 
 unsigned short, char const**, unsigned short*, 
 bool)+0x5d)[0x821b16d]/usr/local/ts/bin/traffic_server(url_host_set(HdrHeap*, 
 URLImpl*, char const*, int, bool)+0x51)[0x82251c1]
 /usr/local/ts/bin/traffic_server(HTTPHdr::set_url_target_from_host_field(URL*)+0x84)[0x8215a74]
 /usr/local/ts/bin/traffic_server(RemapProcessor::setup_for_remap(HttpTransact::State*)+0x272)[0x81c6132]
 /usr/local/ts/bin/traffic_server(HttpSM::do_remap_request(bool)+0x3a)[0x816bf8a]
 /usr/local/ts/bin/traffic_server(HttpSM::set_next_state()+0xad3)[0x81855b3]
 /usr/local/ts/bin/traffic_server(HttpSM::call_transact_and_set_next_state(void
  (*)(HttpTransact::State*))+0xab)[0x816903b]
 /usr/local/ts/bin/traffic_server(HttpSM::handle_api_return()+0x19f)[0x818278f]
 /usr/local/ts/bin/traffic_server(HttpSM::state_api_callout(int, 
 void*)+0x340)[0x8178f60]
 /usr/local/ts/bin/traffic_server(HttpSM::set_next_state()+0x160)[0x8184c40]
 /usr/local/ts/bin/traffic_server(HttpSM::call_transact_and_set_next_state(void
  (*)(HttpTransact::State*))+0xab)[0x816903b]
 /usr/local/ts/bin/traffic_server(HttpSM::handle_api_return()+0x19f)[0x818278f]
 /usr/local/ts/bin/traffic_server(HttpSM::state_api_callout(int, 
 void*)+0x340)[0x8178f60]
 /usr/local/ts/bin/traffic_server(HttpSM::set_next_state()+0x160)[0x8184c40]
 /usr/local/ts/bin/traffic_server(HttpSM::call_transact_and_set_next_state(void
  (*)(HttpTransact::State*))+0xab)[0x816903b]
 /usr/local/ts/bin/traffic_server(HttpSM::state_read_client_request_header(int,
  void*)+0x31d)[0x817cf9d]
 /usr/local/ts/bin/traffic_server(HttpSM::main_handler(int, 
 void*)+0x1a4)[0x8181154]
 /usr/local/ts/bin/traffic_server[0x82f6d4c]
 /usr/local/ts/bin/traffic_server(NetHandler::mainNetEvent(int, 
 Event*)+0x515)[0x82eb295]
 /usr/local/ts/bin/traffic_server(EThread::process_event(Event*, 
 int)+0x1ff)[0x831fa9f]
 /usr/local/ts/bin/traffic_server(EThread::execute()+0x449)[0x8320249]
 {code}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Closed] (TS-852) hostdb and dns system hangup

2011-07-17 Thread mohan_zl (JIRA)

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

mohan_zl closed TS-852.
---

Resolution: Fixed

This issue is covered by TS-833

 hostdb and dns system hangup
 

 Key: TS-852
 URL: https://issues.apache.org/jira/browse/TS-852
 Project: Traffic Server
  Issue Type: Bug
  Components: Core, DNS
Affects Versions: 3.1.0
Reporter: Zhao Yongming
Priority: Critical
  Labels: dns, hostdb
 Fix For: 3.1.0

 Attachments: TS-852.patch


 in my testing, all request that need go OS, fails with 30s timeout, and the 
 slow query shows data from dns missed: 
 {code}
 [Jun 22 15:33:47.183] Server {1106880832} ERROR: [8122411] Slow Request: url: 
 http://download.im.alisoft.com/aliim/AliIM6/update/packages//2011-5-4-10-10-40/0/modulesproxy/8203.xml.wwzip
  status: 0 unique id:  bytes: 0 fd: 0 client state: 6 server state: 0 
 ua_begin: 0.000 ua_read_header_done: 0.000 cache_open_read_begin: 0.000 
 cache_open_read_end: 0.000 dns_lookup_begin: 0.000 dns_lookup_end: -1.000 
 server_connect: -1.000 server_first_read: -1.000 server_read_header_done: 
 -1.000 server_close: -1.000 ua_close: 30.667 sm_finish: 30.667
 [Jun 22 15:33:47.220] Server {1099663680} ERROR: [8122422] Slow Request: url: 
 http://img.uu1001.cn/materials/original/2010-11-22/22-48/a302876929a9c40a8272ac439a16ad25e74edf71.png
  status: 0 unique id:  bytes: 0 fd: 0 client state: 6 server state: 0 
 ua_begin: 0.000 ua_read_header_done: 0.000 cache_open_read_begin: 0.000 
 cache_open_read_end: 0.000 dns_lookup_begin: 0.000 dns_lookup_end: -1.000 
 server_connect: -1.000 server_first_read: -1.000 server_read_header_done: 
 -1.000 server_close: -1.000 ua_close: 30.318 sm_finish: 30.318
 [Jun 22 15:33:47.441] Server {1098611008} ERROR: [8122421] Slow Request: url: 
 http://img02.taobaocdn.com/bao/uploaded/i2/T1mp8QXopdXXblNIZ6_061203.jpg_b.jpg
  status: 0 unique id:  bytes: 0 fd: 0 client state: 6 server state: 0 
 ua_begin: 0.000 ua_read_header_done: 0.000 cache_open_read_begin: 0.000 
 cache_open_read_end: 0.000 dns_lookup_begin: 0.000 dns_lookup_end: -1.000 
 server_connect: -1.000 server_first_read: -1.000 server_read_header_done: 
 -1.000 server_close: -1.000 ua_close: 30.597 sm_finish: 30.597
 [Jun 22 15:33:47.441] Server {1098611008} ERROR: [8122409] Slow Request: url: 
 http://img04.taobaocdn.com/tps/i4/T1EM9gXltt-440-135.jpg status: 0 
 unique id:  bytes: 0 fd: 0 client state: 6 server state: 0 ua_begin: 0.000 
 ua_read_header_done: 0.000 cache_open_read_begin: 0.000 cache_open_read_end: 
 0.000 dns_lookup_begin: 0.000 dns_lookup_end: -1.000 server_connect: -1.000 
 server_first_read: -1.000 server_read_header_done: -1.000 server_close: 
 -1.000 ua_close: 30.948 sm_finish: 30.948
 {code}
 all http SM show from {http} in DNS_LOOKUP
 and traffic.out show nothing with error, when I enable debug on 
 hostdb.*|dns.*:
 {code}
 [Jun 22 15:27:42.391] Server {1108986176} DEBUG: (hostdb) probe 
 img03.taobaocdn.com DB357D60B8247DC7 1 [ignore_timeout = 0]
 [Jun 22 15:27:42.391] Server {1108986176} DEBUG: (hostdb) timeout 64204 
 1308663404 300
 [Jun 22 15:27:42.391] Server {1108986176} DEBUG: (hostdb) delaying force 0 
 answer for img03.taobaocdn.com [timeout 0]
 [Jun 22 15:27:42.411] Server {1108986176} DEBUG: (hostdb) probe 
 img03.taobaocdn.com DB357D60B8247DC7 1 [ignore_timeout = 0]
 [Jun 22 15:27:42.411] Server {1108986176} DEBUG: (hostdb) timeout 64204 
 1308663404 300
 [Jun 22 15:27:42.411] Server {1108986176} DEBUG: (hostdb) DNS 
 img03.taobaocdn.com
 [Jun 22 15:27:42.411] Server {1108986176} DEBUG: (hostdb) enqueuing 
 additional request
 [Jun 22 15:27:42.416] Server {47177168876656} DEBUG: (hostdb) probe 127.0.0.1 
 E9B7563422C93608 1 [ignore_timeout = 0]
 [Jun 22 15:27:42.416] Server {47177168876656} DEBUG: (hostdb) immediate 
 answer for 127.0.0.1
 [Jun 22 15:27:42.422] Server {1098611008} DEBUG: (hostdb) probe 
 img08.taobaocdn.com 945198AE9AE37481 1 [ignore_timeout = 0]
 [Jun 22 15:27:42.422] Server {1098611008} DEBUG: (hostdb) timeout 64281 
 1308663327 300
 [Jun 22 15:27:42.422] Server {1098611008} DEBUG: (hostdb) delaying force 0 
 answer for img08.taobaocdn.com [timeout 0]
 [Jun 22 15:27:42.441] Server {1098611008} DEBUG: (hostdb) probe 
 img08.taobaocdn.com 945198AE9AE37481 1 [ignore_timeout = 0]
 [Jun 22 15:27:42.441] Server {1098611008} DEBUG: (hostdb) timeout 64281 
 1308663327 300
 [Jun 22 15:27:42.441] Server {1098611008} DEBUG: (hostdb) DNS 
 img08.taobaocdn.com
 [Jun 22 15:27:42.441] Server {1098611008} DEBUG: (hostdb) enqueuing 
 additional request
 [Jun 22 15:27:42.470] Server {1099663680} DEBUG: (hostdb) probe 127.0.0.1 
 E9B7563422C93608 1 [ignore_timeout = 0]
 [Jun 22 15:27:42.470] Server {1099663680} DEBUG: (hostdb) immediate answer 
 for 127.0.0.1
 [Jun 22 15:27:42.490] Server