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.

On Sat, Mar 21, 2015 at 5:36 AM, Matthew Wild <mwi...@gmail.com> wrote:

> On 20 March 2015 at 21:25, Simon Hill <simonhill...@gmail.com> wrote:
> > 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?
>
> Try setting the environment variable __FLUSH_LOG=1 before Prosody
> starts. Does it help?
>
> Regards,
> Matthew
>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to prosody-dev@googlegroups.com.
> Visit this group at http://groups.google.com/group/prosody-dev.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"prosody-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to prosody-dev+unsubscr...@googlegroups.com.
To post to this group, send email to prosody-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/prosody-dev.
For more options, visit https://groups.google.com/d/optout.

Reply via email to