Stops working after container restart about dockbix-agent-xxl HOT 11 CLOSED

Yes, you have to remove the zabbix-agent container and start a new one every time. I recommend to use it as a systemd service, so you can create service "hook" which will remove container before start.

from dockbix-agent-xxl.

How did you restart container?

from dockbix-agent-xxl.

I have the exact same problem (Error #10 on container restart). I've restarted my container by rebooting by computer. However, even if I just do a "docker stop zabbix-agent-xxl" followed by a "docker start zabbix-agent-xxl", I run into the same issue (Error #10). My docker run is slightly different though:

docker run \
--name=zabbixagent-xxl \
-p 10250:10050 \
-v /:/rootfs \
-v /var/run:/var/run \
-e "ZA_Server=monitoring.domain.local" \
-e "ZA_ServerActive=monitoring.domain.local" \
-h docker-agent-1 \
-d --restart=always monitoringartist/zabbix-agent-xxl-limited:latest

from dockbix-agent-xxl.

--restart=always

Unfortunately restart policy is not supported. At least not in public free image. I have idea how to fix it, but I don't want to waste my time.
To be honest I don't like Docker restart policy. IMO it's should be task of your Docker orchestration.

from dockbix-agent-xxl.

Ok. However, even if I remove the restart policy from the run command, I still run into the same issue if I do a "docker stop" followed by "docker start". Are you saying that stopping and starting the container aren't supported at all? The only way to use this is removing the container and rebuilding it each time? (Just trying to confirm)

Thanks!

from dockbix-agent-xxl.

docker stop + docker start = docker restart = --restart=always = still the same problem.
Yes, you need to remove old zabbix-agent container and start new one in your case. Container is stateless, so it's not a problem.

from dockbix-agent-xxl.

Does this mean that if a machine reboots, we will have to remove the zabbix-agent container and start a new one every time ?

from dockbix-agent-xxl.

I've got the same issue, and that's quite weird, if I need to recreate container each time instead of just start it again.

Can you put more description for #10 error? Maybe it's possible to solve this issue by user?

from dockbix-agent-xxl.

#10 is in this case: wrapper code was not able to start zabbix-agentd properly
It's expected behaviour/architecture design and you are not able to solve it from the user space.

from dockbix-agent-xxl.

systemd example - https://github.com/monitoringartist/zabbix-agent-xxl#dockerized-zabbix-agent-xxl-service-managed-by-systemd

from dockbix-agent-xxl.

+1 & solve my problem thanks.

from dockbix-agent-xxl.