Thu, 24 Aug 2000 19:34:51 +0000

In terms of the Apache error log example I showed. That was simply an example of what the error log is printing. In the real log there’s a complete path to the script.

Well I appreciate the suggestions I’ve been through all the basics a hundred times. This problem is beyond the actual script and has something to do with the installation or configuration of Perl, which is why it’s in this category not CGI & Perl Help Forums.

I’ve looked around Perl’s site and haven’t found any situations like this. What configuration error would cause ALL scripts to run fine from the prompt but to error from HTTP?

Thanks,

Ken Elliott — Wed, 23 Aug 2000 18:22:54 +0000

If you notice the error apache is printing out.

/path/toscript/script.pl

That is why it is spittin out errors. Look for that line in your script and change it to the real path to your script.

And chmod the folder it's in too.

VulKen
To be the best, you must keep getting better

Wed, 23 Aug 2000 18:14:11 +0000

The point I was trying to convey in my first post was that it’s not a problem with the scripts. I’m by no means a Perl export but I’m positive it’s not the scripts.

Anyone know of any configurations or installation errors that may cause a problem like this?

Ken Elliott — Wed, 23 Aug 2000 17:08:08 +0000

Well the web ones need to have

print "Content-type:text/html\n\n";

if they do, check your permissions. Also, put a -w after yer shabang...

#!/usr/bin/perl -w

Might give you some better reasons in yer log file.

Then check the permissions, like Justin said.

Some people disagree with me, but I have had a few scripts give me that error until I put in the html headers...

Bleh

Make sure they are there, and correct.

Other then that, I don't know what else to say, besides checking the syntax by running the scripts in command line and using the perlchecker (-c)

perl script.pl -c

This will tell if the syntax has some errors.

Hope that helps.
VulKen
Perl makes me wanna hurl

Justin S — Wed, 23 Aug 2000 16:47:39 +0000

Well you've probably checked this, but is the permissions of the file you're trying to open setup correctly?