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

get_disk_io exception with "index out of range" #2

Open
hnbakker opened this issue May 16, 2017 · 4 comments

Comments

Projects
None yet
3 participants
@hnbakker
Copy link

commented May 16, 2017

While running this script on a docker server i did get an "index out of range" on get_disk_io.
Turns out there is no disk info with some containers (diskless?) so i modified the code locally like below:

if disk:
  disk_in = disk[0]['value']
  disk_out = disk[1]['value']
else:
  disk_in = 0
  disk_out = 0

No it runs without issue.

Kind regards,
Herman

@elacheche

This comment has been minimized.

Copy link
Owner

commented May 16, 2017

Thanks for reporting this..

As I never used a "diskless" docker container.. And I don't know how that can be.. Afaik, each OS process (docker or other) will use disk for I/O at any point of it's life cycle..

Can you please share the output of:
docker stats <ct_namz>

To check that there is no disk io data!

Also, can you please tell me what kind of image is that? If there is a public Dockerfile can you please share it?

I'd like to dig more in this issue..

@elacheche elacheche self-assigned this May 16, 2017

@elacheche elacheche added the bug label May 16, 2017

@hnbakker

This comment has been minimized.

Copy link
Author

commented May 17, 2017

Those docker containers are not diskless.
I think its 'docker stats' returning null for zero blkio.

$ docker -v
Docker version 1.13.1-cs3, build 95c9d22

I'm running odoo and ucp (docker datacenter) containers on a centos7 server.

For example docker stats for the odoo container:
CONTAINER CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS
affectionate_mcclintock.1.t5u0f18m0uwglzrbqb3cxm0ac 0.03% 40.07 MiB / 7.64 GiB 0.51% 1.85 kB / 1.3 kB 0 B / 0 B 4

I'm working on getting performance graph's in nagiosxi to see if those containers ever report disk i/o.
Had issues with nrpe agent v2.x which limits to 1k perfdata. Now using v3.x

@elacheche elacheche added the invalid label Aug 25, 2017

@rnt

This comment has been minimized.

Copy link
Contributor

commented Jan 6, 2018

Hi @elacheche , @hnbakker take a good point.
I have some containers that only read from disk... other only write to disk.

So, in PR #6 , commit 8c8ca32 fix this. ;)

@elacheche elacheche removed the invalid label Jan 6, 2018

@elacheche

This comment has been minimized.

Copy link
Owner

commented Jan 6, 2018

PR #6 is merged, @hnbakker can you please try the new version from the master branch and confirm that the PR fixes the bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.