also, the two most common trouble spots when firing up a CGI are
the permissions are wrong (not executable). try:
chmod 755 File_Name.cgi
if you're not sure about it. and make sure that the script is putting
out a HEAD to the browser.
"print header();" in CGI.pm
after those are clear and you've added
use CGI::Carp qw(fatalsToBrowser);
as suggested below, you'll probably have few problems.
On Sunday, April 14, 2002, at 12:00 , Puneet Kishor wrote:
> Hi John,
>
> Now here is one even I can answer...
>
>
> On Sunday, April 14, 2002, at 01:31 PM, John Buono wrote:
>
>> I am trying to run perl scripts through CGI. I am running the straight
>> OSX
>> not the server.
>>
>> Every time I try and run a script through the browser I am given an
>> "Internal Server Error".
>>
>> What am I doing wrong, or what do I need to do.
>>
>>
>
> we don't know what you are doing wrong... to find out, you have to look at
> the error_log. That is stored under /private/var/log/httpd/error_log. Open
> the file with any text editor and scroll to the end. You will be able see
> the messages and explanations. If you are running perl with the -w switch,
> you will see detailed warnings and explanations. Email the list those
> errors and we would be able to help you further.
>
> Here are some additional ways you can look at the log more conveniently..
> .
>
> from the terminal, type
>
> tail /private/var/log/httpd/error_log to see the last 10 lines. Sometimes
> last 10 lines are not enough so you can pass a number to the tail command.
>
> The best way, imo, however, is to use the most excellent desktop_console
> utility (search on Versiontracker). It directs your choice of log file to
> the desktop directly and automatically. So you don't have to go
> squirreling for the error_log.
>
> Also, learn to use CGI::Carp. You will find it helpful.
>
> Hth,
>
> pk/
>
