monitor_docker icon indicating copy to clipboard operation
monitor_docker copied to clipboard

Errors in logs for only one container even when removed from config

Open finity69x2 opened this issue 4 years ago • 2 comments

I've started getting the following errors every few minutes in my HA log:

2020-12-18 18:22:15 ERROR (Thread-4) [custom_components.monitor_docker.helpers] grafana: Cannot determine CPU usage for container ('system_cpu_usage')
2020-12-18 18:22:15 ERROR (Thread-4) [custom_components.monitor_docker.helpers] Raw 'cpu_stats' {'cpu_usage': {'total_usage': 0, 'usage_in_kernelmode': 0, 'usage_in_usermode': 0}, 'throttling_data': {'periods': 0, 'throttled_periods': 0, 'throttled_time': 0}}
2020-12-18 18:22:15 ERROR (Thread-4) [custom_components.monitor_docker.helpers] grafana: Cannot determine memory usage for container ('usage')
2020-12-18 18:22:15 ERROR (Thread-4) [custom_components.monitor_docker.helpers] {}: Raw 'memory_stats' grafana
2020-12-18 18:22:15 ERROR (Thread-4) [custom_components.monitor_docker.helpers] grafana: Can not determine network usage for container ('networks')
2020-12-18 18:22:15 ERROR (Thread-4) [custom_components.monitor_docker.helpers] grafana: No 'networks' found in raw packet
2020-12-18 18:24:18 ERROR (Thread-4) [custom_components.monitor_docker.helpers] grafana: Can not determine network usage for container ('networks')
2020-12-18 18:24:18 ERROR (Thread-4) [custom_components.monitor_docker.helpers] grafana: No 'networks' found in raw packet

I've updated the integration and it shows as the latest version in HACS.

I've updated to the latest version of the grafana image.

I've even removed the grafana container from my list of monitored containers:

monitor_docker:
  - name: Docker
    containers:
      - hassio_supervisor
      - homeassistant
      - addon_a0d7b954_nut
      - qt-openzwave
      - ha-zwave-network
      - z2m-assistant
      - zigbee2mqtt
      #- grafana

And I've even tried stopping the grafana container and I still keep getting those errors in the logs.

finity69x2 avatar Dec 18 '20 23:12 finity69x2

For overall cpu/memory the monitor_docker needs to retrieve the Grafana container too ... How does your docker-compose.yaml or docker run looks like?

Does this only happen to Grafana or other containers too?

ualex73 avatar Jan 01 '21 09:01 ualex73

It only errors for grafana. None of the other configured containers have any errors.

here is my docker run command:

sudo docker run -d -p 3000:3000 --name="grafana" --restart unless-stopped -v /home/finity/docker/grafana:/var/lib/grafana grafana/grafana

it worked fine with no errors until a few weeks ago. I'm not exactly sure when it started tho.

finity69x2 avatar Jan 01 '21 20:01 finity69x2