I may be just living under a rock, but I don't know how to use pdb.set_trace() when not using the development server. If you do this successfully, please let me know.
What I have done is append "print"ings to a file, or configure extra logger outputs. Under mod_wsgi I get some logging output in the apache logs without doing anything special, I don't know how it works with FCGI. Since you say this is an internal tool, you might try DEBUG=True in settings.py and getting users to come look at their 404 screens, since they will then carry extra info. On Thu, Jul 1, 2010 at 10:41 AM, vjimw <im.a.machobea...@gmail.com> wrote: > It only happens in our production environment. We have a stage > environment, which is a mirror of production, that does not have this > behavior and it does not happen on our development or local > environments. The trace is a good idea to try to see more > information. > > On Jul 1, 9:28 am, Bill Freeman <ke1g...@gmail.com> wrote: >> Does it happen when running the development server? If so, you get >> a lot more debugging info right up front (access to variables in each >> stack from, for instance). If it's still not clear you can use the trace >> as a guide as to where to put a pdb.set_trace() (possibly in an if that >> makes it only trigger in the interesting circumstance) so that you can >> poke around. >> >> >> >> On Thu, Jul 1, 2010 at 10:06 AM, vjimw <im.a.machobea...@gmail.com> wrote: >> > Actually, we are getting our Django 404 page. Sorry to be unclear on >> > that. The URLs appears as 404 in the access logs. >> >> > We are actually using fast_cgi per our system administrator and >> > wondered if switching to mod_wsgi might help solve the problem, but it >> > looks like you had the issue with mod_wsgi! >> >> > Did recompiling apache solve the problem for you with your Django app >> > running mod_wsgi? >> >> > Thanks for the fast response. Let me know any other information that >> > my be helpful. >> >> > On Jul 1, 9:00 am, "euan.godd...@googlemail.com" >> > <euan.godd...@gmail.com> wrote: >> >> When you say "an apache 404 error" do you mean a non-Django styled >> >> one? If so, I think there's something wrong with your apache >> >> configuration and not your Django app. What mechanism are you using to >> >> serve the application? I have seen issues like with this mod_wsgi when >> >> the reload mechanism isn't triggered correctly and you have to restart >> >> apache to get it work correctly. I think in that case it was because >> >> I'd compiled apache slightly incorrectly. I never got to the bottom of >> >> the problem. >> >> >> On Jul 1, 2:54 pm, vjimw <im.a.machobea...@gmail.com> wrote: >> >> >> > We are having an issue where valid model objects are returning an >> >> > apache 404 error. Often times, if you hit refresh in the browser a few >> >> > times, the object is returned with the same URL. >> >> >> > We are using Django 1.2.1 >> >> > -- >> > You received this message because you are subscribed to the Google Groups >> > "Django users" group. >> > To post to this group, send email to django-us...@googlegroups.com. >> > To unsubscribe from this group, send email to >> > django-users+unsubscr...@googlegroups.com. >> > For more options, visit this group >> > athttp://groups.google.com/group/django-users?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to django-us...@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. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
