Re: Apache?? problem
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.
--
Sincerely,
David Smead
http://www.amplepower.com.
On Tue, 7 May 2002, Larry Holish wrote:
> On Tue, May 07, 2002 at 03:21:54PM -0700, David Smead wrote:
> >
> > I'm converting an intranet server from RH to Debian and have run into a
> > problem with Apache.
> >
> > On our intranet is a web page that let's users print various documents,
> > via a simple Python CGI. The CGI uses the os.system() function with the
> > appropriate command line in the call.
> >
> > Curiously, the documents get printed, but then Apache announces an
> > internal server error. If I could find a log of the error I'd have some
> > clues, but I can't find were it logs to any of the expected places.
>
> Running woody here, and Apache writes errors to
> /var/log/apache/error.log. Have you tried running the python CGI
> script from the command line, to see if you get any errors there?
>
>
--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: