-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cadivsor tries to monitor systemd .mount units via docker #1510
Comments
Same issue here:
It my case it's a devicemapper mounts |
This generates about 18 000 msg per hour on a cluster with 125 pods. |
same here |
same problem |
same here, use overlay2 as docker filesystem |
Can confirm, happens for me on a DigitalOcean Droplet with Ubuntu 16.04. I'm using docker-compose:
|
same problem. any updates on how to prevent this? |
I think this should fix #1573 |
@jaylinski it works for you? |
@fahimeh2010 I can't tell yet. I'm waiting for the fix to be released in a stable image (https://hub.docker.com/r/google/cadvisor/tags/). |
Hi folks ,
For 24 hours I had 28,800 error message , of course not with the same container ID :P , I use cadvisor as a container cadvisor:latest , I switch for cadvisor:canary (3 Mars 2017) and it fix my problem . I'm very happy, so THANKS a lot for your work ! I know the issue is close , but for other people like me who found this thread this FIX WORK ! Do you have any idea when this fix will be include in the stable release ? |
I'm running
docker version:
docker info:
|
@ntquyen Your logs dont have anything suspicious. People were being spammed with: |
In my logfiles I see a lot of errors like the following about every minute:
It turns out that these uuids belong to .mount units from systemd:
It turns out that these queries originate from the cadvisor plugin in kublet.
I'd like to monitor the error rate of API calls to the docker deamon and this makes it impossible and I think cadivsor should be smart enough to know about
.mount
units and monitor them appropriately.The text was updated successfully, but these errors were encountered: