date:20120402

[jira] [Created] (TS-1182) Add a flag to LogBuffer's for endian used

2012-04-02 Thread Leif Hedstrom (Created) (JIRA)

Add a flag to LogBuffer's for endian used
-

 Key: TS-1182
 URL: https://issues.apache.org/jira/browse/TS-1182
 Project: Traffic Server
  Issue Type: Improvement
  Components: Logging
Reporter: Leif Hedstrom
 Fix For: 3.3.0


After discussions with amc: To support reading logs (either via logcat or log 
collation) on a box with a different endian from where it was generated, we 
need to know which endian we generated the log in. Either that, or go back and 
do the htonl / ntohl  conversions always.  I favor the flag, since most sane 
platforms are little endian anyways (certainly all platforms we support are), 
so why take the cost of the conversions if they are rarely used.

This would let us check the endian flag in e.g. the log collation server, and 
in logcat like tools, and do the conversions only when necessary.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (TS-1156) Multiple time tags in a log format gets bad results

2012-04-02 Thread Leif Hedstrom (Resolved) (JIRA)


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

Leif Hedstrom resolved TS-1156.
---

Resolution: Fixed

Resolved in cc6da81a3250bb9d7b5a276c8e69b9cc00e48e19.

 Multiple time tags in a log format gets bad results
 -

 Key: TS-1156
 URL: https://issues.apache.org/jira/browse/TS-1156
 Project: Traffic Server
  Issue Type: Bug
  Components: Logging
Reporter: Leif Hedstrom
Assignee: Leif Hedstrom
 Fix For: 3.1.4


 It seems putting two (or more) date time tags in a custom log generates bad 
 results. For example, with one such tag, I see:
 {code}
    [%cqtn]
  [19/Mar/2012:14:30:51 -0600] 
 {code}
 vs
 {code}
    [%cqts %cqtn]
   [183876 07/Apr/2028:19:26:39 -0600]
 {code}
 This is obviously not the correct date now for either tags (the first is not 
 correct either). I'm guessing something in the marshalling code might be 
 corrupting the timestamp?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (TS-1178) cop will kill manager server, even cop it self

2012-04-02 Thread Zhao Yongming (Commented) (JIRA)


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

Zhao Yongming commented on TS-1178:
---

