[jira] [Resolved] (TS-4429) Add a --concise option to traffic_logstats

2016-11-30 Thread Leif Hedstrom (JIRA)

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

Leif Hedstrom resolved TS-4429.
---
Resolution: Fixed

> Add a --concise option to traffic_logstats
> --
>
> Key: TS-4429
> URL: https://issues.apache.org/jira/browse/TS-4429
> Project: Traffic Server
>  Issue Type: Improvement
>  Components: Tools
>Reporter: Leif Hedstrom
>Assignee: Leif Hedstrom
> Fix For: 7.1.0
>
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> Many times, it'd be useful for traffic_logstats to exclude certain metrics / 
> data which could (with some effort) be calculated by a collecting agent. Such 
> as, percentage values, or totals / sums.
> Doing this can reduce the number of metrics collected dramatically, without 
> losing any data that can be recreated.



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


[GitHub] trafficserver issue #1239: TS-5069 enhance logstats to report stats per user

2016-11-30 Thread zwoop
Github user zwoop commented on the issue:

https://github.com/apache/trafficserver/pull/1239
  
I landed my changes, so now you have to resolve the conflicts. Sorry bro. :)


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] trafficserver pull request #1238: TS-4429: Adds a --concise (-C) option for ...

2016-11-30 Thread zwoop
Github user zwoop closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[jira] [Work logged] (TS-4429) Add a --concise option to traffic_logstats

2016-11-30 Thread ASF GitHub Bot (JIRA)

 [ 
https://issues.apache.org/jira/browse/TS-4429?focusedWorklogId=32631=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-32631
 ]

ASF GitHub Bot logged work on TS-4429:
--

Author: ASF GitHub Bot
Created on: 30/Nov/16 16:00
Start Date: 30/Nov/16 16:00
Worklog Time Spent: 10m 
  Work Description: Github user zwoop closed the pull request at:

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


Issue Time Tracking
---

Worklog Id: (was: 32631)
Time Spent: 1h 10m  (was: 1h)

> Add a --concise option to traffic_logstats
> --
>
> Key: TS-4429
> URL: https://issues.apache.org/jira/browse/TS-4429
> Project: Traffic Server
>  Issue Type: Improvement
>  Components: Tools
>Reporter: Leif Hedstrom
>Assignee: Leif Hedstrom
> Fix For: 7.1.0
>
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> Many times, it'd be useful for traffic_logstats to exclude certain metrics / 
> data which could (with some effort) be calculated by a collecting agent. Such 
> as, percentage values, or totals / sums.
> Doing this can reduce the number of metrics collected dramatically, without 
> losing any data that can be recreated.



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


[jira] [Work logged] (TS-5069) logstats: add ability to report stats per user instead of host

2016-11-30 Thread ASF GitHub Bot (JIRA)

 [ 
https://issues.apache.org/jira/browse/TS-5069?focusedWorklogId=32632=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-32632
 ]

ASF GitHub Bot logged work on TS-5069:
--

Author: ASF GitHub Bot
Created on: 30/Nov/16 16:14
Start Date: 30/Nov/16 16:14
Worklog Time Spent: 10m 
  Work Description: Github user zwoop commented on the issue:

https://github.com/apache/trafficserver/pull/1239
  
I landed my changes, so now you have to resolve the conflicts. Sorry bro. :)


Issue Time Tracking
---

Worklog Id: (was: 32632)
Time Spent: 40m  (was: 0.5h)

> logstats: add ability to report stats per user instead of host
> --
>
> Key: TS-5069
> URL: https://issues.apache.org/jira/browse/TS-5069
> Project: Traffic Server
>  Issue Type: Bug
>  Components: Logging, Tools
>Reporter: Gancho Tenev
>Assignee: Gancho Tenev
> Fix For: 7.1.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> We would like to enhance {{traffic_logstats}} with the ability to report 
> stats per user instead of host (from the URI).
> Currently the {{traffic_logstats}} expects a binary squid log format defined 
> in the following ATS log config and aggregates and reports stats per the 
> authority part of the URI ({{host:port}} in an usual use-case)
> {code}
>  % % %/% % % % 
> % %/% %"/>
> {code}
> It would be useful for our use-case to be able aggregate and report stats 
> based on the 8th squid log field which is an username of the authenticated 
> client {{%}}).
> In our use-case we need to aggregate and report stats per 
> CDN-customer-specific-tag. 
> For example the new functionality would allow us to replace {{%caun}} with a 
> random header content {{%<\{@CustomerTagHeader\}cqh>}} and report stats per 
> CDN customer by using a new command line parameter {{--report_per_user}} w/o 
> adding extra fields to the binary squid format log expected by 
> {{traffic_logstats}} and keep it backward compatible with the previous 
> version.



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


Failed: trafficserver (dd9da766)

2016-11-30 Thread Read the Docs

Build Failed for trafficserver (latest)



You can find out more about this failure here:
https://readthedocs.org/projects/trafficserver/builds/4734634/

If you have questions, a good place to start is the FAQ:
https://docs.readthedocs.org/en/latest/faq.html



Keep documenting,
Read the Docs
--
http://readthedocs.org


[jira] [Commented] (TS-4426) BaseLogFile::open_file stdout stderr bind error

