from:"Adam Twardowski \(JIRA\)"

[jira] [Commented] (TS-2216) Custom Log %cquup not always initialized properly.

2013-10-15 Thread Adam Twardowski (JIRA)


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

Adam Twardowski commented on TS-2216:
-

The patch from TS-1988 had no effect, but I did notice that to trigger the 
issue all I need to do is telnet to the ATS port and disconnect without sending 
a request. There will be about a 20% chance of corruption at the end of the log 
line.  My latest testing is against 4.0.2

 Custom Log %cquup not always initialized properly.
 

 Key: TS-2216
 URL: https://issues.apache.org/jira/browse/TS-2216
 Project: Traffic Server
  Issue Type: Bug
  Components: Logging
Reporter: Adam Twardowski
 Fix For: 4.1.0


 Noticed this in my log output, it appears that the %cquup log variable is 
 now always initialized properly.
 {code}
 LogFormat
   Name = csv/
   Format = 
 \%cqtn\,\%ttmsf\,\%{X-Forwarded-For}cqh\,\%crc\,\%pssc\,\%cqhl\,\%pscl\,\%cqhm\,\%cquuc\,\%cquuh\,\%cquup\/
 /LogFormat
 12/Sep/2013:17:48:16 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,à
 12/Sep/2013:17:48:17 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡62R
 12/Sep/2013:17:48:17 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡62R
 12/Sep/2013:17:48:17 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,1
 12/Sep/2013:17:48:17 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡62R
 12/Sep/2013:17:48:17 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,±
 12/Sep/2013:17:48:17 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡62R
 12/Sep/2013:17:48:18 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¢62R
 12/Sep/2013:17:48:18 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¢62R
 12/Sep/2013:17:48:19 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,£62R
 12/Sep/2013:17:48:19 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,£62R
 12/Sep/2013:17:48:19 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,
 12/Sep/2013:17:48:19 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,£62R
 12/Sep/2013:17:48:19 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,£62R
 12/Sep/2013:17:48:19 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,·
 12/Sep/2013:17:48:20 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¤62R
 12/Sep/2013:17:48:20 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,r/player.swf
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¥62R
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¥62R
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¥62R
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,!
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¥62R
 12/Sep/2013:17:48:22 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¦62R
 {code}



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Commented] (TS-2216) Custom Log %cquup not always initialized properly.

2013-10-15 Thread Adam Twardowski (JIRA)


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

Adam Twardowski commented on TS-2216:
-

Test6 below also causes the problem, so it appears that the actual issue is in 
cquuh.

{code}
LogFormat
  Name = test6/
  Format = %cquuh %cquuc/
/LogFormat
{code}

 Custom Log %cquup not always initialized properly.
 

 Key: TS-2216
 URL: https://issues.apache.org/jira/browse/TS-2216
 Project: Traffic Server
  Issue Type: Bug
  Components: Logging
Reporter: Adam Twardowski
 Fix For: 4.1.0


 Noticed this in my log output, it appears that the %cquup log variable is 
 now always initialized properly.
 {code}
 LogFormat
   Name = csv/
   Format = 
 \%cqtn\,\%ttmsf\,\%{X-Forwarded-For}cqh\,\%crc\,\%pssc\,\%cqhl\,\%pscl\,\%cqhm\,\%cquuc\,\%cquuh\,\%cquup\/
 /LogFormat
 12/Sep/2013:17:48:16 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,à
 12/Sep/2013:17:48:17 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡62R
 12/Sep/2013:17:48:17 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡62R
 12/Sep/2013:17:48:17 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,1
 12/Sep/2013:17:48:17 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡62R
 12/Sep/2013:17:48:17 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,±
 12/Sep/2013:17:48:17 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡62R
 12/Sep/2013:17:48:18 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¢62R
 12/Sep/2013:17:48:18 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¢62R
 12/Sep/2013:17:48:19 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,£62R
 12/Sep/2013:17:48:19 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,£62R
 12/Sep/2013:17:48:19 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,
 12/Sep/2013:17:48:19 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,£62R
 12/Sep/2013:17:48:19 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,£62R
 12/Sep/2013:17:48:19 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,·
 12/Sep/2013:17:48:20 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¤62R
 12/Sep/2013:17:48:20 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,r/player.swf
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¥62R
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¥62R
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¥62R
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,!
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¥62R
 12/Sep/2013:17:48:22 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¦62R
 {code}



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Commented] (TS-2216) Custom Log %cquup not always initialized properly.

2013-10-14 Thread Adam Twardowski (JIRA)


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

Adam Twardowski commented on TS-2216:
-

Disregard previous comment, I'm also seeing binary data in my logs when logging 
to a local file.

 Custom Log %cquup not always initialized properly.
 

 Key: TS-2216
 URL: https://issues.apache.org/jira/browse/TS-2216
 Project: Traffic Server
  Issue Type: Bug
  Components: Logging
