monitoringartist/dockbix-agent-xxl

Compatibility with Marathon

darkshade9 opened this issue · 1 comments

Any way I can get this to work with Mesos/Marathon?

--container="mesos-ed031b0b-a489-4455-9a03-d11b83a98929-S4.a5eddd84-f247-4f96-85c6-2ac85f8e31c7" --docker="docker" --docker_socket="/var/run/docker.sock" --help="false" --initialize_driver_logging="true" --launcher_dir="/opt/mesosphere/packages/mesos--0335ca0d3700ea88ad8b808f3b1b84d747ed07f0/libexec/mesos" --logbufsecs="0" --logging_level="INFO" --mapped_directory="/mnt/mesos/sandbox" --quiet="false" --sandbox_directory="/var/lib/mesos/slave/slaves/ed031b0b-a489-4455-9a03-d11b83a98929-S4/frameworks/ed031b0b-a489-4455-9a03-d11b83a98929-0000/executors/zabbix-agent.d6972ff9-64b1-11e6-965f-0242e15b1d74/runs/a5eddd84-f247-4f96-85c6-2ac85f8e31c7" --stop_timeout="0ns"
--container="mesos-ed031b0b-a489-4455-9a03-d11b83a98929-S4.a5eddd84-f247-4f96-85c6-2ac85f8e31c7" --docker="docker" --docker_socket="/var/run/docker.sock" --help="false" --initialize_driver_logging="true" --launcher_dir="/opt/mesosphere/packages/mesos--0335ca0d3700ea88ad8b808f3b1b84d747ed07f0/libexec/mesos" --logbufsecs="0" --logging_level="INFO" --mapped_directory="/mnt/mesos/sandbox" --quiet="false" --sandbox_directory="/var/lib/mesos/slave/slaves/ed031b0b-a489-4455-9a03-d11b83a98929-S4/frameworks/ed031b0b-a489-4455-9a03-d11b83a98929-0000/executors/zabbix-agent.d6972ff9-64b1-11e6-965f-0242e15b1d74/runs/a5eddd84-f247-4f96-85c6-2ac85f8e31c7" --stop_timeout="0ns"
Registered docker executor on 10.31.1.12
Starting task zabbix-agent.d6972ff9-64b1-11e6-965f-0242e15b1d74
Zocker XXL v0.9.4b public limited version
Copyright (C) 2014-2016 Jan Garaj - www.monitoringartist.com 
Freeware licence - Usage of this binary is restricted to official monitoringartist Docker images only.
Starting Zabbix Agent [dcosagent003]. Zabbix 3.0.3 XXL (2016-06-26) (revision {ZABBIX_REVISION}).
Press Ctrl+C to exit.

    11:20160817:193606.321 Starting Zabbix Agent [dcosagent003]. Zabbix 3.0.3 XXL (2016-06-26) (revision {ZABBIX_REVISION}).
    11:20160817:193606.321 **** Enabled features ****
    11:20160817:193606.321 IPv6 support:          YES
    11:20160817:193606.321 TLS support:           YES
    11:20160817:193606.321 **************************
    11:20160817:193606.321 using configuration file: /etc/zabbix/zabbix_agentd.conf
    11:20160817:193606.321 loaded modules: zabbix_module_docker.so, zabbix_module_stress.so
    11:20160817:193606.322 agent #0 started [main process]
    12:20160817:193606.322 agent #1 started [collector]
    13:20160817:193606.322 agent #2 started [listener #1]
    14:20160817:193606.322 agent #3 started [listener #2]
    15:20160817:193606.322 agent #4 started [listener #3]
remove /lib/x86_64-linux-gnu//security: directory not empty
Received killTask
Shutting down

CentOS Linux release 7.2.1511 (Core)

Hi Aaron,

I don't see any problem. Zabbix-agent container was up and running, when your Mesos has decided to kill it. IMHO it's a problem with your Mesos/Marathon task config/resources. Maybe you didn't have enough resources, so Mesos/Marathon has killed zabbix-agent task/container. I don't know.

My recommendation: don't use Mesos to start zabbix-agent container - start it as a pure Docker container