2016-11-30 Thread Daniel Xu (JIRA)

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

Daniel Xu commented on TS-4426:
---

I'm not sure I fully understand what you're describing. Is this related to 
TS-4416? See my comment there.



> BaseLogFile::open_file  stdout stderr bind error
> 
>
> Key: TS-4426
> URL: https://issues.apache.org/jira/browse/TS-4426
> Project: Traffic Server
>  Issue Type: Bug
>  Components: Logging, Manager
>Reporter: Song CW
>Assignee: Daniel Xu
> Fix For: 7.1.0
>
>
> The condition "!strcmp(m_name.get(), "stdout")" will never be true when we 
> start  manager with --bind_stderr (--bind_stdout) args, because the name of 
> BaseLogFile struct we set in set_stdout_output is --bind_stdout --bind_stderr.



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


[jira] [Commented] (TS-4416) process_args_ex parse error

2016-11-30 Thread Daniel Xu (JIRA)

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

Daniel Xu commented on TS-4416:
---

[~scwsy00] Are you starting the {{traffic_server}} binary like this: {{sudo 
./traffic_server --bind_stdout --bind_stderr /path/to/log}}? It's not obvious 
to me why it would be happening otherwise.

If you could attach a coredump (if ATS crashed), that would be helpful.

> process_args_ex parse error
> ---
>
> Key: TS-4416
> URL: https://issues.apache.org/jira/browse/TS-4416
> Project: Traffic Server
>  Issue Type: Bug
>  Components: Tools
>Reporter: Song CW
>Assignee: Daniel Xu
> Fix For: 7.1.0
>
> Attachments: (gdb)
>
>
> According to TS-4399, I found something strange in process_args_ex when I 
> starting manager with   --bind_stderr --bind_stdout args!



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


[GitHub] trafficserver pull request #1240: Doc conditional build

2016-11-30 Thread SolidWallOfCode
GitHub user SolidWallOfCode opened a pull request:

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

Doc conditional build

Make the docs not build by default, require a "--enable-docs" argument to 
./config.

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

$ git pull https://github.com/SolidWallOfCode/trafficserver 
doc-conditional-build

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

https://github.com/apache/trafficserver/pull/1240.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 #1240


commit d49dac4a29d2397725cfa4c5751ee539a01068f4
Author: Alan M. Carroll 
Date:   2016-11-23T16:36:30Z

TS-5062: Fix traffic_ctl to track plugin supplied configuration variables.

commit 0617976d82afa1033bec9caa10498369c2a30b5a
Author: Alan M. Carroll 
Date:   2016-11-30T19:50:35Z

Doc: Make building docs an active configuration option.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[jira] [Commented] (TS-4636) traffic.out is open too many times

2016-11-30 Thread Daniel Xu (JIRA)

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

Daniel Xu commented on TS-4636:
---

I haven't done any deep digging, but my hunch is that it has to do with 
{{proxy/Main.cc::bind_outputs}}. That function is opening {{traffic.out}} and 
using {{dup2}} to to redirect stdout & stderr to {{traffic.out}}. 

Correct me if I'm wrong b/c I'm not sure how dup2 is implemented w/ regards to 
opening & closing file descriptors.