Reporter: Adam Twardowski
 Fix For: 4.1.0


 Noticed this in my log output, it appears that the %cquup log variable is 
 now always initialized properly.
 {code}
 LogFormat
   Name = csv/
   Format = 
 \%cqtn\,\%ttmsf\,\%{X-Forwarded-For}cqh\,\%crc\,\%pssc\,\%cqhl\,\%pscl\,\%cqhm\,\%cquuc\,\%cquuh\,\%cquup\/
 /LogFormat
 12/Sep/2013:17:48:16 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,à
 12/Sep/2013:17:48:17 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡62R
 12/Sep/2013:17:48:17 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡62R
 12/Sep/2013:17:48:17 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,1
 12/Sep/2013:17:48:17 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡62R
 12/Sep/2013:17:48:17 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,±
 12/Sep/2013:17:48:17 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡62R
 12/Sep/2013:17:48:18 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¢62R
 12/Sep/2013:17:48:18 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¢62R
 12/Sep/2013:17:48:19 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,£62R
 12/Sep/2013:17:48:19 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,£62R
 12/Sep/2013:17:48:19 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,
 12/Sep/2013:17:48:19 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,£62R
 12/Sep/2013:17:48:19 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,£62R
 12/Sep/2013:17:48:19 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,·
 12/Sep/2013:17:48:20 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¤62R
 12/Sep/2013:17:48:20 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,r/player.swf
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¥62R
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¥62R
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¥62R
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,!
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¥62R
 12/Sep/2013:17:48:22 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¦62R
 {code}



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Commented] (TS-2216) Custom Log %cquup not always initialized properly.

2013-10-08 Thread Adam Twardowski (JIRA)


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

Adam Twardowski commented on TS-2216:
-

In my specific setup, I've got a bunch of servers sending logs to a collation 
server.  The collation server doesn't have any plugins enabled, and the other 
servers just have stats_over_http.so enabled.

 Custom Log %cquup not always initialized properly.
 

 Key: TS-2216
 URL: https://issues.apache.org/jira/browse/TS-2216
 Project: Traffic Server
  Issue Type: Bug
  Components: Logging
Reporter: Adam Twardowski
 Fix For: 4.1.0


 Noticed this in my log output, it appears that the %cquup log variable is 
 now always initialized properly.
 {code}
 LogFormat
   Name = csv/
   Format = 
 \%cqtn\,\%ttmsf\,\%{X-Forwarded-For}cqh\,\%crc\,\%pssc\,\%cqhl\,\%pscl\,\%cqhm\,\%cquuc\,\%cquuh\,\%cquup\/
 /LogFormat
 12/Sep/2013:17:48:16 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,à
 12/Sep/2013:17:48:17 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡62R
 12/Sep/2013:17:48:17 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡62R
 12/Sep/2013:17:48:17 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,1
 12/Sep/2013:17:48:17 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡62R
 12/Sep/2013:17:48:17 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,±
 12/Sep/2013:17:48:17 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡62R
 12/Sep/2013:17:48:18 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¢62R
 12/Sep/2013:17:48:18 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¢62R
 12/Sep/2013:17:48:19 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,£62R
 12/Sep/2013:17:48:19 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,£62R
 12/Sep/2013:17:48:19 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,
 12/Sep/2013:17:48:19 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,£62R
 12/Sep/2013:17:48:19 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,£62R
 12/Sep/2013:17:48:19 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,·
 12/Sep/2013:17:48:20 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¤62R
 12/Sep/2013:17:48:20 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,r/player.swf
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¥62R
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¥62R
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¥62R
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,!
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¥62R
 12/Sep/2013:17:48:22 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¦62R
 {code}



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Commented] (TS-2216) Custom Log %cquup not always initialized properly.

2013-10-08 Thread Adam Twardowski (JIRA)


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

Adam Twardowski commented on TS-2216:
-

I have the plugin loaded, but I rarely ever access the stats page unless 
there's some issue, and there are many thousands of lines like that in my 
access logs.  I don't know if that answers your question or not.  I guess it's 
possible that something odd is happening under the hood that could be causing 
the plugin to generate spontaneous log messages.

Would you suggest that I try disabling the stats module everywhere and see if I 
still get the error?

 Custom Log %cquup not always initialized properly.
 

 Key: TS-2216
 URL: https://issues.apache.org/jira/browse/TS-2216
 Project: Traffic Server
  Issue Type: Bug
  Components: Logging
