Bug #74
closed
tftp and puppet ca errors are not shown in the log file
Added by Ohad Levy over 14 years ago.
Updated over 14 years ago.
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.
- Status changed from New to Ready For Testing
- % Done changed from 0 to 100
- Status changed from Ready For Testing to Assigned
this fix wont work as logger is not defined
- % Done changed from 100 to 0
- Assignee changed from Ohad Levy to Paul Kelly
- Status changed from Assigned to Closed
The fix can be found on github.com/pkelly on bug/74
- 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?)
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.
- Status changed from Feedback to Ready For Testing
- % Done changed from 0 to 100
- Status changed from Ready For Testing to Closed
Also available in: Atom
PDF
Updated by 
Updated by