> traffic.out is open too many times
> --
>
> Key: TS-4636
> URL: https://issues.apache.org/jira/browse/TS-4636
> Project: Traffic Server
>  Issue Type: Bug
>  Components: Core, Logging
>Reporter: James Peach
>Assignee: Daniel Xu
> Fix For: sometime
>
>
> Looks like something is wrong with {{traffic.out}}. I am expecting that this 
> shold only be open twice (for stdout and stderr).
> {noformat}
> traffic_s 12272 nmadmin0w   CHR1,3  0t0 1051 
> /dev/null
> traffic_s 12272 nmadmin1w   REG  202,172377   524555 
> /n/log/trafficserver/traffic.out
> traffic_s 12272 nmadmin2w   REG  202,172377   524555 
> /n/log/trafficserver/traffic.out
> traffic_s 12272 nmadmin3r   DIR  202,1 40962 /
> traffic_s 12272 nmadmin4u   REG  202,1 3839   524557 
> /n/log/trafficserver/manager.log
> traffic_s 12272 nmadmin5u   REG  202,172377   524555 
> /n/log/trafficserver/traffic.out
> traffic_s 12272 nmadmin6u  0,90 6384 
> anon_inode
> traffic_s 12272 nmadmin7u   REG  202,172377   524555 
> /n/log/trafficserver/traffic.out
> traffic_s 12272 nmadmin8u  0,90 6384 
> anon_inode
> traffic_s 12272 nmadmin9u  IPv4   19233316  0t0  TCP *:80 
> (LISTEN)
> traffic_s 12272 nmadmin   10u  IPv4   19233317  0t0  TCP 
> *:443 (LISTEN)
> traffic_s 12272 nmadmin   11u  0,90 6384 
> anon_inode
> traffic_s 12272 nmadmin   12u  0,90 6384 
> anon_inode
> traffic_s 12272 nmadmin   13u  unix 0x8801e2aaf080  0t0 19233322 
> socket
> traffic_s 12272 nmadmin   14u   REG  202,172377   524555 
> /n/log/trafficserver/traffic.out
> traffic_s 12272 nmadmin   15u   REG  202,172377   524555 
> /n/log/trafficserver/traffic.out
> traffic_s 12272 nmadmin   16u  unix 0x8800d9e63c00  0t0 19233956 
> socket
> {noformat}
> {noformat}
> [root@qa1 ~]# lsof -P -p $(pidof traffic_server) | grep traffic.out
> [ET_NET 2317 nobody1u  REG  202,1542101711082 
> /opt/ats/var/log/trafficserver/traffic.out
> [ET_NET 2317 nobody2u  REG  202,1542101711082 
> /opt/ats/var/log/trafficserver/traffic.out
> [ET_NET 2317 nobody5u  REG  202,1542101711082 
> /opt/ats/var/log/trafficserver/traffic.out
> [ET_NET 2317 nobody7u  REG  202,1542101711082 
> /opt/ats/var/log/trafficserver/traffic.out
> [ET_NET 2317 nobody   17u  REG  202,1542101711082 
> /opt/ats/var/log/trafficserver/traffic.out
> [ET_NET 2317 nobody   21u  REG  202,1542101711082 
> /opt/ats/var/log/trafficserver/traffic.out
> {noformat}



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


[GitHub] trafficserver issue #1240: Doc conditional build

2016-11-30 Thread atsci
Github user atsci commented on the issue:

https://github.com/apache/trafficserver/pull/1240
  
Linux build *successful*! See 
https://ci.trafficserver.apache.org/job/Github-Linux/1120/ for details.
 



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] trafficserver issue #1221: TS-5046: Guard against the server_session server_...

2016-11-30 Thread sekimura
Github user sekimura commented on the issue:

https://github.com/apache/trafficserver/pull/1221
  
It looks good so far with #1232. I'm going to close this PR since we don't 
need this anymore.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] trafficserver pull request #1221: TS-5046: Guard against the server_session ...

2016-11-30 Thread sekimura
Github user sekimura closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] trafficserver issue #1240: Doc conditional build

2016-11-30 Thread atsci
Github user atsci commented on the issue:

https://github.com/apache/trafficserver/pull/1240
  
FreeBSD build *successful*! See 
https://ci.trafficserver.apache.org/job/Github-FreeBSD/1227/ for details.
 



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


Failed: trafficserver (58b177f0)

2016-11-30 Thread Read the Docs

Build Failed for trafficserver (latest)



You can find out more about this failure here:
https://readthedocs.org/projects/trafficserver/builds/4735419/

If you have questions, a good place to start is the FAQ:
https://docs.readthedocs.org/en/latest/faq.html



Keep documenting,
Read the Docs
--
http://readthedocs.org


[GitHub] trafficserver issue #1240: Doc conditional build

2016-11-30 Thread zwoop
Github user zwoop commented on the issue:

https://github.com/apache/trafficserver/pull/1240
  
How about this too:

```
diff --git a/ci/jenkins/bin/docs.sh b/ci/jenkins/bin/docs.sh
index 6754040..f5b2a17 100644
--- a/ci/jenkins/bin/docs.sh
+++ b/ci/jenkins/bin/docs.sh
@@ -22,7 +22,7 @@ test ! -z "${WORKSPACE}" && cd "${WORKSPACE}/src"
 
 # This avoids redoing the configure on every doc build, which is somewhat 
annoying
 [ ! -f configure ] && autoreconf -fi
-[ ! -f config.nice ] && ./configure
+[ ! -f config.nice ] && ./configure --enable-docs
 
 cd doc
```


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] trafficserver pull request #1240: Doc conditional build

2016-11-30 Thread zwoop
Github user zwoop closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] trafficserver issue #1240: Doc conditional build

2016-11-30 Thread atsci
Github user atsci commented on the issue:

https://github.com/apache/trafficserver/pull/1240
  
Linux build *successful*! See 
https://ci.trafficserver.apache.org/job/Github-Linux/1121/ for details.
 



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[jira] [Work logged] (TS-5046) SEGV HttpSM::tunnel_handler_server(int event, HttpTunnelProducer *p)

2016-11-30 Thread ASF GitHub Bot (JIRA)

 [ 
https://issues.apache.org/jira/browse/TS-5046?focusedWorklogId=32654=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-32654
 ]

ASF GitHub Bot logged work on TS-5046:
--

Author: ASF GitHub Bot
Created on: 30/Nov/16 22:31
Start Date: 30/Nov/16 22:31
Worklog Time Spent: 10m 
  Work Description: Github user sekimura closed the pull request at:

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


Issue Time Tracking
---

Worklog Id: (was: 32654)
Time Spent: 50m  (was: 40m)

> SEGV HttpSM::tunnel_handler_server(int event, HttpTunnelProducer *p) 
> -
>
> Key: TS-5046
> URL: https://issues.apache.org/jira/browse/TS-5046
> Project: Traffic Server
>  Issue Type: Bug
>  Components: HTTP, Network
>Reporter: Masa Sekimura
>Assignee: Masa Sekimura
> Fix For: 6.2.1
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> one of servers running 6.2.x (729c60b) got a SIGSEGV
> {code}
> (gdb) thread 42
> [Switching to thread 42 (Thread 0x2aaab460d700 (LWP 4145))]
> #0  0x2d6bd37d in __libc_waitpid (pid=, 
> stat_loc=, options=) at 
> ../sysdeps/unix/sysv/linux/waitpid.c:41
> 41../sysdeps/unix/sysv/linux/waitpid.c: No such file or directory.
> (gdb) bt
> #0  0x2d6bd37d in __libc_waitpid (pid=, 
> stat_loc=, options=) at 
> ../sysdeps/unix/sysv/linux/waitpid.c:41
> #1  0x2ab81ec7 in crash_logger_invoke (signo=11, info=0x2aaab460bcf0, 
> ctx=0x2aaab460bbc0) at Crash.cc:164
> #2  
> #3  0x2ac83358 in HttpSM::tunnel_handler_server (this=0x2ab9b4efac00, 
> event=, p=) at HttpSM.cc:3108
> #4  0x2ace1d72 in HttpTunnel::producer_handler 
> (this=this@entry=0x2ab9b4efbf28, event=102, event@entry=100, 
> p=p@entry=0x2ab9b4efc128) at HttpTunnel.cc:1240
> #5  0x2ace3343 in HttpTunnel::producer_run 
> (this=this@entry=0x2ab9b4efbf28, p=p@entry=0x2ab9b4efc128) at 
> HttpTunnel.cc:1020
> #6  0x2ace3d71 in HttpTunnel::tunnel_run (this=0x2ab9b4efbf28, 
> p_arg=0x2ab9b4efc128) at HttpTunnel.cc:787
> #7  0x2ac96f8b in HttpSM::state_api_callout 
> (this=this@entry=0x2ab9b4efac00, event=event@entry=6, 
> data=data@entry=0x0) at HttpSM.cc:1534
> #8  0x2ac9e0d3 in HttpSM::state_api_callback 
> (this=this@entry=0x2ab9b4efac00, event=event@entry=6, 
> data=data@entry=0x0) at HttpSM.cc:1331
> #9  0x2abad6ad in TSHttpTxnReenable (txnp=0x2ab9b4efac00, 
> event=TS_EVENT_HTTP_CONTINUE) at InkAPI.cc:5652
> #10 0x2aaabe845c05 in XInjectResponseHeaders (event=, 
> edata=0x2ab9b4efac00) at xdebug.cc:295
> #11 0x2ab98c04 in INKContInternal::handle_event (this=0x2aaab6bf9dc0, 
> event=60007, edata=0x2ab9b4efac00) at InkAPI.cc:1006
> #12 0x2ac96d10 in HttpSM::state_api_callout 
> (this=this@entry=0x2ab9b4efac00, event=event@entry=6, 
> data=data@entry=0x0) at HttpSM.cc:1452
> #13 0x2ac9e0d3 in HttpSM::state_api_callback 
> (this=this@entry=0x2ab9b4efac00, event=event@entry=6, 
> data=data@entry=0x0) at HttpSM.cc:1331
> #14 0x2abad6ad in TSHttpTxnReenable (txnp=0x2ab9b4efac00, 
> event=TS_EVENT_HTTP_CONTINUE) at InkAPI.cc:5652
> #15 0x2aaabe01ea45 in cont_rewrite_headers (contp=0x2aaab6bf9ee0, 
> event=, edata=0x2ab9b4efac00) at header_rewrite.cc:307
> #16 0x2ab98c04 in INKContInternal::handle_event (this=0x2aaab6bf9ee0, 
> event=60007, edata=0x2ab9b4efac00) at InkAPI.cc:1006
> #17 0x2ac96d10 in HttpSM::state_api_callout (this=0x2ab9b4efac00, 
> event=, data=) at HttpSM.cc:1452
> #18 0x2ac9c910 in HttpSM::set_next_state (this=0x2ab9b4efac00) at 
> HttpSM.cc:7296
> #19 0x2ac96f8b in HttpSM::state_api_callout 
> (this=this@entry=0x2ab9b4efac00, event=event@entry=6, 
> data=data@entry=0x0) at HttpSM.cc:1534
> #20 0x2ac9e0d3 in HttpSM::state_api_callback 
> (this=this@entry=0x2ab9b4efac00, event=event@entry=6, 
> data=data@entry=0x0) at HttpSM.cc:1331
> #21 0x2abad6ad in TSHttpTxnReenable (txnp=0x2ab9b4efac00, 
> event=TS_EVENT_HTTP_CONTINUE) at InkAPI.cc:5652
> #22 0x2aaabf4038d5 in cont_handle_response (contp=, 
> event=, edata=0x2ab9b4efac00) at background_fetch.cc:544
> #23 0x2ab98c04 in INKContInternal::handle_event (this=0x2aaab6bf9d00, 
> event=60006, edata=0x2ab9b4efac00) at InkAPI.cc:1006
> #24 0x2ac96d10 in HttpSM::state_api_callout 
> (this=this@entry=0x2ab9b4efac00, event=event@entry=6, 
> data=data@entry=0x0) at HttpSM.cc:1452
> #25 0x2ac9e0d3 in HttpSM::state_api_callback 
> (this=this@entry=0x2ab9b4efac00, event=event@entry=6, 
> data=data@entry=0x0) at HttpSM.cc:1331
> #26 0x2abad6ad in TSHttpTxnReenable (txnp=0x2ab9b4efac00, 
> event=TS_EVENT_HTTP_CONTINUE) at InkAPI.cc:5652
> #27 0x2aaabe01ea45 in 

