In the future, Alex, you might want to think about putting a 
use CGI::Carp qw(fatalsToBrowser);

[download]
in your code. This will cause all error messages to be prefixed with the text necessary for them to display on Web browsers. Even if you don't use any of CGI's functions, this is solely for ease of debugging.

If you have access to the error logs of web server, look at them; they will contain the error that Perl spewed out:

(Mon Feb 26 17:52:05 2001) (error) (client 10.0.1.2) (Mon Feb 26 17:52:05 2001) bad.cgi: Global symbol "$x" requires explicit package name at bad.cgi line 6.
(Mon Feb 26 17:52:05 2001) (error) (client 10.0.1.2) (Mon Feb 26 17:52:05 2001) bad.cgi: Execution of bad.cgi aborted due to compilation errors. </small

In reply to Re: Perl/Apache Error by mr.nick
in thread Perl/Apache Error by fastkeys

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.