Reporter: Adam Twardowski
 Fix For: 4.1.0


 Noticed this in my log output, it appears that the %cquup log variable is 
 now always initialized properly.
 {code}
 LogFormat
   Name = csv/
   Format = 
 \%cqtn\,\%ttmsf\,\%{X-Forwarded-For}cqh\,\%crc\,\%pssc\,\%cqhl\,\%pscl\,\%cqhm\,\%cquuc\,\%cquuh\,\%cquup\/
 /LogFormat
 12/Sep/2013:17:48:16 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,à
 12/Sep/2013:17:48:17 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡62R
 12/Sep/2013:17:48:17 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡62R
 12/Sep/2013:17:48:17 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,1
 12/Sep/2013:17:48:17 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡62R
 12/Sep/2013:17:48:17 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,±
 12/Sep/2013:17:48:17 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡62R
 12/Sep/2013:17:48:18 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¢62R
 12/Sep/2013:17:48:18 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¢62R
 12/Sep/2013:17:48:19 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,£62R
 12/Sep/2013:17:48:19 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,£62R
 12/Sep/2013:17:48:19 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,
 12/Sep/2013:17:48:19 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,£62R
 12/Sep/2013:17:48:19 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,£62R
 12/Sep/2013:17:48:19 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,·
 12/Sep/2013:17:48:20 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¤62R
 12/Sep/2013:17:48:20 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,r/player.swf
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¥62R
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¥62R
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¥62R
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,!
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¥62R
 12/Sep/2013:17:48:22 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¦62R
 {code}



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Commented] (TS-2216) Custom Log %cquup not always initialized properly.

2013-10-08 Thread Adam Twardowski (JIRA)


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

Adam Twardowski commented on TS-2216:
-

I have the plugin loaded, but I rarely ever access the stats page unless 
there's some issue, and there are many thousands of lines like that in my 
access logs.  I don't know if that answers your question or not.  I guess it's 
possible that something odd is happening under the hood that could be causing 
the plugin to generate spontaneous log messages.

Would you suggest that I try disabling the stats module everywhere and see if I 
still get the error?

 Custom Log %cquup not always initialized properly.
 

 Key: TS-2216
 URL: https://issues.apache.org/jira/browse/TS-2216
 Project: Traffic Server
  Issue Type: Bug
  Components: Logging
Reporter: Adam Twardowski
 Fix For: 4.1.0


 Noticed this in my log output, it appears that the %cquup log variable is 
 now always initialized properly.
 {code}
 LogFormat
   Name = csv/
   Format = 
 \%cqtn\,\%ttmsf\,\%{X-Forwarded-For}cqh\,\%crc\,\%pssc\,\%cqhl\,\%pscl\,\%cqhm\,\%cquuc\,\%cquuh\,\%cquup\/
 /LogFormat
 12/Sep/2013:17:48:16 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,à
 12/Sep/2013:17:48:17 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡62R
 12/Sep/2013:17:48:17 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡62R
 12/Sep/2013:17:48:17 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,1
 12/Sep/2013:17:48:17 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡62R
 12/Sep/2013:17:48:17 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,±
 12/Sep/2013:17:48:17 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡62R
 12/Sep/2013:17:48:18 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¢62R
 12/Sep/2013:17:48:18 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¢62R
 12/Sep/2013:17:48:19 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,£62R
 12/Sep/2013:17:48:19 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,£62R
 12/Sep/2013:17:48:19 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,
 12/Sep/2013:17:48:19 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,£62R
 12/Sep/2013:17:48:19 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,£62R
 12/Sep/2013:17:48:19 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,·
 12/Sep/2013:17:48:20 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¤62R
 12/Sep/2013:17:48:20 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,r/player.swf
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¥62R
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¥62R
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¥62R
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,!
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¥62R
 12/Sep/2013:17:48:22 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¦62R
 {code}



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Commented] (TS-2216) Custom Log %cquup not always initialized properly.

2013-10-08 Thread Adam Twardowski (JIRA)


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

Adam Twardowski commented on TS-2216:
-

So disabling the plugin had no effect.  I also enabled local logging on each 
server in addition to the collation server logging.  What's interesting is that 
none of the local log files are logging the ERROR_UNKNOWN at all, that is only 
showing up on the collation server.  My collation server is just an instance of 
trafficserver-3.2.5, and my actual servers are running 3.3.4, I'm not sure if 
that version mismatch is relevant at all.

 Custom Log %cquup not always initialized properly.
 

 Key: TS-2216
 URL: https://issues.apache.org/jira/browse/TS-2216
 Project: Traffic Server
  Issue Type: Bug
  Components: Logging
