Graham:
I could not run the mod_wsgi test because it apparently will not
load. When I restart Apache with mod_wsgi.so loaded, I get
segmentation faults in the error log:
[Fri Feb 11 09:55:04 2011] [notice] child pid 78060 exit signal
Segmentation fault (11)
The results you asked for:
I stand corrected. By starting apache manually, I was lulled into a
false sense apache would find the shared library. It did not on
reboot. After doing a make clean and issuing your instructions below
and make install, all is well.
Thanks again.
This setting will not be used by mod_wsgi when run
Hi,
Note: I realize that what I am asking to do violates the wsgi spec.
Is there any way for me to use mod_wsgi and not provide the response
status and headers via start_response but instead as part of the body
(all properly formatted, of course)?
Thanks,
John
--
You received this message
Thanks for your patience and answers
2011-02-12 00:56:47,028 INFO PID 8497
2011-02-12 00:56:47,028 INFO PID 8497
but my log still shows the problem
and my httpd.conf
WSGIPythonOptimize 1
WSGISocketPrefix /var/run/wsgi
VirtualHost *:80
ServerName localhost
ServerAlias 127.0.0.1
Try not using Python logging module then, just use 'print' and see if
still occurs. Ie., replace call:
logger.info(urlsMap.urls)
with:
import sys
print sys.stderr, urlsMap.urls
If it only displays once then you will know that it has to do with the
Python logging module and nothing to do
On 12 February 2011 03:36, johnm johnm@gmail.com wrote:
Hi,
Note: I realize that what I am asking to do violates the wsgi spec.
Is there any way for me to use mod_wsgi and not provide the response
status and headers via start_response but instead as part of the body
(all properly
On 12 February 2011 03:02, Michael Bartz michael.ba...@gmail.com wrote:
Graham:
I could not run the mod_wsgi test because it apparently will not
load. When I restart Apache with mod_wsgi.so loaded, I get
segmentation faults in the error log:
[Fri Feb 11 09:55:04 2011] [notice] child pid
here is the output of the command you gave me :
libpthread.so.0 = /lib/tls/libpthread.so.0 (0xb7e04000)
libdl.so.2 = /lib/libdl.so.2 (0xb7dff000)
libutil.so.1 = /lib/libutil.so.1 (0xb7dfb000)
libm.so.6 = /lib/tls/libm.so.6 (0xb7dd8000)
libc.so.6 =
On 12 February 2011 11:50, commonzenpython commonzenpyt...@gmail.com wrote:
here is the output of the command you gave me :
libpthread.so.0 = /lib/tls/libpthread.so.0 (0xb7e04000)
libdl.so.2 = /lib/libdl.so.2 (0xb7dff000)
libutil.so.1 = /lib/libutil.so.1 (0xb7dfb000)
I'm having a problem getting web.py's OpenID working with mod_wsgi. If
I run web.py's webser directly, it works, so I'm guessing it's not a
problem with my code but how apache/mod_wsgi stores files. When I run
the web.py server directly, the openid library will create
a .openid_secret_key file.
On 12 February 2011 17:36, strattonbrazil strattonbra...@gmail.com wrote:
I'm having a problem getting web.py's OpenID working with mod_wsgi. If
I run web.py's webser directly, it works, so I'm guessing it's not a
problem with my code but how apache/mod_wsgi stores files. When I run
the
11 matches
Mail list logo