This type of thing usually happens if the script dies unexpectedly before sending the headers. I'm not very familiar with Bugzilla, so I don't know what would necessarily be causing that. Because you mentioned it only happens occasionally, it will likely be a difficult problem to track down. Does Mozilla do any logging of its own? If so, you might want to turn it on and set it to the highest available level. If not, you may want to go through the code and print status messages to STDERR. Those will go to your error log.

And, of course, you might have better luck asking the Bugzilla people themselves. They might have encountered this problem before. Do they have a mailing list or discussion board (or Bugzilla Bugzilla :) )?

In reply to Re: Perl 500 Internal Server Error by mfriedman
in thread Perl 500 Internal Server Error by tohann

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.