Reporter: Adam Twardowski
 Fix For: 4.1.0


 Noticed this in my log output, it appears that the %cquup log variable is 
 now always initialized properly.
 {code}
 LogFormat
   Name = csv/
   Format = 
 \%cqtn\,\%ttmsf\,\%{X-Forwarded-For}cqh\,\%crc\,\%pssc\,\%cqhl\,\%pscl\,\%cqhm\,\%cquuc\,\%cquuh\,\%cquup\/
 /LogFormat
 12/Sep/2013:17:48:16 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,à
 12/Sep/2013:17:48:17 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡62R
 12/Sep/2013:17:48:17 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡62R
 12/Sep/2013:17:48:17 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,1
 12/Sep/2013:17:48:17 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡62R
 12/Sep/2013:17:48:17 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,±
 12/Sep/2013:17:48:17 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡62R
 12/Sep/2013:17:48:18 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¢62R
 12/Sep/2013:17:48:18 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¢62R
 12/Sep/2013:17:48:19 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,£62R
 12/Sep/2013:17:48:19 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,£62R
 12/Sep/2013:17:48:19 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,
 12/Sep/2013:17:48:19 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,£62R
 12/Sep/2013:17:48:19 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,£62R
 12/Sep/2013:17:48:19 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,·
 12/Sep/2013:17:48:20 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¤62R
 12/Sep/2013:17:48:20 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,r/player.swf
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¥62R
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¥62R
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¥62R
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,!
 12/Sep/2013:17:48:21 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¥62R
 12/Sep/2013:17:48:22 
 -0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¦62R
 {code}



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Created] (TS-2223) Incorrect timezone offset when using %cqtn

2013-09-13 Thread Adam Twardowski (JIRA)

Adam Twardowski created TS-2223:
---

 Summary: Incorrect timezone offset when using %cqtn
 Key: TS-2223
 URL: https://issues.apache.org/jira/browse/TS-2223
 Project: Traffic Server
  Issue Type: Bug
  Components: Logging
Reporter: Adam Twardowski


My logs are showing the incorrect timezone offset for EDT (Eastern Daylight 
time).  ATS logs are showing -0500 when it should be -0400.  Apache returns the 
correct timezone.

ATS:
{code}
13/Sep/2013:13:08:36 -0500...
{code}

Apache:
{code}
[13/Sep/2013:13:07:59 -0400]
{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] [Created] (TS-2216) Custom Log %cquup not always initialized properly.

2013-09-12 Thread Adam Twardowski (JIRA)

Adam Twardowski created TS-2216:
---

 Summary: Custom Log %cquup not always initialized properly.
 Key: TS-2216
 URL: https://issues.apache.org/jira/browse/TS-2216
 Project: Traffic Server
  Issue Type: Bug
  Components: Logging
Reporter: Adam Twardowski


Noticed this in my log output, it appears that the %cquup log variable is now 
always initialized properly.

LogFormat
  Name = csv/
  Format = 
\%cqtn\,\%ttmsf\,\%{X-Forwarded-For}cqh\,\%crc\,\%pssc\,\%cqhl\,\%pscl\,\%cqhm\,\%cquuc\,\%cquuh\,\%cquup\/
/LogFormat


12/Sep/2013:17:48:16 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,à
12/Sep/2013:17:48:17 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡62R
12/Sep/2013:17:48:17 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡62R
12/Sep/2013:17:48:17 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,1
12/Sep/2013:17:48:17 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡62R
12/Sep/2013:17:48:17 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,±
12/Sep/2013:17:48:17 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡62R
12/Sep/2013:17:48:18 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¢62R
12/Sep/2013:17:48:18 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¢62R
12/Sep/2013:17:48:19 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,£62R
12/Sep/2013:17:48:19 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,£62R
12/Sep/2013:17:48:19 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,
12/Sep/2013:17:48:19 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,£62R
12/Sep/2013:17:48:19 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,£62R
12/Sep/2013:17:48:19 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,·
12/Sep/2013:17:48:20 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¤62R
12/Sep/2013:17:48:20 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,r/player.swf
12/Sep/2013:17:48:21 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,
12/Sep/2013:17:48:21 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡
12/Sep/2013:17:48:21 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¥62R
12/Sep/2013:17:48:21 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¥62R
12/Sep/2013:17:48:21 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¥62R
12/Sep/2013:17:48:21 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,!
12/Sep/2013:17:48:21 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¥62R
12/Sep/2013:17:48:22 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¦62R

--
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] [Updated] (TS-2216) Custom Log %cquup not always initialized properly.

2013-09-12 Thread Adam Twardowski (JIRA)


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

Adam Twardowski updated TS-2216:


Description: 
Noticed this in my log output, it appears that the %cquup log variable is now 
always initialized properly.

{code}
LogFormat
  Name = csv/
  Format = 
\%cqtn\,\%ttmsf\,\%{X-Forwarded-For}cqh\,\%crc\,\%pssc\,\%cqhl\,\%pscl\,\%cqhm\,\%cquuc\,\%cquuh\,\%cquup\/
/LogFormat

12/Sep/2013:17:48:16 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,à
12/Sep/2013:17:48:17 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡62R
12/Sep/2013:17:48:17 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡62R
12/Sep/2013:17:48:17 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,1
12/Sep/2013:17:48:17 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡62R
12/Sep/2013:17:48:17 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,±
12/Sep/2013:17:48:17 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡62R
12/Sep/2013:17:48:18 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¢62R
12/Sep/2013:17:48:18 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¢62R
12/Sep/2013:17:48:19 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,£62R
12/Sep/2013:17:48:19 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,£62R
12/Sep/2013:17:48:19 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,
12/Sep/2013:17:48:19 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,£62R
12/Sep/2013:17:48:19 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,£62R
12/Sep/2013:17:48:19 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,·
12/Sep/2013:17:48:20 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¤62R
12/Sep/2013:17:48:20 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,r/player.swf
12/Sep/2013:17:48:21 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,
12/Sep/2013:17:48:21 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡
12/Sep/2013:17:48:21 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¥62R
12/Sep/2013:17:48:21 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¥62R
12/Sep/2013:17:48:21 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¥62R
12/Sep/2013:17:48:21 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,!
12/Sep/2013:17:48:21 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¥62R
12/Sep/2013:17:48:22 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¦62R
{code}

  was:
