You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@trafficserver.apache.org by "Ye, Hong" <Ho...@comcast.com> on 2016/06/20 16:03:44 UTC
ATS5.3 does not reset stats?
Hi guys,
Stats went resetting on my ATS5.3 box. Does anyone have any idea what could be wrong or missed?
It worked fine in ATS4.
[root@denv-urlrw03 ~]# /usr/bin/curl -s localhost/_stats | grep completed_requests
"proxy.process.http.completed_requests": "7017174",
[root@denv-urlrw03 ~]# /usr/bin/traffic_line -c
[root@denv-urlrw03 ~]# /usr/bin/curl -s localhost/_stats | grep completed_requests
"proxy.process.http.completed_requests": "7017205”,
[root@denv-urlrw03 ~]# /usr/bin/traffic_line -c
[root@denv-urlrw03 ~]# /usr/bin/traffic_line -c
[root@denv-urlrw03 ~]# /usr/bin/curl -s localhost/_stats | grep completed_requests
"proxy.process.http.completed_requests": "7017437",
Thanks
Hong
--
Re: ATS5.3 does not reset stats?
Posted by "Ye, Hong" <Ho...@comcast.com>.
I talked to Phil about this. Since 6.2 will release soon, I will stick with current version
For the moment and will try to upgrade to that release later.
Thank James, Leif and Phil!
On 6/20/16, 2:39 PM, "James Peach" <jp...@apache.org> wrote:
>
>> On Jun 20, 2016, at 10:31 AM, Ye, Hong <Ho...@comcast.com> wrote:
>>
>> Does anyone have any idea how this can be fixed? I am in the middle of upgrade and need to
>> make decision quickly if I can move forward.
>
>AFAIK there's no workaround other than backporting the patch.
>
>>
>> Thank you very much for any help.
>>
>>
>>
>>
>> On 6/20/16, 12:03 PM, "Ye, Hong" <Ho...@cable.comcast.com> wrote:
>>
>>> Hi guys,
>>>
>>> Stats went resetting on my ATS5.3 box. Does anyone have any idea what could be wrong or missed?
>>> It worked fine in ATS4.
>>>
>>> [root@denv-urlrw03 ~]# /usr/bin/curl -s localhost/_stats | grep completed_requests
>>> "proxy.process.http.completed_requests": "7017174",
>>>
>>>
>>> [root@denv-urlrw03 ~]# /usr/bin/traffic_line -c
>>> [root@denv-urlrw03 ~]# /usr/bin/curl -s localhost/_stats | grep completed_requests
>>> "proxy.process.http.completed_requests": "7017205”,
>>>
>>> [root@denv-urlrw03 ~]# /usr/bin/traffic_line -c
>>> [root@denv-urlrw03 ~]# /usr/bin/traffic_line -c
>>> [root@denv-urlrw03 ~]# /usr/bin/curl -s localhost/_stats | grep completed_requests
>>> "proxy.process.http.completed_requests": "7017437",
>>>
>>>
>>>
>>> Thanks
>>>
>>> Hong
>>> --
>>>
>>>
>>>
>>>
>
>
Re: ATS5.3 does not reset stats?
Posted by James Peach <jp...@apache.org>.
> On Jun 20, 2016, at 10:31 AM, Ye, Hong <Ho...@comcast.com> wrote:
>
> Does anyone have any idea how this can be fixed? I am in the middle of upgrade and need to
> make decision quickly if I can move forward.
AFAIK there's no workaround other than backporting the patch.
>
> Thank you very much for any help.
>
>
>
>
> On 6/20/16, 12:03 PM, "Ye, Hong" <Ho...@cable.comcast.com> wrote:
>
>> Hi guys,
>>
>> Stats went resetting on my ATS5.3 box. Does anyone have any idea what could be wrong or missed?
>> It worked fine in ATS4.
>>
>> [root@denv-urlrw03 ~]# /usr/bin/curl -s localhost/_stats | grep completed_requests
>> "proxy.process.http.completed_requests": "7017174",
>>
>>
>> [root@denv-urlrw03 ~]# /usr/bin/traffic_line -c
>> [root@denv-urlrw03 ~]# /usr/bin/curl -s localhost/_stats | grep completed_requests
>> "proxy.process.http.completed_requests": "7017205”,
>>
>> [root@denv-urlrw03 ~]# /usr/bin/traffic_line -c
>> [root@denv-urlrw03 ~]# /usr/bin/traffic_line -c
>> [root@denv-urlrw03 ~]# /usr/bin/curl -s localhost/_stats | grep completed_requests
>> "proxy.process.http.completed_requests": "7017437",
>>
>>
>>
>> Thanks
>>
>> Hong
>> --
>>
>>
>>
>>
Re: ATS5.3 does not reset stats?
Posted by "Ye, Hong" <Ho...@comcast.com>.
Does anyone have any idea how this can be fixed? I am in the middle of upgrade and need to
make decision quickly if I can move forward.
Thank you very much for any help.
On 6/20/16, 12:03 PM, "Ye, Hong" <Ho...@cable.comcast.com> wrote:
>Hi guys,
>
>Stats went resetting on my ATS5.3 box. Does anyone have any idea what could be wrong or missed?
>It worked fine in ATS4.
>
>[root@denv-urlrw03 ~]# /usr/bin/curl -s localhost/_stats | grep completed_requests
>"proxy.process.http.completed_requests": "7017174",
>
>
>[root@denv-urlrw03 ~]# /usr/bin/traffic_line -c
>[root@denv-urlrw03 ~]# /usr/bin/curl -s localhost/_stats | grep completed_requests
>"proxy.process.http.completed_requests": "7017205”,
>
>[root@denv-urlrw03 ~]# /usr/bin/traffic_line -c
>[root@denv-urlrw03 ~]# /usr/bin/traffic_line -c
>[root@denv-urlrw03 ~]# /usr/bin/curl -s localhost/_stats | grep completed_requests
>"proxy.process.http.completed_requests": "7017437",
>
>
>
>Thanks
>
>Hong
>--
>
>
>
>
Re: ATS5.3 does not reset stats?
Posted by "Ye, Hong" <Ho...@comcast.com>.
Hi James,
Is there a work around?
Thanks
Hong
On 6/20/16, 1:48 PM, "James Peach" <jp...@apache.org> wrote:
>
>> On Jun 20, 2016, at 9:03 AM, Ye, Hong <Ho...@comcast.com> wrote:
>>
>> Hi guys,
>>
>> Stats went resetting on my ATS5.3 box. Does anyone have any idea what could be wrong or missed?
>> It worked fine in ATS4.
>>
>> [root@denv-urlrw03 ~]# /usr/bin/curl -s localhost/_stats | grep completed_requests
>> "proxy.process.http.completed_requests": "7017174",
>>
>>
>> [root@denv-urlrw03 ~]# /usr/bin/traffic_line -c
>> [root@denv-urlrw03 ~]# /usr/bin/curl -s localhost/_stats | grep completed_requests
>> "proxy.process.http.completed_requests": "7017205”,
>>
>> [root@denv-urlrw03 ~]# /usr/bin/traffic_line -c
>> [root@denv-urlrw03 ~]# /usr/bin/traffic_line -c
>> [root@denv-urlrw03 ~]# /usr/bin/curl -s localhost/_stats | grep completed_requests
>> "proxy.process.http.completed_requests": "7017437",
>
>This sounds like https://issues.apache.org/jira/browse/TS-4271
>
>J
Re: ATS5.3 does not reset stats?
Posted by James Peach <jp...@apache.org>.
> On Jun 20, 2016, at 9:03 AM, Ye, Hong <Ho...@comcast.com> wrote:
>
> Hi guys,
>
> Stats went resetting on my ATS5.3 box. Does anyone have any idea what could be wrong or missed?
> It worked fine in ATS4.
>
> [root@denv-urlrw03 ~]# /usr/bin/curl -s localhost/_stats | grep completed_requests
> "proxy.process.http.completed_requests": "7017174",
>
>
> [root@denv-urlrw03 ~]# /usr/bin/traffic_line -c
> [root@denv-urlrw03 ~]# /usr/bin/curl -s localhost/_stats | grep completed_requests
> "proxy.process.http.completed_requests": "7017205”,
>
> [root@denv-urlrw03 ~]# /usr/bin/traffic_line -c
> [root@denv-urlrw03 ~]# /usr/bin/traffic_line -c
> [root@denv-urlrw03 ~]# /usr/bin/curl -s localhost/_stats | grep completed_requests
> "proxy.process.http.completed_requests": "7017437",
This sounds like https://issues.apache.org/jira/browse/TS-4271
J