The actual cause is probably the same was as was causing: http://code.google.com/p/modwsgi/issues/detail?id=78
and a couple of other problems. When processing configuration, mod_wsgi was allocating long lived memory from wrong pool and the memory would get reused after a while and get corrupted. You could always go through and change all references to 'temp_pool' to 'pool' in mod_wsgi.c to be safe. Graham 2009/3/10 rtl <[email protected]>: > > To wrap this up (took a lot longer than 5 days!) > > On Nov 17 2008, 4:56 pm, rtl <[email protected]> wrote: >> >> I've implemented the WSGIImportScript suggestion on one of the boxes >> and the setting of the PYTHON_EGG_CACHE on the other as an A/B test. >> > > Explicitly setting the PYTHON_EGG_CACHE in the wsgi script before > importing anything has fixed this problem. > > Robert > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en -~----------~----~----~----~------~----~------~--~---