Noticed this in my log output, it appears that the %cquup log variable is now 
always initialized properly.

LogFormat
  Name = csv/
  Format = 
\%cqtn\,\%ttmsf\,\%{X-Forwarded-For}cqh\,\%crc\,\%pssc\,\%cqhl\,\%pscl\,\%cqhm\,\%cquuc\,\%cquuh\,\%cquup\/
/LogFormat


12/Sep/2013:17:48:16 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,à
12/Sep/2013:17:48:17 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡62R
12/Sep/2013:17:48:17 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡62R
12/Sep/2013:17:48:17 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,1
12/Sep/2013:17:48:17 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡62R
12/Sep/2013:17:48:17 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,±
12/Sep/2013:17:48:17 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡62R
12/Sep/2013:17:48:18 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¢62R
12/Sep/2013:17:48:18 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¢62R
12/Sep/2013:17:48:19 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,£62R
12/Sep/2013:17:48:19 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,£62R
12/Sep/2013:17:48:19 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,
12/Sep/2013:17:48:19 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,£62R
12/Sep/2013:17:48:19 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,£62R
12/Sep/2013:17:48:19 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,·
12/Sep/2013:17:48:20 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¤62R
12/Sep/2013:17:48:20 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,r/player.swf
12/Sep/2013:17:48:21 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,
12/Sep/2013:17:48:21 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¡
12/Sep/2013:17:48:21 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¥62R
12/Sep/2013:17:48:21 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¥62R
12/Sep/2013:17:48:21 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¥62R
12/Sep/2013:17:48:21 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,!
12/Sep/2013:17:48:21 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¥62R
12/Sep/2013:17:48:22 
-0500,0.000,-,ERROR_UNKNOWN(90),000,15,0,-,-,-,¦62R


 Custom Log %cquup not always initialized properly.
 

 Key: TS-2216
 URL: https://issues.apache.org/jira/browse/TS-2216
 Project: Traffic Server
  Issue Type: Bug
  Components: Logging
Reporter: Adam Twardowski
 Fix For: 4.1.0


 Noticed this in my log output, it appears that the %cquup log variable is 
 now always initialized properly.
 {code}
 LogFormat
   Name = csv/
   Format =

[jira] [Created] (TS-2159) First log rotation should happen at proxy.config.log.rolling_size_mb

2013-08-26 Thread Adam Twardowski (JIRA)

Adam Twardowski created TS-2159:
---

 Summary: First log rotation should happen at 
proxy.config.log.rolling_size_mb
 Key: TS-2159
 URL: https://issues.apache.org/jira/browse/TS-2159
 Project: Traffic Server
  Issue Type: Improvement
  Components: Logging
Reporter: Adam Twardowski


If a 50MB log file exists, and proxy.config.log.rolling_size_mb is set to 
100MB, then the first log rotate won't happen until it reaches 150MB.  The 
logging system appears to be counting bytes written to the log instead of file 
size.

--
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] [Updated] (TS-2159) First log rotation should happen at proxy.config.log.rolling_size_mb

2013-08-26 Thread Adam Twardowski (JIRA)


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

Adam Twardowski updated TS-2159:


Priority: Minor  (was: Major)

 First log rotation should happen at proxy.config.log.rolling_size_mb
 

 Key: TS-2159
 URL: https://issues.apache.org/jira/browse/TS-2159
 Project: Traffic Server
  Issue Type: Improvement
  Components: Logging
Reporter: Adam Twardowski
Priority: Minor

 If a 50MB log file exists, and proxy.config.log.rolling_size_mb is set to 
 100MB, then the first log rotate won't happen until it reaches 150MB.  The 
 logging system appears to be counting bytes written to the log instead of 
 file size.

--
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] [Created] (TS-2153) traffic_manager -tsArgs doesn't work

2013-08-23 Thread Adam Twardowski (JIRA)

Adam Twardowski created TS-2153:
---

 Summary: traffic_manager -tsArgs doesn't work
 Key: TS-2153
 URL: https://issues.apache.org/jira/browse/TS-2153
 Project: Traffic Server
  Issue Type: Bug
  Components: Management
Reporter: Adam Twardowski


traffic_manager -tsArgs -T 'log.*'

Running the above command on the 4.0.0 branch commit 
c8931df15e33924bb459d40859a0b49331a6dbaf

