Giters

mesos / logstash

Logstash on Mesos

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

No zookeeper configuration given. Please provide "mesos.zk" system property.

akamalov opened this issue · comments

commented

Trying to configure logstash for mesos, getting errors complaining "No zookeeper configuration given. Please provide "mesos.zk" system property."

Configuration is pretty much exactly as in the "Readme" file.

{
  "id": "/logstash",
  "cpus": 1,
  "mem": 1024.0,
  "instances": 1,
  "container": {
    "type": "DOCKER",
    "docker": {
      "image": "mesos/logstash-scheduler:0.0.6",
      "network": "HOST"
    }
  },
  "env": {
    "MESOS_ZK": "leader.mesos:2181",
    "MESOS_ZOOKEEPER_SERVER": "leader.mesos:2181",
    "MESOS_MASTER": "leader.mesos:5050",
    "MESOS_PRINCIPAL": "elasticsearch",
    "MESOS_SECRET": "dc5200a2a22b944d202e",
    "FRAMEWORK_NAME": "logstash",
    "MESOS_ROLE": "logstash",
    "MESOS_USER": "root",
    "LOGSTASH_HEAP_SIZE": "64",
    "LOGSTASH_ELASTICSEARCH_URL": "http://node64.local.net:31100",
    "EXECUTOR_CPUS": "0.5",
    "EXECUTOR_HEAP_SIZE": "128",
    "ENABLE_COLLECTD": "true",
    "ENABLE_SYSLOG": "true",
    "ENABLE_FILE": "true",
    "ENABLE_DOCKER": "true",
    "EXECUTOR_FILE_PATH": "/var/log/* "
  }
}
~
~

Also, in the "Readme" file, there is no mentioning of MESOS_PRINCIPAL or MESOS_SECRET. However, Google's cache does have previously cached file of the readme which mentions these parameters.

commented

Hi @akamalov. Thank you very much for your bug report. Is there any reasons you're not using the latest 0.10-RC1? 0.0.6 is more than 6 months old and not supported anymore.

commented

Ok. I will give it a shot and keep you posted

commented

Great! Bare in mind that configuration differs a lot due to the migration to https://github.com/ContainerSolutions/mesos-starter/tree/0.1.

commented

Used "latest" tag. Still no go :(

[root@node263 ~]# docker run mesos/logstash-scheduler \
>     --mesos.zookeeper.server=leader.mesos:2181 \
>     --mesos.master=leader.mesos:5050 \
>     --framework-name=logstash \
>     --mesos-role='*' \
>     --mesos-user=root \
>     --logstash.heap-size=64 \
>     --logstash.elasticsearch-host=node264.local.net:31100 \
>     --logstash.executor-image=mesos/logstash-executor \
>     --logstash.executor-version=latest \
>     --logstash.syslog-port=514 \
>     --logstash.collectd-port=25826 \
>     --executor.cpus=0.5 \
>     --executor.heap-size=128 \
>     --enable.collectd=true \
>     --enable.syslog=true \
>     --enable.file=true \
>     --enable.docker=true \
>     --executor.file-path='/var/log/*'
Unable to find image 'mesos/logstash-scheduler:latest' locally
latest: Pulling from mesos/logstash-scheduler
a3ed95caeb02: Pull complete 
fac1b01c1a21: Already exists 
21c4bf2bca5e: Already exists 
3cf88d16a178: Already exists 
e405364dc6ee: Already exists 
6bf3d921cf75: Already exists 
2cdb20ae5a11: Already exists 
235e0d63e0dc: Pull complete 
aca0a264c7a1: Pull complete 
33917c88c6b6: Pull complete 
6d2397154de2: Pull complete 
3adb14d5c555: Pull complete 
71e764ae51f7: Pull complete 
Digest: sha256:57bd239afb387cd4c3a4251386a41a034bf9b3136a8c065602cf2e8663a006f6
Status: Downloaded newer image for mesos/logstash-scheduler:latest
No zookeeper configuration given. Please provide "mesos.zk" system property.
[root@node263 ~]#
commented

I wanted to make sure that it works directly with docker, prior to doing it via Marathon.

commented

Never mind. It looks like tag latest is pointing to an old version of the software. Pointed to the 0.10-RC1.