[jira] [Work logged] (TS-5069) logstats: add ability to report stats per user instead of host

2016-11-30 Thread ASF GitHub Bot (JIRA)

 [ 
https://issues.apache.org/jira/browse/TS-5069?focusedWorklogId=32663=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-32663
 ]

ASF GitHub Bot logged work on TS-5069:
--

Author: ASF GitHub Bot
Created on: 01/Dec/16 05:33
Start Date: 01/Dec/16 05:33
Worklog Time Spent: 10m 
  Work Description: Github user atsci commented on the issue:

https://github.com/apache/trafficserver/pull/1239
  
Linux build *successful*! See 
https://ci.trafficserver.apache.org/job/Github-Linux/1122/ for details.
 



Issue Time Tracking
---

Worklog Id: (was: 32663)
Time Spent: 50m  (was: 40m)

> logstats: add ability to report stats per user instead of host
> --
>
> Key: TS-5069
> URL: https://issues.apache.org/jira/browse/TS-5069
> Project: Traffic Server
>  Issue Type: Bug
>  Components: Logging, Tools
>Reporter: Gancho Tenev
>Assignee: Gancho Tenev
> Fix For: 7.1.0
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> We would like to enhance {{traffic_logstats}} with the ability to report 
> stats per user instead of host (from the URI).
> Currently the {{traffic_logstats}} expects a binary squid log format defined 
> in the following ATS log config and aggregates and reports stats per the 
> authority part of the URI ({{host:port}} in an usual use-case)
> {code}
>  % % %/% % % % 
> % %/% %"/>
> {code}
> It would be useful for our use-case to be able aggregate and report stats 
> based on the 8th squid log field which is an username of the authenticated 
> client {{%}}).
> In our use-case we need to aggregate and report stats per 
> CDN-customer-specific-tag. 
> For example the new functionality would allow us to replace {{%caun}} with a 
> random header content {{%<\{@CustomerTagHeader\}cqh>}} and report stats per 
> CDN customer by using a new command line parameter {{--report_per_user}} w/o 
> adding extra fields to the binary squid format log expected by 
> {{traffic_logstats}} and keep it backward compatible with the previous 
> version.



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