this issue is related to the cluster mode 1, and it is triggered in:
{code}
static int
heartbeat_manager()
{
  int err;

#ifdef TRACE_LOG_COP
  cop_log(COP_DEBUG, Entering heartbeat_manager()\n);
#endif
  // the CLI, and the rsport if cluster is enabled.
  err = test_mgmt_cli_port();
  if ((0 == err)  (cluster_type != NO_CLUSTER))
err = test_rs_port();
{code}

here is the tcpdump on port 8088:
{code}
[root@test58 ~]# tcpdump -n -i lo -s 1500 -vX port 8083 or port 8088
tcpdump: listening on lo, link-type EN10MB (Ethernet), capture size 1500 bytes
09:48:21.876800 IP (tos 0x0, ttl 64, id 13344, offset 0, flags [DF], proto TCP 
(6), length 60)
127.0.0.1.46344  127.0.0.1.radan-http: Flags [S], cksum 0x640b (correct), 
seq 2279143422, win 32792, options [mss 16396,sackOK,TS val 321504222 ecr 
0,nop,wscale 9], length 0
0x:  4500 003c 3420 4000 4006 089a 7f00 0001  E..4.@.@...
0x0010:  7f00 0001 b508 1f98 87d8 f7fe    
0x0020:  a002 8018 640b  0204 400c 0402 080a  d.@.
0x0030:  1329 c3de   0103 0309.)..
09:48:21.876812 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), 
length 60)
127.0.0.1.radan-http  127.0.0.1.46344: Flags [S.], cksum 0x4162 (correct), 
seq 2271462468, ack 2279143423, win 32768, options [mss 16396,sackOK,TS val 
321504222 ecr 321504222,nop,wscale 9], length 0
0x:  4500 003c  4000 4006 3cba 7f00 0001  E@.@..
0x0010:  7f00 0001 1f98 b508 8763 c444 87d8 f7ff  .c.D
0x0020:  a012 8000 4162  0204 400c 0402 080a  Ab@.
0x0030:  1329 c3de 1329 c3de 0103 0309.)...)..
09:48:21.876821 IP (tos 0x0, ttl 64, id 13345, offset 0, flags [DF], proto TCP 
(6), length 52)
127.0.0.1.46344  127.0.0.1.radan-http: Flags [.], cksum 0x2a48 (correct), 
ack 1, win 65, options [nop,nop,TS val 321504222 ecr 321504222], length 0
0x:  4500 0034 3421 4000 4006 08a1 7f00 0001  E..44!@.@...
0x0010:  7f00 0001 b508 1f98 87d8 f7ff 8763 c445  .c.E
0x0020:  8010 0041 2a48  0101 080a 1329 c3de  ...A*H...)..
0x0030:  1329 c3de.)..
09:48:21.876903 IP (tos 0x0, ttl 64, id 13346, offset 0, flags [DF], proto TCP 
(6), length 85)
127.0.0.1.46344  127.0.0.1.radan-http: Flags [P.], cksum 0xfe49 (incorrect 
- 0xdcc6), seq 1:34, ack 1, win 65, options [nop,nop,TS val 321504222 ecr 
321504222], length 33
0x:  4500 0055 3422 4000 4006 087f 7f00 0001  E..U4@.@...
0x0010:  7f00 0001 b508 1f98 87d8 f7ff 8763 c445  .c.E
0x0020:  8018 0041 fe49  0101 080a 1329 c3de  ...A.I...)..
0x0030:  1329 c3de 7265 6164 2070 726f 7879 2e63  .)..read.proxy.c
0x0040:  6f6e 6669 672e 6d61 6e61 6765 725f 6269  onfig.manager_bi
0x0050:  6e61 7279 0a nary.
09:48:21.876941 IP (tos 0x0, ttl 64, id 1947, offset 0, flags [DF], proto TCP 
(6), length 52)
127.0.0.1.radan-http  127.0.0.1.46344: Flags [.], cksum 0x2a28 (correct), 
ack 34, win 64, options [nop,nop,TS val 321504222 ecr 321504222], length 0
0x:  4500 0034 079b 4000 4006 3527 7f00 0001  E..4..@.@.5'
0x0010:  7f00 0001 1f98 b508 8763 c445 87d8 f820  .c.E
0x0020:  8010 0040 2a28  0101 080a 1329 c3de  ...@*(...)..
0x0030:  1329 c3de.)..
09:48:21.876983 IP (tos 0x0, ttl 64, id 1948, offset 0, flags [DF], proto TCP 
(6), length 113)
127.0.0.1.radan-http  127.0.0.1.46344: Flags [P.], cksum 0xfe65 (incorrect 
- 0x0738), seq 1:62, ack 34, win 64, options [nop,nop,TS val 321504222 ecr 
321504222], length 61
0x:  4500 0071 079c 4000 4006 34e9 7f00 0001  E..q..@.@.4.
0x0010:  7f00 0001 1f98 b508 8763 c445 87d8 f820  .c.E
0x0020:  8018 0040 fe65  0101 080a 1329 c3de  ...@.e...)..
0x0030:  1329 c3de 0a52 6563 6f72 6420 2770 726f  .)...Record.'pro
0x0040:  7879 2e63 6f6e 6669 672e 6d61 6e61 6765  xy.config.manage
0x0050:  725f 6269 6e61 7279 2720 5661 6c3a 2027  r_binary'.Val:.'
0x0060:  7472 6166 6669 635f 6d61 6e61 6765 7227  traffic_manager'
0x0070:  0a   .
09:48:21.876990 IP (tos 0x0, ttl 64, id 13347, offset 0, flags [DF], proto TCP 
(6), length 52)
127.0.0.1.46344  127.0.0.1.radan-http: Flags [.], cksum 0x29ea (correct), 
ack 62, win 65, options [nop,nop,TS val 321504222 ecr 321504222], length 0
0x:  4500 0034 3423 4000 4006 089f 7f00 0001  E..44#@.@...
0x0010:  7f00 0001 b508 1f98 87d8 f820 8763 c482

[jira] [Created] (TS-1182) Add a flag to LogBuffer's for endian used

[jira] [Resolved] (TS-1156) Multiple time tags in a log format gets bad results

[jira] [Commented] (TS-1178) cop will kill manager server, even cop it self

3 matches

Site Navigation

Mail list logo

Footer information