> I think part of the problem might be django setting the timezone: > https://docs.djangoproject.com/en/dev/ref/settings/#time-zone since the > server already has its localtime as UTC. My theory is that the uwsgi > worker > is picking up this timezone change which presumably is doing the logging > for requests. >
I have searched a bit, and it looks like it is a known behaviour, and (incredibly for me) the expected behaviour. Honestly the only thing popping up in my mind is using syslog, but i do not know if it is a viable solution for you. Another approach would be developing an ad-hoc logging plugin (i think it will require no more than a dozen o lines) simply prepending dates. this is a pretty simple plugin, you can safely ignore lines from 9 to 53: http://projects.unbit.it/uwsgi/browser/plugins/logsocket/logsocket_plugin.c You will then be able to set --log-master to let the master managing logs (its TZ will not be changed by django) -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
