Re: Development server crash with no error message
Am Donnerstag, den 11.12.2008, 10:29 +0100 schrieb Graham Dumpleton: > A problem recently highlighted with the geos stuff though is that it > likes to crash if using it on 64 bit Linux architecture. Good to know. While switching from development to production, we also switched from 64 to 32 bit. . . . Tobias --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Development server crash with no error message
On Dec 11, 8:06 pm, Tobias Kräntzer <[EMAIL PROTECTED]> wrote: > Am Donnerstag, den 11.12.2008, 00:05 +0100 schrieb Andrew Fong: > > > I'm using MySQLdb, cmemcache, PIL, and the django.contrib.gis stuff. > > Hi, we had a similar problem. It turns out, that in our case it was a > multithreading issue with geos/gdal. For instance using apache2 with > wsgi and and allowing only one thread per process was helpful. The development server is single threaded though, so threading shouldn't be an issue. A problem recently highlighted with the geos stuff though is that it likes to crash if using it on 64 bit Linux architecture. That was part of asking what platform, although forgot to ask about whether 32 bit or 64 bit version of Python. Recent threads about this at: http://groups.google.com/group/django-users/browse_frm/thread/e337057e9df9bb9 http://groups.google.com/group/modwsgi/browse_frm/thread/a488d2551c4c7df0 Graham --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Development server crash with no error message
Am Donnerstag, den 11.12.2008, 00:05 +0100 schrieb Andrew Fong: > I'm using MySQLdb, cmemcache, PIL, and the django.contrib.gis stuff. Hi, we had a similar problem. It turns out, that in our case it was a multithreading issue with geos/gdal. For instance using apache2 with wsgi and and allowing only one thread per process was helpful. . . . Tobias --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Development server crash with no error message
Forgot to ask, what platform? On Dec 11, 10:05 am, Andrew Fong <[EMAIL PROTECTED]> wrote: > I'm using MySQLdb, cmemcache, PIL, and the django.contrib.gis stuff. > > On Dec 8, 2:58 pm, Graham Dumpleton <[EMAIL PROTECTED]> > wrote: > > > On Dec 9, 8:50 am, Andrew Fong <[EMAIL PROTECTED]> wrote: > > > > When I'm poking around in my Django app, my development server > > > (manage.py runserver) will sometimes quit without raising an exception > > > or leaving any messages. I am not tinkering around with the code or > > > doing anything that would force a reload. It just decides to quit. > > > > I can check the last request I made before it crashed, but without any > > > exceptions or errors, it's very hard to debug. Does anyone have any > > > tips on getting some more useful output out of acrash? > > > What database adapter are you using? Is it a current version? > > > What other third party packages are you using which use a C extension > > module to do stuff? > > > Graham --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Development server crash with no error message
I'm using MySQLdb, cmemcache, PIL, and the django.contrib.gis stuff. On Dec 8, 2:58 pm, Graham Dumpleton <[EMAIL PROTECTED]> wrote: > On Dec 9, 8:50 am, Andrew Fong <[EMAIL PROTECTED]> wrote: > > > When I'm poking around in my Django app, my development server > > (manage.py runserver) will sometimes quit without raising an exception > > or leaving any messages. I am not tinkering around with the code or > > doing anything that would force a reload. It just decides to quit. > > > I can check the last request I made before it crashed, but without any > > exceptions or errors, it's very hard to debug. Does anyone have any > > tips on getting some more useful output out of acrash? > > What database adapter are you using? Is it a current version? > > What other third party packages are you using which use a C extension > module to do stuff? > > Graham --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Development server crash with no error message
On Tue, Dec 9, 2008 at 4:50 AM, Andrew Fong <[EMAIL PROTECTED]> wrote: > > When I'm poking around in my Django app, my development server > (manage.py runserver) will sometimes quit without raising an exception > or leaving any messages. I am not tinkering around with the code or > doing anything that would force a reload. It just decides to quit. > > I can check the last request I made before it crashed, but without any > exceptions or errors, it's very hard to debug. Does anyone have any > tips on getting some more useful output out of a crash? I just ran into the same problem. In my case however, I happen to know exactly which requests causes the crash, it happened everytime I query a model (say Entry.objects.all()). So I ran: from myproj.myapp.models import Entry Entry.objects.all() from 'manage.py shell' and I immediately saw from the exceptions that there was an infinite recursion. It turned out that I defined a custom Manager's get_query_set() in a very wrong way causing an infinite loop (I stupidly returned self.filter(...) instead of calling super like the doc says). I don't know if this would help in your case, but I thought I share anyway, just in case. Ronny --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Development server crash with no error message
On Dec 9, 8:50 am, Andrew Fong <[EMAIL PROTECTED]> wrote: > When I'm poking around in my Django app, my development server > (manage.py runserver) will sometimes quit without raising an exception > or leaving any messages. I am not tinkering around with the code or > doing anything that would force a reload. It just decides to quit. > > I can check the last request I made before it crashed, but without any > exceptions or errors, it's very hard to debug. Does anyone have any > tips on getting some more useful output out of a crash? What database adapter are you using? Is it a current version? What other third party packages are you using which use a C extension module to do stuff? Graham --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Development server crash with no error message
When I'm poking around in my Django app, my development server (manage.py runserver) will sometimes quit without raising an exception or leaving any messages. I am not tinkering around with the code or doing anything that would force a reload. It just decides to quit. I can check the last request I made before it crashed, but without any exceptions or errors, it's very hard to debug. Does anyone have any tips on getting some more useful output out of a crash? -- Andrew --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
