Generating more readable errors with mod

nysus has asked for the wisdom of the Perl Monks concerning the following question:

By default, error messages generated by mod_perl get dumped into the apache log file. Unfortunately, the log files show the literal \n character for new lines instead of an actual line break. This makes reading lengthy error messages difficult, resulting in lost time and aggravation.

How and where can I output the error messages so new lines will appear properly?

$PM = "Perl Monk's";
$MCF = "Most Clueless ~~Friar~~ ~~Abbot~~ ~~Bishop~~ ~~Pontiff~~ ~~Deacon~~ ~~Curate~~ Priest";
$nysus = $PM . ' ' . $MCF;
Click here if you love Perl Monks

Comment on Generating more readable errors with mod_perl Download Code

Replies are listed 'Best First'.
Re: Generating more readable errors with mod_perl by Discipulus (Canon) on Nov 25, 2017 at 13:13 UTC
Hello nysus, I'm not the best mod_perl nor Apache expert here around but I suspect this is not a mod_perl issue but an Apache one: > Starting from 2.0.49, the Apache logging API escapes everything that goes to error_log.. `CFLAGS="-DAP_UNSAFE_ERROR_LOG_UNESCAPED" ./configure` seems to be the related configuration, but must be enabled at build time.. ;=( It's supposed to be a security issue: you must investigate it further. See here L* There are no rules, there are no thumbs.. Reinvent the wheel, then learn The Wheel; may be one day you reinvent one of THE WHEELS.	[reply] [d/l]
Re^2: Generating more readable errors with mod_perl by nysus (Parson) on Nov 26, 2017 at 05:04 UTC
I was wondering if there was a way to redirect errors to something other than the apache log file. That way I wouldn't be limited to the apache log file constraints. $PM = "Perl Monk's"; $MCF = "Most Clueless ~~Friar~~ ~~Abbot~~ ~~Bishop~~ ~~Pontiff~~ ~~Deacon~~ ~~Curate~~ Priest"; $nysus = $PM . ' ' . $MCF; Click here if you love Perl Monks	[reply]
Re^3: Generating more readable errors with mod_perl (Log4perl) by Discipulus (Canon) on Nov 26, 2017 at 09:26 UTC
I think there is: see Log4perl faqs L* There are no rules, there are no thumbs.. Reinvent the wheel, then learn The Wheel; may be one day you reinvent one of THE WHEELS.	[reply] [d/l]
Re: Generating more readable errors with mod_perl by ww (Archbishop) on Nov 25, 2017 at 13:45 UTC
I don't use mod_perl (and don't know much about it, but which one are you using?) but suspect you can trap the errors using `eval`; that's a supposition supported by this: https://perl.apache.org/docs/2.0/user/porting/compat.html "`In mod_perl 2.0, <Perl> sections errors are now always fatal. Any error in them will cause an immediate server startup abort, dumping the error to STDERR. To avoid this, eval {} can be used to trap errors and ignore them. In mod_perl 1.0, strict was somewhat of a misnomer." (direct from big-G)` FWIW, trapping with an `eval` does NOT appear to be exclusively mod_perl 2; SO has this; unsurprisingly, so does PM. Spirit of the Monastery	[reply] [d/l] [select]


Pathologically Eclectic Rubbish Lister
	PerlMonks

Generating more readable errors with mod_perl