Date: Fri, 31 Oct 2008 17:28:32 -0400 From: Michael Powell <nightrecon@verizon.net> To: freebsd-questions@freebsd.org Subject: Re: pyhton apache Message-ID: <geftb7$s62$1@ger.gmane.org> References: <235b80000810311312u46dc0979ndf7d4dc0687095fb@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
tethys ocean wrote:
> Hi all
>
> I have a problem, a freebsd box that is apache22 and python25-2.5.2_3,
> mod_python-3.3.1_2 after upgrading phyton web site has stoped with this
> error "Internal Server Error"
[snip]
> [Fri Oct 31 05:05:15 2008] [notice] Digest: done
> [Fri Oct 31 05:05:16 2008] [notice] Apache/2.2.6 (FreeBSD) mod_ssl/2.2.6
> OpenSSL/0.9.7e-p1 mod_python/3.3.1 Python/2.4.4 PHP/5.2.4 with
^^^^^^^^^^^^
Well Apache seems to think it is still using Python 2.4.4.
> Suhosin-Patch configured -- resuming normal operations
> [Fri Oct 31 10:06:21 2008] [error] [client 195.217.151.57] client sent
> HTTP/1.1 request without hostname (see RFC2616 section 14.23):
> /w00tw00t.at.ISC.SANS.DFind:)
>
[snip]
I can't be of much help with this as I am not a Python expert by any means,
but the first thing that occurs to me is to ask: did you rebuild/reinstall
mod_python after you upgraded to python25? If not you might want to try
that first. Restart Apache and see if it no longer shows the Python 2.4.4.
As far as the Python environment(s), you may want to ensure that all
vestiges of the old python24 are truly gone (especially prior to rebuilding
mod_python).
You may also try and find confirmation somehow whether or not the code that
is failing on the web server is even compatible with python25. In such a
case either update the failing code or downgrade back to python24.
If the server is "production" and you just need it back up fast you may
consider returning it to its pre-python25 upgrade condition. Then conduct
your python25 experimentation on a non-production test box.
Before any major change of this sort I _always_ do backup dumps of my
server. So if something goes south I can immediately restore the server to
the state it was in prior to mucking it up.
-Mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?geftb7$s62$1>