On Jan 30, 1:33 pm, Noah <[EMAIL PROTECTED]> wrote: > It doesn't happen on every page view... the server runs fine for days > and then POOF collapse, every site
Just a clarification on your configuration for mod_python. Each of these sites runs in a separate Python interpreter instance. Yes/No? This would be the case if they are in separate VirtualHost containers and you have set NameVirtualHost correctly and not set PythonInterpreter directive. If this is the case, then it would suggest that the conflict would have to be occurring in a C extension module, thus possibly that for postgresql. This would be the only way it could effect the different sites running in the different Python interpreter instances at the same time. Only way of isolating the sites so that at least only the one site causing the problem is affected, would be to use mod_wsgi daemon mode, or FASTCGI, SCGI, AJP solutions. That way each site could be run in separate processes. Graham > On Jan 29, 7:06 pm, Ivan Illarionov <[EMAIL PROTECTED]> wrote: > > > > Our database is utf8 we explicitly convert ignoring errors to utf8 > > > before passing to textile. Also it's not 1 page that poops it's every > > > site pooping at once. > > > That means that the problem is inside something that shows on every > > page. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
