Do the error logs show anything?

One possibility is that you are running out of database connections, or else saturating the mysql server to the point of timing out. Add error checking to your DBI calls to see if that is the case. You probably would prefer missing images to page death, so the RaiseError attribute is contraindicated. Just add the same sort of error checking you use for the connection to the statement handle's execute method.

Update: "Premature end..." means the script exited before printing the headers. That means it hit die somewhere, a fatal runtime error, or else didn't compile correctly. Have you tried running from the command line? If it compiles correctly, the problem is likely to be dbi related. Try to get some useful messages into the log with diagnostics, Carp, etc.

After Compline,
Zaxo

In reply to Re: Multiple Script calls by Zaxo
in thread Multiple Script calls by cidaris

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.