-
Notifications
You must be signed in to change notification settings - Fork 268
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
Can't detect docker stat directory #2
Comments
Ok, I did a little debug and it seems that when there is no container running the module doesn't detect the stat directory and makes the whole agent to fail. I think a check must be included so the module does not make the agent to fail completely but to retry to scan the stat directory. I don't know if I am clear enough. In any case feel free to ask me anything and I will be happy to help. |
I didn't test it with Docker 1.2. Let me check. |
Hello the issue is the one I mentioned on my second comment and probably has not to do with docker 1.2. If no container is running the module cannot find the stats folder and breaks so zabbix-agent cannot start. I hope this helps. |
No containers are running:
And it started fine:
I'm not able to reproduce your issue. Could you run some command on your system, please?:
Do you have some SELinux?:
|
No SELinux, I'm on Ubuntu 14.04.
"docker ps -a" shows all my containers that are on "Exited" state, so it is big
This is the only "unusual" output.
but I have the same on my local system also (Opensuse 13.1). |
Ok, next commands:
|
Here they are.
|
If no containers were starting from last server start, then /sys/fs/cgroup/cpuacct/docker structure is not initialized. But if you start (stop) some container, then sys/fs/cgroup/cpuacct/docker starts to exist. I'll fix it soon. Thank you for cooperation and bug report. |
Hello, Thanks for the great work. Yes this is the issue. After a reboot the structure is not initialized. I hope you will expand the module soon to add more features. If you need anything additional, feel free to ping me. Regards. |
Done. You can check latest build (see link in readme, if you need so file). Now module starts and then tries to find stat directory. If no stat dir is found, then it will try to find again, when discovery function is called.
Please feel free to test it and let me know your result. |
Hello can you build the module also. I pulled again and there is no module. |
Build process is automated - drone.io provides binary so file now. Link is available also in readme. |
Yes I saw that after my comment ;). Will test and update you. Thanks. |
I can confirm that all is fine. zabbix-agent starts even with no containers running after a clean reboot. Thanks for the good work on this. |
Unfortunately after sometime it breaks again. Here is the log:
|
Got it. Problem resolved and tested in build #27 - it should be OK now. |
Seems fine now!. I will re-open in any case of problem. Thanks for the good job! I hope you will extend it soon. |
BTW: I've raised feature request https://support.zabbix.com/browse/ZBXNEXT-2460 |
Hello,
Hope you find the time to improve this.
I have problem to make it run with zabbix 2.2.6 and docker 1.2.0 on Ubuntu 14.04. The error I'm seeing on the log file is:
3363:20140913:083549.992 Starting Zabbix Agent [dockerdev.str5.net]. Zabbix 2.2.6 (revision 48483).
3363:20140913:083549.992 using configuration file: /etc/zabbix/zabbix_agentd.conf
3363:20140913:083549.992 Can't detect docker stat directory
3363:20140913:083549.992 cannot initialize module "zabbix_module_docker.so"
3363:20140913:083549.992 loading modules failed, exiting...
Any hints?
Regards,
Stratos.
The text was updated successfully, but these errors were encountered: