Bernardo Gomez Palacio

In order to move to Supervisor Zabbix needs to get patched such that it doesn't fork when the server(s) start. That work is still pending.

@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...

Thanks @Franselbaer I am currently running it on a CentOS. Could you please share with me which version of Ubuntu and Docker you are using?

Thank you @Franselbaer, I do my due diligence to replicate the issue. We can have mounts where the logs would be written to, I was planning on doing this anyway...

@Franselbaer the _monit_ & _AppArmor_ issue referenced in #13 was causing the syslogs to grow very quickly and might be related. Could you please run the container with the following...

@Franselbaer let me know if the changes above helped you out.

@meltonpineda we need to move out of _monit_, is already causing several stability issues. As reference #22

@azurewraith I am migrating to `supervisord` but haven't yet finished. I'll push a labeled image that we can test out and see if `supervisord` helps out on stabilizing the container.

@azurewraith sorry for the late reply. I have the [feature/22-supervisord](/berngp/docker-zabbix/tree/feature/22-supervisord) to address the migration from `monit` to `supervisor`. It still not working but will keep track to such effort through...

Hi @joachimmueller if you want to do a backup and upgrade the container you can: 1. stop the container. 2. Use the approach that [docker-backpu](https://github.com/docker-infra/docker-backup) suggests to create a backup....