prosody v.0.10 docker does not log to logspout

[Simon Hill]

I'm trying to use https://github.com/gliderlabs/logspout to siphon remote prosody docker logs to Paper Trail. I have the config 

"*console"; -- Log to the console, useful for debugging with daemonize=false

For some unknown reason, logspout doesn't pick this up. I have a couple of other containers running on this device, which capture fine. so I think it has something to do with prosody.

Is there anything I can do to fix that?

Thanks!

Si

[Matthew Wild]

Try setting the environment variable __FLUSH_LOG=1 before Prosody
starts. Does it help?

Regards,
Matthew

[Simon Hill]

Thanks Matt. It turned out that it had nothing to do with prosody. Logs are capturing fine now.I had a misconfigured log capture filter meant to filter out weave traffic that was also knocking out anything with 'debug' in it. oops.

--
You received this message because you are subscribed to a topic in the Google Groups "prosody-dev" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/prosody-dev/wN0KbMxmExI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to prosody-dev...@googlegroups.com.
To post to this group, send email to proso...@googlegroups.com.
Visit this group at http://groups.google.com/group/prosody-dev.
For more options, visit https://groups.google.com/d/optout.