For debugging CGI,
use CGI::Carp qw/fatalsToBrowser/;
can be quite helpful.

Instead of getting a 500 error, you should get a screen with error messages. Doesn't work in all situations, especially when you're getting the error because the web server isn't executing the script at all.

Some things that might cause that...
- shebang line (does /usr/local/bin/perl really exist?)
- execute permissions on the file (chmod)
- apache ExecCGI directive for the file's location
- apache's access and suexec log (file owned by correct user/group?)

Good Luck

In reply to Re: CGI on the console by Perimus
in thread CGI on the console by raflach

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.