search

fw42 / logspout-splunk

Send docker container logs to Splunk
6 stars 2 forks source link

Endless writing of ...Wrote to Splunk #2

Open petestorey26 opened 8 years ago

petestorey26 commented 8 years ago

I tried to start a container from the image using the suggested command:

docker run --env DEBUG=1 --name="logspout" \
    --volume=/var/run/docker.sock:/tmp/docker.sock \
    --publish=0.0.0.0:8002:80 b356b141ddc2

(obviously with the correct image name), but it won't start unless I specify a route in the docker run command, otherwise I just get it stopping immediately with:

# logspout v3.1-dev-custom by gliderlabs
# adapters: splunk
# options : persist:/mnt/routes
# jobs    : http[logs,routes]:80 pump
# routes  : none
2016/05/02 00:19:57  ended: %!s(<nil>)

I thus start it with a route added to the docker run command of splunk://172.17.0.1:1514 , which works, however it writes vast numbers of "...Wrote " entries to the port. I turned off --env DEBUG=1 but that doesn't seem to help.

Any ideas? (And does starting logspout without a route work for you?)

randomxxxx commented 8 years ago

Same issue here - did you ever resolve this problem? Thanks!