[jira] [Work logged] (TS-5046) SEGV HttpSM::tunnel_handler_server(int event, HttpTunnelProducer *p)

2016-11-30 Thread ASF GitHub Bot (JIRA)

 [ 
https://issues.apache.org/jira/browse/TS-5046?focusedWorklogId=32653=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-32653
 ]

ASF GitHub Bot logged work on TS-5046:
--

Author: ASF GitHub Bot
Created on: 30/Nov/16 22:31
Start Date: 30/Nov/16 22:31
Worklog Time Spent: 10m 
  Work Description: Github user sekimura commented on the issue:

https://github.com/apache/trafficserver/pull/1221
  
It looks good so far with #1232. I'm going to close this PR since we don't 
need this anymore.


Issue Time Tracking
---

Worklog Id: (was: 32653)
Time Spent: 50m  (was: 40m)

> SEGV HttpSM::tunnel_handler_server(int event, HttpTunnelProducer *p) 
> -
>
> Key: TS-5046
> URL: https://issues.apache.org/jira/browse/TS-5046
> Project: Traffic Server
>  Issue Type: Bug
>  Components: HTTP, Network
>Reporter: Masa Sekimura
>Assignee: Masa Sekimura
> Fix For: 6.2.1
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> one of servers running 6.2.x (729c60b) got a SIGSEGV
> {code}
> (gdb) thread 42
> [Switching to thread 42 (Thread 0x2aaab460d700 (LWP 4145))]
> #0  0x2d6bd37d in __libc_waitpid (pid=, 
> stat_loc=, options=) at 
> ../sysdeps/unix/sysv/linux/waitpid.c:41
> 41../sysdeps/unix/sysv/linux/waitpid.c: No such file or directory.
> (gdb) bt
> #0  0x2d6bd37d in __libc_waitpid (pid=, 
> stat_loc=, options=) at 
> ../sysdeps/unix/sysv/linux/waitpid.c:41
> #1  0x2ab81ec7 in crash_logger_invoke (signo=11, info=0x2aaab460bcf0, 
> ctx=0x2aaab460bbc0) at Crash.cc:164
> #2  
> #3  0x2ac83358 in HttpSM::tunnel_handler_server (this=0x2ab9b4efac00, 
> event=, p=) at HttpSM.cc:3108
> #4  0x2ace1d72 in HttpTunnel::producer_handler 
> (this=this@entry=0x2ab9b4efbf28, event=102, event@entry=100, 
> p=p@entry=0x2ab9b4efc128) at HttpTunnel.cc:1240
> #5  0x2ace3343 in HttpTunnel::producer_run 
> (this=this@entry=0x2ab9b4efbf28, p=p@entry=0x2ab9b4efc128) at 
> HttpTunnel.cc:1020
> #6  0x2ace3d71 in HttpTunnel::tunnel_run (this=0x2ab9b4efbf28, 
> p_arg=0x2ab9b4efc128) at HttpTunnel.cc:787
> #7  0x2ac96f8b in HttpSM::state_api_callout 
> (this=this@entry=0x2ab9b4efac00, event=event@entry=6, 
> data=data@entry=0x0) at HttpSM.cc:1534
> #8  0x2ac9e0d3 in HttpSM::state_api_callback 
> (this=this@entry=0x2ab9b4efac00, event=event@entry=6, 
> data=data@entry=0x0) at HttpSM.cc:1331
> #9  0x2abad6ad in TSHttpTxnReenable (txnp=0x2ab9b4efac00, 
> event=TS_EVENT_HTTP_CONTINUE) at InkAPI.cc:5652
> #10 0x2aaabe845c05 in XInjectResponseHeaders (event=, 
> edata=0x2ab9b4efac00) at xdebug.cc:295
> #11 0x2ab98c04 in INKContInternal::handle_event (this=0x2aaab6bf9dc0, 
> event=60007, edata=0x2ab9b4efac00) at InkAPI.cc:1006
> #12 0x2ac96d10 in HttpSM::state_api_callout 
> (this=this@entry=0x2ab9b4efac00, event=event@entry=6, 
> data=data@entry=0x0) at HttpSM.cc:1452
> #13 0x2ac9e0d3 in HttpSM::state_api_callback 
> (this=this@entry=0x2ab9b4efac00, event=event@entry=6, 
> data=data@entry=0x0) at HttpSM.cc:1331
> #14 0x2abad6ad in TSHttpTxnReenable (txnp=0x2ab9b4efac00, 
> event=TS_EVENT_HTTP_CONTINUE) at InkAPI.cc:5652
> #15 0x2aaabe01ea45 in cont_rewrite_headers (contp=0x2aaab6bf9ee0, 
> event=, edata=0x2ab9b4efac00) at header_rewrite.cc:307
> #16 0x2ab98c04 in INKContInternal::handle_event (this=0x2aaab6bf9ee0, 
> event=60007, edata=0x2ab9b4efac00) at InkAPI.cc:1006
> #17 0x2ac96d10 in HttpSM::state_api_callout (this=0x2ab9b4efac00, 
> event=, data=) at HttpSM.cc:1452
> #18 0x2ac9c910 in HttpSM::set_next_state (this=0x2ab9b4efac00) at 
> HttpSM.cc:7296
> #19 0x2ac96f8b in HttpSM::state_api_callout 
> (this=this@entry=0x2ab9b4efac00, event=event@entry=6, 
> data=data@entry=0x0) at HttpSM.cc:1534
> #20 0x2ac9e0d3 in HttpSM::state_api_callback 
> (this=this@entry=0x2ab9b4efac00, event=event@entry=6, 
> data=data@entry=0x0) at HttpSM.cc:1331
> #21 0x2abad6ad in TSHttpTxnReenable (txnp=0x2ab9b4efac00, 
> event=TS_EVENT_HTTP_CONTINUE) at InkAPI.cc:5652
> #22 0x2aaabf4038d5 in cont_handle_response (contp=, 
> event=, edata=0x2ab9b4efac00) at background_fetch.cc:544
> #23 0x2ab98c04 in INKContInternal::handle_event (this=0x2aaab6bf9d00, 
> event=60006, edata=0x2ab9b4efac00) at InkAPI.cc:1006
> #24 0x2ac96d10 in HttpSM::state_api_callout 
> (this=this@entry=0x2ab9b4efac00, event=event@entry=6, 
> data=data@entry=0x0) at HttpSM.cc:1452
> #25 0x2ac9e0d3 in HttpSM::state_api_callback 
> (this=this@entry=0x2ab9b4efac00, event=event@entry=6, 
> data=data@entry=0x0) at HttpSM.cc:1331
> #26 0x2abad6ad in TSHttpTxnReenable 

