That happens in
Everything when it can't get a database connection. As you say, that only happens under high loads, or when
someone falls asleep on the database power switch. From that error message, I could probably find the particular modules
vroom's modified to set up Perl Monks, but that depends on whether or not I have an account on willowisp or not. :)
I don't use fatalsToBrowser in production code for precisely that reason. It's easy enough to add in paranoid error checking and give the user something sane while logging enough detail to make troubleshooting easier. But that's just the way Everything is configured straight out of the tarball.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.