Because of 1 and 2 we can assume the script itself is ok and the problem is somewhere in the surroundings as somebody already stated
I'm sorry, but you cannot assume that. You could if the error was 502 Bad Gateway, but a 500 Internal Server Error means your program is broken.

To figure out where, add this code to the top of your script 

BEGIN {
    $|=1;
    print "Content-type: text/html\n\n";
    use CGI::Carp('fatalsToBrowser');
}

[download]
Or add this 
  BEGIN {
      use CGI::Carp qw(carpout); 
      open(ERROR_LOG, ">>my_error_log") 
                      or die("my_error_log: $!\n");
      carpout(\*ERROR_LOG); 
  }

[download]

In reply to Re^3: Getting random "Internal Server Errors" by Anonymous Monk
in thread Getting random "Internal Server Errors" by polki

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.