Hi all, I am facing the dreaded "Unhandled Exception" raised by Flup. The sad part is its raised at the webserver(lighttpd+flup) level and not at the application level(Django). So no 500 email is raised about where the problem is. Our entire team struggled hard to cleanup the codebase, incase of any ambigous imports and someones of that sort, just to be eliminate the chances of raising errors due to the ambiguous imports. And we cleaned up many things in the code. Still the same exception. To be frank I am really frustrated with Flup's error handling. It doesn't tell you anything, worst of all, it shows the same "Unhandled Exception" to the Users. How do I get pass this. I checked the lighttpd logs, all I see is "Interface Error/Connection already closed." Its only occuring when my applicaiton is running in FCGI mode. so the problem is with how flup is actually dealing with my code(application). How do I get pass this. I checked for alternatives for flup, but Django depends on flup explicitly(which is one more restriction, and puzzled me)(Reference:django_src/django/core/servers/ fastcgi.py line:100 / 131)
How do I debug(atleast) this scenario and solve the problem? Please help me out. The application is down since 3 days. :( --~--~---------~--~----~------------~-------~--~----~ 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
