You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 17, 2021. It is now read-only.
On a fairly generic setup, with some standard items, and some External checks, the container is slowly creating zombie processes.
This seems to be related to the init problem, described in "A correct init process" section, on the baseimage-docker website, and in the pid-1-zombie-reaping-problem article.
Just for kicks, i've added a snippet of the Zabbix server, monitoring itself, with 3 hosts configured.
The text was updated successfully, but these errors were encountered:
kdkaergaard
changed the title
leaving zombie processes / no reaping
Lleaving zombie processes / No reaping
Oct 4, 2015
kdkaergaard
changed the title
Lleaving zombie processes / No reaping
Leaving zombie processes / No reaping
Oct 4, 2015
@kdkaergaard true, I have a (branch)[https://github.com/berngp/docker-zabbix/tree/feature/22-supervisord] that actually is meant to capture the effort to move to supervisord and avoid this. Adding syslog, as the link you mentions describes, is also a good idea.
My current problem is just that I have not been able to invest time in this project. Hopefully soon.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
On a fairly generic setup, with some standard items, and some External checks, the container is slowly creating zombie processes.
This seems to be related to the init problem, described in "A correct init process" section, on the baseimage-docker website, and in the pid-1-zombie-reaping-problem article.
Just for kicks, i've added a snippet of the Zabbix server, monitoring itself, with 3 hosts configured.
![zombieprocesses](https://cloud.githubusercontent.com/assets/5849148/10269488/4d328110-6ad9-11e5-8f4f-bb142518c784.PNG)
The text was updated successfully, but these errors were encountered: