Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ELK has all been up, logspout run through the docker run #3

Closed
MagicStarTrace opened this issue Jan 3, 2017 · 9 comments
Closed

ELK has all been up, logspout run through the docker run #3

MagicStarTrace opened this issue Jan 3, 2017 · 9 comments

Comments

@MagicStarTrace
Copy link

MagicStarTrace commented Jan 3, 2017

docker run -d bekt/logspout-logstash -e ROUTE_URIS: logstash://ip:5000 -v /var/run/docker.sock:/var/run/docker.sock

root@docker:~# docker  logs  714959c7b1c7
# logspout v3.2-dev-custom by gliderlabs
# adapters: tcp logstash raw udp
# options : persist:/mnt/routes
!! bad adapter: 

What should I do ?

@Bekt
Copy link
Owner

Bekt commented Jan 3, 2017

Is logstash://ip:5000 accessible from inside of the container?

@MagicStarTrace
Copy link
Author

MagicStarTrace commented Jan 4, 2017

docker compose logstash:
logstash:
image: elkstack/logstash-logspout
ports:
- 5000:5000/udp
restart: unless-stopped
command: -f /opt/logstash/sample.conf

=========================================================

root@vm10-140-92-130:# nc -w2 -u 10.140.31.128 5000
root@vm10-140-92-130:
# echo $?
0
root@vm10-140-92-130:~
docker run -d bekt/logspout-logstash -e ROUTE_URIS: logstash://10.140.31.128:5000 -v /var/run/docker.sock:/var/run/docker.sock

root@vm10-140-92-130:~# docker logs 4544785d3fd2

logspout v3.2-dev-custom by gliderlabs

adapters: udp tcp logstash raw

options : persist:/mnt/routes

!! bad adapter:
root@vm10-140-92-130:~#

Port normal, how should I do?

-e ROUTE_URIS: logstash://10.140.31.128:5000/udp ,The same can not 。

Please help me, thank you

@MagicStarTrace
Copy link
Author

@Bekt Please help me, thank you!

@Bekt
Copy link
Owner

Bekt commented Jan 10, 2017

Can you post your full docker-compose file? From the snippet above, it looks like you didn't mount the /opt/logstash/sample.conf file in logstash.

@MagicStarTrace
Copy link
Author

The sample.conf file is in the mirror

@Bekt
Copy link
Owner

Bekt commented Jan 10, 2017

Can you give me a docker-compose file I can run? Otherwise I have no idea with the given information.

@MagicStarTrace
Copy link
Author

Customized mirrors.
Mirror problem should not, and now logspout use compose, logspout with logstash use is no problem, it should not be a component of the problem. Now I have multiple logspout need to run in different nodes, can not use compose to run it

@MagicStarTrace
Copy link
Author

version: '2'
services:
elasticsearch:
image: 10.140.92.130:8050/elkstack/elasticsearch
restart: unless-stopped
ports:
- 9200:9200
kibana:
image: 10.140.92.130:8050/elkstack/kibana:latest
restart: unless-stopped
environment:
- ELASTICSEARCH_URL=http://elasticsearch:9200
ports:
- 5601:5601
logstash:
image: 10.140.92.130:8050/elkstack/logstash-logspout
ports:
- 5000/udp:5000/udp
restart: unless-stopped
command: -f /opt/logstash/sample.conf
redis:
image: redis
restart: unless-stopped

@Bekt
Copy link
Owner

Bekt commented Mar 12, 2017

Hey @huyifanstar, were you able to figure out?

@Bekt Bekt closed this as completed Mar 12, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants