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

Endless writing of ...Wrote to Splunk #2

Open
petestorey26 opened this issue May 2, 2016 · 1 comment
Open

Endless writing of ...Wrote to Splunk #2

petestorey26 opened this issue May 2, 2016 · 1 comment

Comments

@petestorey26
Copy link

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
Copy link

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

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