On Tue, Mar 11, 2014 at 9:24 PM, Nick Santos <ultraa...@gmail.com> wrote:
> Hey Shawn, > > What does your web stack and environment look like? If it's failing during > a fork with an out of memory, that makes me wonder if the host process for > django is consuming a chunk of memory for some reason, and when it gets > forked, it'll get replicated over (which supposedly would fail, even with > copy on write, with certain OS settings - I'm far from an expert in this > area). Have you tested this code on another machine to see if it exhibits > the same behavior? > -Nick > > Nick, Thanks for the ideas. It was being run with gunicorn. I'll try with other options, such as runserver and try to get it working on a separate machine. The reason I've only been testing it on one server is that it's the one set up with the gpg keychain our single-sign-on needs. Shawn -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAOzwKwE4F%3DbEgU0Q4S5Sqw8pYm20OfGmV76dDLEyQYQbZ8xPyA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
