[
https://issues.apache.org/jira/browse/TS-818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045541#comment-13045541
]
Bryan Call commented on TS-818:
-------------------------------
Reviews changes. I didn't seen anywhere in the code that these stats are
incremented or decremented.
I do see these other stats being used:
proxy/SocksProxy.cc:
SOCKSPROXY_INC_STAT(socksproxy_http_connections_stat);
proxy/SocksProxy.cc:
SOCKSPROXY_INC_STAT(socksproxy_tunneled_connections_stat);
Looks like there needs to be some cleanup work with the socks stats. I think
this is a good change to do for now, being that the release of 3.0.0 is
coming...
> Assertion/abort when starting TS with SOCKS proxy enabled
> ---------------------------------------------------------
>
> Key: TS-818
> URL: https://issues.apache.org/jira/browse/TS-818
> Project: Traffic Server
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.1.9, 2.1.8
> Environment: Linux x86-64
> Reporter: Yakov Markovitch
> Assignee: Leif Hedstrom
> Fix For: 3.1.0, 3.0.0
>
> Attachments: trafficserver.2.1.8.socks-reg-stat.patch
>
>
> When attempting to start TS with
> CONFIG proxy.config.socks.socks_needed INT 1
> CONFIG proxy.config.socks.socks_version INT 5
> TS aborts at startup with the following message:
> FATAL: RecProcess.cc:738: failed assert `false`
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
