Hi Roberto, This indeed fixes the truncation issue, thanks!
Is there any way to switch to line buffering? Right now it appears all at once, only after the application has fully loaded. --nate On Thu, Jul 16, 2015 at 2:02 AM, Roberto De Ioris <[email protected]> wrote: > > > Hi, > > > > I've found that enabling any option (touch-reopen, log-maxsize, or just > > log-master) that enables master logging causes a significant change in > the > > way that uWSGI handles application startup logs. Instead of line > > buffering, > > the startup log is fully buffered and appears to be truncated at 32KB. > > log-master-bufsize can increase this limit up to 64KB but does not seem > to > > go higher - and my reading on log-max-bufsize suggests it's only supposed > > to be the tunable parameter for the size of a single message anyway. Is > > the > > worker end of the log pipe buffering output from the application and > > sending it as a single message? > > > > The application I work with is large and loads a huge number of > > components, > > and as such, the startup log is very large, and unfortunately, unless I > > disable master logging, almost all of this is lost. > > > > I've created a very simple example to reproduce the truncation: > > > > https://gist.github.com/natefoo/7c9c072e4e46225028f8 > > > > Thanks, > > --nate > > _______________________________________________ > > uWSGI mailing list > > [email protected] > > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi > > > > Hi, you can tune the max send/recv socket buffer with > > /proc/sys/net/core/rmem_max > /proc/sys/net/core/wmem_max > > log packets are written via a socketpair channel > > -- > Roberto De Ioris > http://unbit.com > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
