one thing, when dealing with debugging 500's, always try running the script from the cmd line and make sure you get the output you were looking for.. CGI::Carp helps as well, but it's a good habit to test your code from the cmd line.. CGI.pm allows you to do this, and asks for query parameters before running the code.. just enter your query string and hit ctrl-D to run the script. It will usually tell you what went wrong.
You can also check the error log files, but that tends to be more cumbersome.. (if you can work with more than one terminal, use a different terminal to tail -f the error log).
-Syn0

In reply to Re: 500 server error with no explenation by synapse0
in thread 500 server error with no explenation by JBowes

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.