[jira] [Created] (TS-5070) Add configuration variables to set file permissions for diags.log & traffic.out

2016-11-30 Thread Daniel Xu (JIRA)
Daniel Xu created TS-5070:
-

 Summary: Add configuration variables to set file permissions for 
diags.log & traffic.out
 Key: TS-5070
 URL: https://issues.apache.org/jira/browse/TS-5070
 Project: Traffic Server
  Issue Type: Improvement
  Components: Logging
Reporter: Daniel Xu


It would be useful to be able to control file permissions for {{diags.log}} and 
{{traffic.out}}.



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


[jira] [Assigned] (TS-5070) Add configuration variables to set file permissions for diags.log & traffic.out

2016-11-30 Thread Daniel Xu (JIRA)

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

Daniel Xu reassigned TS-5070:
-

Assignee: Daniel Xu

> Add configuration variables to set file permissions for diags.log & 
> traffic.out
> ---
>
> Key: TS-5070
> URL: https://issues.apache.org/jira/browse/TS-5070
> Project: Traffic Server
>  Issue Type: Improvement
>  Components: Logging
>Reporter: Daniel Xu
>Assignee: Daniel Xu
>
> It would be useful to be able to control file permissions for {{diags.log}} 
> and {{traffic.out}}.



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


[jira] [Work logged] (TS-5069) logstats: add ability to report stats per user instead of host

