You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficcontrol.apache.org by GitBox <gi...@apache.org> on 2020/11/19 20:37:41 UTC

[GitHub] [trafficcontrol] shamrickus opened a new issue #5310: TM reporting "errors" when Cache is unreachable

shamrickus opened a new issue #5310:
URL: https://github.com/apache/trafficcontrol/issues/5310


   <!--
   ************ STOP!! ************
   If this issue identifies a security vulnerability, DO NOT submit it! Instead, contact
   the Apache Traffic Control Security Team at security@trafficcontrol.apache.org and follow the
   guidelines at https://www.apache.org/security/ regarding vulnerability disclosure.
   
   - For *SUPPORT QUESTIONS*, use the Traffic Control slack (https://s.apache.org/atc-slack)
   or Traffic Control mailing lists (https://trafficcontrol.apache.org/mailing_lists).
   - Before submitting, please **SEARCH GITHUB** for a similar issue or PR.
   -->
   
   ## I'm submitting a ...
   <!-- delete all those that don't apply -->
   <!--- security vulnerability (STOP!! - see above)-->
   -  bug report
   
   ## Traffic Control components affected ...
   <!-- delete all those that don't apply -->
   -  Traffic Monitor
   
   ## Current behavior:
   If a Cache is unreachable from TM and `{tmHost}/publish/CacheStats` is called, "errors" will be spit out in the TM logs
   
   ```
   ❯ docker-compose logs trafficmonitor | grep "does not contain"
   trafficmonitor_1   | ERROR: resultstathistory.go:500: 2020-11-19T20:32:06.051943336Z: Cache mid-023 does not contain interface eth0
   ```
   <!-- Describe how the bug manifests -->
   
   ## Expected behavior:
   This error is actually a warning, furthermore it should not be logging in the case that the server is inaccessible as that is handled else where, and this results in a significant amount of log entries.
   <!-- Describe what the behavior would be without the bug -->
   
   ## Minimal reproduction of the problem with instructions:
   Change a Cache in a CDN to have an incorrect ip address/fqdn, perform a snapshot.
   Wait a few seconds/minutes and inspect the trafficmonitor logs for "Cache {name} does not contain interface {intf}"
   <!--
   If the current behavior is a bug, please provide the *STEPS TO REPRODUCE* and
   include the applicable TC version.
   -->
   
   <!--
   e.g. stacktraces, related issues, suggestions how to fix (feel free to delete
   this section)
   -->
   
   <!--
   Licensed to the Apache Software Foundation (ASF) under one
   or more contributor license agreements.  See the NOTICE file
   distributed with this work for additional information
   regarding copyright ownership.  The ASF licenses this file
   to you under the Apache License, Version 2.0 (the
   "License"); you may not use this file except in compliance
   with the License.  You may obtain a copy of the License at
   
       https://apache.org/licenses/LICENSE-2.0
   
   Unless required by applicable law or agreed to in writing,
   software distributed under the License is distributed on an
   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
   KIND, either express or implied.  See the License for the
   specific language governing permissions and limitations
   under the License.
   -->
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [trafficcontrol] zrhoffman closed issue #5310: TM reporting "errors" when Cache is unreachable

Posted by GitBox <gi...@apache.org>.
zrhoffman closed issue #5310:
URL: https://github.com/apache/trafficcontrol/issues/5310


   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org