All those errors are safe to ignore. The server didn't log anything about your script's failure! Your server's logging is incomplete.

On getting a request,

  1. Your script dies (Nothing logged!!!)
  2. Your server is configured to return 500.shtml when a 500 error occurs, but you didn't create it (harmless). So the web server logs this error and generates a 404 for 500.shtml.
  3. Your server is configured to return 404.shtml when a 404 error occurs, but you didn't create it (harmless). So the web server logs this and returns the default error message.

Since you can't rely on the server logs, you'll need to use 

use CGI::Carp qw( fatalsToBrowser );

[download]

In reply to Re: Weird error log message by ikegami
in thread Weird error log message by Nik

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.