At a guess it has an C extension component and that component is not designed properly to work in Python sub interpreters. Force the use of the main interpreter as documented in:
http://code.google.com/p/modwsgi/wiki/ApplicationIssues#Python_Simplified_GIL_State_API IOW, try adding: WSGIApplicationGroup %{GLOBAL} into your Apache configuration. Alternatively and as explained elsewhere in that document, you have a shared library version or symbol conflict with other stuff being loaded into Apache. This can especially happen if you are also loading PHP into the same Apache. Graham On 16 October 2011 18:36, pbzRPA <[email protected]> wrote: > Hi > > I was wondering if anyone had a similar problem when trying to use > pango in django running under mod_wsgi on apache. > > I am running > > |20:11:06|# cat /etc/debian_version > 6.0.3 > > When I run a runserver on the same server it works fine but the moment > I "import pango" in any of my modules the mod_wsgi apache server > raises a 500 error. > > I did the whole installation using apt-get and installed pygtk. > > I would appreciate any help to try and debug this issue. The only > thing in my apache error.log is : > > child pid 3642 exit signal Segmentation fault (11) > > Thanks > > -- > 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. > > -- 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.
