Refactor #2586
Stacktrace printing should work on Passenger
| Status: | Accepted | Start date: | 09/02/2009 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | plumbing | |||
| Target version: | 2.7.x | |||
| Affected Puppet version: | 0.24.8 | Branch: | ||
| Keywords: | ||||
| Votes: | 2 |
Description
Most likely, this means building a stack printing service that sends everything to the logs, rather than just printing on stdout as is done now.
This also means going through all of the code and fixing the existing calls to print traces.
It might make sense to, at the same time, refactor our error handling a bit – we currently don’t create specific error classes for the various places we raise errors, and if we did, we could probably have the error creation automatically produce stack traces as appopriate. This would itself be a good bit of work so should probably be considered separately, but it’s at least worth considering.
History
Updated by Lawrence Ludwig over 2 years ago
ideally nothing should go to std out or std err and redirect all output to log file. anything that goes to —logdest console should be std out only and not std err.
Updated by James Turnbull over 2 years ago
- Target version changed from 2.6.0 to 2.7.x