On Wed, Oct 19, 2005 at 03:31:11AM -0700, Radhika wrote:
>
> Hi,
Hi,
> I am migrating my webserver from apache1.3 to apache2.I am running
> apache2.0.54 on debian3.1
One of the differences between Apache 1.3 and Apache 2 in Debian is how
the module loading is defined.
In Apache2 you enable
Hi,
I am migrating my webserver from apache1.3 to apache2.I am running apache2.0.54 on debian3.1
One of my customer is reported the error message about the apache2 errorwhenever they try to access the .cgi page they are getting the following error.
Server error!The server encountered an in
I thank all those individuals who helped me with my CGI problem.
I finally figured out the problem with suEXEC giving internal server
errors with CGI scripts. Apparently the directory was mode 0775 instead
of 0755 ... suEXEC checks to make sure the directory is only writable by
the user. Curre
On Mon, 8 Dec 1997, Paul Miller wrote:
> Alright, this is really weird. After adding those lines it ran fine and
> now it runs w/o those lines.. maybe my permissions were wrong, but I'm
> sure they were 755 root/root. hmm.. Anyhow, now it only runs in the
> /cgi-bin and not the user's director
Perl's "idiot's guide to solving cgi problems" didn't have any helpful
hints for my problem. Although it did say something about running the
server as a user which could write in all the cgi directories, which
didn't seem right. Currently Apache runs as www-data/www-data which is
enough access to
On Mon, 8 Dec 1997, Paul Miller wrote:
> I can run other cgi scripts, so that can't be the problem...
>
You didn't tell us, if you have accepted our advice to take a look at
perl's "idiot's guide to solving cgi problems".
Anyway, change the script like this:
#!/usr/bin/perl
open (OUT, ">/tmp/
On Mon, 8 Dec 1997, Hamish Moffatt wrote:
> On Sun, Dec 07, 1997 at 11:29:08PM -0500, Paul Miller wrote:
> > Unfortunately that is the first thing... it runs on other systems, so I'm
> > clueless.. It wasn't able to run from the server cgi-bin, so I don't
> > think it is suEXEC's problem, but Apa
On Sun, Dec 07, 1997 at 11:29:08PM -0500, Paul Miller wrote:
> Unfortunately that is the first thing... it runs on other systems, so I'm
> clueless.. It wasn't able to run from the server cgi-bin, so I don't
> think it is suEXEC's problem, but Apache's.
Hmmm, ok, I apologise for getting a bit car
On Sun, 7 Dec 1997, Paul Miller wrote:
: Unfortunately that is the first thing... it runs on other systems, so I'm
: clueless.. It wasn't able to run from the server cgi-bin, so I don't
: think it is suEXEC's problem, but Apache's.
:
: Thanks
Are you sure that you have a directive set up for y
Unfortunately that is the first thing... it runs on other systems, so I'm
clueless.. It wasn't able to run from the server cgi-bin, so I don't
think it is suEXEC's problem, but Apache's.
Thanks
On Mon, 8 Dec 1997, Hamish Moffatt wrote:
> On Sun, Dec 07, 1997 at 05:19:01PM -0500, Paul Miller wro
I took his script, just as it was posted earlier, and installed it
on my machine here. It ran flawlessly as a CGI program and gave me
the thankyou notice (the script was posted a couple of days ago).
I sent him the same script I made, and it doesn't work on his
system, I am using perl5.003, and
On Sun, Dec 07, 1997 at 05:19:01PM -0500, Paul Miller wrote:
> hmmm... that means something is wrong with Apache, suEXEC, or Perl 5.004.
> Do I need any special perl libs/files for cgi?
>
> I've been able to run files which use sh (bash) and awk fine.. so I think
> there is something wrong w/ perl
On 07-Dec-97 Paul Miller wrote:
>hmmm... that means something is wrong with Apache, suEXEC, or Perl 5.004.
>Do I need any special perl libs/files for cgi?
The code you showed doesn't need anything but perl. If the command "whence perl"
shows /usr/bin/perl, and dselect is working for you (or anyot
hmmm... that means something is wrong with Apache, suEXEC, or Perl 5.004.
Do I need any special perl libs/files for cgi?
I've been able to run files which use sh (bash) and awk fine.. so I think
there is something wrong w/ perl.
Thanks
Paul
On Sun, 7 Dec 1997, Troy wrote:
> It works (as is) on
On Sun, 7 Dec 1997, Paul Miller wrote:
> I didn't write this script and don't know perl, so I don;t know what is
> wrong...
>
As someone pointed out: the Idiot's Guide To Solving CGI Problems at
www.perl.com is great.
If you want to use CGI's scripts written in perl, I strongly advice you to
rea
On Sun, 7 Dec 1997, Hamish Moffatt wrote:
> You probably forgot to output the content type & the following blank line.
> Something like
>
> print "Content-type: text/html\n\n"
>
> would usually do it.
I didn't write this script and don't know perl, so I don;t know what is
wrong...
---
#!/usr/
I wrote:
> Have a look at the Don't-be-offended-by-the-name Idiot's Guide to
> Solving Perl CGI Problems. Although it's aimed at
> comp.lang.perl.misc, it's still got a lot of good advice.
It must be too late at night... That's at
http://www.perl.com/CPAN/doc/FAQs/cgi/idiots-guide.html>
--
Paul Miller <[EMAIL PROTECTED]> writes:
> How can I fix this problem?
>
> ***
> Internal Server Error
>
> The server encountered an internal error or misconfiguration and was
> unable to complete your request.
[snip]
Have a look at the Don't-be-offended-by-the-name Idiot's Guide to
Solving Per
On Sat, Dec 06, 1997 at 11:57:22PM -0500, Paul Miller wrote:
> On Sat, 6 Dec 1997, Alex Yukhimets wrote:
> > > How can I fix this problem?
> > Run "perl -c" on your script and see what happens.
> > Plus check if it is mode 755.
>
> syntax OK
>
> perl is mode 755.. should the script be? I tried t
/bin/sh
/path-to-cgi/script.pl 2>/tmp/cgi-error.$$
Then call your script and look at the cgi-error. ( will be the
pid) to see what went wrong. Also, look at your apache log messages.
Brandon
-
Brandon Mitchell <[EMAIL PROTECTED]> "We all know linux is great...
On Sat, 6 Dec 1997, Alex Yukhimets wrote:
> > How can I fix this problem?
>
> Run "perl -c" on your script and see what happens.
> Plus check if it is mode 755.
syntax OK
perl is mode 755.. should the script be? I tried the script at 755 is it
still didn't work...
-Paul
--
TO UNSUBSCRIBE FR
> How can I fix this problem?
Run "perl -c" on your script and see what happens.
Plus check if it is mode 755.
Alex Y.
--
_
_( )_
( (o___ +---+
| _ 7 |Alexander Yukhimets|
\(")|
How can I fix this problem?
***
Internal Server Error
The server encountered an internal error or misconfiguration and was
unable to complete your request.
Please contact the server administrator, [EMAIL PROTECTED] and
inform them of the time the error occurred, and
anything you might have done
Maarten Boekhold <[EMAIL PROTECTED]> wrote:
: Apart from the other suggestions, there might just be an error in your
: script that causes output from perl *before* you send the header. Or
: maybe you'r running with 'perl -w' and have a variable that you use only
: once. That causes output too w
On Mon, 15 Sep 1997, Dave Neuer wrote:
> I am trying to get a CGI script written in Perl running, and I keep
> getting a wierd error that I don't understand:
>
> "access to /usr/lib/cgi-bin/testscript.pl failed for *machine name*,
> reason: Premature end of script headers"
>
> Anyone know what t
Dave Neuer <[EMAIL PROTECTED]> wrote:
: I am trying to get a CGI script written in Perl running, and I keep
: getting a wierd error that I don't understand:
:
: "access to /usr/lib/cgi-bin/testscript.pl failed for *machine name*,
: reason: Premature end of script headers"
:
: Anyone know what this
Dave Neuer wrote:
> I am trying to get a CGI script written in Perl running, and I keep
> getting a wierd error that I don't understand:
>
> "access to /usr/lib/cgi-bin/testscript.pl failed for *machine name*,
> reason: Premature end of script headers"
>
> Anyone know what this means? Other Perl
I am trying to get a CGI script written in Perl running, and I keep
getting a wierd error that I don't understand:
"access to /usr/lib/cgi-bin/testscript.pl failed for *machine name*,
reason: Premature end of script headers"
Anyone know what this means? Other Perl scripts with similar
constructi
28 matches
Mail list logo
