Sorry to be so slow in responding. We were able to turn debugging
on... and no one saw a 404 error with debugging on. Of course,
debugging took a toll on the database server so we were not able to
just leave it on.
We have audited our code and we were able to clean up quite a bit but
we do see thi
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
No, the database is pretty standard (mysql 5.1.37-community). This is
an 'in-house' tool and we have about 15 consistent users. They hit is
pretty heavily and notice this issue during that time, but it also
pops up throughout the day. It does seem to be "fixed," albeit
temporarily, after we restart
On Thu, Jul 1, 2010 at 3:41 PM, vjimw 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 se
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
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 t
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!
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 tr
8 matches
Mail list logo
