[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Apache?? problem



On Tue, May 07, 2002 at 09:40:57PM -0700, David Smead wrote:
> Larry,
> 
> Yes, the script works from the command line.  As mentioned, it also works
> as a CGI, but after executing the print command it comes back with an
> Internal Server Error, code 500.
> 
> I've since discovered that any or the os.<process_managment> functions
> also bomb, after they are executed.  Even the simple os.system( 'echo
> something'); produces the server error.
> 
> Unfortunately there are three things different than the system that has
> been working for a year now:  Debian with 2.4.18 kernel instead of RH7.1
> and 2.4.2-2; Apache 1.3.24 instead of 1.3.19 and Python 2.1.3 using GCC
> 2.95 instead of 2.1 using GCC 2.96.

I still suspect this is a problem with your script.  In my experience
the 500 error is always from invalid HTTP headers.  A common problem I
have seen is that only one set of headers can be returned for a
response, and after the headers have been ended with a blank line, you
can't write more.

One other troubleshooter I use in python cgi is the function
cgi.test().  This prints headers, and displays environment and form
variables from your script.

The people over at comp.lang.python may be able to help you out more.

HTH,
Larry
-- 
Larry Holish
<ljholish@speakeasy.net>


-- 
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org



Reply to: