On Tue, Apr 6, 2010 at 5:12 PM, Lana Lewis <lana@...> wrote:
> Sorry, I was buried in a job. Okay, no the server isn't a Mac server, it is
> through Network Solutions and is Linux, I think. I work on a Mac and just
> don't know where error logs are located.
Big hosting companies like Network Solutions generally have some
sort of solution in place for keeping error logs, which may not be
obvious to -- or even reachable by -- customers. If they have a user
guide or FAQ, I would search it for information on error logs and/or
CGI trouble-shooting. If not, you could contact their tech support to
see if you can get access to the error logs.
The Apache error log is likely capturing an error message from the
Perl script interpreter, which would tell us exactly what the problem
> I uploaded through Fetch ...
I presume with FTP.
It's been ages since I used a Mac, so I can't tell you where in the
Fetch GUI to look for this option, but: Make sure you uploaded the
script in "ASCII mode", and not "binary" or "automatic" or anything
like that. This refers to an option in the FTP protocol itself,
dealing with how text files are processed. If you get it wrong, that
can cause the script to be mangled, resulting in this kind of error.
> ... changed the Permission to 755
I'm pretty sure this is not a permissions issue. That will usually
result in an HTTP 403 error, "Forbidden", or similar. Or maybe a copy
of the script appearing in the web browser. I think the server is
trying to run the script, and then Perl and/or the script aborts with
a fatal error.