If you have shell access to the server where the scripts live, you should
be able to see more descriptive error messages by executing the script
directly, ex:
$ /usr/local/cgi-bin/yourFile.cgi
Ross
At 07:56 PM 5/7/2001 -0700, Chip Wiegand wrote:
>Hi,
>I have download some perl/cgi scripts from various web sites and
>am having the darndest time getting them to work. I have my own apache
>web server to work on, so cgi access is no problem. I am running FreeBSD
>on my client machine to download the scripts, do the configuring, then
>copy the files, via nfs shared drives, to the apache web server, another
>FreeBSD machine. I know it works because I have written some basic
>scripts learned from books and they work properly. but with the ones
>I have downloaded as described I always get the dreaded 'Internal Server
>Error' message. The error log shows 'Premature end of script errors'.
>I've made sure to point the shebang line to the proper location of
>perl. I thought that error message was usually in regards to the file
>having been ftp'd binary instead of ascii, but since I am not using
>ftp that shouldn't be a factor.
>Any suggestions as to what I should be changing so I can get some scripts
>to run properly?
>
>--
>Regards,
>
>Chip
