You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2016/11/07 23:03:58 UTC

[jira] [Resolved] (TS-5043) Too many Note() on config reloads

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

Leif Hedstrom resolved TS-5043.
-------------------------------
    Resolution: Invalid

> Too many Note() on config reloads
> ---------------------------------
>
>                 Key: TS-5043
>                 URL: https://issues.apache.org/jira/browse/TS-5043
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Configuration, Logging
>            Reporter: Leif Hedstrom
>
> Seeing this when I do a "traffic_ctl config reload"
> {code}
> Nov  7 21:21:37 s_sys@host traffic_manager[12821]: {0x7f3374df0700} NOTE: updated diags config
> Nov  7 21:21:37 s_sys@host traffic_manager[12821]: {0x7f3374df0700} NOTE: updated diags config
> Nov  7 21:21:37 s_sys@host traffic_manager[12821]: {0x7f3374df0700} NOTE: updated diags config
> Nov  7 21:21:37 s_sys@host traffic_manager[12821]: {0x7f3374df0700} NOTE: updated diags config
> Nov  7 21:21:37 s_sys@host traffic_manager[12821]: {0x7f3374df0700} NOTE: updated diags config
> Nov  7 21:21:37 s_sys@host traffic_manager[12821]: {0x7f3374df0700} NOTE: updated diags config
> Nov  7 21:21:37 s_sys@host traffic_manager[12821]: {0x7f3374df0700} NOTE: updated diags config
> Nov  7 21:21:37 s_sys@host traffic_manager[12821]: {0x7f3374df0700} NOTE: updated diags config
> Nov  7 21:21:37 s_sys@host traffic_manager[12821]: {0x7f3374df0700} NOTE: updated diags config
> Nov  7 21:21:37 s_sys@host traffic_manager[12821]: {0x7f3374df0700} NOTE: updated diags config
> Nov  7 21:21:37 s_sys@host traffic_manager[12821]: {0x7f3374df0700} NOTE: updated diags config
> Nov  7 21:21:37 s_sys@host traffic_manager[12821]: {0x7f3374df0700} NOTE: updated diags config
> Nov  7 21:21:44 s_sys@host traffic_server[12832]: {0x2aaab3e05700} NOTE: updated diags config
> Nov  7 21:21:44 s_sys@host traffic_server[12832]: {0x2aaab3e05700} NOTE: updated diags config
> Nov  7 21:21:44 s_sys@host traffic_server[12832]: {0x2aaab3e05700} NOTE: updated diags config
> Nov  7 21:21:44 s_sys@host traffic_server[12832]: {0x2aaab3e05700} NOTE: updated diags config
> Nov  7 21:21:44 s_sys@host traffic_server[12832]: {0x2aaab3e05700} NOTE: updated diags config
> Nov  7 21:21:44 s_sys@host traffic_server[12832]: {0x2aaab3e05700} NOTE: updated diags config
> Nov  7 21:21:44 s_sys@host traffic_server[12832]: {0x2aaab3e05700} NOTE: updated diags config
> Nov  7 21:21:44 s_sys@host traffic_server[12832]: {0x2aaab3e05700} NOTE: updated diags config
> Nov  7 21:21:44 s_sys@host traffic_server[12832]: {0x2aaab3e05700} NOTE: updated diags config
> Nov  7 21:21:44 s_sys@host traffic_server[12832]: {0x2aaab3e05700} NOTE: updated diags config
> Nov  7 21:21:44 s_sys@host traffic_server[12832]: {0x2aaab3e05700} NOTE: updated diags config
> Nov  7 21:21:44 s_sys@host traffic_server[12832]: {0x2aaab3e05700} NOTE: updated diags config
> {code}
> Don't know why, but that seems either wrong, or insanely verbose.



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