search

ramkrishanbhatt / modwsgi

Automatically exported from code.google.com/p/modwsgi
0 stars 0 forks source link

mod_wsgi 2.3 crashes on debian 4.0r5 powerpc #116

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Install Debian 4.0r5 powerpc
2. Install trac, libapache2-mod-wsgi from etch-backports
3. View /var/log/apache2/*err*

What is the expected output? What do you see instead?
The trac homepage

What version of the product are you using? On what operating system?
mod_wsgi 2.3, python 2.4, trac 0.11.1, debian 4.0r5

Please provide any additional information below.
My first runs with apache's logging set to info gave me the following
information in /var/log/apache2/error.log:

[Fri Oct 31 15:54:52 2008] [notice] child pid 8817 exit signal Segmentation
fault (11)

Incrementing the verbosity level to debug, it says:

[Fri Oct 31 15:39:53 2008] [notice] child pid 8357 exit signal Segmentation
fault (11)
[Fri Oct 31 15:39:54 2008] [info] mod_wsgi (pid=8425): Attach interpreter ''.
[Fri Oct 31 15:39:56 2008] [notice] child pid 8425 exit signal Segmentation
fault (11)
[Fri Oct 31 15:39:57 2008] [info] mod_wsgi (pid=8460): Attach interpreter ''.

I decided to attach gdb and see what happens (apache2ctl stop; gdb
/usr/sbin/httpd, then run -X and re-call the url):

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1026659552 (LWP 8750)]
0x0e185518 in _PyType_Lookup () from /usr/lib/libpython2.4.so.1.0

Original issue reported on code.google.com by rannyak...@gmail.com on 31 Oct 2008 at 2:58

GoogleCodeExporter commented 8 years ago 
I need to clarify: I expected to see the Trac 0.11.1 homepage. I know the
configuration I use for Trac with Mod_WSGI and SQLite is correct since I test
generated configurations for trac on rhel4 i386, rhel5 i386, netbsd4 i386 and 
debian4
i386. On these platforms the exact same configuration has always worked without 
issue.

Today I started testing my generated config on PPC debian4 for the first time 
and I
experience the above. I hope I can help further in fixing this, either in 
mod_wsgi or
if need be, in debian4 ppc upstream.

Original comment by rannyak...@gmail.com on 31 Oct 2008 at 3:02

GoogleCodeExporter commented 8 years ago 
Also of importance: Running trac through tracd works without problems.

Original comment by rannyak...@gmail.com on 31 Oct 2008 at 3:07

GoogleCodeExporter commented 8 years ago 
Are you, or were you also loading mod_python into the same Apache instance?

Using both together, where one or the other is using static Python library can 
cause crashes or undefined symbols 
in Python library. See:

  http://code.google.com/p/modwsgi/wiki/InstallationIssues

When taking out mod_python, ensure that you did a full 'stop' of Apache, and 
not just a 'restart'. If you don't fully 
stop Apache it may not properly unload mod_python because it doesn't properly 
clean up after itself.

Check on that and then we can move forward to look at other things.

Original comment by Graham.Dumpleton@gmail.com on 31 Oct 2008 at 9:33

GoogleCodeExporter commented 8 years ago 
No followup so believe it was an environment issue that was sorted out by 
reporter.

Original comment by Graham.Dumpleton@gmail.com on 6 Feb 2009 at 7:50