resulted in no running traffic_server and the following ps output

nobody   16807  0.1  0.9 410884 18272 pts/0Sl+  16:58   0:00 
traffic_manager -tsArgs -T log.*
nobody   16816  0.0  0.0  0 0 pts/0Z+   16:58   0:00 
[traffic_manager] defunct
root 16818  0.0  0.0 103240   864 pts/1S+   16:59   0:00 grep tr


manger.log output
--
[Aug 23 17:09:52.965] {0x7f61127b07e0} STATUS: opened 
/usr/local/var/log/trafficserver/manager.log
[Aug 23 17:09:52.966] {0x7f61127b07e0} NOTE: updated diags config
[Aug 23 17:09:52.967] Manager {0x7f61127b07e0} NOTE: [main] Traffic Server 
Args: ' -T log.*'
[Aug 23 17:09:52.967] Manager {0x7f61127b07e0} NOTE: [ClusterCom::ClusterCom] 
Node running on OS: 'Linux' Release: '2.6.32-358.el6.x86_64'
[Aug 23 17:09:52.968] Manager {0x7f61127b07e0} NOTE: 
[LocalManager::listenForProxy] Listening on port: 80
[Aug 23 17:09:52.968] Manager {0x7f61127b07e0} NOTE: [TrafficManager] Setup 
complete
[Aug 23 17:09:53.986] Manager {0x7f61127b07e0} NOTE: [LocalManager::startProxy] 
Launching ts process
[Aug 23 17:09:53.989] Manager {0x7f61127b07e0} FATAL: 
[LocalManager::startProxy] ts options must contain -M
[Aug 23 17:09:53.989] Manager {0x7f61127b07e0} FATAL:  (last system error 0: 
Success)
[Aug 23 17:09:53.989] Manager {0x7f61127b07e0} NOTE: 
[LocalManager::mgmtShutdown] Executing shutdown request.
[Aug 23 17:09:53.989] Manager {0x7f61127b07e0} NOTE: 
[LocalManager::processShutdown] Executing process shutdown request.



--
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] [Created] (TS-2140) Stats module is showing proxy.process.cache.direntries.used greater then proxy.process.cache.direntries.total

2013-08-19 Thread Adam Twardowski (JIRA)

Adam Twardowski created TS-2140:
---

 Summary: Stats module is showing 
proxy.process.cache.direntries.used greater then 
proxy.process.cache.direntries.total
 Key: TS-2140
 URL: https://issues.apache.org/jira/browse/TS-2140
 Project: Traffic Server
  Issue Type: Bug
  Components: Stats
Reporter: Adam Twardowski


using the stats_over_http.so module, reported 
proxy.process.cache.direntries.used is greater then 
proxy.process.cache.direntries.total