2016-11-30 Thread ASF GitHub Bot (JIRA)

 [ 
https://issues.apache.org/jira/browse/TS-5069?focusedWorklogId=32664=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-32664
 ]

ASF GitHub Bot logged work on TS-5069:
--

Author: ASF GitHub Bot
Created on: 01/Dec/16 05:35
Start Date: 01/Dec/16 05:35
Worklog Time Spent: 10m 
  Work Description: Github user atsci commented on the issue:

https://github.com/apache/trafficserver/pull/1239
  
FreeBSD build *successful*! See 
https://ci.trafficserver.apache.org/job/Github-FreeBSD/1228/ for details.
 



Issue Time Tracking
---

Worklog Id: (was: 32664)
Time Spent: 1h  (was: 50m)

> logstats: add ability to report stats per user instead of host
> --
>
> Key: TS-5069
> URL: https://issues.apache.org/jira/browse/TS-5069
> Project: Traffic Server
>  Issue Type: Bug
>  Components: Logging, Tools
>Reporter: Gancho Tenev
>Assignee: Gancho Tenev
> Fix For: 7.1.0
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> We would like to enhance {{traffic_logstats}} with the ability to report 
> stats per user instead of host (from the URI).
> Currently the {{traffic_logstats}} expects a binary squid log format defined 
> in the following ATS log config and aggregates and reports stats per the 
> authority part of the URI ({{host:port}} in an usual use-case)
> {code}
>  % % %/% % % % 
> % %/% %"/>
> {code}
> It would be useful for our use-case to be able aggregate and report stats 
> based on the 8th squid log field which is an username of the authenticated 
> client {{%}}).
> In our use-case we need to aggregate and report stats per 
> CDN-customer-specific-tag. 
> For example the new functionality would allow us to replace {{%caun}} with a 
> random header content {{%<\{@CustomerTagHeader\}cqh>}} and report stats per 
> CDN customer by using a new command line parameter {{--report_per_user}} w/o 
> adding extra fields to the binary squid format log expected by 
> {{traffic_logstats}} and keep it backward compatible with the previous 
> version.



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


[GitHub] trafficserver issue #1239: TS-5069 enhance logstats to report stats per user

2016-11-30 Thread atsci
Github user atsci commented on the issue:

https://github.com/apache/trafficserver/pull/1239
  
FreeBSD build *successful*! See 
https://ci.trafficserver.apache.org/job/Github-FreeBSD/1228/ for details.
 



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] trafficserver issue #1239: TS-5069 enhance logstats to report stats per user

2016-11-30 Thread atsci
Github user atsci commented on the issue:

https://github.com/apache/trafficserver/pull/1239
  
Linux build *successful*! See 
https://ci.trafficserver.apache.org/job/Github-Linux/1122/ for details.
 



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] trafficserver issue #1239: TS-5069 enhance logstats to report stats per user

2016-11-30 Thread gtenev
Github user gtenev commented on the issue:

https://github.com/apache/trafficserver/pull/1239
  
@zwoop no problems, should be good now


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] trafficserver issue #1239: TS-5069 enhance logstats to report stats per user

2016-11-30 Thread atsci
Github user atsci commented on the issue:

https://github.com/apache/trafficserver/pull/1239
  
Linux build *successful*! See 
https://ci.trafficserver.apache.org/job/Github-Linux/1123/ for details.
 



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[jira] [Work logged] (TS-5069) logstats: add ability to report stats per user instead of host

2016-11-30 Thread ASF GitHub Bot (JIRA)

 [ 
https://issues.apache.org/jira/browse/TS-5069?focusedWorklogId=32670=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-32670
 ]

ASF GitHub Bot logged work on TS-5069:
--

Author: ASF GitHub Bot
Created on: 01/Dec/16 05:53
Start Date: 01/Dec/16 05:53
Worklog Time Spent: 10m 
  Work Description: Github user atsci commented on the issue:

https://github.com/apache/trafficserver/pull/1239
  
Linux build *successful*! See 
https://ci.trafficserver.apache.org/job/Github-Linux/1123/ for details.
 



Issue Time Tracking
---

Worklog Id: (was: 32670)
Time Spent: 1h 10m  (was: 1h)

> logstats: add ability to report stats per user instead of host
> --
>
> Key: TS-5069
> URL: https://issues.apache.org/jira/browse/TS-5069
> Project: Traffic Server
>  Issue Type: Bug
>  Components: Logging, Tools
>Reporter: Gancho Tenev
>Assignee: Gancho Tenev
> Fix For: 7.1.0
>
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> We would like to enhance {{traffic_logstats}} with the ability to report 
> stats per user instead of host (from the URI).
> Currently the {{traffic_logstats}} expects a binary squid log format defined 
> in the following ATS log config and aggregates and reports stats per the 
> authority part of the URI ({{host:port}} in an usual use-case)
> {code}
>  % % %/% % % % 
> % %/% %"/>
> {code}
> It would be useful for our use-case to be able aggregate and report stats 
> based on the 8th squid log field which is an username of the authenticated 
> client {{%}}).
> In our use-case we need to aggregate and report stats per 
> CDN-customer-specific-tag. 
> For example the new functionality would allow us to replace {{%caun}} with a 
> random header content {{%<\{@CustomerTagHeader\}cqh>}} and report stats per 
> CDN customer by using a new command line parameter {{--report_per_user}} w/o 
> adding extra fields to the binary squid format log expected by 
> {{traffic_logstats}} and keep it backward compatible with the previous 
> version.



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


