Skip to content
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

error getting docker info: No such file or directory #84

Closed
mindscratch opened this issue Aug 3, 2015 · 10 comments
Closed

error getting docker info: No such file or directory #84

mindscratch opened this issue Aug 3, 2015 · 10 comments
Labels
bug unexpected problem or unintended behavior

Comments

@mindscratch
Copy link
Contributor

Running telegraf 0.1.4 on CentOS 7 with Docker 1.7.1 fails to gather docker metrics. What I get is

error getting docker info: open /sys/fs/cgroup/cpuacct/docker//cpuacct.stat: no such file or directory

I tried running find / -name docker -type d and only found:

/run/docker
/var/lib/docker
/etc/docker
/usr/libexec/docker

Perhaps the cgroup paths are different in CentOS/RHEL 7?

@sparrc
Copy link
Contributor

sparrc commented Aug 5, 2015

@mindscratch can you please run docker ps and docker version ?

@mindscratch
Copy link
Contributor Author

Docker 1.7.1

The output from docker ps isn't as each type get because it's on a separate
network (i can't just copy/paste).
On Aug 5, 2015 6:15 PM, "Cameron Sparr" notifications@github.com wrote:

@mindscratch https://github.com/mindscratch can you please run docker ps
and docker version ?


Reply to this email directly or view it on GitHub
#84 (comment).

@maxekman
Copy link

This also happens to me with boot2docker (OS X) and Docker v1.7.1.

@sparrc
Copy link
Contributor

sparrc commented Aug 10, 2015

@maxekman, The docker plugin is not supported on OSX, because it is not possible to poll for docker information from the OSX, telegraf would have to be running from within the boot2docker VM for it to work.

I also realize that the supported plugins for various OSes need to be better documented, this is going to be a point of future work.

@maxekman
Copy link

Thanks for explaining. Then it will at least hopefully work in the deployment at CoreOS.

Max Ekman
Software Engineer

+46 708 710504
max@looplab.se

> looplab.se

On 10 aug 2015, at 17:36, Cameron Sparr notifications@github.com wrote:

@maxekman, The docker plugin is not supported on OSX, because it is not possible to poll for docker information from the OSX, telegraf would have to be running from within the boot2docker VM for it to work.

I also realize that the supported plugins for various OSes need to be better documented, this is going to be a point of future work.


Reply to this email directly or view it on GitHub.

@aheusingfeld
Copy link

@sparrc I seem to have the same problem on An AWS EC2 instance running docker 1.6.2! Is there any documentation on which volumes telegraf needs - might also be dependant on the OS, I assume

@sparrc
Copy link
Contributor

sparrc commented Aug 10, 2015

@aheusingfeld This is something I'm looking into at the moment, unfortunately the docker functionality is completely based on the gopsutil package, which hasn't been the most stable option in terms of cross-platform functionality and build: https://github.com/shirou/gopsutil

@sparrc sparrc added bug unexpected problem or unintended behavior and removed Need More Info labels Sep 9, 2015
@kenzodeluxe
Copy link

Same here:
$ cat /etc/issue
Ubuntu 15.04
$ uname -a
Linux kenzo-qa 3.19.0-26-generic #28-Ubuntu SMP Tue Aug 11 14:16:32 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
$ docker --version
Docker version 1.8.1, build d12ea79

@sparrc
Copy link
Contributor

sparrc commented Sep 10, 2015

I believe that this PR: #180 will fix it, waiting on the author to sign the CLA and then will get this merged ASAP, thank you everyone for the issue reports

sparrc pushed a commit that referenced this issue Sep 11, 2015
@sparrc
Copy link
Contributor

sparrc commented Sep 17, 2015

I'm marking this as closed by PR #180, please re-open if that did not fix it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug unexpected problem or unintended behavior
Projects
None yet
Development

No branches or pull requests

5 participants