Project

General

Profile

Actions

Bug #74

closed

tftp and puppet ca errors are not shown in the log file

Added by Ohad Levy about 15 years ago. Updated about 15 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Proxy gateway
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

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.

Actions #1

Updated by Ohad Levy about 15 years ago

  • Status changed from New to Ready For Testing
  • % Done changed from 0 to 100
Actions #2

Updated by Ohad Levy about 15 years ago

  • Status changed from Ready For Testing to Assigned

this fix wont work as logger is not defined

Actions #3

Updated by Ohad Levy about 15 years ago

  • % Done changed from 100 to 0
Actions #4

Updated by Ohad Levy about 15 years ago

  • Assignee changed from Ohad Levy to Paul Kelly
Actions #5

Updated by Paul Kelly about 15 years ago

  • Status changed from Assigned to Closed

The fix can be found on github.com/pkelly on bug/74

Actions #6

Updated by Ohad Levy about 15 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?)

Actions #7

Updated by Paul Kelly about 15 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.

Actions #8

Updated by Paul Kelly about 15 years ago

  • Status changed from Feedback to Ready For Testing
  • % Done changed from 0 to 100
Actions #9

Updated by Ohad Levy about 15 years ago

  • Status changed from Ready For Testing to Closed
Actions

Also available in: Atom PDF