ahromis / swarm-elk Goto Github PK

I tried setting up ELK stack on Google Cloud Platform but looks like your docker-compose file has the below entry hard-coded:

    image: kibana:latest
    ports:
      - "5601:5601"
    environment:
      ELASTICSEARCH_URL: http://elasticsearch:9200
    networks:
      - elk
    deploy:
      mode: replicated
      replicas: 1
    healthcheck:
      test: wget -qO- http://localhost:5601 > /dev/null
      interval: 30s
      retries: 3

Due to which it tried to reach out to hostname called elasticsearch and fails out there.

First of all thanks for the time spent on building the compose. Good Work.

However i'm not able to build the index with that command:
docker run -dit --log-driver=gelf --log-opt gelf-address=udp://<logstash-host>:12201 alpine ping 8.8.8.8
i do also try:
docker run -dit --log-driver=gelf --log-opt gelf-address=udp://<logstash-host>:12201 alpine logger error

after i telnet on-to the logstach on port 10514 and send some strange keys, i was able to build the index.

any ideas?

Docker 1.13-cs1-rc1
UCP 2.1.0-beta1

vm.max_map_count was updated.

[root@beta-c105 ~]# sysctl -p
vm.max_map_count = 262144

From the logs :

# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 1973026816 bytes for committing reserved memory.
# An error report file with more information is saved as:
# /tmp/hs_err_pid1.log
OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x000000008a660000, 1973026816, 0) failed; error='Cannot allocate memory' (errno=12)

I know that this has been posted before but it was closed and I am having the same issue. I have attached a screenshot and here are the contents of my docker-composer.yml:

version: "3.3"

services:

elasticsearch:
command: elasticsearch -Enetwork.host=0.0.0.0 -Ediscovery.zen.ping.unicast.hosts=elasticsearch
environment:
ES_JAVA_OPTS: -Xms2g -Xmx2g
image: elasticsearch:5
ulimits:
memlock: -1
nofile:
hard: 65536
soft: 65536
nproc: 65538
volumes:
- /usr/share/elasticsearch/data
networks:
- elk
deploy:
mode: replicated
replicas: 1
endpoint_mode: dnsrr
kibana:
image: kibana:latest
ports:
- "5601:5601"
environment:
ELASTICSEARCH_URL: http://elasticsearch:9200
networks:
- elk
deploy:
mode: replicated
replicas: 1
healthcheck:
test: wget -qO- http://localhost:5601 > /dev/null
interval: 30s
retries: 3
logstash:
hostname: logstash
command: sh -c "logstash -e 'input { syslog { type => syslog port => 10514 } gelf { } } output { stdout { codec => rubydebug } elasticsearch { hosts => [ "elasticsearch" ] } }'"
image: logstash:alpine
ports:
- "10514:10514/tcp"
- "10514:10514/udp"
- "12201:12201/udp"
networks:
- elk
deploy:
mode: replicated
replicas: 2

networks:
elk:
driver: overlay
driver_opts:
encrypted: "true"

The /_cluster/health API call gives you the health of the cluster, not the individual node. If you lose a node in the cluster, calls to /_cluster/health on the healthy nodes will return status: yellow, which can lead to healthy tasks being killed.