Re: Python Segfaults with Django 1.1

> > i have a problem on a debian lenny machine which is not easy to
> > track down. It started with Apache2 mod_wsgi crashes (segfault in
> > libapr) after the migration from mod_python. The server crashes
> > sporadic and everytime with another view called, but everytime
> > after a while (2-7 Days, depending on traffic).
> Probably not related, but you never know... I've seen this happen in
> ye olde days with a zope server that you'd start in daemon mode from
> the terminal. After 2-4 days the terminal would die and suddenly the
> perfectly-running zope server would have nowhere to print its console
> output once an infrequent error occured. And it would die.
> The wsgi stuff works differently, so this shouldn't be the problem.
> Mentioning it anyway, perhaps it rings some distant bell :-)

I got another clue, it seems that the python process runs out of file
handles. After 10k requests (via ab -c 1 -n 10000) i got several "not
found" io exceptions like "/dev/urandom not found", TemplateError:
Template xy not found and this one : Error Opening
file /path/to/geoip/GeoIP.dat

Maybe that is why the mod_python setup runs fine, due to the restart
for each request.

Sven

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