{ global: {
proxy.process.version.server.short: 3.3.4-dev,
proxy.process.version.server.long: Apache Traffic Server - traffic_server - 
3.3.4-dev - (build # 63013 on Jul 30 2013 at 13:23:55),
proxy.process.version.server.build_number: 63013,
proxy.process.version.server.build_time: 13:23:55,
proxy.process.version.server.build_date: Jul 30 2013,
proxy.process.version.server.build_machine: X,
proxy.process.version.server.build_person: root,
proxy.process.http.completed_requests: 1771631878,
proxy.process.http.total_incoming_connections: 1771779452,
proxy.process.http.total_client_connections: 1771779452,
proxy.process.http.total_client_connections_ipv4: 1771779452,
proxy.process.http.total_client_connections_ipv6: 0,
proxy.process.http.total_server_connections: 486478731,
proxy.process.http.total_parent_proxy_connections: 0,
proxy.process.http.avg_transactions_per_client_connection: 1.15,
proxy.process.http.avg_transactions_per_server_connection: 1.00,
proxy.process.http.avg_transactions_per_parent_connection: 0.00,
proxy.process.http.client_connection_time: 0,
proxy.process.http.parent_proxy_connection_time: 0,
proxy.process.http.server_connection_time: 0,
proxy.process.http.cache_connection_time: 0,
proxy.process.http.transaction_counts.errors.pre_accept_hangups: 0,
proxy.process.http.transaction_totaltime.errors.pre_accept_hangups: 
0.00,
proxy.process.http.transaction_counts.errors.empty_hangups: 0,
proxy.process.http.transaction_totaltime.errors.empty_hangups: 0.00,
proxy.process.http.transaction_counts.errors.early_hangups: 0,
proxy.process.http.transaction_totaltime.errors.early_hangups: 0.00,
proxy.process.http.incoming_requests: 1766073976,
proxy.process.http.outgoing_requests: 484585207,
proxy.process.http.incoming_responses: 486478535,
proxy.process.http.invalid_client_requests: 240,
proxy.process.http.missing_host_hdr: 0,
proxy.process.http.get_requests: 1765677046,
proxy.process.http.head_requests: 392884,
proxy.process.http.trace_requests: 8,
proxy.process.http.options_requests: 1562,
proxy.process.http.post_requests: 662,
proxy.process.http.put_requests: 7,
proxy.process.http.push_requests: 0,
proxy.process.http.delete_requests: 0,
proxy.process.http.purge_requests: 0,
proxy.process.http.connect_requests: 0,
proxy.process.http.extension_method_requests: 1807,
proxy.process.http.client_no_cache_requests: 0,
proxy.process.http.broken_server_connections: 63475,
proxy.process.http.cache_lookups: 1765896837,
proxy.process.http.cache_writes: 119147534,
proxy.process.http.cache_updates: 7812961,
proxy.process.http.cache_deletes: 60058,
proxy.process.http.tunnels: 5017,
proxy.process.http.throttled_proxy_only: 0,
proxy.process.http.request_taxonomy.i0_n0_m0: 0,
proxy.process.http.request_taxonomy.i1_n0_m0: 0,
proxy.process.http.request_taxonomy.i0_n1_m0: 0,
proxy.process.http.request_taxonomy.i1_n1_m0: 0,
proxy.process.http.request_taxonomy.i0_n0_m1: 0,
proxy.process.http.request_taxonomy.i1_n0_m1: 0,
proxy.process.http.request_taxonomy.i0_n1_m1: 0,
proxy.process.http.request_taxonomy.i1_n1_m1: 0,
proxy.process.http.icp_suggested_lookups: 0,
proxy.process.http.client_transaction_time: 0,
proxy.process.http.client_write_time: 0,
proxy.process.http.server_read_time: 0,
proxy.process.http.icp_transaction_time: 0,
proxy.process.http.icp_raw_transaction_time: 0,
proxy.process.http.parent_proxy_transaction_time: 0,
proxy.process.http.parent_proxy_raw_transaction_time: 0,
proxy.process.http.server_transaction_time: 0,
proxy.process.http.server_raw_transaction_time: 0,
proxy.process.http.user_agent_request_header_total_size: 797103745655,
proxy.process.http.user_agent_response_header_total_size: 697699513781,
proxy.process.http.user_agent_request_document_total_size: 419549,
proxy.process.http.user_agent_response_document_total_size: 190278962740080,
proxy.process.http.origin_server_request_header_total_size: 265407277593,
proxy.process.http.origin_server_response_header_total_size: 127176507932,
proxy.process.http.origin_server_request_document_total_size: 419549,
proxy.process.http.origin_server_response_document_total_size: 
23039301010838,
proxy.process.http.parent_proxy_request_total_bytes: 0,
proxy.process.http.parent_proxy_response_total_bytes: 0,
proxy.process.http.pushed_response_header_total_size: 0,
proxy.process.http.pushed_document_total_size: 0,
proxy.process.http.response_document_size_100:

[jira] [Updated] (TS-2140) Stats module is showing proxy.process.cache.direntries.used greater then proxy.process.cache.direntries.total

2013-08-19 Thread Adam Twardowski (JIRA)


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

Adam Twardowski updated TS-2140:


Priority: Minor  (was: Major)

 Stats module is showing proxy.process.cache.direntries.used greater then 
 proxy.process.cache.direntries.total
 -

 Key: TS-2140
 URL: https://issues.apache.org/jira/browse/TS-2140
 Project: Traffic Server
  Issue Type: Bug
  Components: Stats
Reporter: Adam Twardowski
Priority: Minor

 using the stats_over_http.so module, reported 
 proxy.process.cache.direntries.used is greater then 
 proxy.process.cache.direntries.total
 { global: {
 proxy.process.version.server.short: 3.3.4-dev,
 proxy.process.version.server.long: Apache Traffic Server - traffic_server 
 - 3.3.4-dev - (build # 63013 on Jul 30 2013 at 13:23:55),
 proxy.process.version.server.build_number: 63013,
 proxy.process.version.server.build_time: 13:23:55,
 proxy.process.version.server.build_date: Jul 30 2013,
 proxy.process.version.server.build_machine: X,
 proxy.process.version.server.build_person: root,
 proxy.process.http.completed_requests: 1771631878,
 proxy.process.http.total_incoming_connections: 1771779452,
 proxy.process.http.total_client_connections: 1771779452,
 proxy.process.http.total_client_connections_ipv4: 1771779452,
 proxy.process.http.total_client_connections_ipv6: 0,
 proxy.process.http.total_server_connections: 486478731,
 proxy.process.http.total_parent_proxy_connections: 0,
 proxy.process.http.avg_transactions_per_client_connection: 1.15,
 proxy.process.http.avg_transactions_per_server_connection: 1.00,
 proxy.process.http.avg_transactions_per_parent_connection: 0.00,
 proxy.process.http.client_connection_time: 0,
 proxy.process.http.parent_proxy_connection_time: 0,
 proxy.process.http.server_connection_time: 0,
 proxy.process.http.cache_connection_time: 0,
 proxy.process.http.transaction_counts.errors.pre_accept_hangups: 0,
 proxy.process.http.transaction_totaltime.errors.pre_accept_hangups: 
 0.00,
 proxy.process.http.transaction_counts.errors.empty_hangups: 0,
 proxy.process.http.transaction_totaltime.errors.empty_hangups: 0.00,
 proxy.process.http.transaction_counts.errors.early_hangups: 0,
 proxy.process.http.transaction_totaltime.errors.early_hangups: 0.00,
 proxy.process.http.incoming_requests: 1766073976,
 proxy.process.http.outgoing_requests: 484585207,
 proxy.process.http.incoming_responses: 486478535,
 proxy.process.http.invalid_client_requests: 240,
 proxy.process.http.missing_host_hdr: 0,
 proxy.process.http.get_requests: 1765677046,
 proxy.process.http.head_requests: 392884,
 proxy.process.http.trace_requests: 8,
 proxy.process.http.options_requests: 1562,
 proxy.process.http.post_requests: 662,
 proxy.process.http.put_requests: 7,
 proxy.process.http.push_requests: 0,
 proxy.process.http.delete_requests: 0,
 proxy.process.http.purge_requests: 0,
 proxy.process.http.connect_requests: 0,
 proxy.process.http.extension_method_requests: 1807,
 proxy.process.http.client_no_cache_requests: 0,
 proxy.process.http.broken_server_connections: 63475,
 proxy.process.http.cache_lookups: 1765896837,
 proxy.process.http.cache_writes: 119147534,
 proxy.process.http.cache_updates: 7812961,
 proxy.process.http.cache_deletes: 60058,
 proxy.process.http.tunnels: 5017,
 proxy.process.http.throttled_proxy_only: 0,
 proxy.process.http.request_taxonomy.i0_n0_m0: 0,
 proxy.process.http.request_taxonomy.i1_n0_m0: 0,
 proxy.process.http.request_taxonomy.i0_n1_m0: 0,
 proxy.process.http.request_taxonomy.i1_n1_m0: 0,
 proxy.process.http.request_taxonomy.i0_n0_m1: 0,
 proxy.process.http.request_taxonomy.i1_n0_m1: 0,
 proxy.process.http.request_taxonomy.i0_n1_m1: 0,
 proxy.process.http.request_taxonomy.i1_n1_m1: 0,
 proxy.process.http.icp_suggested_lookups: 0,
 proxy.process.http.client_transaction_time: 0,
 proxy.process.http.client_write_time: 0,
 proxy.process.http.server_read_time: 0,
 proxy.process.http.icp_transaction_time: 0,
 proxy.process.http.icp_raw_transaction_time: 0,
 proxy.process.http.parent_proxy_transaction_time: 0,
 proxy.process.http.parent_proxy_raw_transaction_time: 0,
 proxy.process.http.server_transaction_time: 0,
 proxy.process.http.server_raw_transaction_time: 0,
 proxy.process.http.user_agent_request_header_total_size: 797103745655,
 proxy.process.http.user_agent_response_header_total_size: 697699513781,
 proxy.process.http.user_agent_request_document_total_size: 419549,
 proxy.process.http.user_agent_response_document_total_size: 
 190278962740080,
 proxy.process.http.origin_server_request_header_total_size: 265407277593,
 proxy.process.http.origin_server_response_header_total_size: 127176507932,
 proxy.process.http.origin_server_request_document_total_size:

[jira] [Commented] (TS-2216) Custom Log %cquup not always initialized properly.

[jira] [Commented] (TS-2216) Custom Log %cquup not always initialized properly.

[jira] [Commented] (TS-2216) Custom Log %cquup not always initialized properly.

[jira] [Commented] (TS-2216) Custom Log %cquup not always initialized properly.

[jira] [Commented] (TS-2216) Custom Log %cquup not always initialized properly.

[jira] [Commented] (TS-2216) Custom Log %cquup not always initialized properly.

[jira] [Commented] (TS-2216) Custom Log %cquup not always initialized properly.

[jira] [Created] (TS-2223) Incorrect timezone offset when using %cqtn

[jira] [Created] (TS-2216) Custom Log %cquup not always initialized properly.

[jira] [Updated] (TS-2216) Custom Log %cquup not always initialized properly.

[jira] [Created] (TS-2159) First log rotation should happen at proxy.config.log.rolling_size_mb

[jira] [Updated] (TS-2159) First log rotation should happen at proxy.config.log.rolling_size_mb

[jira] [Created] (TS-2153) traffic_manager -tsArgs doesn't work

[jira] [Created] (TS-2140) Stats module is showing proxy.process.cache.direntries.used greater then proxy.process.cache.direntries.total

[jira] [Updated] (TS-2140) Stats module is showing proxy.process.cache.direntries.used greater then proxy.process.cache.direntries.total

15 matches

Site Navigation

Mail list logo

Footer information