Bug #74
closed
tftp and puppet ca errors are not shown in the log file
Description
when an error occurred to run puppetca or to generate the tftp files, the error does not show up in the log files when running in production mode.
Updated by Ohad Levy over 14 years ago
- Status changed from New to Ready For Testing
- % Done changed from 0 to 100
Applied in changeset f860d3d0f39595dbaf25ab8243fc6c785b02162c.
Updated by Ohad Levy over 14 years ago
- Status changed from Ready For Testing to Assigned
this fix wont work as logger is not defined
Updated by Ohad Levy over 14 years ago
- Assignee changed from Ohad Levy to Paul Kelly
Updated by Paul Kelly over 14 years ago
- Status changed from Assigned to Closed
The fix can be found on github.com/pkelly on bug/74
Updated by Ohad Levy over 14 years ago
- Status changed from Closed to Feedback
your fix always creates a new logger, is this on purpose? (e.g. will it work correctly if the logger already exists?)
Updated by Paul Kelly over 14 years ago
I always create a new logger when the application is running as a cgi web service. In this mode there is no persistence so each GET triggers a new instantiation of the whole GW library. The last call's logger is gone so we need a new one. Well, I think that it works that way.
I am also pretty sure that multiple loggers for one file are OK but don't quote me on it.
Updated by Paul Kelly over 14 years ago
- Status changed from Feedback to Ready For Testing
- % Done changed from 0 to 100
Applied in changeset be1a3faea9b2889b44c27e997f038e92abb048a7.
Updated by Ohad Levy over 14 years ago
- Status changed from Ready For Testing to Closed