On 28-Jul-09, at 8:40 PM, Karen Tracey wrote:
>
> I don't know if it's still an issue but I have a vague recollection  
> of seeing a similar problem mentioned fairly recently, and reported  
> as fixed by upgrading psycopg2.  I'm not up on psycopg2 levels -- is  
> 2.0.7 the latest?
>
> You can see the original problem report here:
>
> http://lists.initd.org/pipermail/psycopg/2007-July/005565.html
>
> and it states the problem may also occur under mod_wsgi.  The "fixed  
> by running under mod_wsgi" implication may be because you can  
> configure things under mod_wsgi such that you don't have multiple  
> Python sub interpreters, but if your configuration doesn't ensure  
> that then I think you can still see the problem under mod_wsgi.  So  
> an alternative way to fix/debug it may be to ensure your mod_wsgi  
> configuration does not result in the problem situation described in  
> that ticket.
>
> Karen
>
> >


Thanks!

I updated to the latest version of psycopg2 (2.0.9) and restarted  
apache and at first it seemed to be fixed, then the problem reappeared  
after a few minutes, so I went the re-configuring mod_wsgi route and I  
haven't had any problems since (it's difficult to say for sure that  
the issue is fixed, since the problem is intermittent.)

The lines I had to add to my Virtualhost's config in the end were:

WSGIDaemonProcess virtualhost.domain.name threads=15
WSGIProcessGroup virtualhost.domain.name

- Dave
--~--~---------~--~----~------------~-------~--~----~
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 
django-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to