Replying to myself. Using WSGIDaemonProcess fixes the problem as the python code is then interpreted by apache processes dedicated to wsgi that don't serve HTTP requests.
(I'm surprised reviewboard deployment script doesn't enable that automatically). On Friday, May 2, 2014 3:46:09 PM UTC+1, Stephane Chazelas wrote: > > Hello, > > I've got an apache server (prefork mpm) with several virtual hosts, one of > them running reviewboard (a python web application (django) using wsgi) via > mod_wsgi and another one running bugzilla (CGI). > > It seems that reviewboard somehow does a "os.environ['TZ'] = 'UTC'". > > What happens is that after an apache process has served a reviewboard page > that has interpreted that, its TZ remains set to UTC. If that process later > serves a bugzilla request, bugzilla will think the local timezone is UTC > and the timestamps will be wrong. > > Also, that affects the timestamps in apache logs (at least with 2.4.6, not > with 2.4.9), those apache processes that have served reviewboard pages > before write UTC timestamps while the other ones write localtime timestamps. > > What would be the best way to guard against that? > > Can we tell wsgi to restore the environment after it has served a request? > Can we dedicate apache processes to wsgi queries only? > > Thanks, > Stephane > -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/modwsgi. For more options, visit https://groups.google.com/d/optout.
