admin login returns 500 error

[Floyd Arguello]

Hi all,

I've been working on this a few hours now, and I feel like someone has
dropped a BFR on my head. Logging into the Django Admin returns a very
informative 500 error. Anyone run into this before? Any ideas?

Thanks,
Floyd

[Graham Dumpleton]

If it is so informative of an error, maybe you should post what it is
here along with any details of exceptions from the error log files of
the hosting mechanism being used. Details on how you are hosting
Django, ie., builtin server, Apache with mod_python, mod_wsgi, or
fastcgi etc, would also help otherwise all we can do is polish our
crystal balls. :-)

Graham

[Floyd Arguello]

Ok, I'll help you help me :)

Running latest svn on Apache 2.2 with mod_python - error log doesn't
show a thing. The 500 error really isn't too helpful... just tells me
it's something with the server. Using latest stable Postgres and Python
2.4.3. RHEL5 64bit. Using lighttpd to serve the media files.

Thanks,
Floyd

[jmDesktop]

Does everything work with runserver?

> > Graham- Hide quoted text -
>
> - Show quoted text -

[Malcolm Tredinnick]

On Wed, 2008-03-26 at 08:10 -0700, Floyd Arguello wrote:
> Ok, I'll help you help me :)
>
> Running latest svn on Apache 2.2 with mod_python - error log doesn't
> show a thing. The 500 error really isn't too helpful... just tells me
> it's something with the server.

It might not be too helpful to you, but it's the only thing we have to
work with. All you've said is "something went wrong" and you're giving
us no other information. It will tell us if the problem if inside Django
or mod_python, for a start. It will also possibly provide other clues
that might be useful in debugging.

Malcolm

--
On the other hand, you have different fingers.
http://www.pointy-stick.com/blog/

[Graham Dumpleton]

On Mar 27, 2:10 am, Floyd Arguello <floyd.li...@gmail.com> wrote:
> Ok, I'll help you help me :)
>
> Running latest svn on Apache 2.2 with mod_python

Which version of mod_python?

> - error log doesn't
> show a thing. The 500 error really isn't too helpful... just tells me
> it's something with the server.

Let us judge that by telling us the full text shown from the whole
error page, not just an excerpt. From this we can tell if it is a
generic Apache error document response or a Django generated error
document.

Also post your mod_python configuration that you are using to setup
mod_python to execute Django. Ensure that you have enabled:

PythonDebug On

Also indicate whether you have multi language error documents enabled
in Apache. Ie., whether the following is uncommented:

# Multi-language error messages
#Include conf/extra/httpd-multilang-errordoc.conf

I wouldn't be surprised if you have this enabled, have caused some
error and Apache can't serve up the multi language error document
because you are pushing everything into Django. You may need:

<Location /error>
SetHandler None
</Location>

If it is an Apache internal 500 error, there should be something in
the Apache error logs. It may not be Python specific, so don't assume
what you are seeing isn't relevant. Remember what last thing in Apache
error logs are (both main and virtual host if used), do request and if
anything extra added, post it here.

In short, you need to provide as much information as possible, else we
cannot help you. Saying it doesn't work is not enough.

Graham