[jira] [Work logged] (TS-5069) logstats: add ability to report stats per user instead of host

2016-11-30 Thread ASF GitHub Bot (JIRA)

 [ 
https://issues.apache.org/jira/browse/TS-5069?focusedWorklogId=32672=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-32672
 ]

ASF GitHub Bot logged work on TS-5069:
--

Author: ASF GitHub Bot
Created on: 01/Dec/16 06:03
Start Date: 01/Dec/16 06:03
Worklog Time Spent: 10m 
  Work Description: Github user gtenev commented on the issue:

https://github.com/apache/trafficserver/pull/1239
  
@zwoop no problems, should be good now


Issue Time Tracking
---

Worklog Id: (was: 32672)
Time Spent: 1.5h  (was: 1h 20m)

> logstats: add ability to report stats per user instead of host
> --
>
> Key: TS-5069
> URL: https://issues.apache.org/jira/browse/TS-5069
> Project: Traffic Server
>  Issue Type: Bug
>  Components: Logging, Tools
>Reporter: Gancho Tenev
>Assignee: Gancho Tenev
> Fix For: 7.1.0
>
>  Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> We would like to enhance {{traffic_logstats}} with the ability to report 
> stats per user instead of host (from the URI).
> Currently the {{traffic_logstats}} expects a binary squid log format defined 
> in the following ATS log config and aggregates and reports stats per the 
> authority part of the URI ({{host:port}} in an usual use-case)
> {code}
>  % % %/% % % % 
> % %/% %"/>
> {code}
> It would be useful for our use-case to be able aggregate and report stats 
> based on the 8th squid log field which is an username of the authenticated 
> client {{%}}).
> In our use-case we need to aggregate and report stats per 
> CDN-customer-specific-tag. 
> For example the new functionality would allow us to replace {{%caun}} with a 
> random header content {{%<\{@CustomerTagHeader\}cqh>}} and report stats per 
> CDN customer by using a new command line parameter {{--report_per_user}} w/o 
> adding extra fields to the binary squid format log expected by 
> {{traffic_logstats}} and keep it backward compatible with the previous 
> version.



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


[GitHub] trafficserver issue #1239: TS-5069 enhance logstats to report stats per user

2016-11-30 Thread atsci
Github user atsci commented on the issue:

https://github.com/apache/trafficserver/pull/1239
  
FreeBSD build *successful*! See 
https://ci.trafficserver.apache.org/job/Github-FreeBSD/1229/ for details.
 



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[jira] [Work logged] (TS-5069) logstats: add ability to report stats per user instead of host

2016-11-30 Thread ASF GitHub Bot (JIRA)

 [ 
https://issues.apache.org/jira/browse/TS-5069?focusedWorklogId=32671=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-32671
 ]

ASF GitHub Bot logged work on TS-5069:
--

Author: ASF GitHub Bot
Created on: 01/Dec/16 05:55
Start Date: 01/Dec/16 05:55
Worklog Time Spent: 10m 
  Work Description: Github user atsci commented on the issue:

https://github.com/apache/trafficserver/pull/1239
  
FreeBSD build *successful*! See 
https://ci.trafficserver.apache.org/job/Github-FreeBSD/1229/ for details.
 



Issue Time Tracking
---

Worklog Id: (was: 32671)
Time Spent: 1h 20m  (was: 1h 10m)

> logstats: add ability to report stats per user instead of host
> --
>
> Key: TS-5069
> URL: https://issues.apache.org/jira/browse/TS-5069
> Project: Traffic Server
>  Issue Type: Bug
>  Components: Logging, Tools
>Reporter: Gancho Tenev
>Assignee: Gancho Tenev
> Fix For: 7.1.0
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> We would like to enhance {{traffic_logstats}} with the ability to report 
> stats per user instead of host (from the URI).
> Currently the {{traffic_logstats}} expects a binary squid log format defined 
> in the following ATS log config and aggregates and reports stats per the 
> authority part of the URI ({{host:port}} in an usual use-case)
> {code}
>  % % %/% % % % 
> % %/% %"/>
> {code}
> It would be useful for our use-case to be able aggregate and report stats 
> based on the 8th squid log field which is an username of the authenticated 
> client {{%}}).
> In our use-case we need to aggregate and report stats per 
> CDN-customer-specific-tag. 
> For example the new functionality would allow us to replace {{%caun}} with a 
> random header content {{%<\{@CustomerTagHeader\}cqh>}} and report stats per 
> CDN customer by using a new command line parameter {{--report_per_user}} w/o 
> adding extra fields to the binary squid format log expected by 
> {{traffic_logstats}} and keep it backward compatible with the previous 
> version.



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


[GitHub] trafficserver issue #1175: socks.config - dest_ip rule issue

2016-11-30 Thread 06chaynes
Github user 06chaynes commented on the issue:

https://github.com/apache/trafficserver/issues/1175
  
I will enable logging and check for issues as soon as I can circle back 
around to this. Thanks again for your assistance.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---